In the absence of logs, nobody is going to be able to help you much. On Wednesday, March 23, 2022 at 7:02:36 AM UTC-7 [email protected] wrote:
> This is what I tried first - rather than using weewx-multi I duplicated > the original weewx script to weewx-tempest, changed everything VP2-related > to Tempest (database, config, etc.) and tried to start it. Nothing at all - > no error, no log, just nothing. If I started the Tempest instance, then the > VP2 one wouldn't start. I'm sure "something" was blocking/locking something > but never could find it, and since weewx-multi was designed to handle this > I went that route. > > On Tuesday, March 22, 2022 at 4:45:38 PM UTC-8 [email protected] > wrote: > >> Tom: >> >> I had trouble with this configuration back 2 years ago when I ran both a >> SDR and a Acurite instance of WeeWX using a reporting instance to report >> the results for both. >> >> What I did was I created a shell script for each instance (eg wx-sdr, >> wx-acurite, wx-rpt) and used cron to execute each at reboot. Here is a >> snippet of my script that I used: >> >> #WX_SDR Instance execution >> HOME=/home/weewx >> CONF_FILE=/home/weewx/conf/wx_sdr.conf >> LOG_FILE=/home/weewx/logs/wx_sdr.log >> echo "using $CONF_FILE" >> >> cd $HOME >> >> ./bin/weewxd $CONF_FILE >> $LOG_FILE >> >> WeeWX will start an instance and I just had it report its results in a >> log. You can modify this to use logrotate as prescribed in the wiki >> >> logging ยท weewx/weewx Wiki (github.com) >> <https://github.com/weewx/weewx/wiki/logging#save-weewx-log-messages-to-a-separate-file> >> >> hope this helps! >> >> Doug Jenkins >> largoweather.com >> >> >> On Tue, Mar 22, 2022 at 6:26 PM Tom Hogland <[email protected]> wrote: >> >>> I haven't been able to find any record of this behavior. Adjusted my >>> working weewx with VP2 to use weewx-multi, added the second config, etc. >>> all per the docs, naming/databases/configs etc. Running "/etc/init.d/weewx >>> start" fires up both instances, both are working correctly (updating >>> webroot files etc.). Problem is, "weewx status" shows neither is running, >>> and "weewx stop" says the same, however "weewx restart" closes and restarts >>> them both without issue. Specifying either instance name does the same - >>> status or stop says not running, restart works fine. Looking at the ps >>> listing - both are there and working fine... pid files in /run are also >>> correct. I don't see any issues in the script itself. >>> >>> I imagine there's something simple to this but I can't find it - anyone >>> know what's causing the failure to see the correct status? Or is there a >>> simple solution that I just failed to dig out of the docs/forum? >>> >>> -Tom >>> >>> >>> -- 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/81db2dbe-409b-47f0-815f-dfe454dc58c9n%40googlegroups.com.
