Micetro by Men&Mice

Latest versions

Search all documentation

Child pages
  • Troubleshooting the Men & Mice DNS Server Controller for Unix-type Operating Systems
Skip to end of metadata
Go to start of metadata


You can login to the Men & Mice Suite, but you cannot access one or more DNS Servers managed by the Suite.


The Men & Mice Central Service (mmcentrald) cannot connect to the Men & Mice DNS Server Controller Service (mmremoted).


Try to log in as the administrator user. After you dismiss the error dialog, if the Management Console doesn’t ask you again to log in, then take the following steps:
  • Click on DNS Servers on the left, then select the problem server in the main pane.
  • Select "Edit Server Name..." (Version 6.1 onwards), check that the Servers hostname used in the tool actually resolves to the correct IP Address and that the IP Address shown is the correct IP Address of the DNS Server
  • If the above step doesn't solve the issue, choose the menu item Server > Delete. This won’t affect the name server’s data in any way - your zones will still be there, but this step will remove all change history from the DNS Server as well as all Access Permissions.
  • Choose the menu item File > New > DNS Server. You may need to specify the server’s address. This reconnects you to the DNS Server Controller.
If that doesn’t fix the problem, then see if the DNS Server Controller is actually running.

Open a root shell and execute the init script mmremote with the argument status. For example, on a Linux system:
/etc/init.d/mmremote status
Note that on FreeBSD, the init script is stored in /usr/local/etc/rc/mmremote.

If the DNS Server Controller is running, try restarting it. Execute the init script with the argument restart. For example:
/etc/init.d/mmremote restart
If this doesn’t fix the problem, contact Men & Mice technical support.

If the DNS Server Controller will not start, start it in debug mode. Figure out what command line parameters it needs by examining the PARAMS variable declaration near the top of the init script, and then execute the mmremoted command with those parameters plus -ll5 -debug. For example, it might look like this:
/usr/sbin/mmremoted -debug -ll5 -unamed -gnamed -t/var/chroot/named -c/etc/named.conf 

You should see one or more error messages, along with other output. If you can’t figure out the problem from this, send us the whole command output for examination. If for some reason the program doesn’t stop by itself, type control-c to stop it.