re-start tmm
1 TopicAfter update to 14.1 re-starting some services
Hi, I've updated a test-F5 (VE with LAB-License) to version 14.1.0.3. Now I see in the tmsh every few seconds these logs: [CODE] Broadcast message from systemd-journald@hostname (Wed 2019-04-24 12:33:07 CEST): logger[13322]: Re-starting tmm3 2019 Apr 24 12:33:07 hostname logger[13322]: Re-starting tmm3 Broadcast message from systemd-journald@hostname (Wed 2019-04-24 12:33:26 CEST): logger[14260]: Re-starting bigd 2019 Apr 24 12:33:26 hostname logger[14260]: Re-starting bigd Broadcast message from systemd-journald@hostname (Wed 2019-04-24 12:33:27 CEST): logger[14329]: Re-starting tmipsecd 2019 Apr 24 12:33:27 hostname logger[14329]: Re-starting tmipsecd Broadcast message from systemd-journald@hostname (Wed 2019-04-24 12:34:08 CEST): logger[17958]: Re-starting tmm 2019 Apr 24 12:34:08 hostname logger[17958]: Re-starting tmm Broadcast message from systemd-journald@hostname (Wed 2019-04-24 12:34:08 CEST): logger[17967]: Re-starting tmm1 2019 Apr 24 12:34:08 hostname logger[17967]: Re-starting tmm1 Broadcast message from systemd-journald@hostname (Wed 2019-04-24 12:34:08 CEST): logger[17976]: Re-starting tmm2 2019 Apr 24 12:34:08 hostname logger[17976]: Re-starting tmm2 Broadcast message from systemd-journald@hostname (Wed 2019-04-24 12:34:08 CEST): logger[17987]: Re-starting tmm3 2019 Apr 24 12:34:08 hostname logger[17987]: Re-starting tmm3 Broadcast message from systemd-journald@hostname (Wed 2019-04-24 12:34:27 CEST): logger[18885]: Re-starting bigd 2019 Apr 24 12:34:27 hostname logger[18885]: Re-starting bigd Broadcast message from systemd-journald@hostname (Wed 2019-04-24 12:34:50 CEST): logger[20492]: Re-starting tmipsecd [/CODE] (why can't I paste a code-block with more than one line???) the prompt changes from "inoperative" to "admd Down" to "active" and so on. any suggestions? thanks772Views0likes1Comment