You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by paulhr <pa...@orthogroup.holdings> on 2016/05/13 21:33:12 UTC
tomee-plume.service: Failed at step USER spawning /opt/tomee
I am getting the following errors when trying to start tomee-plume as a
service using a tomee-plume.service file.
========================================================
Systemd unit file for tomee-plume
[Unit]
Description=Apache TomEE Plume
After=syslog.target network.target
[Service]
Type=forking
Environment=JAVA_HOME=/usr/lib/jvm/jre
Environment=CATALINA_PID=/opt/tomcat/temp/tomee-plume.pid
Environment=CATALINA_HOME=/opt/tomee-plume
Environment=CATALINA_BASE=/opt/tomee-plume
Environment='CATALINA_OPTS=-Xms512M -Xmx1024M -server -XX:+UseParallelGC'
Environment='JAVA_OPTS=-Djava.awt.headless=true
-Djava.security.egd=file:/dev/./urandom'
ExecStart=/opt/tomee-plume/bin/startup.sh
ExecStop=/opt/tomee-plume/bin/shutdown.sh
User=tomcat
Group=tomcat
[Install]
WantedBy=multi-user.target
========================================================
I also changed the user and group to "tomee-plume"
May 13 18:01:01 burrowingOwl.orthogroup.holdings CROND[10210]: (root) CMD
(run-parts /etc/cron.hourly)
May 13 18:01:01 burrowingOwl.orthogroup.holdings run-parts[10213]:
(/etc/cron.hourly) starting 0anacron
May 13 18:01:01 burrowingOwl.orthogroup.holdings run-parts[10219]:
(/etc/cron.hourly) finished 0anacron
May 13 18:01:01 burrowingOwl.orthogroup.holdings run-parts[10221]:
(/etc/cron.hourly) starting mcelog.cron
May 13 18:01:01 burrowingOwl.orthogroup.holdings run-parts[10225]:
(/etc/cron.hourly) finished mcelog.cron
May 13 18:01:05 burrowingOwl.orthogroup.holdings polkitd[1030]: Registered
Authentication Agent for unix-process:10226:275800
May 13 18:01:05 burrowingOwl.orthogroup.holdings systemd[10232]:
tomee-plume.service: Failed at step USER spawning /opt/tomee
-- Subject: Process /opt/tomee-plume/bin/startup.sh could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /opt/tomee-plume/bin/startup.sh could not be executed and
failed.
--
-- The error number returned by this process is 3.
May 13 18:01:05 burrowingOwl.orthogroup.holdings systemd[1]: Starting Apache
TomEE Plume...
-- Subject: Unit tomee-plume.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit tomee-plume.service has begun starting up.
May 13 18:01:05 burrowingOwl.orthogroup.holdings systemd[1]:
tomee-plume.service: Control process exited, code=exited status=
May 13 18:01:05 burrowingOwl.orthogroup.holdings systemd[1]: Failed to start
Apache TomEE Plume.
-- Subject: Unit tomee-plume.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit tomee-plume.service has failed.
--
-- The result is failed.
May 13 18:01:05 burrowingOwl.orthogroup.holdings systemd[1]:
tomee-plume.service: Unit entered failed state.
May 13 18:01:05 burrowingOwl.orthogroup.holdings audit[1]: SERVICE_START
pid=1 uid=0 auid=4294967295 ses=4294967295 subj=syst
May 13 18:01:05 burrowingOwl.orthogroup.holdings systemd[1]:
tomee-plume.service: Failed with result 'exit-code'.
May 13 18:01:05 burrowingOwl.orthogroup.holdings polkitd[1030]: Unregistered
Authentication Agent for unix-process:10226:2758
--
View this message in context: http://tomee-openejb.979440.n4.nabble.com/tomee-plume-service-Failed-at-step-USER-spawning-opt-tomee-tp4678431.html
Sent from the TomEE Users mailing list archive at Nabble.com.
Re: tomee-plume.service: Failed at step USER spawning /opt/tomee
Posted by Romain Manni-Bucau <rm...@gmail.com>.
What is in tomee logs?
Le 14 mai 2016 00:08, "paulhr" <pa...@orthogroup.holdings> a écrit :
> I am getting the following errors when trying to start tomee-plume as a
> service using a tomee-plume.service file.
>
> ========================================================
> Systemd unit file for tomee-plume
> [Unit]
> Description=Apache TomEE Plume
> After=syslog.target network.target
>
> [Service]
> Type=forking
>
> Environment=JAVA_HOME=/usr/lib/jvm/jre
> Environment=CATALINA_PID=/opt/tomcat/temp/tomee-plume.pid
> Environment=CATALINA_HOME=/opt/tomee-plume
> Environment=CATALINA_BASE=/opt/tomee-plume
> Environment='CATALINA_OPTS=-Xms512M -Xmx1024M -server -XX:+UseParallelGC'
> Environment='JAVA_OPTS=-Djava.awt.headless=true
> -Djava.security.egd=file:/dev/./urandom'
>
> ExecStart=/opt/tomee-plume/bin/startup.sh
> ExecStop=/opt/tomee-plume/bin/shutdown.sh
>
> User=tomcat
> Group=tomcat
>
> [Install]
> WantedBy=multi-user.target
>
> ========================================================
>
> I also changed the user and group to "tomee-plume"
>
> May 13 18:01:01 burrowingOwl.orthogroup.holdings CROND[10210]: (root) CMD
> (run-parts /etc/cron.hourly)
> May 13 18:01:01 burrowingOwl.orthogroup.holdings run-parts[10213]:
> (/etc/cron.hourly) starting 0anacron
> May 13 18:01:01 burrowingOwl.orthogroup.holdings run-parts[10219]:
> (/etc/cron.hourly) finished 0anacron
> May 13 18:01:01 burrowingOwl.orthogroup.holdings run-parts[10221]:
> (/etc/cron.hourly) starting mcelog.cron
> May 13 18:01:01 burrowingOwl.orthogroup.holdings run-parts[10225]:
> (/etc/cron.hourly) finished mcelog.cron
> May 13 18:01:05 burrowingOwl.orthogroup.holdings polkitd[1030]: Registered
> Authentication Agent for unix-process:10226:275800
> May 13 18:01:05 burrowingOwl.orthogroup.holdings systemd[10232]:
> tomee-plume.service: Failed at step USER spawning /opt/tomee
> -- Subject: Process /opt/tomee-plume/bin/startup.sh could not be executed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- The process /opt/tomee-plume/bin/startup.sh could not be executed and
> failed.
> --
> -- The error number returned by this process is 3.
> May 13 18:01:05 burrowingOwl.orthogroup.holdings systemd[1]: Starting
> Apache
> TomEE Plume...
> -- Subject: Unit tomee-plume.service has begun start-up
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit tomee-plume.service has begun starting up.
> May 13 18:01:05 burrowingOwl.orthogroup.holdings systemd[1]:
> tomee-plume.service: Control process exited, code=exited status=
> May 13 18:01:05 burrowingOwl.orthogroup.holdings systemd[1]: Failed to
> start
> Apache TomEE Plume.
> -- Subject: Unit tomee-plume.service has failed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit tomee-plume.service has failed.
> --
> -- The result is failed.
> May 13 18:01:05 burrowingOwl.orthogroup.holdings systemd[1]:
> tomee-plume.service: Unit entered failed state.
> May 13 18:01:05 burrowingOwl.orthogroup.holdings audit[1]: SERVICE_START
> pid=1 uid=0 auid=4294967295 ses=4294967295 subj=syst
> May 13 18:01:05 burrowingOwl.orthogroup.holdings systemd[1]:
> tomee-plume.service: Failed with result 'exit-code'.
> May 13 18:01:05 burrowingOwl.orthogroup.holdings polkitd[1030]:
> Unregistered
> Authentication Agent for unix-process:10226:2758
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/tomee-plume-service-Failed-at-step-USER-spawning-opt-tomee-tp4678431.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>