I have had this problem for a couple months now but finally caught the cause of it, i have installed pulseway on my server using the guide from @PTRFRLL but after about 1 or 2 hours after the server boots it always fails with this error:

 

traps: pulsewayd[9174] general protection fault ip:abb9d4 sp:1501673f8ca8 error:0 in pulsewayd[407000+713000]

Looking on the forum it doesnt seem that anyone has had this issue with pulseway, but they have had it with other programs, apart from bad ram could it be the usb drive as the config file is located there?

 

I did have a user script that just started the service every hour but I would rather try to fix the problem than put tape on it

mediaserver-diagnostics-20240405-1936.zip

I've been having the same problem for the last ~6 months or so? I think there are two problems:

 

- Pulseway keeps crashing

- Pulseway installs a service that starts itself if it crashes, now it leaves an error saying is not able to create this service. Probably the first problem has always been there, but now we see it because of this.

 

May 14 04:40:04 Tower pulseway: Starting Pulseway Daemon version 9.5 (2024013001)
May 14 04:40:04 Tower pulseway: Service watcher check failed with code 127
May 14 04:40:04 Tower pulseway: Failed to enable watcher setvice: 127
May 14 04:40:04 Tower pulseway: Failed to start watcher setvice: 127
May 14 04:40:04 Tower pulseway: Configuration read successfully!
May 14 04:40:06 Tower pulseway: Loaded report data stored locally from the previous session

 

maybe a permission issue? did you manage to fix it?

Updating to pulseway 9.6 and to unraid 6.12.11 seems to have sorted it for me.
Done a couple of restarts and its been active in pulseway for over 48hrs. Ususally couldnt get past 30 seconds.

Unfortunately I never manage to fix / figure out what was happening so I Just stopped using pulseway.

 

Updating to unraid 6.12.11 hasn't seemed to fix the issue for me either so I dont know what it is, also getting the same error as well

 

Doesn't seem like it will work so will just have to go without it.

To make matters worse, I discovered that my server wasn't shuting down anymore. If I turn off the server between 1 hour our so after restart, it turns off good. Buit if I wait a day or so it wont turn off. I mention it because the last enter in the log is always a pulseway error every time the server is not able to turn off correctly:

 

Jul 18 10:29:45 Tower kernel: bond0 (unregistering): Released all slaves
Jul 18 10:29:45 Tower rc.inet1: ip link set lo down
Jul 18 10:29:45 Tower elogind-daemon[1687]: Received signal 15 [TERM]
Jul 18 10:29:45 Tower pulseway: Error sending notification: SOAP 1.1 fault SOAP-ENV:Server[no subcode]#012"No Recovery"#012Detail: get host by name failed in tcp_connect()

 

I can't assure this is the cause, but I've uninstall pulseway alltogether, so I will test the next days...

FYI, in the end, Pulseway had nothing to do with the server not shutting down.

 

I've reinstalled it and updated to 6.12.11 and since then it crashes a lot less. But it still crashes once in a while.