Q. I upgraded InterMapper on a Linux box and now intermapperd won't start. What troubleshooting steps can I take?
A. The following steps will help Dartware engineers:
1. Ensure there are no log files in the /var/local/InterMapper_Settings/InterMapper_Logs folder that are greater than 2 GB in size. Log files greater than 2 GB can prevent the intermapperd from starting.
2. Check for the presence of a lock file:
#service intermapperd status". If you see the message "intermapperd dead but subsys locked, delete the /var/lock/subsys/intermapperd file.
3. Check in /var/log/messages for intermapper-related messages:
# grep intermapperd /var/log/messages
4. Make sure the InterMapper server is stopped:
# /etc/init.d/intermapperd stop
5. Run InterMapper in debug mode:
# /usr/local/bin/intermapperd -d -f /usr/local/etc/intermapperd.conf 2>&1 | tee -a InterMapper_Debug.txt
(That's all one line.)
This should run a number of self-tests and then start the InterMapper server, sending the logging to both the screen and the file InterMapper_Debug.txt. If the prompt ever comes back, that's the sign of a crash, and we'd like to see the contents of the InterMapper_Debug.txt file.
