Amd_and_aliases

title: amd and aliases date: 2005-04-12 06:19:05

Weird problem yesterday when moving a server: for some reason, amd would not start up properly when it rebooted in its new location. Same network setttings, same chunk of network, so wtf?

ps showed that its terminal was con -- console, I presume -- which was doubly weird. I logged into another machine to make sure that was abnormal, and yes it was. amq -f gave the error program not registered, and sure enough rpcinfo -p showed the usual suspects sans amd.

Well, the only thing different about this machine is that it's got some jails running (which don't need to be running anymore, but I hadn't had a chance to shut them down). That meant some additional aliases for its outside interface in /etc/rc.conf on the subnet I set aside for this sort of thing. I commented them out, rebooted, and presto -- no more problems. Maybe something to do with picking which interface to listen on?