I had the exact same problem arjendra had and used the same solution (killing rpc.statd) to get the mailbox back up and running (e.g get rid of the "zmmailboxdctl is not running." message). But I found the reason why and would like to share.
Quote:
Originally Posted by arjendra  I don't settings service rpc.statd run on 993 & don't know why this happen |
I didn't set rpc.statd to any port either.
rpc.statd takes random ports. Phoenix is right, you can set the port.
`man rpc.statd` says
Code:
-p, --port port
specify a port for rpc.statd to listen on. By default, rpc.statd will ask
portmap(8) to assign it a port number. As of this writing, there is not a standard
port number that portmap always or usually assigns. Specifying a port may be use-
ful when implementing a firewall. So I tried locking down the port that rpc.statd will listen on in /etc/sysconfig/nfs by uncommenting MOUNTD_PORT, STATD_PORT and setting a port number.
The solution was found here:
TCP port 993 hijacked by mountd, rpc.statd
After rebooting, rpc.statd was listening on the port indicated in STATD_PORT and Zimbra procresses were running.