This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

FILR fails to start since Feb. 14 2023

Hello,

I did no update or something else, since two days my FILR 5 tells me "service unavailable".

First I took a look to hdd-space, but it seems ok (/var/ uses 39% the rest 16 % or less).

running rcfilr start shows:

Job for filr.service failed because the control process exited with error code.

jounalctl shows:

Subject: A start job for unit filr.service has begun execution
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: lists.freedesktop.org/.../systemd-devel
â–‘â–‘
â–‘â–‘ A start job for unit filr.service has begun execution.
â–‘â–‘
â–‘â–‘ The job identifier is 6604.
Feb 17 09:10:26 FALFILR filr[9677]: cat: /filrinstall/configurationDetails.properties: Permission denied
Feb 17 09:10:26 FALFILR filr[9687]: touch: cannot touch '/opt/novell/filr/apache-tomcat/logs/catalina.out': Permission denied
Feb 17 09:10:26 FALFILR filr[9681]: /opt/novell/filr/apache-tomcat/bin/catalina.sh: line 526: /opt/novell/filr/apache-tomcat/logs/catalina.out: Permission denied
Feb 17 09:10:26 FALFILR systemd[1]: filr.service: Control process exited, code=exited, status=1/FAILURE
â–‘â–‘ Subject: Unit process exited
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: lists.freedesktop.org/.../systemd-devel
â–‘â–‘
â–‘â–‘ An ExecStart= process belonging to unit filr.service has exited.
â–‘â–‘
â–‘â–‘ The process' exit code is 'exited' and its exit status is 1.
Feb 17 09:10:26 FALFILR systemd[1]: filr.service: Failed with result 'exit-code'.
â–‘â–‘ Subject: Unit failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: lists.freedesktop.org/.../systemd-devel
â–‘â–‘
â–‘â–‘ The unit filr.service has entered the 'failed' state with result 'exit-code'.
Feb 17 09:10:26 FALFILR systemd[1]: Failed to start Micro Focus Filr Service.
â–‘â–‘ Subject: A start job for unit filr.service has failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: lists.freedesktop.org/.../systemd-devel
â–‘â–‘
â–‘â–‘ A start job for unit filr.service has finished with a failure.
â–‘â–‘
â–‘â–‘ The job identifier is 6604 and the job result is failed.

I don't know, where the permission error will come from, nothing should have been changed in the last weeks.

The system is down, can anybody help me?

Holger

  • Verified Answer

    +1

    Ok,
    I could solve the problem, but it's much scary because I don't know, where it came from:

    I tried "zypper up" in hope of refreshing the part of the system that was broken.
    It answered with a failure "unable to get local issuer certificate".

    So i tried
    https://www.suse.com/support/kb/doc/?id=000018620
    to repair the missing hardlink at "/etc/pki/trust/anchors" (indeed, it was disappeared!) with
    ln -s /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT.pem
    In the last step "suse" told me to run "update-ca-certificates", but it came with errors "couldnt create file" and "error 2".

    Next step I've found, that
    /var/lib/ca-certificates
    didn't exist (where did it gone???) and created it new with
    mkdir /var/lib/ca-certificates

    Now zypper up worked fine and after applying 320 Updates and reboot, my FILR 5 works!


    Ok, this thread seems to be solved by myself, but the question remains, if there is an problem in FILR itself that caused this sh**.


    Holger

  • 0   in reply to 

    I just set off to reply (but not really to deliver this solution). Just some questions.

    Perfect you solved it and shared it to us!


    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to 

    Same issue(! identical messages) here (Small deployment) we solved this by restore the backup from the evening before.

    Before I state that there were were some trouble with symbolic links ...