Look at the log file. We are always happy to take questions, but the first thing someone will ask is, "What did you find in the log file?"
--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9e86020c-1a88-4b0a-b47f-6133c5432b88n%40googlegroups.com.
--
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/96076e7b-357f-48a3-acb9-9a9e88093af6n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/abf06977-25b8-40cc-b70d-7522eb9db682n%40googlegroups.com.
It turns out that there were some other privilege problems, resulting from the 5.02 update, but I managed to get journalctl to show me the detailed error logs, which it apparently keeps, and /var/log/messages apparently doesn't. The previous crt exceptions were, indeed, in journalctl's logs and they allowed me to identify and fix the rest. I think that everything is now really sorted, but a nominally minor utility update, liable to be included in a routine apt full-upgrade, should not create this big a mess!
That was one of the many permissions-related problems caused by the update! Changing the registered user of a complex program that reads and writes many files in many places, without making sure that the user knows the consequences
... the new registered user didn't have access to the serial port.
The crt problem was as you said and was the second one to surface after the first had been fixed. Subsequent to fixing that, I had to correct the access rights to the folders corresponding to a number of 'sites' that my copy of weewx creates.
There were essentially no issues with the 4.x->5.x update. What I wasn't prepared for was an update from 5.01 to 5.02 clobbering everything that was previously working in 5.01. I don't think that it is reasonable to expect the user to carefully (re-)read all the documentation before doing/allowing a 'second decimal place' update.
What I wasn't prepared for was an update from 5.01 to 5.02 clobbering everything that was previously working in 5.01. I don't think that it is reasonable to expect the user to carefully (re-)read all the documentation before doing/allowing a 'second decimal place' update.
My existing installation includes a number of custom skins and custom services. There would be much more than copying over the db involved in the ''clean install' approach, though I did think of doing that after everything fell apart.