The management interface occasionally gets stuck opening a socket or dbus timeouts. The recommendation is to restart the interface.
This will not have any impact on the storage or shares, it just restarts the management interface.
Run the command: svcadm -v disable nm{s,v,cd} nbs nmdtrace dbus rmvolmgr
Example output of that command below:
root@amber:/volumes# svcadm -v disable nm{s,v,cd} nbs nmdtrace dbus rmvolmgr
svc:/application/nms:default disabled.
svc:/application/nmv:default disabled.
svc:/application/nmcd:default disabled.
svc:/system/dbus:default disabled.
svc:/application/nmdtrace:default disabled.
svc:/application/nbs:default disabled.
svc:/system/filesystem/rmvolmgr:default disabled.
After running this, wait a full 60 seconds, and then type: svcs nm{s,v,cd} nbs nmdtrace dbus rmvolmgr
Example output of what you should see below:
root@amber:/volumes# svcs nm{s,v,cd} nbs nmdtrace dbus rmvolmgr
STATE STIME FMRI
disabled 14:23:41 svc:/application/nmcd:default
disabled 14:23:41 svc:/application/nmv:default
disabled 14:23:48 svc:/application/nmdtrace:default
disabled 14:24:12 svc:/application/nms:default
disabled 14:24:12 svc:/application/nbs:default
disabled 14:24:13 svc:/system/dbus:default
disabled 14:24:17 svc:/system/filesystem/rmvolmgr:default
If you run this command and see something like this:
root@amber:/volumes# svcs nm{s,v,cd} nbs nmdtrace dbus rmvolmgr
STATE STIME FMRI
disabled 14:23:41 svc:/application/nmcd:default
disabled 14:23:41 svc:/application/nmv:default
disabled 14:23:48 svc:/application/nmdtrace:default
online Jul_08 svc:/system/dbus:default
online Jul_08 svc:/application/nbs:default
online* 14:23:41 svc:/application/nms:default
online* 14:24:17 svc:/system/filesystem/rmvolmgr:default
Then you need to wait another 60 seconds and check again. If you still see anything but the first printout (with all services showing as disabled), wait a third 60 seconds and check one last time.
Once all of the services are disabled, type: svcadm -v enable nm{s,v,cd} nbs nmdtrace dbus rmvolmgr
Example output below:
root@amber:/volumes# svcadm -v enable nm{s,v,cd} nbs nmdtrace dbus rmvolmgr
svc:/application/nms:default enabled.
svc:/application/nmv:default enabled.
svc:/application/nmcd:default enabled.
svc:/application/nbs:default enabled.
svc:/application/nmdtrace:default enabled.
svc:/system/dbus:default enabled.
svc:/system/filesystem/rmvolmgr:default enabled.
Then wait a full 60 seconds. Once 60 seconds has elapsed, type this command: svcs nm{s,v,cd} nbs nmdtrace dbus rmvolmgr
Example output below:
root@amber:/volumes# svcs nm{s,v,cd} nbs nmdtrace dbus rmvolmgr
STATE STIME FMRI
online 14:36:19 svc:/system/dbus:default
online 14:36:19 svc:/application/nbs:default
online 14:36:20 svc:/application/nmdtrace:default
online 14:36:26 svc:/application/nms:default
online 14:36:26 svc:/application/nmv:default
online 14:36:29 svc:/application/nmcd:default
online 14:36:35 svc:/system/filesystem/rmvolmgr:default
If you see an output like the above, you can now attempt to login to the NMV or NMC and see if they respond. If they do, you should be in good shape. If you do not see an output like the above, and instead see an output where services have a status of offline and one or more have a status of online*, wait another 60 seconds and check again. Repeat up to 5 times (it can take up to 5 minutes in some extreme cases). If after 5 minutes your output still doesn't look like the above, please let me know and be sure to include all the output from the above commands.