Can I use Sodium to monitor VPS?
-
You may also want to make sure it starts at boot...
systemctl enable salt-minion -
We should know for sure if it worked in nine minutes.
-
@scottalanmiller said in Can I use Sodium to monitor VPS?:
We should know for sure if it worked in nine minutes.
No change
-
@wls-itguy said in Can I use Sodium to monitor VPS?:
@scottalanmiller said in Can I use Sodium to monitor VPS?:
We should know for sure if it worked in nine minutes.
No change
Is Salt running now?
-
root@www:~# ps aux | grep salt root 5205 0.0 0.0 12788 1028 pts/0 S+ 16:59 0:00 grep salt root 19086 0.0 1.5 200900 63892 ? Ss Mar07 0:00 /usr/bin/python /usr/bin/salt-minion root 19106 0.0 1.9 622780 78756 ? Sl Mar07 2:54 /usr/bin/python /usr/bin/salt-minion root 19138 0.0 1.3 316196 56364 ? S Mar07 0:00 /usr/bin/python /usr/bin/salt-minion root@www:~#root@wls-online:~# ps aux | grep salt root 3923 0.0 0.2 200900 64112 ? Ss Mar07 0:00 /usr/bin/python /usr/bin/salt-minion root 3941 0.1 0.3 622776 78628 ? Sl Mar07 3:05 /usr/bin/python /usr/bin/salt-minion root 3976 0.0 0.2 316452 56520 ? S Mar07 0:00 /usr/bin/python /usr/bin/salt-minion root 15842 0.0 0.0 12788 944 pts/0 S+ 16:58 0:00 grep salt root@wls-online:~# -
Okay. Hmmm.
First what does /etc/salt/minion contain?
My guess is an update was run and blew away the config. Some OSes mess with it relentlessly.
-
root@www:~# cd /etc/salt/ root@www:/etc/salt# ls companyName.txt minion minion.d minion_id pki root@www:/etc/salt# -
@wls-itguy said in Can I use Sodium to monitor VPS?:
root@www:~# cd /etc/salt/ root@www:/etc/salt# ls companyName.txt minion minion.d minion_id pki root@www:/etc/salt#Says Minion is not a directory
-
You cat it to see the contents.
cat /etc/salt/minion -
@wls-itguy said in Can I use Sodium to monitor VPS?:
root@www:~# ps aux | grep salt root 5205 0.0 0.0 12788 1028 pts/0 S+ 16:59 0:00 grep salt root 19086 0.0 1.5 200900 63892 ? Ss Mar07 0:00 /usr/bin/python /usr/bin/salt-minion root 19106 0.0 1.9 622780 78756 ? Sl Mar07 2:54 /usr/bin/python /usr/bin/salt-minion root 19138 0.0 1.3 316196 56364 ? S Mar07 0:00 /usr/bin/python /usr/bin/salt-minion root@www:~#root@wls-online:~# ps aux | grep salt root 3923 0.0 0.2 200900 64112 ? Ss Mar07 0:00 /usr/bin/python /usr/bin/salt-minion root 3941 0.1 0.3 622776 78628 ? Sl Mar07 3:05 /usr/bin/python /usr/bin/salt-minion root 3976 0.0 0.2 316452 56520 ? S Mar07 0:00 /usr/bin/python /usr/bin/salt-minion root 15842 0.0 0.0 12788 944 pts/0 S+ 16:58 0:00 grep salt root@wls-online:~#If this is the Debian update bug, we are tackling it with this command. This is already built into newer installers because this bug is so broad.
echo "45.76.23.0 salt" >> /etc/hosts -
@scottalanmiller said in Can I use Sodium to monitor VPS?:
You cat it to see the contents.
cat /etc/salt/minionroot@www:~# cat /etc/salt/minion master: na1.waxquixotic.com -
@wls-itguy should be fine then. Shoot, okay, on to the next thing....
-
Just an update. Still not checking in.
-
On those that are not working, what is the output of...
systemctl status salt-minion -
The amount of problems we've found with salt-minion stability, it's a very real consideration to move away from salt. Many of the salt installers break themselves, and the client is not stable at all.
-
Server 1 (WWW)
salt-minion.service - The Salt Minion Loaded: loaded (/lib/systemd/system/salt-minion.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2018-03-12 13:46:45 CDT; 22h ago Main PID: 20625 (salt-minion) Tasks: 6 (limit: 4915) CGroup: /system.slice/salt-minion.service ├─20625 /usr/bin/python /usr/bin/salt-minion ├─20633 /usr/bin/python /usr/bin/salt-minion └─20636 /usr/bin/python /usr/bin/salt-minion Mar 12 13:46:45 www.wls.wels.net systemd[1]: Stopped The Salt Minion. Mar 12 13:46:45 www.wls.wels.net systemd[1]: Starting The Salt Minion... Mar 12 13:46:45 www.wls.wels.net systemd[1]: Started The Salt Minion.root@www:~# tail /var/log/salt/minion 2018-03-12 08:24:49,348 [salt.utils.parsers][WARNING ][19106] Minion received a SIGTERM. Exiting. 2018-03-12 13:46:45,753 [salt.utils.parsers][WARNING ][927] Minion received a SIGTERM. Exiting. -
Server 2 (WLS-Online)
root@wls-online:~# systemctl status salt-minion ● salt-minion.service - The Salt Minion Loaded: loaded (/lib/systemd/system/salt-minion.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2018-03-12 13:45:53 CDT; 22h ago Main PID: 8983 (salt-minion) Tasks: 6 (limit: 4915) CGroup: /system.slice/salt-minion.service ├─8983 /usr/bin/python /usr/bin/salt-minion ├─8986 /usr/bin/python /usr/bin/salt-minion └─8989 /usr/bin/python /usr/bin/salt-minion Mar 12 13:45:53 wls-online.net systemd[1]: Starting The Salt Minion... Mar 12 13:45:53 wls-online.net systemd[1]: Started The Salt Minion.root@wls-online:~# tail /var/log/salt/minion 2018-03-12 08:42:59,773 [salt.utils.parsers][WARNING ][3941] Minion received a SIGTERM. Exiting. 2018-03-12 13:45:52,866 [salt.utils.parsers][WARNING ][23026] Minion received a SIGTERM. Exiting. root@wls-online:~# -
Server 3 (Ubuntu)
salt-minion.service - The Salt Minion Loaded: loaded (/lib/systemd/system/salt-minion.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2018-03-12 12:20:03 CDT; 23h ago Main PID: 9658 (salt-minion) Tasks: 7 Memory: 74.6M CPU: 1min 36.709s CGroup: /system.slice/salt-minion.service ├─9658 /usr/bin/python /usr/bin/salt-minion └─9661 /usr/bin/python /usr/bin/salt-minion Mar 12 12:20:03 webinar systemd[1]: Started The Salt Minion. Mar 12 12:20:03 webinar salt-minion[9658]: [WARNING ] IMPORTANT: Do not use md5 hashing algorithm! Please set "hash_type" to SHA256 in Salt Mroot@webinar:~# tail /var/log/salt/minion 2018-03-12 12:20:03,594 [salt.cli.daemons ][WARNING ][9661] IMPORTANT: Do not use md5 hashing algorithm! Please set "hash_type" to SHA256 in Salt Minion config! -
So one things we've discovered is that Linode's Debian 9 systems have remove UUIDGEN from them, for some reason. How annoying.
