Bug 258053 - sysutils/py-salt: etc/rc.d/salt_minion: WARNING: failed to start salt_minion
Summary: sysutils/py-salt: etc/rc.d/salt_minion: WARNING: failed to start salt_minion
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-ports-bugs (Nobody)
Depends on:
Reported: 2021-08-26 06:52 UTC by O. Hartmann
Modified: 2021-09-22 05:03 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (christer.edwards)


Note You need to log in before you can comment on or make changes to this bug.
Description O. Hartmann 2021-08-26 06:52:30 UTC
After updating ports/packages to py38-salt 3003.2, salt minion do not start anymore _on a subset of systems_. All hosts affected running FreeBSD 13.0-RELENG-p4, most of the working/none-working salt_minion installations are running inside jails of the same OS flavor and version as the ports are taken from the very same source (simply to make clear that working/none-working jails/hosts share the same base OS and the same repo where the packages has been taken and installed from).

Installed port is:
py38-salt-3003.2 sysutils/py-salt

Host's OS is
FreeBSD 13.0-RELEASE-p4 releng/13.0-n244760-940681634ee amd64

The error is:
# service salt_minion restart
salt_minion not running? (check /var/run/salt-minion.pid).
Starting salt_minion.
Traceback (most recent call last):
  File "/usr/local/bin/salt-minion", line 33, in <module>
    sys.exit(load_entry_point('salt==3003.2', 'console_scripts', 'salt-minion')())
  File "/usr/local/bin/salt-minion", line 25, in importlib_load_entry_point
    return next(matches).load()
/usr/local/etc/rc.d/salt_minion: WARNING: failed to start salt_minion

According to some findings on the net, this could be related to some problems with libraries, but I'm unable to discover the differences without disturbing or destroying services we rely on those specific hosts. Jails/Hosts with lots of py38- related installations, like several Apache24 services, seem to fail, while, for instance, Apache24-free servers (only Icinga2 as master installed) work fine. The source on the net referred to above is:


It is Linux, not FreeBSD, but it might be a hint for the maintainer.
Comment 1 O. Hartmann 2021-09-22 05:03:21 UTC
The problem is still present and doesn't vanish with a complete reinstall of the port.