Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

jmxtrans fail to start on CentOS/Fedora after a reboot

See original GitHub issue

After installing jmxtrans on CentOS or Fedora using RPM package and rebooting:

[root@fedora25 user]# /etc/init.d/jmxtrans start
Starting JmxTrans...
[root@fedora25 user]# /etc/init.d/jmxtrans status
JmxTrans is not running.

This is caused by the PID dir “/var/run/jmxtrans/” that does not exists because /var/run/ is a tmpfs filesystem which is not persisted across reboot. This is the case at least on CentOS 7 and Fedora 25.

It’s solved by creating the folder and changing ownership:

[root@fedora25 user]# mkdir /var/run/jmxtrans
[root@fedora25 user]# chown jmxtrans:jmxtrans /var/run/jmxtrans
[root@fedora25 user]# /etc/init.d/jmxtrans start
Starting JmxTrans...
[root@fedora25 user]# /etc/init.d/jmxtrans status
JmxTrans is running (2483).

Issue Analytics

State:
Created 6 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

bkrajmalnikcommented, Sep 27, 2017

My workaround was to modify the wrapper script. First, I changed the chkconfig line to start at 80. Then, under the definition of the PIDDIR, I added:

# create run dir for pid file
[ -d $PIDDIR ] || mkdir $PIDDIR
chown jmxtrans $PIDDIR

1reaction

gehelcommented, Jun 22, 2017

side note to this issue, we should move to systemd and let systemd handle do the watchdog, output parsing, etc and get rid of appassembler… this might be easier / nicer