Hi, Damjan, Just to rule out whether "debug" appears in the log file more than once you could do this:
$ grep 'debug' /etc/weewx/weewx.conf If there is a debug = 1 followed later by debug = 0 (and it is not commented out with a preceeding #), then the later one will likely take precedence. And to see if the daemon is dying somehow unexpectedly, please paste the output from this command: $ ps -ef | grep weewx | grep -v grep One more thing. My logs go to syslog. Just to rule it out, you could try grep'ing there: $ grep weewx /var/log/syslog And to make a copy to share, it would be something like: $ grep weewx /var/log/syslog > /var/tmp/weewx.log (And you could upload /var/tmp/weewx.log, but only if it actually has recent log entries). Regards, Leon -- Leon Shaner :: Dearborn, Michigan (iPad Pro) > On Apr 11, 2019, at 12:37 PM, Damjan Hajsek <hajsek.dam...@gmail.com> wrote: > > Hi > <2019-04-11 18_34_45-_etc_weewx_weewx.conf - root@194.249.178.190 - Editor - > WinSCP.png> > > Yes I really changed debug to 1 in conf file. I am from GMT +2 > And I tested, date shows real date and time as it should be > Why there is no logs I don't know, that is all what I get for fev hours after > starting it manually. > > Dne četrtek, 11. april 2019 18.27.31 UTC+2 je oseba Leon Shaner napisala: >> >> Hi, Damjan, >> >> I do not see debug output. Did you change debug = 0 to debug = 1 in the >> conf file? >> >> Other than that, there is a thread where folks mentioned issues when the >> date is off by too much... >> I can't tell what time zone your host is set to, but I would guess UTC or >> GMT, no? >> In my case I have the host time zone set to my local time zone and when I >> type "date" it shows the current local time. Mine works, so it could be a >> factor. >> >> Other than that, I posted just yesterday about an issue with Wunderground-RF >> (rapid fire) not working unless I also explicitly forced Wunderground-PWS >> on. The setting to do that is in the Wunderground section and you can try >> adding it right under the rapidfire = True a la: >> >> archive_post = True >> >> I'm on 1.3.9-1 and you're on 1.3.8, so while it is worth a shot, it might >> not be the issue in your case. >> >> Regards, >> Leon >> -- >> Leon Shaner :: Dearborn, Michigan (iPad Pro) >> >>> On Apr 11, 2019, at 11:35 AM, Damjan Hajsek <hajsek...@gmail.com> wrote: >>> >>> Here is log with debug enabled. >>> >>> http://zerobin.povej.net/?18327ca6959d12c6#NusymzsEuAoTuXNt9tVsZL1+VG4jZO28VhSVYjJxwC0= >>> >>> >>> Dne četrtek, 11. april 2019 15.17.35 UTC+2 je oseba gjr80 napisala: >>>> >>>> Ok, so you do have logs. The startup log extract you posted looks fine to >>>> me. What's happens next in the log? Need to see at least the next 5 >>>> minutes of log. >>>> Not that it seems to be required but your attempt at running WeeWX >>>> directly failed because WeeWX could not find weewx.conf, you need to >>>> provide the path to weewx.conf in full eg: >>>> >>>> $ sudo weewxd /etc/weewx/weewx.conf >>>> >>>> Gary >>>> >>> >>> -- >>> 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...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. > > -- > 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+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > <2019-04-11 18_34_45-_etc_weewx_weewx.conf - root@194.249.178.190 - Editor - > WinSCP.png> -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
