Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync failed #2908

Closed
crdxfire opened this issue Apr 15, 2020 · 16 comments · Fixed by #2912
Closed

Sync failed #2908

crdxfire opened this issue Apr 15, 2020 · 16 comments · Fixed by #2912

Comments

@crdxfire
Copy link

Expected behavior

Sync with iCloud acct

Actual behavior

Sync failed

Mail app

Mail app version: (see apps admin page, e.g. 0.5.3)
1.3.0

Mailserver or service: (e.g. Outlook, Yahoo, Gmail, Exchange,...)
iCloud

Server configuration

Operating system: (e.g. Debian 8)
Ubuntu 18.04

Web server: (e.g. Apache, Nginx,...)
Apache

Database: (e.g. MariaDB, SQLite or PostgreSQL)
MadiaDB

PHP version: (e.g. 7.0)
7.2..24

Nextcloud Version: (see admin page, e.g. 13.0.2)
18.0.3

Client configuration

Browser: (e.g. Firefox 48)
Several tested, mainly Brave

Operating system: (e.g. Arch Linux)
macOS 10.15.4

[mail] Error: OCA\Mail\Exception\ServiceException: Sync failed: at <>

  1. /var/www/nextcloud/apps/mail/lib/Service/Sync/SyncService.php line 107
    OCA\Mail\Service\Sync\ImapToDbSynchronizer->sync(OCA\Mail\Account {}, OCA\Mail\Db\Mailbox {id: 267}, 42, [], true)
  2. /var/www/nextcloud/apps/mail/lib/Controller/FoldersController.php line 131
    OCA\Mail\Service\Sync\SyncService->syncMailbox(OCA\Mail\Account {}, "INBOX", 42, [], false, null)
  3. /var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php line 170
    OCA\Mail\Controller\FoldersController->sync(12, "SU5CT1g=", [], true, null)
  4. /var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php line 99
    OC\AppFramework\Http\Dispatcher->executeController(OCA\Mail\Controller\FoldersController {}, "sync")
  5. /var/www/nextcloud/lib/private/AppFramework/App.php line 125
    OC\AppFramework\Http\Dispatcher->dispatch(OCA\Mail\Controller\FoldersController {}, "sync")
  6. /var/www/nextcloud/lib/private/AppFramework/Routing/RouteActionHandler.php line 47
    OC\AppFramework\App::main("OCA\Mail\Cont ... r", "sync", OC\AppFramework\ ... {}, {accountId: "12" ... "})
  7. <>
    OC\AppFramework\Routing\RouteActionHandler->__invoke({accountId: "12" ... "})
  8. /var/www/nextcloud/lib/private/Route/Router.php line 299
    call_user_func(OC\AppFramework\ ... {}, {accountId: "12" ... "})
  9. /var/www/nextcloud/lib/base.php line 1008
    OC\Route\Router->match("/apps/mail/api/ ... c")
  10. /var/www/nextcloud/index.php line 38
    OC::handleRequest()

POST /index.php/apps/mail/api/accounts/12/folders/SU5CT1g%3D/sync
from 46.90.225.233 by mp at 2020-04-15T10:57:45+00:00

@ChristophWurst
Copy link
Member

please check nextcloud.log for the full log message and trace

@crdxfire
Copy link
Author

Yesterday I upgraded the Mail app. I found a thread regarding the body height in the reading pane, what is fine now. :) With the previous (stable / released) version the iCloud account worked. I looked into the nextcloud.log, but unfortunately that doesn't help. There is a 2nd account connected to Microsoft365 and all is well. Tested another IMAP-Account, no problem at all. The nextcloud.log contains no further information other than above. I'm sorry - I would really like to be more specific and spent already a few hours with locating the problem. Do you have any other ideas?

@no-response no-response bot removed the needs info label Apr 15, 2020
@ChristophWurst
Copy link
Member

The Nextcloud mail app offers an extensive logging system to make it easier identifying and tracking down bugs. Please enable debug mode and set the log level to debug in your admin settings. Then, try to reproduce your issue and take another look at data/nextcloud.log and data/horde_imap.log.

@ChristophWurst
Copy link
Member

Mail app version: (see apps admin page, e.g. 0.5.3)
1.3.0

That is the RC, I guess?

@crdxfire
Copy link
Author

Mail app version: (see apps admin page, e.g. 0.5.3)
1.3.0

That is the RC, I guess?

Yes, sir.

@crdxfire
Copy link
Author

How can I revert it to the released version? :/

@ChristophWurst
Copy link
Member

Restore your backup.

@ChristophWurst
Copy link
Member

If you're interested in actually helping getting the problem fixed, please provide the logs with the instructions given. Otherwise there is nothing we can help with until someone else runs into this and provides the details. There are simply too many possible ways this could fail.

@crdxfire
Copy link
Author

crdxfire commented Apr 15, 2020

Thanks for the follow-up, Christoph. I'll try to do so in the evening. Gave it a first shot, but with no helpful results for now. I understand there is no way back without a backup. So it's completely my fault, as I don't have one yet. We are still evaluating Nextcloud and not really in production, although it would be a relatively big effort to start from scratch now. As I said - I messed it up and don't want to blame it on your app. Thank you for your time. Best, Markus

@no-response no-response bot removed the needs info label Apr 15, 2020
@ChristophWurst
Copy link
Member

Once there is more info we can check if this is the same as #2909.

@Bables55

This comment has been minimized.

@ChristophWurst
Copy link
Member

@crdxfire please see #2912

@ChristophWurst
Copy link
Member

And #2910 (comment)

@ChristophWurst
Copy link
Member

@Bables55 please open a new ticket. I can see why that fails for you but we'll have to debug why that old flagged inbox is still there. This should have vanished after the update.

@ChristophWurst
Copy link
Member

@Bables55 see #2913. Someone else ran into the same error ✌️

@ChristophWurst
Copy link
Member

v1.3.1 was just released. Please update ✌️

@ChristophWurst ChristophWurst unpinned this issue May 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants