Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to restart salt-minion on Arista #63044

Open
hokie1999 opened this issue Nov 8, 2022 · 3 comments
Open

Unable to restart salt-minion on Arista #63044

hokie1999 opened this issue Nov 8, 2022 · 3 comments
Labels
Bug broken, incorrect, or confusing behavior needs-triage v2018.3 unsupported version

Comments

@hokie1999
Copy link

hokie1999 commented Nov 8, 2022

Description

Unable to restart salt-minion on Arista load balancer running as

ps -ef | grep salt-minion
root 21393 1 0 2019 ? 3-03:28:39 /usr/bin/python /usr/bin/salt-minion -d <<<< daemon

How would I do that?

Setup

Arista DCS-7150S-52-CL-SSD-F
Hardware version: 02.02
Serial number: JPE15151411
System MAC address: 001c.73b5.09db

Software image version: 4.19.0F-2GB
Architecture: i386
Internal build version: 4.19.0F-2GB-6005119.4190F
Internal build ID: 5969f1e5-2623-40f9-839e-749fdf7c794a

salt --version
salt 2018.3.0-2772-g34b3b90 (Oxygen)

/etc/redhat-release
Fedora release 18 (Spherical Cow)

Steps to Reproduce the behavior

Have tried:

on the arista:

salt-call service.restart salt-minion

systemctl restart salt-minion

service salt-minion restart

salt-call cmd.run 'systemctl restart salt-minion'

There is no reference to salt-minion in /usr/lib/systemd/system or in /etc/rc.d service --status-all and systemctl list-unit-files does not list salt-minion

Expected behavior

Looking for correct command to restart salt-minion. This is related to the need to re-point minion to new salt-master controllers via the /etc/salt/minion file

Screenshots
na

Versions Report
Salt Version:
Salt: 2018.3.0-2772-g34b3b90

Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: 2.4.2
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
ioflo: Not Installed
Jinja2: 2.8
libgit2: Not Installed
libnacl: Not Installed
M2Crypto: 0.21.1
Mako: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.4.8
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: 2.6.1
pycryptodome: Not Installed
pygit2: Not Installed
Python: 2.7.5 (default, Aug 26 2017, 23:44:09)
python-gnupg: Not Installed
PyYAML: 3.12
PyZMQ: 15.3.0
RAET: Not Installed
smmap: Not Installed
timelib: Not Installed
Tornado: 4.4.2
ZMQ: 4.1.4

System Versions:
dist: fedora 4.19.0
locale: ANSI_X3.4-1968
machine: x86_64
release: 3.4.43.Ar-5956591.4190F
system: Linux
version: Arista Networks EOS 4.19.0

Additional context

@hokie1999 hokie1999 added Bug broken, incorrect, or confusing behavior needs-triage labels Nov 8, 2022
@OrangeDog
Copy link
Contributor

OrangeDog commented Nov 9, 2022

Please can you fix the formatting and add an issue title?

However, 2018.3.0 is very old, unsupported, and has many security vulnerabilities.
How you restart it would depend on how it was installed and started in the first place, but your Salt system should really be upgraded at the soonest opportunity.

@OrangeDog OrangeDog added the v2018.3 unsupported version label Nov 9, 2022
@hokie1999
Copy link
Author

hokie1999 commented Nov 9, 2022

Can someone suggest a way to restart it? what about commands: kill 9 PID and /usr/bin/salt-minion-d Is there an easier way?

@hokie1999 hokie1999 changed the title [BUG] [BUG] -- Unable to restart salt-minion on Arista Nov 9, 2022
@hokie1999 hokie1999 changed the title [BUG] -- Unable to restart salt-minion on Arista Unable to restart salt-minion on Arista Nov 9, 2022
@OrangeDog
Copy link
Contributor

If that was how it was started in the first place, then that's the only way to restart it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior needs-triage v2018.3 unsupported version
Projects
None yet
Development

No branches or pull requests

2 participants