Jump to content
View in the app

A better way to browse. Learn more.

Pulseway

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

jdmaloney

Members
  • Joined

  • Last visited

Reputation Activity

  1. Like
    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]

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.