"An unexpected error occurred" #1065
Labels
bug
Something isn't working
Comments
|
OK, through Console.app I found the log reports, and they seem ok to share (I removed what looked like a token) This was the second time, in a few days the same error occurred, the previous one was at 2024-07-19 19:14:55 |
|
That is very strange. From your traces, it appears that the failing call is to the Are you using Dropbox with a team account? And did you recently join or leave a Dropbox team? The error seems to be occurring in the context of the Dropbox root folder changing. |
|
No, I use my Dropbox account since a long time, never had a paid or team account, and I don’t move around many files.
The only uncommon thing recently has been deleting two root folders that start with a @ sign , I have the feeling that could have something to do with it.
|
|
|
I’m seeing the same error recently, probaly 3–4 times already. I’m not using a Dropbox team account. Please let me know how can I investigate further. |
|
Thanks for the infos! In this case, the Could you increase the log level to DEBUG and wait until you see the error again? The logs for the error should then contain a request ID. If you can share this, I'll forward it to Dropbox support to investigate. |
|
How do I set the debug level to DEBUG?
… Message ID: ***@***.***>
|
See https://maestral.app/cli/log I also experience similar issue. Had to redownload Dropbox after disk change. Simple account, a lot of files, but download-only overnight. After restart (noticed few hours after failure) downloading continued OK. @samschott, this is a most recent log, with request_id 87f43247562649868e4db183fdef5cf0. Please see, if my case fits topic's starter's, as my stacktrace is somewhat different, though giving same P.S. Side topic: I also seen a different symptom - failure ( |
|
I got the maestral.log2024-07-24 19:24:00 sync DEBUG: Waiting for local changes since cursor: 1721834519.5139976
2024-07-24 19:24:31 sync DEBUG: Detected remote changes: False
...skipping...
File "/nix/store/8fd7ch5lrhqggj8yfapi2psfpxpr1z2l-python3.11-dropbox-12.0.0/lib/python3.11/site-packages/dropbox/dropbox_client.py", line 326, in request
res = self.request_json_string_with_retry(host,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/nix/store/8fd7ch5lrhqggj8yfapi2psfpxpr1z2l-python3.11-dropbox-12.0.0/lib/python3.11/site-packages/dropbox/dropbox_client.py", line 476, in request_json_string_with_r>
return self.request_json_string(host,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/nix/store/7n060rjpakwa6zhqmrz8km96fqm96bya-python3.11-maestral-1.9.3/lib/python3.11/site-packages/maestral/client.py", line 165, in request_json_string
return super().request_json_string(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/nix/store/8fd7ch5lrhqggj8yfapi2psfpxpr1z2l-python3.11-dropbox-12.0.0/lib/python3.11/site-packages/dropbox/dropbox_client.py", line 595, in request_json_string
self.raise_dropbox_error_for_resp(r)
File "/nix/store/8fd7ch5lrhqggj8yfapi2psfpxpr1z2l-python3.11-dropbox-12.0.0/lib/python3.11/site-packages/dropbox/dropbox_client.py", line 638, in raise_dropbox_error_for_re>
raise AuthError(request_id, err)
dropbox.exceptions.AuthError: AuthError('c0abb87efd86448584143fb73d19f6e3', AuthError('route_access_denied', None))
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/nix/store/7n060rjpakwa6zhqmrz8km96fqm96bya-python3.11-maestral-1.9.3/lib/python3.11/site-packages/maestral/manager.py", line 767, in _handle_sync_thread_errors
yield
File "/nix/store/7n060rjpakwa6zhqmrz8km96fqm96bya-python3.11-maestral-1.9.3/lib/python3.11/site-packages/maestral/manager.py", line 615, in download_worker
if self.check_and_update_path_root():
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/nix/store/7n060rjpakwa6zhqmrz8km96fqm96bya-python3.11-maestral-1.9.3/lib/python3.11/site-packages/maestral/manager.py", line 391, in check_and_update_path_root
if self._needs_path_root_update():
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/nix/store/7n060rjpakwa6zhqmrz8km96fqm96bya-python3.11-maestral-1.9.3/lib/python3.11/site-packages/maestral/manager.py", line 414, in _needs_path_root_update
account_info = self.sync.client.get_account_info()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/nix/store/7n060rjpakwa6zhqmrz8km96fqm96bya-python3.11-maestral-1.9.3/lib/python3.11/site-packages/maestral/client.py", line 627, in get_account_info
with convert_api_errors():
File "/nix/store/4rf5qybw37b4lh1g0xczlv14sqdbmnpm-python3-3.11.9/lib/python3.11/contextlib.py", line 158, in __exit__
self.gen.throw(typ, value, traceback)
File "/nix/store/7n060rjpakwa6zhqmrz8km96fqm96bya-python3.11-maestral-1.9.3/lib/python3.11/site-packages/maestral/errorhandling.py", line 92, in convert_api_errors
raise dropbox_to_maestral_error(exc, dbx_path, local_path)
maestral.exceptions.MaestralApiError: An unexpected error occurred. Please contact the developer with the traceback information from the logs.
2024-07-29 18:08:30 manager INFO: Shutting down threads...
2024-07-29 18:08:30 sync INFO: Sync aborted
2024-07-29 18:08:30 manager INFO: Paused |
|
Just adding another stack trace that appears to be the same issue: |
|
I have the same issue. |
|
This is also happening to me roughly every 24-48 hours since this issue was opened, so likely a change on Dropbox's end. I use an account that has always been free and personal (not team). At the moment it seems Maestral gets stuck after the error rather than terminating and allowing itself to be restarted, but I'm on 1.7.3 so maybe that behaviour has changed... |
|
An unexpected error occurred. We are seeing this about once per day lately using the GUI macOS app. Maestral: 1.9.4 |
|
The route_access_denied issue has been discussed on the Dropbox Forums, with no resolution yet: |
|
And yesterday it was updated with a message from Dropbox staff that it has been fixed:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Recently this window started popping up.
To Reproduce
No idea! 🤷🏻♂️ Happens from time to time.
Expected behaviour
It shouldn't happen, I guess.
System:
python3 -V=> Python 3.12.4Additional context
Let me know where to get the logs and how to get them to you privately (I have no idea if they contain sensitive info).
The text was updated successfully, but these errors were encountered: