[bug] caldav-client process does not finish and eats all cpu power

asked 2015-10-13 10:43:32 +0300

btux gravatar image

updated 2015-10-13 10:43:52 +0300

Several times now I noticed my jolla phone to have run hot. In all cases this was caused by caldav-client which was eating up all cpu power for some time. Only help is to kill the process via terminal.

This always happened in cases of a unstable internet connection. I think the client started to sync and lost connection in the sync process.

I wonder why no one else has reported this. I use caldav-client to sync with an owncloud instance going through an openvpn network, so this might be a cornercase. I suspect a problem with lost openvpn connections.

edit retag flag offensive close delete

Comments

1

Thanks for the report. If you can get logs for me, I can investigate further:

1) ensure that /etc/systemd/journald.conf has RateLimitBurst=5000 and RateLimitInterval=10s - and if you had to change them, reboot device

2) restart sync daemon with extra logging enabled

 systemctl --user stop msyncd
 killall msyncd
 MSYNCD_LOGGING_LEVEL=8 devel-su -p msyncd

3) leave that running, and connect a new terminal to collect logs from journal:

 devel-su journalctl -af | grep caldav

4) trigger sync via Settings | Accounts -> Longpress CalDAV -> Sync

The logs from the second (journalctl) terminal should be useful. Please redact any personal information and then send the logs to chris dot adams at jolla dot com and I will investigate.

Thanks, Chris.

chris.adams ( 2015-10-13 12:49:29 +0300 )edit

I also see this for the first time and have been running 1.1.9.28 for quite a while. If you cannot manage to get the log, I will also give it a try!

paulvt ( 2015-10-14 18:37:14 +0300 )edit

Please try. This occurs randomly and I do not know when I will have the time to collect logs when it does.

btux ( 2015-10-14 19:29:09 +0300 )edit

Unfortunately it went away with a reboot.. will have a look next time.

paulvt ( 2015-10-15 22:59:26 +0300 )edit

I'm experiencing the same problem. I've sent some logs to Chris.

birefringence ( 2016-06-23 23:57:19 +0300 )edit