Jump to content
Pulseway 9.14 🔥

Featured Replies

Posted
  • Staff

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

  • 1 month later...

@collector, it doesnt remove the config.xml file but it does break something...

[root@COOPER ~]# cd /etc/pcmonitor/
[root@COOPER pcmonitor]# ls
config.xml
[root@COOPER pcmonitor]# /etc/init.d/pcmonitor restart
/etc/pcmonitor/config.xml not found. exit

Stopping pcmonitor daemon:                                 [  OK  ]
/etc/pcmonitor/config.xml not found. exit

Starting pcmonitor daemon:                                 [  OK  ]
[root@COOPER pcmonitor]#

Any ideas guys ? As you can see config.xml does exist !

Hi Mark,

Thanks for the reply. It looks as if when doing the 'update' it changes the properties of the config.xml.

I just ran:

chmod 777 /etc/pcmonitor/config.xml

And it all now works fine !

Although did just notice it duplicated my server on my dashboard/app. One server was offline and the other online. Have removed the offline one now.

On a CentOS 6.5 x64 box.

Hope this helps.

Craig

Also just ran on 2 other CentOS 6.4 boxes.

The error '/etc/pcmonitor/config.xml not found. exit' is a false positive. As the pcmonitord runs OK but shows that error before I run the chmod command.

  • 3 weeks later...
  • 5 months later...

Create an account or sign in to comment