weewx dead

[Marco Citossi]

I've tried to restart a lot of times but I get this error. 
"Checking for weewx: weewx dead but pid file exists."

What could be the problem?

Thank.

M.

[Graham Eddy]

delete the pid file. then it will start (and create new pid file)

⊣GE⊢

--
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 weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/979e0836-166b-4da1-abca-dd37f5d9e483n%40googlegroups.com.

[Marco Citossi]

I don't find the pid file in the ps list.

I've tried to restart the webserver but same problem.

[vince]

Marco - what os (and version) are you running and which version of weewx ?

In older os using init.d startup files the pid file would be in /var/run if that helps any in looking for it.   Generally trying to stop weewx twice and then start it (not 'restart') used to work.

[Marco Citossi]

Hi vince! 

Centos 7, weewx 3.8.0.a1

I've find pid in /var/run...deleted, stopped weewx 2 times (failed), start again but nothing same problem.

Thanks.

[Marco Citossi]

Anyway also from the other webserver with weewx 5 I get an error.

Could be a problem of firewall again?

 

weewx.service - WeeWX
   Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2024-07-31 22:28:35 CEST; 2s ago
     Docs: https://weewx.com/docs
  Process: 59322 ExecStart=/usr/bin/weewxd /etc/weewx/weewx.conf (code=exited, status=4)
 Main PID: 59322 (code=exited, status=4)

CRITICAL weewx.engine:     ****      Vantage.__init__(self, **config_dict[DRIVER_NA>
CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py">
CRITICAL weewx.engine:     ****      self.port.openPort()
CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py">
weewx.engine:     ****      raise weewx.WeeWxIOError(ex)
weewx.engine:     ****  weewx.WeeWxIOError: [Errno 113] No route to host
CRITICAL __main__: Unable to load driver: [Errno 113] No route to host
weewxd[59322]: CRITICAL __main__:     ****  Exiting...
weewx.service: Main process exited, code=exited, status=4/NOPERMISSION
weewx.service: Failed with result 'exit-code'.

[vince]

If you're running weewx 5.1 yes it is very likely you need the weewx user added to the group(s) needed to access network devices.   See the wiki and FAQ and many (many) other posts here with how to debug and fix the problem.