Jump to content

Pulseway Daemon Crash on Linux (RHEL 8.5 and Debian 11)


jdmaloney
 Share

Recommended Posts

Over the past day, Pulseway daemons on my RHEL 8 systems and the one Debian 11 system I have crash on their own accord with the following in the logs:
 

May 12 22:22:13 ZZZhostname systemd[1]: Starting Remotely Monitor and Control IT Systems...
May 12 22:22:23 ZZZhostname systemd[1]: Started Remotely Monitor and Control IT Systems.
May 12 22:22:23 ZZZhostname pulseway[1472867]: Got exception signal: 11
May 12 22:22:23 ZZZhostname kernel: pulsewayd[1472867]: segfault at 7fffd0b8f11e ip 0000000000480968 sp 00007ffed0b7f040 error 6 in pulsewayd[406000+589000]
May 12 22:22:23 ZZZhostname kernel: Code: ee 4c 89 ef c6 44 24 40 00 48 89 d3 0f 29 44 24 30 e8 4c d6 30 00 89 de 48 89 ef e8 72 ef ff ff 89 c0 49 8d 7c 24 10 49 89 ed <c6> 84 04 90 01 01 00 00 49 89 3c 24 41 8b 4d 00 49 83 c5 04 8d 91
May 12 22:22:23 ZZZhostname systemd[1]: Started Process Core Dump (PID 1472869/UID 0).
May 12 22:22:24 ZZZhostname systemd-coredump[1472870]: Resource limits disable core dumping for process 1472867 (pulsewayd).
May 12 22:22:24 ZZZhostname systemd-coredump[1472870]: Process 1472867 (pulsewayd) of user 0 dumped core.
May 12 22:22:24 ZZZhostname systemd[1]: pulseway.service: Main process exited, code=dumped, status=11/SEGV
May 12 22:22:24 ZZZhostname systemd[1]: pulseway.service: Failed with result 'core-dump'.

No updates have happened on these systems within the 3-5 days leading up to the crashes (am running latest version of Pulseway) and I cannot get the Pulseway daemons to restart clean.  Sometimes I can get it to run (kind of, see output below) but I don’t get information from my host in the Pulseway app/the host still shows as offline:

