Error in Stop/Start Server
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 278
- Joined: Wed Oct 03, 2007 8:45 am
It looks like the message you included in your question provides a reason the server would not stop =>
Access is denied for the stop operation on Server MBean because of insufficient or empty credentials.
ADMU4113E: Verify that username and password information is on the command line (-username and -password) or in the <conntype>.client.props file.
-
- Participant
- Posts: 176
- Joined: Wed Nov 15, 2006 5:48 am
Well, to stop the server we always use the command stopServer.sh without indicated the user and password.sjfearnside wrote:It looks like the message you included in your question provides a reason the server would not stop =>
Access is denied for the stop operation on Server MBean because of insufficient or empty credentials.
ADMU4113E: Verify that username and password information is on the command line (-username and -password) or in the <conntype>.client.props file.
Why now is different ?
Question : we didn't stop the repository, This could be same process that are working in the repository and so it's not possible to stop the server ?
Thanks for all help
Rai
-
- Premium Member
- Posts: 278
- Joined: Wed Oct 03, 2007 8:45 am
-
- Premium Member
- Posts: 278
- Joined: Wed Oct 03, 2007 8:45 am
Here is some information I have collected but not used. I provide it for your reference in hopes that you may find it helpful.
Also, I have instructions from a vendor support person that you can reboot the server to clear the port.Use "ipcrm -m" to get rid of those two entries. FIN_WAIT and CLOSE_WAIT status on Solaris are set to timeout after a given period of time, use "ndd -get /dev/tcp tcp_time_wait_interval" to get the timed wait interval and "ndd -get /dev/tcp tcp_fin_wait_2_flush_interval" to get the FIN_WAIT2 (and the CLOSE_WAIT, I think). These values are in milliseconds, but it can be a long wait.
-
- Premium Member
- Posts: 892
- Joined: Thu Oct 16, 2003 5:18 am
-
- Participant
- Posts: 176
- Joined: Wed Nov 15, 2006 5:48 am
-
- Premium Member
- Posts: 278
- Joined: Wed Oct 03, 2007 8:45 am
Can you clarify the statement =>
Are the other applications running when you are trying to stop WAS?
Are the other applications using/interacting with WAS?
Are you saying this is a virtualized server or something else like MQ services are also running on the server?Since we have many other aplicantions in the same machine, it will be a hard work to shutdown the machine.
Are the other applications running when you are trying to stop WAS?
Are the other applications using/interacting with WAS?
-
- Participant
- Posts: 176
- Joined: Wed Nov 15, 2006 5:48 am
Are you saying this is a virtualized server or something else like MQ services are also running on the server?
NO
Are the other applications running when you are trying to stop WAS?
YES
Are the other applications using/interacting with WAS?
NO
The other application are ORACLE and other project that dosen't have DataStage jobs (only pl/sql)
merci
Rai
NO
Are the other applications running when you are trying to stop WAS?
YES
Are the other applications using/interacting with WAS?
NO
The other application are ORACLE and other project that dosen't have DataStage jobs (only pl/sql)
merci
Rai
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 176
- Joined: Wed Nov 15, 2006 5:48 am
-
- Premium Member
- Posts: 278
- Joined: Wed Oct 03, 2007 8:45 am
-
- Participant
- Posts: 176
- Joined: Wed Nov 15, 2006 5:48 am
-
- Participant
- Posts: 176
- Joined: Wed Nov 15, 2006 5:48 am
-
- Participant
- Posts: 47
- Joined: Mon May 07, 2007 10:35 pm
Re: The LoggingAgent.sh process stopped unexpectedly
Hi,
I'm also facing the same issue, while restarting the services. I am unable to start Loggignagent.sh .. It gives me the same error message.
quick response would be highly appreciated.
I'm also facing the same issue, while restarting the services. I am unable to start Loggignagent.sh .. It gives me the same error message.
quick response would be highly appreciated.
FD