install ims52.hf2.03 failed and start-admin hung
I am using iMS5.2 without patches.
I failed to install ims52.hf2.03:
I could not stop iMS using stop-msg. It hung and even could not be killed.
Then, I rebooted the whole server and ranperl imspatch.sh, imspatch.sh hung without any output when I chose:
Which of the above component(s) do you have installed [1]: 1
Next, I tried to start iMS. however, start-admin and start-msg hung.
Please help.
This is on a solaris 8 box.
Thanks.
[501 byte] By [
learner_xa] at [2007-11-26 8:16:14]
# 2
> It sounds like you have partially installed the
> patch
>
> Look in the installation directories for a patch
> backout option. do that.
>
> then try to install it again.
The problem is it looks like the patch is not installed at all, and there are no installation direcories for the patch.
And before I installed the patch, start-admin and start-msg already hung without any output or log for debugging.
So, I wonder what could be possible reasons for the hanging of start-admin and start-msg.
Thanks.
# 3
So, your mail server wouild not install BEFORE you tried patching?
What does patching have to do with your issue, then?
You may want to check:
1. The user that Messaging/admin run as. does the user exist, and does the user have a valid login, home directory, and such?
2. The user's uid number in unix. Was that changed?
3. The user's group. does that exist, and was it changed?
4. Is any of the Messaging on a NFS mount that's not there?
5. Is your LDAP server running and responsive?
# 4
> So, your mail server wouild not install BEFORE you
> tried patching?
Yes, start-msg and start-admin hang before I tried to install the patch.
> What does patching have to do with your issue, then?
Maybe the reason caused the failure of installation of the patch is same as that caused the above problem.
>
> You may want to check:
>
> 1. The user that Messaging/admin run as. does the
> user exist, and does the user have a valid login,
> home directory, and such?
yes.
> 2. The user's uid number in unix. Was that
> changed?
>
no.
> 3. The user's group. does that exist, and was it
> changed?
exist and not changed.
>
> 4. Is any of the Messaging on a NFS mount that's not
> there?
no.
>
> 5. Is your LDAP server running and responsive?
yes.
I have no clue where to start debug.
Thanks.
# 5
Since BOTH start-msg and start-admin fail, likely somehting changed on the only thing that they share. LDAP.
Could the admin password have been expired or changed?
you could use the system utility, "truss" to see what's failing:
truss -laef -vall -wall -o output.txt ./start-msg
and examine the output.txt for failures. This can be a large, somewhat confusing file, one that you may want to contact tech support to help you analyse.
