Steve Benoit wrote: > One of my techs is attempting to install a new copy of Intermapper server and > move our maps from the old server to the new server. He is having problems > which he describes below: > [...] > Oct 11 14:37:29 bainterm01 intermapperd[26354]: ASSERT#UNIX#5.0.4#itsFiledes > != > kInvalidFileDescriptor#XFileHandle_Unix.cpp#219#Linux/2.6.18-92.1.13.el5#Ex55#As2# > Oct 11 14:37:34 bainterm01 intermapperd[26354]: ExitProcess with status 1. > XBugReport > Oct 11 14:37:34 bainterm01 relaunch: [4554] '/usr/local/bin/intermapperd -f > /usr/local/etc/intermapperd.conf --no-daemonize' exited with status 1. > Relaunch in 10 seconds... > Oct 11 14:37:44 bainterm01 intermapperd[26424]: InterMapper daemon started. > (euid=intermapper[100], egid=root[0]) > Oct 11 14:37:50 bainterm01 intermapperd[26424]: InterMapper daemon ready."
> > Does anyone have any suggestions I can pass along to him ? Just for context, these are the messages that appear in your /var/log/messages or /var/log/syslog file on Unix-like systems when InterMapper encounters an assertion. Note that InterMapper only records start and stop messages using the Unix syslog facility. There is a lot of more detail in InterMapper's own debug log, including the stack trace where the ASSERT occurred. Please have your tech locate the log lines surrounding the 10/11 14:37 event in his InterMapper debug log and email them to [EMAIL PROTECTED] This log is located at /var/local/InterMapper_Settings/InterMapper Logs. Thanks, Bill Fisher Dartware, LLC ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED]
