SSMS Smart Software Manager Satellite HA IP down

[olivermatt1]

We are running Smart Software Manager Satellite Classic Edition 5.1.0 in HA Deployment and cannot connect to the virtual cluster ip anymore. Both nodes are up and running. A ping to the ip address of each node is successful, but the Web GUI is not accessible any more.

We had that issue once and rebooting both nodes solved the problem in the past. Now we've tried rebooting the nodes again but the cluster IP and GUI stays down. Web GUI is also not reachable over the ip of the cluster nodes.

According to the troubleshooting section in the user guide we've tried to check the cluster status and manually stop/start the cluster without success.

[admin@satellite-node-01 ~]$ pcs cluster start --all

Error: Unable to connect to localhost ([Errno 111] Connection refused)

[admin@satellite-node-01 ~]$ pcs status

Error: cluster is not currently running on this node

Any ideas?

Kind regards

Oliver

[olivermatt1 · Accepted solution]

Solved: the directory /var/log was on 100%. Deleting old messages files on both nodes and rebooting solved the issue.

[admin@satellite-node-02 ~]$ df -h

Filesystem                Size  Used Avail Use% Mounted on

/dev/mapper/vg1-lv_root    29G  4.5G   24G  16% /

devtmpfs                  3.9G     0  3.9G   0% /dev

tmpfs                     3.9G   39M  3.8G   1% /dev/shm

tmpfs                     3.9G  385M  3.5G  10% /run

tmpfs                     3.9G     0  3.9G   0% /sys/fs/cgroup

/dev/sda1                1014M  133M  882M  14% /boot

/dev/mapper/vg1-lv_log    4.7G  4.7G   20K 100% /var/log

/dev/mapper/vg1-lv_tmp    2.0G   33M  2.0G   2% /tmp

/dev/mapper/vg1-lv_audit  2.0G   71M  2.0G   4% /var/log/audit

tmpfs                     783M     0  783M   0% /run/user/1000

[admin@satellite-node-02 ~]$ ls -l /var/log

total 4687964

drwx------. 3 root      root            118 Jun 24 03:11 aide

drwxr-xr-x. 2 root      root            191 May 22 04:40 anaconda

drwx------. 2 root      root             99 Jul  4 00:55 audit

-rw-------. 1 root      utmp              0 May 22 04:20 btmp-20190601

-rw-------. 1 root      utmp              0 Jun  1 03:44 btmp-20190701

drwxr-xr-x. 2 chrony    chrony            6 Nov 14  2016 chrony

drwxr-xr-x. 2 root      root           4096 Jul  3 04:19 cluster

-rw-------. 1 root      root        2396618 May 26 03:50 cron-20190526

-rw-------. 1 root      root        5202576 Jun  3 03:38 cron-20190603

-rw-------. 1 root      root        3899487 Jun  9 03:23 cron-20190609

-rw-------. 1 root      root         462848 Jul  3 03:31 cron-20190616

-rw-r--r--. 1 root      root         111124 Jul  3 03:51 dmesg

-rw-r--r--. 1 root      root         111088 Jul  3 03:31 dmesg.old

-rw-r--r--. 1 root      root            117 May 22 05:24 firewalld

-rw-------. 1 root      root           1415 May 22 04:28 grubby

drwx------. 2 root      root            112 Jul  3 11:19 httpd

-rw-r--r--. 1 root      root         293168 Jul  4 02:08 lastlog

-rw-------. 1 root      root        1998177 May 26 03:50 maillog-20190526

-rw-------. 1 root      root        4381053 Jun  3 03:38 maillog-20190603

-rw-------. 1 root      root        3285446 Jun  9 03:23 maillog-20190609

-rw-------. 1 root      root         438272 Jul  3 03:30 maillog-20190624

drwxr-x---. 2 mysql     mysql            25 May 22 04:28 mariadb

-rw-------. 1 root      root      555627786 May 26 03:50 messages-20190526

-rw-------. 1 root      root     1320309304 Jun  3 03:38 messages-20190603

-rw-------. 1 root      root     2541226547 Jun  9 03:23 messages-20190609

-rw-------. 1 root      root      294031360 Jul  3 03:31 messages-20190630

drwxrwxrwx. 2 root      root              6 May 22 04:30 mysql

-rw-r-----. 1 mysql     mysql          4096 Jul  3 11:20 mysqld.log

drwxr-xr-x. 2 ntp       ntp               6 Apr 13  2018 ntpstats

-rw-rw----. 1 hacluster haclient       1964 Jul  3 11:18 pacemaker.log