DT Messaging can not start - head scratcher 1

[daneicher]

I had a working install. To my knowledge nothing changed.
I rebooted the server this morning and received a message DT Messaging system could not start.

It keeps pointing me to resolv.conf and hosts. Checked all of them out and played with them and have not been able to resolve the problem.

Althought, if I go in to smit mktcpip and just make two small changes, everything starts up fine.

These two changes are:
1. putting in a default gateway.
2. saying yes to start services.

Then I can logout and use the system fine until next reboot.

When the system reboots, the default gateway again is gone, and I get the DT Messaging error again.

Can someone point me down the right path?

Thanks,
Dan

 

[RodKnowlton]

You can manually set the gateway at startup in /etc/rc.net.

Find the "Traditional Configuration" section, and within that section you should find examples of setting static routes. Below these examples, add this:

/usr/sbin/route add default xx.xx.xx.xx >>$LOGFILE 2>&1

where xx.xx.xx.xx is the numeric IP address of your gateway.

Rod Knowlton
IBM Certified Advanced Technical Expert pSeries and AIX 5L

 

[daneicher]

Thanks, but the error message about DT Messaging was sending me down the wrong path. I beat on the problem from the statd -a angle. What I found was in smit I was entering information for a static tcp/ip setup (ip, netmask, gateway) - somehow dhcpcd was running. It looks like these were fighting. I went in to rc.tcpip and commented out dhcpcd and all is now happy.

Thanks for the information.
d.