Mark

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!

Pulseway is not available in AppStore. Native M1 agent is in QA and will be released in 2 weeks. (at the moment the agent is emulated via Rosetta 2 on M1) 
You can un uninstall the agent via Terminal:
 
sudo launchctl unload /Library/LaunchDaemons/com.pulseway.PulsewayHelper.plist sudo launchctl unload /Library/PrivilegedHelperTools/com.pulseway.PulsewayHelper sudo launchctl unload /Library/PrivilegedHelperTools/com.pulseway.PulsewayCommandHelper sudo rm -v /Library/PrivilegedHelperTools/com.pulseway.Pulseway*  

Hi,
Please contact support@pulseway.com and we'll get in touch.
Thanks!
Mark

Hi,
pulseway-registration is under /usr/sbin.
Mark
 

Hi,
You can download the Linux agent version 6.0 from here: https://www.pulseway.com/downloads
Mark

Hi,
Pulseway supports CentOS 6+.
Best regards,
Mark
 
 
 

Hi,
You can make a systemctl service:
[Unit] Description=HA Bridge Wants=network.target After=network.target [Service] Type=simple ExecStart=/usr/bin/java -jar -Dserver.port=8090 -Dconfig.file=/home/pi/habridge/habridge.config /home/pi/habridge/ha-bridge-3.5.1.jar > /home/pi/habridge/habridge-log.txt 2>&1 [Install] WantedBy=multi-user.target  
Mark

Hi KenL
Unfortunately Pulseway Linux agent doesn't support RH version 5.
Best regards,
Mark

Hi Yohan,
Can you please send an email to support@pulseway.com with /var/log/messages file and output of the following:
cat /proc/cpuinfo uname -a openssl -v ldd --version   Thanks!   Regards, Mark  

The configuration of the services depends on the operating system and the init daemon (UPSTART, SYSVINIT or SYSTEMD).  Debian Jessie use SYSTEMD as system and service manager. Try to change DaemonType="UPSTART" to DaemonType="SYSTEMD".
Mark
 

Hi Norman,
Please edit /etc/init.d/pulseway and change : # chkconfig: 98 98 03 with: # chkconfig: 35 98 03 Then run this: /sbin/chkconfig --add pulseway/sbin/chkconfig --level 35 pulseway on Regards,
Mark
 
 

Hi Toby,
Thank you for reporting this. Can you, please, run in Terminal:
df -hRegards,
Mark

Hi,

This is your replay from other thread after I tested your configure file with a vanilla FC16 installation:

"Yes, it works. I can see two new machines - one offline and one online.
So, what might cause the problem on my machine ? :("

We don't what you have installed on your machine, we don't know how your machine is configured. All our release we test then against fresh VANILLA distributions. And your config file WORKS with a fresh install of FC16.

Mark

Hi,
 
Correct configuration for sshd service on Fedora is:
 
<Service Name="sshd.service" DisplayName="SSH Daemon" IsDaemon="true" DaemonType="SYSTEMD" Path="" StartParameters="" CanBeStopped="true" Enabled="true"/>
 
Regards,
Mark

Hi,
 
'Name' can be modified editing 'Computer Information' section from config.xml (/etc/pulseway/config.xml):
<!--Computer Information--> <!--Name: the name you want this computer to be listed as (Default: Linux computer name)--> <!--Group: the name of the group you want this computer to be listed in (Default: "Default")--> <ComputerInformation Name="" Group="" /> Regards,
Mark

Hi,
 
"pcmonitord" is the name of the binary. "pcmonitor" is the name of service script. 
Starting the service with "pcmonitord start" it's in fact a hack. The install process should register "pcmonitor" as a service script. 
The PCMonitor package does not support Gentoo systems yet. This does not mean it is not running fine on Gentoo. (or Slackware, or Arch) 
 
Regards,
Mark

Hi,

Thanks for reporting!
Is the error persistent (you get the error all the time) ? What service is running on 443?
I'll try to match your environment to replicate the issue.

Regards,
Mark

Hi,

Thanks for reporting!
Is the error persistent (you get the error all the time) ? What service is running on 443?
I'll try to match your environment to replicate the issue.

Regards,
Mark

In order to manually upgrade the Pulseway agent to the latest version, the old version need to be removed first:
rpm -e pcmonitor or dpkg --remove pcmonitor
 
Check if pcmonitord process is still running:
ps auxw | grep pcmonitord
 
Kill the process if it is still running:
killall pcmonitord
 
Install the new version:
rpm -Uhv pulseway_xXX.rpm
or
dpkg -i pulseway_xXX.deb
 
Start the pulseway service:
/etc/init.d/pulseway start

You can remove existing one: rpm -e pcmonitor and install new one: rpm -ihv pcmonitor_x64.rpm
or you can force reinstall: rpm -ihv pcmonitor_x64.rpm --force

Hi,
 
Thanks for reporting this problem. This issue will be fixed in the next version.
 
Regards,
Mark

Hi,
 
It's on our roadmap.
 
regards,
Mark

Hi,



PCMonitorHelper it's a LaunchDaemon. Even if you will kill it from Activity Monitor, process respawns. LaunchDaemon's are controlled by launchd. The correct way to load/unload is via launchctl.

Mark

To uninstall it use the following steps:

1. Uncheck "Show at login".

2. Delete PCMonitor from /Applications

3. As superuser (sudo su -) :
launchctl remove com.mobilepcmonitor.PCMonitorHelper
rm -rf /Library/LaunchDaemons/com.mobilepcmonitor.PCMonitorHelper.plist
rm -rf /Library/PrivilegedHelperTools/com.mobilepcmonitor.PCMonitorHelper
rm -rf /var/root/Library/Application\ Support/PCMonitor/

The final 1.0 version will have an uninstaller.