I've been doing something similar for years, and one or a couple of tricks 
is to specify the
pid file location and name.  In my case, I use a single directory, but 
multiple config files,
multiple skin directories, and separate archive directories and database 
names.
I use a perl script to do the restarting (can't stand systemd).

Chris

On Wednesday, March 23, 2022 at 5:17:09 PM UTC-6 [email protected] wrote:

> I'm using 4.7 installed on Ubuntu server - I downloaded the github version 
> of weewx-multi since the Ubuntu package doesn't include it. There's no log 
> info - it just doesn't work correctly when trying to stop or report status, 
> while it *does* work correctly when starting or restarting. Just walked 
> back through the script, thinking maybe there was a typo in PIDFILE or 
> related, but nothing looks amiss. So, I re-grabbed a new copy from github 
> and saved it. Didn't touch anything in it - set all the variables in 
> /etc/default/weewx-multi and tried again - same result. Restart worked, but 
> status says it isn't running. Checked /run/tempest.pid and it correlates to 
> the actual pid of the running tempest instance. Killed all the running 
> weewx instances, deleted the pid files, started them back up with weewx 
> start vp2 and weewx start tempest, both are running, both pids are the same 
> as the pid files created, and yet it still says neither is running when 
> querying status...
>
> This is truly weird, although since it's running and doing all it's 
> weather goodness it's not an emergency or anything. I might let it stew for 
> a few days and look at it again this weekend.
>
>
>
> On Wed, Mar 23, 2022 at 9:44 AM matthew wall <[email protected]> wrote:
>
>> tom,
>>
>> which operating system are you using, and which release?
>>
>> which version of weewx are you using?  more importantly, which 
>> weewx-multi script are you using?
>>
>> if you are not using weewx-multi from the latest weewx release (4.7.0), 
>> could you grab weewx-multi from github and see if that behaves any 
>> differently from the weewx-multi currently on your system?
>>
>> m
>>
>> -- 
>> 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/nZjzDRm6dtY/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/146ab416-728b-4ce3-bdb5-e1b366b52efbn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/146ab416-728b-4ce3-bdb5-e1b366b52efbn%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/61428b99-91ea-428f-8e7b-31be8d38e81an%40googlegroups.com.

Reply via email to