Installed Pulseway again on Ubuntu Server 20.04. Everything works great, however syslog is swamped with continues stream of messages :
Apr 27 11:28:08 minivm pulseway[725]: Failed 3 times to send state for terminal C85310A3-6EAB-4755-8B05-E748663DA84A agent id 20725EFE-D9CD-49CD-B5F6-B8C6EE48062C last error SOAP 1.1 fault SOAP-ENV:Client[no subcode]
"Error 400: HTTP 400 Bad Request"
Detail: [no detail]
After restarting service (that did not seem react correct on restart command, but started when using start command), error is gone:
Apr 27 18:31:30 minivm systemd[1]: Stopping Remotely Monitor and Control IT Systems...
Apr 27 18:31:30 minivm systemd[1]: pulseway.service: Succeeded.
Apr 27 18:31:30 minivm systemd[1]: Stopped Remotely Monitor and Control IT Systems.
Apr 27 18:31:30 minivm systemd[1]: pulseway.service: Found left-over process 2254 (bash) in control group while starting unit. Ignoring.
Apr 27 18:31:30 minivm systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 27 18:31:30 minivm systemd[1]: pulseway.service: Found left-over process 31573 (bash) in control group while starting unit. Ignoring.
Apr 27 18:31:30 minivm systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 27 18:31:30 minivm systemd[1]: pulseway.service: Found left-over process 31791 (docker) in control group while starting unit. Ignoring.
Apr 27 18:31:30 minivm systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 27 18:31:30 minivm systemd[1]: Started Remotely Monitor and Control IT Systems.
Apr 27 18:31:30 minivm pulseway: Starting Pulseway Daemon version 6.5 (2019082205)
Apr 27 18:31:30 minivm pulseway: Error acquiring unique lock. Another process may use the file. Code: 11, Resource temporarily unavailable
Apr 27 18:31:30 minivm systemd[1]: pulseway.service: Main process exited, code=exited, status=1/FAILURE
Apr 27 18:31:30 minivm systemd[1]: pulseway.service: Failed with result 'exit-code'.
Apr 27 18:31:55 minivm systemd[1]: Starting resolvconf-pull-resolved.service...
Apr 27 18:31:55 minivm systemd[1]: resolvconf-pull-resolved.service: Succeeded.
Apr 27 18:31:55 minivm systemd[1]: Finished resolvconf-pull-resolved.service.
Apr 27 18:33:16 minivm systemd[1]: Started Remotely Monitor and Control IT Systems.
Apr 27 18:33:16 minivm pulseway: Starting Pulseway Daemon version 6.5 (2019082205)
Apr 27 18:33:16 minivm pulseway: Configuration read successfully!
I suspect error was caused by attempt to remotely execute commands, in remove terminal window.
Error messages in the syslog
in Linux
Posted · Edited by Leon
Installed Pulseway again on Ubuntu Server 20.04. Everything works great, however syslog is swamped with continues stream of messages :
Apr 27 11:28:08 minivm pulseway[725]: Failed 3 times to send state for terminal C85310A3-6EAB-4755-8B05-E748663DA84A agent id 20725EFE-D9CD-49CD-B5F6-B8C6EE48062C last error SOAP 1.1 fault SOAP-ENV:Client[no subcode] "Error 400: HTTP 400 Bad Request" Detail: [no detail]After restarting service (that did not seem react correct on restart command, but started when using start command), error is gone:
Apr 27 18:31:30 minivm systemd[1]: Stopping Remotely Monitor and Control IT Systems... Apr 27 18:31:30 minivm systemd[1]: pulseway.service: Succeeded. Apr 27 18:31:30 minivm systemd[1]: Stopped Remotely Monitor and Control IT Systems. Apr 27 18:31:30 minivm systemd[1]: pulseway.service: Found left-over process 2254 (bash) in control group while starting unit. Ignoring. Apr 27 18:31:30 minivm systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Apr 27 18:31:30 minivm systemd[1]: pulseway.service: Found left-over process 31573 (bash) in control group while starting unit. Ignoring. Apr 27 18:31:30 minivm systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Apr 27 18:31:30 minivm systemd[1]: pulseway.service: Found left-over process 31791 (docker) in control group while starting unit. Ignoring. Apr 27 18:31:30 minivm systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Apr 27 18:31:30 minivm systemd[1]: Started Remotely Monitor and Control IT Systems. Apr 27 18:31:30 minivm pulseway: Starting Pulseway Daemon version 6.5 (2019082205) Apr 27 18:31:30 minivm pulseway: Error acquiring unique lock. Another process may use the file. Code: 11, Resource temporarily unavailable Apr 27 18:31:30 minivm systemd[1]: pulseway.service: Main process exited, code=exited, status=1/FAILURE Apr 27 18:31:30 minivm systemd[1]: pulseway.service: Failed with result 'exit-code'. Apr 27 18:31:55 minivm systemd[1]: Starting resolvconf-pull-resolved.service... Apr 27 18:31:55 minivm systemd[1]: resolvconf-pull-resolved.service: Succeeded. Apr 27 18:31:55 minivm systemd[1]: Finished resolvconf-pull-resolved.service. Apr 27 18:33:16 minivm systemd[1]: Started Remotely Monitor and Control IT Systems. Apr 27 18:33:16 minivm pulseway: Starting Pulseway Daemon version 6.5 (2019082205) Apr 27 18:33:16 minivm pulseway: Configuration read successfully!I suspect error was caused by attempt to remotely execute commands, in remove terminal window.
Is this a known issue?
Why would agent re-tries infinitely it seems?
thanks