First thought is to open two terminals. In the first one run *sudo tail -f /var/log/syslog* In the second run your start commands. Additionally, make sure you run* sudo /etc/init.d/weewx stop* first, or use* restart / reload *instead
*.* run* sudo /etc/init.d/weewx status *or* sudo service weewx status* immediately after and you will be given a short log extract, a status report of that daemon You can add -x to the top of */etc/init.d/weewx* - ie #!/bin/sh -x to get some feedback - whether it's helpful or not is probably debatable. Make sure you* run systemctl daemon-reload *anytime you edit an init.d config file. Second thought - have you changed from a deb to a setup.py install recently? ie:- is it the correct init.d script for your installation? Cheers Glenn rorpi - read only raspberry pi + weewx: now with scripts <https://github.com/glennmckechnie/rorpi-raspberrypi> On 3 November 2016 at 09:27, J.L. Blom <[email protected]> wrote: > I have since a few weeks an annoying problem. I cannot start weewx anymore > with the startup script, only by starting manual. > So sudo service weewx start doesn't work but sudo /home/weewx/bin/weewxd > /home/weewx/weewx.conf works. > sudo service weewx start doesn't give an error but does not start weewx > sudo /etc/init.d/weewx start gives: > "[ ok ] Starting weewx (via systemctl): weewx.service" doesn't start > weewx either. > I have no clue how to test where something goes wrong except by putting > echo lines in the startup script but maybe matt or thomas know what is > causing this problem and know how to solve it. > I'm running weewx v 3.5.0 (still not upgraded to 3.6.0) on a raspberrypi 2 > (as my odriod-C2 crashed mysteriously). > Joep > > -- 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]. For more options, visit https://groups.google.com/d/optout.
