Problem to start Tomcat 9.

Ranch Hand

Posts: 675

posted 9 months ago

Number of slices to send:

Optional 'thank-you' note:

Send

Hi, I've installed Tomcat 9 in my Centos 8, after created tomcat.service I getting error when start.
tomcat.service:

systemctl start tomcat:

See "systemctl status tomcat.service" and "journalctl -xe" for details.
[root@vps48786 ~]# journalctl -xe
--
-- Unit setroubleshootd.service has begun starting up.
Aug 19 11:48:04 vps48786.publiccloud.com.br dbus-daemon[630]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd'
Aug 19 11:48:04 vps48786.publiccloud.com.br systemd[1]: Started SETroubleshoot daemon for processing new SELinux denial logs.
-- Subject: Unit setroubleshootd.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit setroubleshootd.service has finished starting up.
--
-- The start-up result is done.
Aug 19 11:48:06 vps48786.publiccloud.com.br setroubleshoot[7174]: AnalyzeThread.run(): Cancel pending alarm
Aug 19 11:48:06 vps48786.publiccloud.com.br dbus-daemon[630]: [system] Activating service name='org.fedoraproject.SetroubleshootPrivileged' requested by ':1.528' (uid=995 pid=7174 comm="/u>
Aug 19 11:48:07 vps48786.publiccloud.com.br dbus-daemon[630]: [system] Successfully activated service 'org.fedoraproject.SetroubleshootPrivileged'
Aug 19 11:48:08 vps48786.publiccloud.com.br setroubleshoot[7174]: SELinux is preventing /usr/lib/systemd/systemd from execute access on the file startup.sh. For complete SELinux messages r>
Aug 19 11:48:08 vps48786.publiccloud.com.br setroubleshoot[7174]: SELinux is preventing /usr/lib/systemd/systemd from execute access on the file startup.sh.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that systemd should be allowed execute access on the startup.sh file by default.
                                                                  Then you should report this as a bug.
                                                                  You can generate a local policy module to allow this access.
                                                                  Do
                                                                  allow this access for now by executing:
                                                                  # ausearch -c '(artup.sh)' --raw | audit2allow -M my-artupsh
                                                                  # semodule -X 300 -i my-artupsh.pp

Aug 19 11:48:08 vps48786.publiccloud.com.br setroubleshoot[7174]: AnalyzeThread.run(): Set alarm timeout to 10
Aug 19 11:48:19 vps48786.publiccloud.com.br systemd[1]: setroubleshootd.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit setroubleshootd.service has successfully entered the 'dead' state.
Aug 19 11:48:24 vps48786.publiccloud.com.br sshd[7192]: error: Unable to load host key: /etc/ssh/ssh_host_ecdsa_key
Aug 19 11:48:24 vps48786.publiccloud.com.br sshd[7192]: error: Unable to load host key: /etc/ssh/ssh_host_ed25519_key

I appreciate any help to solve this problem because I don't have a minimum idea that I resolve this.
Thanks and best regards.

Tim Holloway

Saloon Keeper

Posts: 27851

196

I like...

posted 9 months ago

Number of slices to send:

Optional 'thank-you' note:

Send

Quick fix:

This will turn off selinux enforcing. I am sorry to say that selinux can be major pain for most users.

It is possible to set up rules to allow selinux to work with Tomcat in enforcing mode, but they're more trouble than they are worth for you.

The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.

You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.

Cezar Apulchro

Ranch Hand

Posts: 675

posted 8 months ago

Number of slices to send:

Optional 'thank-you' note:

Send

Very very good, Tomcat is working fine.
Thanks and best regards.

With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.