hi Gary

what is strange that i can find no record of weewx attempting to run in the 
syslog yes debug is set to 1

normally when you have a problem  you can see weewx starting then failing 
showing and error message

in my case no reference  of weewx trying to start? most strange i have 
never seen that before

what i have found

if i uninstalled the GW1000 driver/extension weewx started working again
i have reinstalled  GW1000 and ran it as a driver
it works perfectly as a driver but not as an extension

The GW1000 driver is picking up the sensor information from my WS3000 
weather station

if the GW1000 driver can see data from my WS3000 there must be some 
similarities on how the drivers work

could it just be a conflict between WS3000 driver and GW1000 installed as 
an extension.

i have the GW1000  working perfectly configured as a driver  and its 
reading date from the WS3000 weather station

so it works but 

thanks for your help





On Tuesday, May 9, 2023 at 10:08:19 PM UTC+1 gjr80 wrote:

> What you have presented (other than the WeeWX daemon failing to start) is 
> expected behaviour. When you run WeeWX directly by invoking weewxd from 
> the command line you are running WeeWX as a foreground process (as opposed 
> to a background process when WeeWX is run as a daemon). When you close the 
> terminal in which you invoked this foreground process the foreground 
> process is closed (that is why WeeWX is normally run as a daemon). As part 
> of the WeeWX foreground process closing the process shuts down any 
> sub-ordinate threads, one of which is the GatewayCollector thread used by 
> the Ecowitt gateway device service. The corresponding entry in log extract 
> is not an error, rather it is informational telling you the thread was 
> closed in a controlled manner.
>
> What you need to do is to determine why the WeeWX daemon is not 
> starting/running. To do this make sure all WeeWX instances are closed. Edit 
> weewx.conf and set debug = 1. Start the WeeWX daemon and monitor the 
> WeeWX log. Let WeeWX run for at least two archive periods, or until it 
> encounters an error, and then post a log extract showing the entire WeeWX 
> startup through until the error occurs or the two archive periods have 
> passed.
>
> Gary
>
> On Tuesday, 9 May 2023 at 22:37:48 UTC+10 vigilance wx wrote:
>
>> Hi 
>>
>> I am running a fresh install of weewx 3.9.2 on raspberrypi with python 2.7
>>
>> I have installed WS3000 as a driver and working fine
>>
>>  
>>
>> I have then install GW1000 as a service
>>
>>  
>>
>> Its works fine initially pefect no problems
>>
>> I then reboot the pi  weewx fails will not start
>>
>> Weewx will not run as a daemon
>>
>> I open a putty window
>>
>> I can start it directly with  
>>
>> sudo ./bin/weewxd weewx.conf
>>
>>  
>>
>> if  then open a second putty window I can see data from both the GW1000 
>> and WS3000 in the syslog
>>
>> if close the first original  putty window
>>
>>  
>>
>> I get this error in the second putty window syslog 
>>
>>  
>>
>> May  9 13:26:55 raspberrypiwx weewx[1647]: gw1000: Next update in 20 
>> seconds
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]: engine: Main loop exiting. 
>> Shutting engine down.
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]: gw1000: GatewayCollector 
>> thread has been terminated
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]: engine: Caught unrecoverable 
>> exception in engine:
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]:     ****  [Errno 5] 
>> Input/output error
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]:     ****  Traceback (most 
>> recent call last):
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]:     ****    File 
>> "/home/weewx/bin/weewx/engine.py", line 894, in main
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]:     ****      engine.run()
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]:     ****    File 
>> "/home/weewx/bin/weewx/engine.py", line 191, in run
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]:     ****      
>> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]:     ****    File 
>> "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]:     ****      callback(event)
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]:     ****    File 
>> "/home/weewx/bin/weewx/engine.py", line 725, in new_loop_packet
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]:     ****      
>> to_sorted_string(event.packet).encode('utf-8'))
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]:     ****  IOError: [Errno 5] 
>> Input/output error
>>
>> May  9 13:26:56 raspberrypiwx weewx[1647]:     ****  Exiting.
>>
>> May  9 13:26:56 raspberrypiwx systemd[1]: session-c5.scope: Succeeded.
>>
>>  
>>
>> Something is stopping weewx after I install the GW1000 service and the pi 
>> is rebooted
>>
>>  
>>
>> Thanks for any help
>>
>

-- 
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/63519f4c-4cbf-4eb1-a871-eb6a4551f252n%40googlegroups.com.

Reply via email to