Support Tip: Access Manager Console and IDP servers installed on SLES

0 Likes

Access Manager Console and IDP servers installed on SLES fail to run logrotate

Error: Ignoring novell-ac because of bad file mode - must be 0644 or 0444. <br>

Error: Ignoring novell-devman because of bad file mode - must be 0644 or 0444 <br>

Error: skipping [logfilename] because parent directory has insecure permissions

Environment

  • Access Manager 4.5.4
  • Access Manager 5.0
  • Access Manager 5.0.1

Situation: logrotate fails to run based on two different permission problems

  1. Error: "bad file mode - must be 0644 or 0444"

    - Unit logrotate.service has begun starting up.
    Sep 09 11:55:45 login logrotate[12983]: error: Ignoring novell-ac because of bad file mode - must be 0644 or 0444.
    Sep 09 11:55:45 login logrotate[12983]: error: Ignoring novell-devman because of bad file mode - must be 0644 or 0444.
    Sep 09 11:55:45 login logrotate[12983]: error: skipping "/var/opt/novell/tomcat9/logs/host-manager.2021-09-09.log" because p>
    Sep 09 11:55:45 login logrotate[12983]: error: skipping "/var/opt/novell/tomcat9/logs/localhost.2021-09-09.log" because pare>
    Sep 09 11:55:45 login logrotate[12983]: error: skipping "/var/opt/novell/tomcat9/logs/manager.2021-09-09.log" because parent>
    Sep 09 11:55:45 login logrotate[12983]: error: skipping "/var/opt/novell/tomcat9/logs/catalina.out" because parent directory>
    Sep 09 11:55:45 login systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
    Sep 09 11:55:45 login systemd[1]: Failed to start Rotate log files.
    -- Subject: Unit logrotate.service has failed
    -- Defined-By: systemd
    -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit logrotate.service has failed.
    --
    -- The result is failed.
    Sep 09 11:55:45 login systemd[1]: logrotate.service: Unit entered failed state.
    Sep 09 11:55:45 login systemd[1]: logrotate.service: Failed with result 'exit-code'.
     
  2. Error: "parent directory has insecure permissions"

    -- Unit logrotate.service has begun starting up.
    Sep 09 12:06:44 login logrotate[13774]: error: skipping "/var/opt/novell/tomcat9/logs/host-manager.2021-09-09.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrot>
    Sep 09 12:06:44 login logrotate[13774]: error: skipping "/var/opt/novell/tomcat9/logs/localhost.2021-09-09.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate>
    Sep 09 12:06:44 login logrotate[13774]: error: skipping "/var/opt/novell/tomcat9/logs/manager.2021-09-09.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate w>
    Sep 09 12:06:44 login logrotate[13774]: error: skipping "/var/opt/novell/tomcat9/logs/catalina.out" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/>
    Sep 09 12:06:44 login systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
    Sep 09 12:06:44 login systemd[1]: Failed to start Rotate log files.
    -- Subject: Unit logrotate.service has failed
    -- Defined-By: systemd
    -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit logrotate.service has failed.

Resolution

Change the following file permissions to solve the above listed problems
  1. "chmod 0644 /etc/logrotate.d/novell-*will fix one part of the problem"
  2. "chmod 754 /var/opt/novell/tomcat9/logs"

Find support article here: https://portal.microfocus.com/s/article/KM000001842?language=en_US

Labels:

Support Tip
Comment List
Anonymous
Related Discussions
Recommended