...
| Code Block |
|---|
svcadm disable rpc/bind svcadm disable rpc/meta svcadm enable system/mdmonitor |
Verify your changes,
| Code Block |
|---|
svcs -a | grep "rpc/bind:";svcs -a | grep "rpc/meta:";svcs -a | grep "system/mdmonitor:"
disabled Jun_17 svc:/network/rpc/bind:default
uninitialized Jun_17 svc:/network/rpc/meta:default
online Jun_17 svc:/system/mdmonitor:default |
Optionally if you are using a newer version of grep via GTools,
| Code Block | ||
|---|---|---|
| ||
svcs -a | grep 'rpc/bind:\|rpc/meta:\|system/mdmonitor:'
disabled Jun_17 svc:/network/rpc/bind:default
online Jun_17 svc:/system/mdmonitor:default
uninitialized Jun_17 svc:/network/rpc/meta:default |
| Warning |
|---|
Dickson, would you know why even though we manually disabled rpc/meta: shows up as uninitialized? |
Details
Based on the linked articles this is a dependency issue.
| Info |
|---|
When I talk about states I am referring to the STATE as represented when running the svcs -a command. Still researching if the other articles are also referring to thisA service can be in the following states, online, offline, uninitialized and disabled. |
The mdmonitor daemon is needed to sync the meta devices at system start up. If svc:/system/mdmonitor is not running, the devices come into maintenance state.
The cause according to Engle Victor's postdisabledpost is an "optional_all" dependency of svc:/network/rpc/meta. "optional_all" allows mdmonitord to start if svc:/network/rpc/meta is disabled or in our case uninitialized but not if it is in the offline state . Because of this or in our case uninitialized. As are result, svc:/system/mdmonitor is put into the offline state.
...