Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-18009

Artifactory does not start as a service after running InstallService.sh on RedHat

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: 6.5.9
    • Fix Version/s: None
    • Component/s: startup
    • Labels:
    • Severity:
      Medium

      Description

      Artifactory does not start as a service after running InstallService.sh script on RedHat 7.5.

      It looks like you do not need to run InstallService.sh script when installing an RPM. Once the RPM installation of Artifactory is complete, you can easily start the instance by running service artifactory start command. The problem arises when a user is unaware of that, and runs the /opt/jfrog/artifactory/bin/installService.sh script unintentionally. After that, when running service artifactory start it fails fails with the following ERRORs:

      [root@ip-10-0-3-223 bin]# service artifactory start
      Redirecting to /bin/systemctl start artifactory.service
      Job for artifactory.service failed because a configured resource limit was exceeded. See "systemctl status artifactory.service" and "journalctl -xe" for details.
      .

      .

      [root@ip-10-0-3-223 ~]# systemctl status artifactory.service
      ● artifactory.service - Setup Systemd script for Artifactory in Tomcat Servlet Engine
         Loaded: loaded (/usr/lib/systemd/system/artifactory.service; enabled; vendor preset: disabled)
         Active: activating (auto-restart) (Result: resources) since Sat 2018-12-08 03:34:19 UTC; 789ms ago
        Process: 11805 ExecStart=/opt/jfrog/artifactory/bin/artifactoryManage.sh start (code=exited, status=0/SUCCESS)
       Main PID: 30831 (code=exited, status=0/SUCCESS)

      Dec 08 03:34:19 ip-10-0-3-223.us-west-2.compute.internal systemd[1]: Failed to start Setup Systemd script for Artifactory in Tomcat Servlet Engine.
      Dec 08 03:34:19 ip-10-0-3-223.us-west-2.compute.internal systemd[1]: Unit artifactory.service entered failed state.
      Dec 08 03:34:19 ip-10-0-3-223.us-west-2.compute.internal systemd[1]: artifactory.service failed.

      Also attached the screenshot of an ERROR.

      Steps to reproduce:

       

      1. Install RedHat 7.5
      2. Install Artifactory as RPM- yum install jfrog-artifactory-pro
      3. Once installed, run /opt/jfrog/artifactory/bin/installService.sh script
      4. It will notify you that the following directories are missing 
        1. /opt/jfrog/artifactory/etc/
        2. /opt/jfrog/artifactory/etc.original/
      5. Once you create those two directories, re-run /opt/jfrog/artifactory/bin/installService.sh script
      6. Try to start the instance as a service: service artifactory start

       

      The only workaround I am aware of is by re-installing the instance/node completely, and not running /opt/jfrog/artifactory/bin/installService.sh script.

      OR just start the instance using the /opt/jfrog/artifactory/bin/artifactory.sh.

       

        Attachments

          Activity

              People

              Assignee:
              Unassigned
              Reporter:
              timt Tim Telman (Inactive)
              Votes:
              11 Vote for this issue
              Watchers:
              19 Start watching this issue

                Dates

                Created:
                Updated:

                  Sync Status

                  Connection: RTFACT Sync
                  RTMID-18009 -
                  SYNCHRONIZED
                  • Last Sync Date: