If I try to start the service I get:
Job for tomcat7.service failed because the control process exited with
error code.
See "systemctl status tomcat7.service" and "journalctl -xe" for details.
Then using systemctl status I get:
dspace@essays-deb8:~$ sudo systemctl status tomcat7.service
● tomcat7.service - LSB: Start Tomcat.
Loaded: loaded (/etc/init.d/tomcat7; generated)
Active: failed (Result: exit-code) since Fri 2020-09-18 08:32:52 CDT;
11s ago
Docs: man:systemd-sysv-generator(8)
Process: 14682 ExecStart=/etc/init.d/tomcat7 start (code=exited,
status=1/FAILURE)
Sep 18 08:32:46 essays-deb8 systemd[1]: Starting LSB: Start Tomcat....
Sep 18 08:32:52 essays-deb8 tomcat7[14682]: Starting Tomcat servlet engine:
tomcat7 failed!
Sep 18 08:32:52 essays-deb8 systemd[1]: tomcat7.service: Control process
exited, code=exited, status=1/FAILURE
Sep 18 08:32:52 essays-deb8 systemd[1]: tomcat7.service: Failed with result
'exit-code'.
Sep 18 08:32:52 essays-deb8 systemd[1]: Failed to start LSB: Start Tomcat..
dspace@essays-deb8:~$
dspace@essays-deb8:~$ sudo journalctl -xe
Sep 18 08:32:52 essays-deb8 systemd[1]: Failed to start LSB: Start Tomcat..
-- Subject: A start job for unit tomcat7.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit tomcat7.service has finished with a failure.
--
-- The job identifier is 1043 and the job result is failed.
Sep 18 08:32:52 essays-deb8 sudo[14678]: pam_unix(sudo:session): session
closed for user root
Sep 18 08:32:55 essays-deb8 sshd[14710]: pam_unix(sshd:auth):
authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rh
Sep 18 08:32:57 essays-deb8 sshd[14710]: Failed password for root from
75.51.34.205 port 46348 ssh2
Sep 18 08:32:58 essays-deb8 sshd[14710]: Received disconnect from
75.51.34.205 port 46348:11: Bye Bye [preauth]
Sep 18 08:32:58 essays-deb8 sshd[14710]: Disconnected from authenticating
user root 75.51.34.205 port 46348 [preauth]
Sep 18 08:33:03 essays-deb8 sudo[14712]: dspace : TTY=pts/0 ;
PWD=/home/dspace ; USER=root ; COMMAND=/bin/systemctl status
Sep 18 08:33:03 essays-deb8 sudo[14712]: pam_unix(sudo:session): session
opened for user root by dspace(uid=0)
Sep 18 08:33:03 essays-deb8 sudo[14712]: pam_unix(sudo:session): session
closed for user root
Sep 18 08:33:44 essays-deb8 sshd[14720]: pam_unix(sshd:auth):
authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rh
Sep 18 08:33:47 essays-deb8 sshd[14720]: Failed password for root from
103.89.176.74 port 43918 ssh2
Sep 18 08:34:57 essays-deb8 sshd[14732]: Invalid user fragocompta from
142.93.223.118 port 55282
Sep 18 08:34:57 essays-deb8 sshd[14732]: pam_unix(sshd:auth): check pass;
user unknown
Sep 18 08:34:57 essays-deb8 sshd[14732]: pam_unix(sshd:auth):
authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rh
Sep 18 08:34:59 essays-deb8 sshd[14732]: Failed password for invalid user
fragocompta from 142.93.223.118 port 55282 ssh2
Sep 18 08:35:01 essays-deb8 CRON[14739]: pam_unix(cron:session): session
opened for user root by (uid=0)
Sep 18 08:35:01 essays-deb8 CRON[14740]: (root) CMD (command -v debian-sa1
> /dev/null && debian-sa1 1 1)
Sep 18 08:35:01 essays-deb8 CRON[14739]: pam_unix(cron:session): session
closed for user root
Sep 18 08:35:12 essays-deb8 sshd[14742]: Invalid user info from
107.181.174.74 port 45706
Sep 18 08:35:12 essays-deb8 sshd[14742]: pam_unix(sshd:auth): check pass;
user unknown
Sep 18 08:35:12 essays-deb8 sshd[14742]: pam_unix(sshd:auth):
authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rh
Sep 18 08:35:14 essays-deb8 sshd[14742]: Failed password for invalid user
info from 107.181.174.74 port 45706 ssh2
Sep 18 08:35:14 essays-deb8 sshd[14742]: Received disconnect from
107.181.174.74 port 45706:11: Bye Bye [preauth]
Sep 18 08:35:14 essays-deb8 sshd[14742]: Disconnected from invalid user
info 107.181.174.74 port 45706 [preauth]
Sep 18 08:35:25 essays-deb8 sshd[14744]: pam_unix(sshd:auth):
authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rh
Sep 18 08:35:25 essays-deb8 sshd[14746]: pam_unix(sshd:auth):
authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rh
Sep 18 08:35:27 essays-deb8 sshd[14744]: Failed password for root from
104.214.25.194 port 48786 ssh2
Sep 18 08:35:28 essays-deb8 sshd[14746]: Failed password for root from
222.186.173.238 port 64688 ssh2
Sep 18 08:35:28 essays-deb8 sshd[14744]: Received disconnect from
104.214.25.194 port 48786:11: Bye Bye [preauth]
Sep 18 08:35:28 essays-deb8 sshd[14744]: Disconnected from authenticating
user root 104.214.25.194 port 48786 [preauth]
Sep 18 08:35:30 essays-deb8 sudo[14748]: dspace : TTY=pts/0 ;
PWD=/home/dspace ; USER=root ; COMMAND=/bin/journalctl -xe
Sep 18 08:35:30 essays-deb8 sudo[14748]: pam_unix(sudo:session): session
opened for user root by dspace(uid=0)
I cannot actually find the location for the Tomcat7 logs. Which leads me to
believe that an update/upgrade caused tomcat to be moved/deleted.
Jeff
On Fri, Sep 18, 2020 at 8:12 AM Mark H. Wood <[email protected]> wrote:
> On Thu, Sep 17, 2020 at 08:36:09AM -0700, Jeff Mitchell wrote:
> > I thought it was because of the apache issue from a couple months back
> but
> > I have since updated and still nothing. I cannot get Tomcat7 to start or
> > run either.
>
> That explains the 503. If Tomcat is not running, then your proxy
> setup cannot contact the thing that it is proxy for. Thus the service
> is unavailable.
>
> > Tomcat appears to be installed as when I try to install again
> > it says it is on the current version.
> >
> > I am running Debian 10.
> >
> > A kick in a direction to get this working would be awesome. I thought
> about
> > getting the DB and assetstore off the server and moving it to a new one
> but
> > wasn't sure if that would solve my issue or not.
>
> If Tomcat won't start, it should at least be leaving some clues in its
> log files. What do the logs say?
>
> --
> Mark H. Wood
> Lead Technology Analyst
>
> University Library
> Indiana University - Purdue University Indianapolis
> 755 W. Michigan Street
> Indianapolis, IN 46202
> 317-274-0749
> www.ulib.iupui.edu
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "DSpace Technical Support" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/dspace-tech/NBEsezGo5BI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/20200918130925.GA32280%40IUPUI.Edu
> .
>
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/CAKeosKcPw%3DjCo8uLX7pB3s7J_MTj%3D11yUXaeJsuiZUoqc3WNSg%40mail.gmail.com.