root@YYYhostname:~# systemctl status pulseway
● pulseway.service - Remotely Monitor and Control IT Systems
     Loaded: loaded (/etc/systemd/system/pulseway.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-05-12 22:26:56 CDT; 1min 2s ago
    Process: 995459 ExecStartPre=/bin/sleep 10 (code=exited, status=0/SUCCESS)
   Main PID: 995637 (pulsewayd)
      Tasks: 3 (limit: 114195)
     Memory: 3.4M
        CPU: 301ms
     CGroup: /system.slice/pulseway.service
             └─995637 /usr/sbin/pulsewayd --no-daemonize

May 12 22:26:59 YYYhostname pulseway[995637]: Error while registering computer:SOAP 1.1 fault SOAP-ENV:Client[no subcode]
                                            "Error 400: HTTP 400 Bad Request"
                                            Detail: [no detail]
May 12 22:27:05 YYYhostname pulseway[995637]: Error while registering computer:SOAP 1.1 fault SOAP-ENV:Client[no subcode]
                                            "Error 400: HTTP 400 Bad Request"
                                            Detail: [no detail]
May 12 22:27:11 YYYhostname pulseway[995637]: Error while registering computer:SOAP 1.1 fault SOAP-ENV:Client[no subcode]
                                            "Error 400: HTTP 400 Bad Request"
                                            Detail: [no detail]
May 12 22:27:17 YYYhostname pulseway[995637]: Error while registering computer:SOAP 1.1 fault SOAP-ENV:Client[no subcode]
                                            "Error 400: HTTP 400 Bad Request"
                                            Detail: [no detail]
May 12 22:27:23 YYYhostname pulseway[995637]: Error while registering computer:SOAP 1.1 fault SOAP-ENV:Client[no subcode]
                                            "Error 400: HTTP 400 Bad Request"
                                            Detail: [no detail]
May 12 22:27:30 YYYhostname pulseway[995637]: Error while registering computer:SOAP 1.1 fault SOAP-ENV:Client[no subcode]
                                            "Error 400: HTTP 400 Bad Request"
                                            Detail: [no detail]
May 12 22:27:35 YYYhostname pulseway[995637]: Error while registering computer:SOAP 1.1 fault SOAP-ENV:Client[no subcode]
                                            "Error 400: HTTP 400 Bad Request"
                                            Detail: [no detail]
May 12 22:27:42 YYYhostname pulseway[995637]: Error while registering computer:SOAP 1.1 fault SOAP-ENV:Client[no subcode]
                                            "Error 400: HTTP 400 Bad Request"
                                            Detail: [no detail]
May 12 22:27:49 YYYhostname pulseway[995637]: Error while registering computer:SOAP 1.1 fault SOAP-ENV:Client[no subcode]
                                            "Error 400: HTTP 400 Bad Request"
                                            Detail: [no detail]
May 12 22:27:56 YYYhostname pulseway[995637]: Error while registering computer:SOAP 1.1 fault SOAP-ENV:Client[no subcode]
                                            "Error 400: HTTP 400 Bad Request"
                                            Detail: [no detail]

Link to comment
Share on other sites

Posted (edited)

Same here. A few days ago, daemon for a couple Debian servers just randomly crashed around 0300 and will not start again. Tried to remove and re-install but nothing. Pretty sure an update for Pulseway was pushed that caused it. There were no changes/updates on the systems that could have caused it. Installing current version does not fix it, even after purging install.

 

pulseway.service - Remotely Monitor and Control IT Systems
   Loaded: loaded (/etc/systemd/system/pulseway.service; enabled; vendor preset: enabled)
   Active: failed (Result: core-dump) since Sat 2022-05-14 07:35:57 CDT; 4s ago
  Process: 20048 ExecStart=/usr/sbin/pulsewayd --no-daemonize (code=dumped, signal=BUS)
  Process: 19981 ExecStartPre=/bin/sleep 10 (code=exited, status=0/SUCCESS)
 Main PID: 20048 (code=dumped, signal=BUS)

May 14 07:35:47 DD-SVR systemd[1]: Starting Remotely Monitor and Control IT Systems...
May 14 07:35:57 DD-SVR systemd[1]: Started Remotely Monitor and Control IT Systems.
May 14 07:35:57 DD-SVR pulseway[20048]: Starting Pulseway Daemon version 8.11 (2022050601)
May 14 07:35:57 DD-SVR systemd[1]: pulseway.service: Main process exited, code=dumped, status=7/BUS
May 14 07:35:57 DD-SVR systemd[1]: pulseway.service: Failed with result 'core-dump'.

 

 

 

Edited by LinuxDragon
Link to comment
Share on other sites

  • Staff

We have tried to replicate the issues on vanilla RHEL8.5 and Debian11 environments but everything works as expected. 

Can you upload somewhere the core-dump and PM the link? Will be useful to include the config.xml as well. We'll investigate this with priority.

Thanks!

Link to comment
Share on other sites

Posted (edited)

No core dump was produced even though the output shows one was being created. I have a few personally archived Pulseway versions so I installed the older version and can confirm it starts no problem.

● pulseway.service - LSB: Monitor and Control Everything IT from Any Smartphone or Tablet
   Loaded: loaded (/etc/init.d/pulseway; generated)
   Active: active (running) since Sun 2022-05-15 07:34:23 CDT; 3s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 15533 ExecStart=/etc/init.d/pulseway start (code=exited, status=0/SUCCESS)
 Main PID: 13502 (code=dumped, signal=SEGV)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/pulseway.service
           └─15540 /usr/sbin/pulsewayd

May 15 07:34:23 DD-SVR systemd[1]: Starting LSB: Monitor and Control Everything IT from Any Smartphone or 
May 15 07:34:23 DD-SVR pulseway[15539]: Starting Pulseway Daemon version 4.9.3 (2016100601)
May 15 07:34:23 DD-SVR systemd[1]: Started LSB: Monitor and Control Everything IT from Any Smartphone or T
May 15 07:34:23 DD-SVR pulseway[15540]: Configuration read successfully!

 

Edited by LinuxDragon
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...