Avatar billede margitbork Nybegynder
19. februar 2009 - 09:26 Der er 5 kommentarer og
1 løsning

Fejl ved start af websphere service - cannot create another system semaphore

Jeg har en websphere application server, der kører som service på en windows server. Den har kørt i flere år. I denne weekend efter genstart af serveren, vil servicen ikke starte. Den svarer med denne fejl i event loggen:

The IBM WebSphere Application Server V5 - ProdServer service terminated with the following error:
Cannot create another system semaphore.

og denne

Could not determine the process id of the java process. Changing the IBMWAS5Service - ProdServer service status to the "stopped" state.  To prevent this error, try recreating this service with the -logRoot parameter.  The value of the logRoot parameter should be the directory in which the server's .pid file is created.

Hvad kan der være sket ? Hvordan får jeg den til at køre igen ?

Margit
Avatar billede margitbork Nybegynder
19. februar 2009 - 09:40 #1
Jeg fandt denne fejl i stopServer.log:

[17-02-09 06:52:55:422 CET] 75e063d9 ManagerAdmin  I TRAS0017I: The startup trace state is *=all=disabled.
[17-02-09 06:52:55:438 CET] 75e063d9 AdminTool    A ADMU3100I: Reading configuration for server: server1
[17-02-09 06:53:03:781 CET] 75e063d9 WsServerStop  E ADMU3002E: Exception attempting to process server server1
[17-02-09 06:53:03:781 CET] 75e063d9 WsServerStop  E ADMU3007E: Exception javax.management.JMRuntimeException: ADMN0022E: Access denied for the stop operation on Server MBean due to insufficient or empty credentials.
[17-02-09 06:53:03:953 CET] 75e063d9 WsServerStop  A ADMU3007E: Exception javax.management.JMRuntimeException: ADMN0022E: Access denied for the stop operation on Server MBean due to insufficient or empty credentials.
    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(SOAPConnectorClient.java:610)
    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:579)
    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:464)
    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:289)
    at $Proxy0.invoke(Unknown Source)
    at com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.java:162)
    at com.ibm.ws.management.tools.WsServerStop.sendWaitStop(WsServerStop.java:316)
    at com.ibm.ws.management.tools.WsServerStop.runTool(WsServerStop.java:213)
    at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:173)
    at com.ibm.ws.management.tools.WsServerStop.main(WsServerStop.java:86)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
    at java.lang.reflect.Method.invoke(Method.java:391)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:189)

[17-02-09 06:53:03:969 CET] 75e063d9 AdminTool    E ADMU0111E: Program exiting with error: javax.management.JMRuntimeException: ADMN0022E: Access denied for the stop operation on Server MBean due to insufficient or empty credentials.
    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(SOAPConnectorClient.java:610)
    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:579)
    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:464)
    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:289)
    at $Proxy0.invoke(Unknown Source)
    at com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.java:162)
    at com.ibm.ws.management.tools.WsServerStop.sendWaitStop(WsServerStop.java:316)
    at com.ibm.ws.management.tools.WsServerStop.runTool(WsServerStop.java:213)
    at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:173)
    at com.ibm.ws.management.tools.WsServerStop.main(WsServerStop.java:86)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
    at java.lang.reflect.Method.invoke(Method.java:391)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:189)

[17-02-09 06:53:03:969 CET] 75e063d9 AdminTool    A ADMU0111E: Program exiting with error: javax.management.JMRuntimeException: ADMN0022E: Access denied for the stop operation on Server MBean due to insufficient or empty credentials.
    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleAdminFault(SOAPConnectorClient.java:610)
    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeTemplate(SOAPConnectorClient.java:579)
    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:464)
    at com.ibm.ws.management.connector.soap.SOAPConnectorClient.invoke(SOAPConnectorClient.java:289)
    at $Proxy0.invoke(Unknown Source)
    at com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.java:162)
    at com.ibm.ws.management.tools.WsServerStop.sendWaitStop(WsServerStop.java:316)
    at com.ibm.ws.management.tools.WsServerStop.runTool(WsServerStop.java:213)
    at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:173)
    at com.ibm.ws.management.tools.WsServerStop.main(WsServerStop.java:86)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
    at java.lang.reflect.Method.invoke(Method.java:391)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:189)

[17-02-09 06:53:03:969 CET] 75e063d9 AdminTool    A ADMU4113E: Verify that user and password information is on the command line (-user and -password) or in the <conntype>.client.props file.
[17-02-09 06:53:03:969 CET] 75e063d9 AdminTool    A ADMU0211I: Error details may be seen in the file: D:\WebSphere\ProdServer\logs\server1\stopServer.log
[17-02-09 06:53:03:969 CET] 75e063d9 AdminTool    A ADMU1211I: To obtain a full trace of the failure, use the -trace

Så muligvis ligger der noget fra en fejlagtig stop af servicen, og låser for at jeg kan starte servicen igen.

Jeg håber der er noget der har en ide om hvad det kan være.
Avatar billede margitbork Nybegynder
19. februar 2009 - 09:41 #2
og startServer.log har disse linier:
[19-02-09 08:27:45:703 CET] 75c2077f ManagerAdmin  I TRAS0017I: The startup trace state is *=all=disabled.
[19-02-09 08:27:45:719 CET] 75c2077f AdminTool    A ADMU3100I: Reading configuration for server: server1
[19-02-09 08:27:46:469 CET] 75c2077f AdminTool    A ADMU3028I: Conflict detected on port 8880.  Likely causes: a) An instance of the server server1 is already running  b) some other process is using port 8880
[19-02-09 08:27:46:625 CET] 75c2077f AdminTool    A ADMU3027E: An instance of the server may already be running: server1
[19-02-09 08:27:46:625 CET] 75c2077f WsServerLaunc E ADMU3002E: Exception attempting to process server server1
[19-02-09 08:27:46:625 CET] 75c2077f WsServerLaunc E ADMU3007E: Exception com.ibm.websphere.management.exception.AdminException: ADMU3027E: An instance of the server may already be running: server1
    at com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.java:209)
    at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:173)
    at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:93)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
    at java.lang.reflect.Method.invoke(Method.java:391)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:189)
Avatar billede margitbork Nybegynder
19. februar 2009 - 09:45 #3
Den websphere server jeg har er:
IBM WebSphere Application Server, 5.1.1
Build Number: a0426.01
Build Date: 06/27/2004
Avatar billede margitbork Nybegynder
19. februar 2009 - 10:55 #4
Det ser umiddelbart ud til at processen er kørende, der er bare ingen kontakt med den, hverken fra services, task manager eller http serveren...
Avatar billede margitbork Nybegynder
19. februar 2009 - 10:55 #5
Men den låser log-filerne, og skriver også nogle fejllogs ind i mellem.
Avatar billede margitbork Nybegynder
19. februar 2009 - 13:03 #6
Hehe - der var en der havde været i gang med at skifte passwords i mandags, det var så skiftet tilbage, og han var taget på ferie...Nå men vi fik løst problemet.
Avatar billede Ny bruger Nybegynder

Din løsning...

Tilladte BB-code-tags: [b]fed[/b] [i]kursiv[/i] [u]understreget[/u] Web- og emailadresser omdannes automatisk til links. Der sættes "nofollow" på alle links.

Loading billede Opret Preview
Kategori
Uanset kodesprog, så giver vi dig mulighederne for at udvikle det, du behøver.

Log ind eller opret profil

Hov!

For at kunne deltage på Computerworld Eksperten skal du være logget ind.

Det er heldigvis nemt at oprette en bruger: Det tager to minutter og du kan vælge at bruge enten e-mail, Facebook eller Google som login.

Du kan også logge ind via nedenstående tjenester