Mediator fails to start after mediator server upgrade
Applies to
- ONTAP 9
- ONTAP MEDIATOR
- Metrocluster
Issue
Mediator fails to start after mediator RHEL server OS upgrade
Example:
The unit ontap_mediator.service has entered the 'failed' state with result 'exit-code'.
Sep 25 09:52:00 mediator.ucs.xxx.xxx systemd[1]: Failed to start ONTAP Mediator.
-- Subject: Unit ontap_mediator.service has failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit ontap_mediator.service has failed.
--
-- The result is failed.
Sep 25 09:52:00 mediator.ucs.xxx.xxx systemd[1]: ontap_mediator.service: Service RestartSec=100ms expired, scheduling restart.
Sep 25 09:52:00 mediator.ucs.xxx.xxx systemd[1]: ontap_mediator.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit ontap_mediator.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Sep 25 09:52:00 mediator.ucs.xxx.xxx systemd[1]: Stopped ONTAP Mediator.
-- Subject: Unit ontap_mediator.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit ontap_mediator.service has finished shutting down.