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