Skip to main content
NetApp Knowledge Base

ONTAP Mediator crashes and fails to start mediator-scst.service

Views:
1,110
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
MetroCluster
Last Updated:

Applies to

  • ONTAP Mediator
  • Metrocluster-IP
  • Cent OS
  • RHEL

Issue

  • The MetroCluster Mediator connection status reports as false for all nodes. 

::> metrocluster configuration-settings mediator show
Mediator IP     Port    Node                    Configuration Connection
                                                Status        Status
--------------- ------- ----------------------- ------------- -----------
10.XXX.YYY.Z
                31784   Node001-n2            true          false
                        Node001-n1            true          false
                        Node002-n2            true          false
                        Node002-n1            true          false

  • Mediator fails to start the scst service with following error message:

systemctl start mediator-scst
Job for mediator-scst.service failed because the control process exited with error code.
See "systemctl status mediator-scst.service" and "journalctl -xe" for details.

May 23 11:50:27 bovprodwemediator001 kernel: [15767]: dev_vdisk: ***ERROR***: opening /mnt/iscsi_space/mb.63b89d7d-6cce-11ed-b879-d039ea9e40a8:d04ee6db-6ccf-11ed-aac3-d039ea9e418a:1.0 failed: -2
 May 23 11:50:27 bovprodwemediator001 kernel: [15767]: scst: ***ERROR***: New device handler's vdisk_fileio attach() failed: -2

Mar 25 15:38:05 scst[28788]: FATAL: Received the following error:
Mar 25 15:38:05 scst[28788]: A fatal error occurred. See "dmesg" for more information.

Mar 25 15:39:01 kernel: scst: SCST unloaded
Mar 25 15:39:01 systemd[1]: mediator-scst.service: Control process exited, code=exited status=1
Mar 25 15:39:01 systemd[1]: mediator-scst.service: Failed with result 'exit-code'.
Mar 25 15:39:01 systemd[1]: Failed to start mediator-scst.service.

mediator-scst.service failed to start.
Dec 10 14:30:29 mediator01 systemd[1]: Starting ONTAP Mediator...
Dec 10 14:30:33 mediator01 ontap_mediator[1041]: mount: /opt/netapp/lib/ontap_mediator/log: wrong fs type, bad >
Dec 10 14:30:35 mediator01 ontap_mediator[1179]: [uWSGI] getting INI configuration from /opt/netapp/lib/ontap_m>
Dec 10 14:31:59 mediator01 systemd[1]: Started ONTAP Mediator.
[admin@mediator01 ~]$ systemctl status mediator-scst
× mediator-scst.service
     Loaded: loaded (/etc/systemd/system/mediator-scst.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Tue 2024-12-10 14:30:31 HKT; 20min ago
    Process: 1141 ExecStart=/etc/init.d/scst start (code=exited, status=5)
        CPU: 58ms

Dec 10 14:30:31 mediator01 systemd[1]: mediator-scst.service: Scheduled restart job, restart counter is at 5.
Dec 10 14:30:31 mediator01 systemd[1]: Stopped mediator-scst.service.
Dec 10 14:30:31 mediator01 systemd[1]: mediator-scst.service: Start request repeated too quickly.
Dec 10 14:30:31 mediator01 systemd[1]: mediator-scst.service: Failed with result 'exit-code'.
Dec 10 14:30:31 mediator01 systemd[1]: Failed to start mediator-scst.service.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.