Centos 8: installing procps-ng-3.3.15-3.el8.x86_64 cmon stop to run.

Follow

Paolo Bernardoni

• December 17, 2020 08:50

updating with yum to latest release of centos 8 cmon do not open port 9500

If i don't upgrade procps-ng from rpm procps-ng-3.3.15-1.el8.x86_64 to procps-ng-3.3.15-3.el8.x86_64 cmon run ok.

Error: Failed to connect to 127.0.0.1 port 9500: Connection refused.

cmon.cnf key is correct.

Thank you

Paolo

0

• Official comment

  

  Krzysztof Ksiazek

  • December 18, 2020 09:18

  Hi,

  Can you please try to start the cmon by hand on the more recent procps-ng? In order to reproduce it I upgraded by CentOS8 and while systemctl was unable to handle cmon, I was still able to run the command (cmon --rpc-port=9500 --bind-addr='127.0.0.1' --events-client='http://127.0.0.1:9510' --cloud-service='http://127.0.0.1:9518') by hand.

  Please let us know if that's the case for you as well.

  Comment actions Permalink
• 

  Pon Suresh Pandian

  • December 17, 2020 09:05

  Hi Paolo,

  Please create a support ticket for this issue it will be helpful us to analyse further.

  0

  Comment actions Permalink
• 

  Jorma Tuomainen

  • December 18, 2020 06:45

  Hi,

  I can confirm this, didn't work after upgrade (googled this post)

  with current procps-ng (procps-ng-3.3.15-3.el8.x86_64):

  # /etc/init.d/cmon restart
  Stopping cmon : /etc/init.d/cmon: line 162: kill: (2537) - No such process
  /etc/init.d/cmon: line 162: kill: (2536) - No such process
  Terminated

  downgraded from vault to procps-ng-3.3.15-1.el8.x86_64:

  # /etc/init.d/cmon restart
  Stopping cmon : failed
  Schema : Schema auto-upgrade succeed (version 107060).
  The Cmon Controller is initializing.
  Going to daemonize.. - cmon will write a log in /var/log/cmon.log from now
  Starting cmon --rpc-port=9500 --bind-addr='127.0.0.1' --events-client='http://127.0.0.1:9510' --cloud-service='http://127.0.0.1:9518' : ok

  And everything is working again.

  0

  Comment actions Permalink
• 

  Paolo Bernardoni

  • December 18, 2020 09:34

  hi, installed procps-ng-3.3.15-3.el8.x86_64 and run cmon from CLI

  # cmon --rpc-port=9500 --bind-addr='127.0.0.1' --events-client='http://127.0.0.1:9510' --cloud-service='http://127.0.0.1:9518'
  The Cmon Controller is initializing.
  Going to daemonize.. - cmon will write a log in /var/log/cmon.log from now

  cluster control run without error.

  Paolo

   

  0

  Comment actions Permalink

Please sign in to leave a comment.