Hi David,

   As for stopping weewx, kill 535 will work, but systemd will likely 
restart it very soon.  I ran into an similar issue
the other day with systemd.  In this case it was for NUT (ups monitoring 
stuff).  The systemctl stop <service unit>
didn't stop the daemon (same message you got).  I ended up disabling the 
service unit and killed the processes by hand.
For weewx, I have a perl script that runs from cron that starts weewx if 
it's down.  Works great, except that I have to
remember to stop weewx by hand in care of a reboot or shutdown.  Some 
people like systemd.  I'm not one of them.

Chris


On Monday, December 18, 2023 at 1:10:12 AM UTC-7 David Hindley wrote:

> Thanks for your reply Vince.  Completely understand re network. I am using 
> Ethernet rather than WiFi for both my Rpi which hosts weewx and my davis 
> weather station. 
>
> Does anyone have any input on my question about stopping weewx please? 
> Repeated here: 
>
> In the meantime, I am having trouble stopping weewx - not sure if this is 
> related to my ongoing pipe errors or not.  When I type 
>
> ps -aux|grep weewx
>
> I get
>
> root       535  5.6  6.1 117524 58128 ?        Sl   10:16   2:42 python2 
> /usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid 
> /etc/weewx/weewx.conf
> pi        2130  0.0  0.0   4368   564 pts/0    S+   11:04   0:00 grep 
> --color=auto weewx
>
> And, then typing 
>
> sudo /etc/init.d/weewx stop
>
> produces
>
>  Stopping weewx (via systemctl): weewx.service.
>
> but then repeating the grep command, still shows the 535 process still 
> running?
>
> How do I stop weewx - do I have to use kill 535 perhaps?
>
> Thanks
>
> David. 
> On Sat, 16 Dec 2023 at 19:39, vince <[email protected]> wrote:
>
>> Sorry - we can't fix your network.  Lots of legacy embedded type 2.4GHz 
>> wifi things have issues staying on the network and stable.   I'd suggest 
>> you try to see if your wifi is being interfered with from a neighbor 
>> perhaps.  Maybe you can switch which channel your wifi is on.
>>
>> FWIW, we have too many neighbors here with misconfigured wifi to even 
>> count, depending on who moves in/out and who visits them occasionally.  
>> What I eventually needed to do was (a) move everything in the house that 
>> could do it over to 5GHz wifi, and (b) buy a Unifi AcLite AP and basically 
>> try to out-radiate the neighbors.  Problem went away at that point.
>>
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/q67cvEsXtjQ/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected].
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b4ebe949-5ee5-4221-b91c-ba84e21d64f4n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/b4ebe949-5ee5-4221-b91c-ba84e21d64f4n%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/e9f3e79b-d362-4c4d-8d37-f3e2832d1f55n%40googlegroups.com.

Reply via email to