После очередного обновления установился net-misc/networkmanager-1.4.4-r1
У меня в runlevel default забит stunnel
После перегрузки stunnel блокирует сеть
Feb 23 16:28:51 cldm /etc/init.d/stunnel[3852]: stunnel: waiting for NetworkManager (50 seconds)
Feb 23 16:28:51 cldm /etc/init.d/netmount[3854]: netmount: waiting for stunnel (50 seconds)
Feb 23 16:28:51 cldm /etc/init.d/NetworkManager[3853]: NetworkManager: waiting for stunnel (50 seconds)
Feb 23 16:28:51 cldm /etc/init.d/vixie-cron[3864]: vixie-cron: waiting for NetworkManager (50 seconds)
Feb 23 16:28:51 cldm /etc/init.d/calculate-core[3857]: calculate-core: waiting for stunnel (50 seconds)
Feb 23 16:28:51 cldm /etc/init.d/alsasound[3855]: alsasound: waiting for NetworkManager (50 seconds)
Feb 23 16:28:51 cldm /etc/init.d/cupsd[3858]: cupsd: waiting for stunnel (50 seconds)
Feb 23 16:28:51 cldm /etc/init.d/local[3865]: local: waiting for NetworkManager (50 seconds)
Feb 23 16:28:51 cldm /etc/init.d/samba[3861]: samba: waiting for stunnel (50 seconds)
Feb 23 16:28:51 cldm /etc/init.d/sshd[3863]: sshd: waiting for NetworkManager (50 seconds)
. . .
Feb 23 16:29:00 cldm /etc/init.d/stunnel[3852]: stunnel: waiting for NetworkManager (41 seconds)
Feb 23 16:29:00 cldm /etc/init.d/NetworkManager[3853]: NetworkManager: waiting for stunnel (41 seconds)
Feb 23 16:29:00 cldm /etc/init.d/netmount[3854]: netmount: waiting for stunnel (41 seconds)
Feb 23 16:29:00 cldm /etc/init.d/vixie-cron[3864]: vixie-cron: waiting for NetworkManager (41 seconds)
Feb 23 16:29:00 cldm /etc/init.d/calculate-core[3857]: calculate-core: waiting for stunnel (41 seconds)
Feb 23 16:29:00 cldm /etc/init.d/samba[3861]: samba: waiting for stunnel (41 seconds)
Feb 23 16:29:00 cldm /etc/init.d/cupsd[3858]: cupsd: waiting for stunnel (41 seconds)
Feb 23 16:29:00 cldm /etc/init.d/local[3865]: local: waiting for NetworkManager (41 seconds)
Feb 23 16:29:00 cldm /etc/init.d/alsasound[3855]: alsasound: waiting for NetworkManager (41 seconds)
Feb 23 16:29:00 cldm /etc/init.d/sshd[3863]: sshd: waiting for NetworkManager (41 seconds)
. . .
Feb 23 16:29:41 cldm /etc/init.d/NetworkManager[3853]: NetworkManager: timed out waiting for stunnel
Feb 23 16:29:41 cldm /etc/init.d/stunnel[3852]: stunnel: timed out waiting for NetworkManager
Feb 23 16:29:41 cldm /etc/init.d/stunnel[3852]: ERROR: cannot start stunnel as NetworkManager would not start
Feb 23 16:29:41 cldm /etc/init.d/netmount[3854]: netmount: timed out waiting for stunnel
Feb 23 16:29:41 cldm /etc/init.d/vixie-cron[3864]: vixie-cron: timed out waiting for NetworkManager
Feb 23 16:29:41 cldm /etc/init.d/cupsd[3858]: cupsd: timed out waiting for stunnel
Feb 23 16:29:41 cldm /etc/init.d/calculate-core[3857]: calculate-core: timed out waiting for stunnel
После истечения таймаутов сеть все же стартует и стартуют все сервисы кроме stunnel
Вручную теперь stunnel нормально стартует.
Откат на net-misc/networkmanager-1.4.0-r1 ставит все на место.
Правда вылезает еще такое
rc-status
Runlevel: default
NetworkManager [ started ]
stunnel [ started ]
......
calculate-core [ +stopped+ ]
При ручном запуске calculate-core стартует, но как-то странно
# /etc/init.d/calculate-core start
calculate-core | * Start calculate core ...
calculate-core | * start-stop-daemon: /usr/sbin/cl-core is already running [ ok ]
Что тут можно сделать? Блокировать networkmanager-1.4.4-r1, или есть другой выход?
P.S. Ситуация повторилась на CLDX
Увеличил вдвое ожидание в init-скрипте calculate-core
С for waiting in {0…24} на for waiting in {0…48} и calculate-core при перезагрузке стартовал