Details

    • Type: Improvement
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Customer was experiencing issue with the systemd after upgrading to RHEL 7.7 in regards with the existing jira RTFACT-19850 and Customer proposed these changes to our implementation:

      1)Alias=artifactory.service[root@uls-ot-artifa3 logs]# cd /etc/systemd/system
      [root@uls-ot-artifa3 system]# ls -l
      total 4
      lrwxrwxrwx. 1 root root 43 Sep 20 13:13 artifactory.service -> /usr/lib/systemd/system/artifactory.service

      This symlink apparently deployed from your RPM is not required. The file in /etc is used to override the file in /usr/lib/systemd/system/ provided by the RPM. Linking them makes no sense and has no impact on the service state. It only makes it more confusing and difficult if somebody wants to override the default service file.

      2) /usr/lib/systemd/system/artifactory.service should not be executable, this causes warnings in the logs while starting.

      3) Your systemd unit seems to point to an old school sysv init script in /opt/jfrog/artifactory/bin/artifactoryManage.sh .
      This is really strange and seriously complicates debugging...
      I propose to replace all that and get some inspiration in other Tomcat applications, like for example Atlassian Jira, that works fine with RHEL 7.7...

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              divijak Divija Kandukoori
            • Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: