Hi, Whilst log extracts showing individual error traces can be important, seeing the wider picture can be equally important in tracking down such an issue. Could I suggest that you identify one of the times when WeeWX has ‘stopped’ and then post the log from say 15-20 minutes beforehand through until you restarted WeeWX. Don’t edit the log (other than taking the extract) and make sure you include a good 10 minutes of log after the error occurred. That way we see what WeeWX was doing at the time of the problem and in the immediate period after.
When Tom said avoid posting large log extracts that was really aimed at preventing direct posting of 7-8 hours of log. Gary On Thursday, 17 December 2020 at 18:13:43 UTC+10 Mauro De Lauretis wrote: > I've found also this: > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: Caught > unrecoverable exception: > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > can't start new thread > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > Traceback (most recent call last): > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > File "/home/weewx/bin/weewxd", line 148, in main > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > engine = weewx.engine.StdEngine(config_dict) > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > File "/home/weewx/bin/weewx/engine.py", line 81, in __init__ > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > self.loadServices(config_dict) > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > File "/home/weewx/bin/weewx/engine.py", line 153, in loadServices > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > obj = weeutil.weeutil.get_object(svc)(self, config_dict) > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > File "/home/weewx/bin/weewx/restx.py", line 1430, in __init__ > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > self.archive_thread.start() > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > File "/usr/lib/python3.7/threading.py", line 847, in start > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > _start_new_thread(self._bootstrap, ()) > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > RuntimeError: can't start new thread > > Dec 17 05:00:32 raspberrypi weewx[22459] CRITICAL __main__: **** > Exiting. > > > Il giorno mercoledì 16 dicembre 2020 alle 22:08:25 UTC+1 Mauro De Lauretis > ha scritto: > >> Tom, maybe I've found the problem of the stopping: >> >> Dec 16 00:13:45 raspberrypi weewx[2295]: Stopping weewx weather system: >> weewx not running.... >> >> Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Succeeded. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: Stopped LSB: weewx weather system. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25134 (sh) in control group while starting unit. Ignoring. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean >> termination of a previous run, or service implementation deficiencies. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25135 (wget) in control group while starting unit. Ignoring. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean >> termination of a previous run, or service implementation deficiencies. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25137 (sh) in control group while starting unit. Ignoring. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean >> termination of a previous run, or service implementation deficiencies. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25138 (wget) in control group while starting unit. Ignoring. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean >> termination of a previous run, or service implementation deficiencies. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25139 (sh) in control group while starting unit. Ignoring. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean >> termination of a previous run, or service implementation deficiencies. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25140 (wget) in control group while starting unit. Ignoring. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean >> termination of a previous run, or service implementation deficiencies. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25160 (sh) in control group while starting unit. Ignoring. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean >> termination of a previous run, or service implementation deficiencies. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25161 (wget) in control group while starting unit. Ignoring. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: This usually indicates unclean >> termination of a previous run, or service implementation deficiencies. >> >> Dec 16 00:13:45 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25163 (sh) in control group while starting unit. Ignoring. >> >> Dec 16 00:13:46 raspberrypi systemd[1]: This usually indicates unclean >> termination of a previous run, or service implementation deficiencies. >> >> Dec 16 00:13:46 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25165 (wget) in control group while starting unit. Ignoring. >> >> Dec 16 00:13:46 raspberrypi systemd[1]: This usually indicates unclean >> termination of a previous run, or service implementation deficiencies. >> >> Dec 16 00:13:46 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25168 (sh) in control group while starting unit. Ignoring. >> >> Dec 16 00:13:46 raspberrypi systemd[1]: This usually indicates unclean >> termination of a previous run, or service implementation deficiencies. >> >> Dec 16 00:13:46 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25170 (wget) in control group while starting unit. Ignoring. >> >> Dec 16 00:13:46 raspberrypi systemd[1]: This usually indicates unclean >> termination of a previous run, or service implementation deficiencies. >> >> Dec 16 00:13:46 raspberrypi systemd[1]: weewx.service: Found left-over >> process 25177 (sh) in control group while starting unit. Ignoring. >> >> Il giorno mercoledì 16 dicembre 2020 alle 17:35:59 UTC+1 Mauro De >> Lauretis ha scritto: >> >>> Thank you! >>> >>> Il giorno mercoledì 16 dicembre 2020 alle 16:24:54 UTC+1 >>> [email protected] ha scritto: >>> >>>> on the computer where you run ssh: >>>> scp root@rpi:/var/log/syslog . >>>> >>>> Please, note the dot at the end. Replace "rpi" by the IP address or >>>> name of your RPi. May be, you need to replace "root" by "pi" or "user" to >>>> get it work. >>>> >>>> After that you will find a file named "syslog" in the current >>>> directory. You can open it with any text editor. >>>> >>>> >>>> Mauro De Lauretis schrieb am Mittwoch, 16. Dezember 2020 um 16:03:17 >>>> UTC+1: >>>> >>>>> Yes, I can ssh into my RPi, but I don't know how to scp the log. >>>>> >>>>> Il giorno mercoledì 16 dicembre 2020 alle 15:28:09 UTC+1 >>>>> [email protected] ha scritto: >>>>> >>>>>> If you can ssh into your RPi, you could scp the log to >>>>>> somewhere convenient. Then upload it to a cloud service such as >>>>>> pastebin.com. >>>>>> >>>>>> Alternatively, you can use a text editor to trim it down to the >>>>>> essentials, then post it here. But, please don't post anything too big >>>>>> here. >>>>>> >>>>>> -tk >>>>>> >>>>>> On Wed, Dec 16, 2020 at 6:04 AM Mauro De Lauretis < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> You're right, Tom. >>>>>>> If not attached the log because I should copy and paste you the >>>>>>> exactly moment when Weewx stops reporting, but how can I do it when I'm >>>>>>> not >>>>>>> logged on my Raspberry when it happens? Are there other possibilities? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Il giorno mercoledì 16 dicembre 2020 alle 14:41:45 UTC+1 >>>>>>> [email protected] ha scritto: >>>>>>> >>>>>>>> Sorry, but it does not look like you attached the log. >>>>>>>> >>>>>>>> On Wed, Dec 16, 2020 at 5:32 AM Mauro De Lauretis < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi Tom, >>>>>>>>> I've never thought that the log is interesting, simply I was not >>>>>>>>> able to see where the error is. :-) >>>>>>>>> >>>>>>>>> Station Hardware is a Davis Vantage Pro2, while the debug is >>>>>>>>> already set to debug = 1. >>>>>>>>> >>>>>>>>> Regards >>>>>>>>> Mauro >>>>>>>>> >>>>>>>>> Il giorno mercoledì 16 dicembre 2020 alle 14:11:56 UTC+1 >>>>>>>>> [email protected] ha scritto: >>>>>>>>> >>>>>>>>>> I know you think the log is uninteresting, but to more >>>>>>>>>> experienced eyes, it may contain some clues. Be sure to set debug=1. >>>>>>>>>> >>>>>>>>>> Also, what kind of hardware? >>>>>>>>>> >>>>>>>>>> On Wed, Dec 16, 2020 at 2:46 AM Mauro De Lauretis < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hello, >>>>>>>>>>> >>>>>>>>>>> I have been experiencing an issue for the last two weeks, and so >>>>>>>>>>> far have not been able to determine the cause. I was hoping someone >>>>>>>>>>> may >>>>>>>>>>> have some ideas. >>>>>>>>>>> >>>>>>>>>>> I am running the Weather34 Skin ( >>>>>>>>>>> https://github.com/steepleian/weewx-Weather34) >>>>>>>>>>> Weewx 4.2.0. >>>>>>>>>>> MySQL Database >>>>>>>>>>> OS Rasbian on Raspberry >>>>>>>>>>> >>>>>>>>>>> At fixed intervals (7-8 hours, more and less) the system stops >>>>>>>>>>> entering data into the database and upload files into my web >>>>>>>>>>> server, but I >>>>>>>>>>> cannot see any suitable information or error from the syslog. If I >>>>>>>>>>> restart >>>>>>>>>>> Weewx, everything turns to work great. Then, after this "famous" >>>>>>>>>>> 7-8 hours, >>>>>>>>>>> Weewx stops again to report and doesn't work before I make a >>>>>>>>>>> manually >>>>>>>>>>> restart. >>>>>>>>>>> >>>>>>>>>>> If anyone has any ideas it would be very much appreciated. >>>>>>>>>>> >>>>>>>>>>> Thanks >>>>>>>>>>> Mauro >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> 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 [email protected]. >>>>>>>>>>> To view this discussion on the web visit >>>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/364687cb-7bc2-43d2-aaca-0b946a933da2n%40googlegroups.com >>>>>>>>>>> >>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/364687cb-7bc2-43d2-aaca-0b946a933da2n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>>>> . >>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>> 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 [email protected]. >>>>>>>>> >>>>>>>> To view this discussion on the web visit >>>>>>>>> https://groups.google.com/d/msgid/weewx-user/b3643aac-d236-463c-ab38-3a282ef5db2fn%40googlegroups.com >>>>>>>>> >>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/b3643aac-d236-463c-ab38-3a282ef5db2fn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>> . >>>>>>>>> >>>>>>>> -- >>>>>>> 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 [email protected]. >>>>>>> >>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/weewx-user/fe500236-0b9c-4db4-a555-57c78ec08e06n%40googlegroups.com >>>>>>> >>>>>>> <https://groups.google.com/d/msgid/weewx-user/fe500236-0b9c-4db4-a555-57c78ec08e06n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> >>>>>> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4c3ac6a4-b5fb-49fb-96da-00b070326e7en%40googlegroups.com.
