Re: systemd service fails to start rhel7.8

[Tomasz Torcz <tomek@xxxxxxxxxxxxxx>]

On Tue, May 05, 2020 at 08:48:17AM +0000, Aviram, Nimrod wrote:
> After upgrading OS to RHEL 7.8 , the service fails to start.
> I'm usually creating a basic user (cfrm) to run Catalina but I've also tried with root and received the same exception.
> 
> [Unit]
> Description=cfrmic
> [Service]
> User=cfrm
> Environment=JAVA_HOME=$JAVA_HOME

  This line is weird.

> PIDFile=/opt/ic/Appserver/logs/tomcat.pid
> WorkingDirectory=/opt/ic
> Type=forking
> ExecStart=/opt/ic/manager.sh start
> ExecStop=/opt/ic/manager.sh stop
> TimeoutStartSec=60
> TimeoutStopSec=180
> 
> [Install]
> WantedBy=multi-user.target
> 
> 
> 
> Journalctl -xe -->
> 
> May 05 04:45:13 US02VLAPP8519 systemd[1]: Starting cfrmic...
> -- Subject: Unit cfrmic.service has begun start-up
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit cfrmic.service has begun starting up.
> May 05 04:45:13 US02VLAPP8519 su[2249]: pam_unix(su-l:auth): auth could not identify password for [cfrm]
> May 05 04:45:13 US02VLAPP8519 su[2249]: pam_sss(su-l:auth): authentication failure; logname= uid=1001 euid=0 tty= ruser=cfrm rhost= user=cfrm
> May 05 04:45:13 US02VLAPP8519 su[2249]: pam_sss(su-l:auth): received for user cfrm: 10 (User not known to the underlying authentication module)


  Clearly user cfrm does not exists from PAM point of view. That's the
problem.
  I also doubt you have the same problem when running as root. Maybe you
didn't do 'systectl daemon-reload' after changing the unit file?


-- 
Tomasz Torcz                        Once you've read the dictionary,
tomek@xxxxxxxxxxxxxx                every other book is just a remix.
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel