Detected 1 process that is running outdated executables (jumpcloud-agent)
I got this alarm in my WHM security advisor:

I already tried all provided instructions. So what I get:
- this is always jumpcloud-agent process
- after process restart alarm remains, but with new PID
- after server reboot alarm remains, with the same PID
This looks like some bug.
Maybe there are some fixes, I haven't found one, so I'll try my luck here
Additional info:
- server runs on AWS ubuntu 24.04
- I have a gut feeling that there were no such problems when I was running cPanel on Ubuntu 22.04
-
Hey there! That process is specific to Jumpcloud or AWS users, and isn't part of a default cPanel installation. However, if the same PID remains after a reboot happens, it may be something we need to look at.
Could you submit a ticket so this can be investigated on your machine?
0 -
At the moment I cannnot give ssh access to my machine.
For now I found a solutionto restart process and adding always restart to outdated process using:systemctl restart jcagent.service
/usr/local/cpanel/scripts/find_outdated_services --always-restartand I hope the alarm won't popup again when jumpcloud-agent do automatic update.
0 -
cPRex but the problem is back after host restart, now the PID changes after servise restart, but the alarm does not disapear((
0 -
It would seem that there are other issues with the Service Manager page on your particular system since you're also running into the issue mentioned here:
https://support.cpanel.net/hc/en-us/community/posts/39254828411799
At this point it would be best to create a ticket as I suspect there is one overarching problem with the machine instead of multiple small issues.
0 -
This problems did not occure while I was running Ubuntu 22.04 and started only after migration to 24.04
I assume that ptoblem with jumpcloud-agent alarm has simmilar root as the problem with kernel vertions:
https://support.cpanel.net/hc/en-us/community/posts/39254828411799/comments/39315561722391Setup was identical for ubuntu 22.04 before and there were no alarms like that.
0
Please sign in to leave a comment.
Comments
5 comments