perfSONAR User Q&A and Other Discussion

[Phil Reese <>]

    Hi Andy,
    
    You know me, I kept poking at this sore.  Think I found what the
    issue is:
    
    × maddash-server.service - MaDDash Scheduler and REST Server
         Loaded: loaded (/usr/lib/systemd/system/maddash-server.service;
    enabled; preset: disabled)
         Active: failed (Result: exit-code) since Thu 2023-10-26
    13:57:39 PDT; 6min ago
       Duration: 7ms
       Main PID: 5927 (code=exited, status=127)
            CPU: 19ms
    
    Oct 26 13:57:39 md-5 systemd[1]: Starting MaDDash Scheduler and REST
    Server...
    Oct 26 13:57:39 md-5 systemd[1]: Started MaDDash Scheduler and REST
    Server.
    Oct 26 13:57:39 md-5 systemd[1]: maddash-server.service: Main
    process exited, code=exited, status=127/n/a
    Oct 26 13:57:39 md-5 systemd[1]: maddash-server.service: Failed with
    result 'exit-code'.
    Oct 26 13:57:40 md-5 systemd[1]:
    /usr/lib/systemd/system/maddash-server.service:7: PIDFile=
    references a path below legacy directory /var/run/, updating
    /var/run/maddash/maddash-server.pid →
    /run/maddash/maddash-server.pid; please update the unit file
    accordingly.
    
    I wanted to see what was really wrong.  I brought up a Rock9 box,
    did all the pre steps and installed the MaDDash RPM.  I had a
    feeling it was the maddash-server not starting correctly and this
    confirms it.
    
    Take look as to why, when you have some time.
    
    Thanks,
    Phil

On 10/24/23 6:10 AM, Andrew Lake wrote:

">

I did multiple installs with SELinux enabled on Rocky 9 and it worked fine. One of the times I had a problem where MaDDash didn’t start because it couldn’t find java, but doing a “systemctl restart maddash-server” fixed things. I wonder if you ran into something like that unrelated to selinux. Maybe some strange install race condition on EL9 with java?