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

Useless error-mesage "[ERROR] '(UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna'" #1132

Closed
htgoebel opened this issue Jan 3, 2021 · 5 comments

Comments

@htgoebel
Copy link

htgoebel commented Jan 3, 2021

When running radicale --verify-storage I get quite some error messages like this, which - sorry to say - are no use:

[2021-01-03 21:29:41 +0100] [3411] [ERROR] '(UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna'

or

[2021-01-03 21:29:44 +0100] [3411] [ERROR] 'Amsterdam, Belgrade, Berlin, Brussels, Budapest, Madrid, Paris, Prague, Stockholm'

Expected result:
In the error message I'd like to learn

  • what is the error - what is wrong
  • in which file
  • if the file contains several entries: which entry is the bogus one
@pavinjosdev
Copy link

Which Radicale version are you using? The problem might be with the config file /etc/radicale/config, or with older versions, the logging config file as well. Try setting the log level to debug for more info.

@htgoebel
Copy link
Author

htgoebel commented Apr 6, 2021

Radicale-3.0.6

Changing the log-level is not a solution, since the error-message should be meaningful.

I can't see how the meaningless text "'Amsterdam, Belgrade, Berlin, Brussels, Budapest, Madrid, Paris, Prague, Stockholm'" should depend on the configuration.

@pavinjosdev
Copy link

I suggested setting log level to debug to see what could've potentially led to such an error message, confusing thought it may be. Once we have a reproducible test case, maybe this can be classified as a bug and receive appropriate attention.

@htgoebel
Copy link
Author

I'm afraid, I can't reproduce this anymore. Closing.

@htgoebel
Copy link
Author

htgoebel commented Nov 29, 2021

By chance I had the same error again, was able to reproduce it and tracked it down. It is cause bey vobject, see skarim/vobject/issues/174

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants