Need Help with PID File Error while starting JBoss Service

1,014 views
Skip to first unread message

Sheldon Dsouza

unread,
Oct 11, 2021, 8:13:20 PM10/11/21
to WildFly
Hi,

We are using JBoss 7.1 and since could not find any support, sending email to this group.

Basically we downloaded and setup JBoss 7.1 some years back and it was working fine and even jboss service would start up fine.

As part of an unrelated activity, a Kernel upgrade was required on our AWS Cloud EC2 Server with OS: Red Hat Enterprise Linux (on which JBoss 7.1 was setup).

After the Kernel Upgrade, it was noticied that jboss service stopped running fine.
However, is the error seen via: systemctl status jboss.service

jboss.service - SYSV: JBoss AS Standalone
   Loaded: loaded (/etc/rc.d/init.d/jboss; bad; vendor preset: disabled)
   Active: failed (Result: protocol) since Thu 2021-09-30 13:47:47 EDT; 41min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 3648 ExecStart=/etc/rc.d/init.d/jboss start (code=exited, status=0/SUCCESS)

Sep 30 13:47:16 ip-10-50-0-16.ec2.internal su[3666]: (to jboss) root on none
Sep 30 13:47:47 ip-10-50-0-16.ec2.internal jboss[3648]: Starting jboss-as: [  OK  ]
Sep 30 13:47:47 ip-10-50-0-16.ec2.internal systemd[1]: New main PID 3733 does not belong to service, and PID file is not owned by root. Refusing.
Sep 30 13:47:47 ip-10-50-0-16.ec2.internal systemd[1]: New main PID 3733 does not belong to service, and PID file is not owned by root. Refusing.
Sep 30 13:47:47 ip-10-50-0-16.ec2.internal systemd[1]: Failed to start SYSV: JBoss AS Standalone.
Sep 30 13:47:47 ip-10-50-0-16.ec2.internal systemd[1]: Unit jboss.service entered failed state.
Sep 30 13:47:47 ip-10-50-0-16.ec2.internal systemd[1]: jboss.service failed.

-------------------

Please advise on how the error with PID file can be resolve.
Or if any queries.

Thanks,
Sheldon

Michael Douglass

unread,
Oct 11, 2021, 10:49:14 PM10/11/21
to wil...@googlegroups.com

Search (duckduckgo) for "PID file is not owned by root. Refusing.". There are a lot of hits including some suggested fixes

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/0aa400da-b5f3-42a6-9782-c438858dd8f0n%40googlegroups.com.

Tomaž Cerar

unread,
Oct 12, 2021, 3:32:19 AM10/12/21
to Sheldon Dsouza, WildFly
just delete the pid file and restart the service.

Reply all
Reply to author
Forward
0 new messages