Fresh Installed Shibboleth IdP 3 Is Not Able to Run Successfully

calvin.a calvin.a at wph.com.sg
Sun Nov 18 22:25:31 EST 2018


Hello Shibboleth Users,

I have installed of Shibboleth IdP 3 to my windows server, by following the
guide:
https://wiki.shibboleth.net/confluence/display/IDP30/WindowsInstallation

It is a vanilla installation, with Jetty also following the embedded Jetty
from Shibboleth.

When I start Shibboleth via Windows Services list, after a short while,
Shibboleth is down.
Commons Daemon log showed that service was managed to start successfully.

[2018-11-16 17:47:29] [debug] ( prunsrv.c:1729) [ 3340] Commons Daemon
procrun log initialized
[2018-11-16 17:47:29] [info]  ( prunsrv.c:1733) [ 3340] Commons Daemon
procrun (1.1.0.0 64-bit) started
[2018-11-16 17:47:29] [info]  ( prunsrv.c:1643) [ 3340] Running 'shibd_idp'
Service...
[2018-11-16 17:47:29] [debug] ( prunsrv.c:1417) [ 9252] Inside
ServiceMain...
[2018-11-16 17:47:29] [debug] ( prunsrv.c:885 ) [ 9252]
reportServiceStatusE: dwCurrentState = 2, dwWin32ExitCode = 0, dwWaitHint =
3000, dwServiceSpecificExitCode = 0
[2018-11-16 17:47:29] [info]  ( prunsrv.c:1175) [ 9252] Starting service...
[2018-11-16 17:47:29] [debug] ( javajni.c:236 ) [ 9252] loading jvm
'C:\Program Files\Java\jdk1.8.0_181\jre\bin\server\jvm.dll'
[2018-11-16 17:47:29] [debug] ( javajni.c:753 ) [ 9244] Jvm Option[0]
-Didp.home=C:/Program Files (x86)/Shibboleth/IdP
[2018-11-16 17:47:29] [debug] ( javajni.c:753 ) [ 9244] Jvm Option[1]
-Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.Slf4jLog
[2018-11-16 17:47:29] [debug] ( javajni.c:753 ) [ 9244] Jvm Option[2]
-Djava.io.tmpdir=C:/Program Files (x86)/Shibboleth/IdP/jetty-base/tmp
[2018-11-16 17:47:29] [debug] ( javajni.c:753 ) [ 9244] Jvm Option[3]
-XX:+UseG1GC
[2018-11-16 17:47:29] [debug] ( javajni.c:753 ) [ 9244] Jvm Option[4]
-Djava.class.path=C:\Program Files (x86)\Shibboleth\Jetty\\start.jar
[2018-11-16 17:47:29] [debug] ( javajni.c:753 ) [ 9244] Jvm Option[5] exit
[2018-11-16 17:47:29] [debug] ( javajni.c:753 ) [ 9244] Jvm Option[6] abort
[2018-11-16 17:47:29] [debug] ( javajni.c:753 ) [ 9244] Jvm Option[7]
-Xms256m
[2018-11-16 17:47:29] [debug] ( javajni.c:753 ) [ 9244] Jvm Option[8]
-Xmx2048m
[2018-11-16 17:47:29] [debug] ( javajni.c:937 ) [ 9244] argv[0] =
jetty.base=C:\Program Files (x86)\Shibboleth\IdP\\jetty-base
[2018-11-16 17:47:29] [debug] ( javajni.c:937 ) [ 9244] argv[1] =
jetty.logging.dir=C:\Program Files (x86)\Shibboleth\IdP\\jetty-base\logs
[2018-11-16 17:47:29] [debug] ( javajni.c:937 ) [ 9244] argv[2] =
STOP.PORT=8963
[2018-11-16 17:47:29] [debug] ( javajni.c:937 ) [ 9244] argv[3] =
STOP.Key={331CF121-F372-4362-93D4-DE159616B383}
[2018-11-16 17:47:29] [debug] ( javajni.c:990 ) [ 9244] Java Worker thread
started org/eclipse/jetty/start/Main:main
[2018-11-16 17:47:30] [debug] ( prunsrv.c:1235) [ 9252] Java started
org/eclipse/jetty/start/Main
[2018-11-16 17:47:30] [info]  ( prunsrv.c:1333) [ 9252] Service started in
1300 ms.
[2018-11-16 17:47:30] [debug] ( prunsrv.c:885 ) [ 9252]
reportServiceStatusE: dwCurrentState = 4, dwWin32ExitCode = 0, dwWaitHint =
0, dwServiceSpecificExitCode = 0
[2018-11-16 17:47:30] [debug] ( prunsrv.c:1572) [ 9252] Waiting for worker
to finish...
[2018-11-16 17:47:55] [debug] ( javajni.c:504 ) [ 9852] Exit hook with exit
code -2
[2018-11-16 17:47:55] [debug] ( prunsrv.c:960 ) [ 9852] Start exit hook
called ...
[2018-11-16 17:47:55] [debug] ( prunsrv.c:961 ) [ 9852] VM exit code: -2


I installed in Windows Server 2016, using Java 1.8
"JAVA_HOME" variable is set to C:\Program Files\Java\jdk1.8.0_181


Are there any misconfigurations or settings that I have not performed? Or
are there faulty in the installed Java / JVM in my server?
Thank you.

Regards,
Calvin



--
Sent from: http://shibboleth.1660669.n2.nabble.com/Shibboleth-Users-f1660767.html


More information about the users mailing list