Error occurring: 500 Internal server error

[Peter Schober]

* Tomomi <test.demo.adobe.2 at gmail.com> [2019-07-23 10:01]:
> tomcat log is below;

So when you wrote before that you don't have any logs at all...

* Tomomi <test.demo.adobe.2 at gmail.com> [2019-07-18 03:35]:
> There is no log at all.
> /opt/shibboleth-idp/logs
> /usr/share/tomcat/logs

... you meant that there are no logs from the IDP application, not
that you don't even have tomcat logs? Well, the logs from the
Shibboleth IDP application will not go to Tomcat's logs so all the
above says is that you don't have your IDP's logs, I guess.

There are infinite ways of having a non-working setup so there's not
much left other than you telling us how exactly you installalled and
configured Tomcat.

E.g. you said the command "wget -O - http://localhost/idp/status" worked.
So how did you configure Tomcat to bind to port 80? By default (I just
checked) Tomcat7 -- CentOS 7 only has Tomcat7 -- runs as user Tomcat
and binds to port 8080 without anything in place that would allow it
to bind to port 80. So does the IDP run as user root or as user tomcat
(for the latter case you'd have to have used some other technique to
allow it to bind to that port).

And whom do the files in the IDP installation directory
(/opt/shibboleth-idp by default) belong to (including conf, metadata
and logs)? root? tomcat?

What instructions were you following to install the IDP? Do Tomcat's
logs show that the idp context was deployed correctly?

$ journalctl -u tomcat.service | grep 'Deployment of configuration descriptor .* has finished'

Any errors in Tomcat's catalina and localhost (default) logs?

$ fgrep SEVERE /var/log/tomcat/*.log


> The web application [/idp] appears to have started a thread named
> [AsyncAppender-Worker-ASYNC_PROCESS] but has
> failed to stop it. This is very likely to create a memory leak.
> One or more listeners failed to start. Full details will be found in the
> appropriate container log file
> 
> Do you have any reason for the error.

That line start with "WARNING", so it's a warning, not an error.
Ignore that.

-peter