Staff Mark Posted February 9, 2014 Staff Posted February 9, 2014 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 Paul 1
collector Posted March 24, 2014 Posted March 24, 2014 Does removing the old version also remove the config file?
Craigusus Posted March 31, 2014 Posted March 31, 2014 @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 !
Staff Mark Posted March 31, 2014 Author Staff Posted March 31, 2014 Hi, @Craigusus: What distro? stop/start sequence works? Just wander if is something related to restart only. Mark
Craigusus Posted March 31, 2014 Posted March 31, 2014 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
Craigusus Posted March 31, 2014 Posted March 31, 2014 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.
Staff Mark Posted April 16, 2014 Author Staff Posted April 16, 2014 Must be an issue with permisions. I've installed an vanilla CentOS 6.4 in vm, install pcmonitor and started with no issues. Regards, Mark
castumon Posted October 7, 2014 Posted October 7, 2014 There is an simple test -x command in the startscript, therefore you need an chmod 744 on config.xml.
Staff Mark Posted October 7, 2014 Author Staff Posted October 7, 2014 "confix.xml" permision is 744 (part of install script) unless is manually changed.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now