systemctl status Shibboleth
Lohr, Donald
lohrda at jmu.edu
Fri May 8 15:13:05 UTC 2020
1) On one IdP server "systemctl status Shibboleth" returns:
Shibboleth.service - Shibboleth Identity Provider
Loaded: loaded (/etc/systemd/system/Shibboleth.service; enabled;
vendor preset: disabled)
*Active: **active**(running) since Sun 2020-05-03 03:01:32 EDT; 5 days ago*
Main PID: 827 (java)
CGroup: /system.slice/Shibboleth.service
├─ 827 /usr/lib/jvm/*jdk-11.0.2*/bin/java
-Djetty.host=0.0.0.0 -Didp.home=/opt/shibboleth-idp
-Djava.io.tmpdir=/opt/jetty/shib-base/tmp -jar /opt/jetty/start.jar
jetty.home=/opt/jetty jetty.base=/opt...
└─1103 /usr/lib/jvm/*jdk-11.0.2*/bin/java -Xmx1500m
-XX:MaxPermSize=128m -Djava.io.tmpdir=tmp -Djetty.home=/opt/jetty
-Djetty.base=/opt/jetty/shib-base -Djava.io.tmpdir=tmp
-Didp.home=/opt/shibboleth...
The /java -version/ command on that server reports:
openjdk version "*11.0.2*" 2019-01-15
OpenJDK Runtime Environment 18.9 (build *11.0.2+9*)
OpenJDK 64-Bit Server VM 18.9 (build *11.0.2+9, **mixed mode*)
The /whereis java/ command on that server reports:
java: /usr/bin/java /usr/lib/java /etc/java /usr/share/java
/usr/lib/jvm/*jdk-11.0.2*/bin/java
2) On another IdP server "systemctl status Shibboleth" returns:
Shibboleth.service - Shibboleth Identity Provider
Loaded: loaded (/etc/systemd/system/Shibboleth.service; enabled;
vendor preset: disabled)
*Active: active (running) since Thu 2020-05-07 08:54:46 EDT; 1 day 1h ago*
Main PID: 1654 (java)
CGroup: /system.slice/Shibboleth.service
├─1654 /etc/alternatives/java -Djetty.host=0.0.0.0
-Didp.home=/opt/shibboleth-idp -Djava.io.tmpdir=/opt/jetty/shib-base/tmp
-jar /opt/jetty/start.jar jetty.home=/opt/jetty jetty.base=/opt/jetty/shi...
└─1761
/usr/lib/jvm/*java-11-openjdk-11.0.7.10-4.el7_8.x86_64*/bin/java
-Xmx1500m -XX:MaxPermSize=128m -Djava.io.tmpdir=tmp
-Djetty.home=/opt/jetty -Djetty.base=/opt/jetty/shib-base
-Djava.io.tmpdir=...
systemd[1]: *Shibboleth.service failed.*
systemd[1]: Started Shibboleth Identity Provider.
java[1654]: OpenJDK 64-Bit Server VM warning: Ignoring option
MaxPermSize; support was removed in 8.0
java[1654]: 2020-05-07 08:54:50.376:INFO::main: Logging initialized @993ms
java[1654]: 2020-05-07 08:54:51.041:INFO::main: Redirecting
stderr/stdout to
/opt/jetty-distribution-9.3.24.v20180605/shib-base/logs/2020_05_07.stderrout.log
java[1654]: WARNING: An illegal reflective access operation has occurred
java[1654]: WARNING: Illegal reflective access by
org.springframework.beans.BeanUtils
(file:/opt/jetty-distribution-9.3.24.v20180605/shib-base/tmp/jetty-0.0.0.0-80-i...
java[1654]: WARNING: Please consider reporting this to the maintainers
of org.springframework.beans.BeanUtils
java[1654]: WARNING: Use --illegal-access=warn to enable warnings of
further illegal reflective access operations
java[1654]: WARNING: All illegal access operations will be denied in a
future release
Hint: Some lines were ellipsized, use -l to show in full.
The /java -version/ command on that server reports:
openjdk version "*11.0.**7*" 2020-04-14 LTS
OpenJDK Runtime Environment 18.9 (build *11.0.7+10*-LTS)
OpenJDK 64-Bit Server VM 18.9 (build *11.0.7+10*-LTS, *mixed mode, sharing*)
The /whereis java/ command on that server reports:
java: /usr/bin/java /usr/lib/java /etc/java /usr/share/java
/usr/share/man/man1/java.1.gz
In my current role, I do not manage the server hardware, OS, or java
flavor/version. But am seeking help on the "systemd[1]:
*Shibboleth.service failed.*" Error.
Thanks again,
Don
--
D o n a l d L o h r
I n f o r m a t i o n S y s t e m s
J a m e s M a d i s o n U n i v e r s i t y
5 4 0 . 5 6 8 . 3 7 3 0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20200508/a31fb961/attachment.htm>
More information about the users
mailing list