[jira] [Created] (RANGER-1372) There are some errors when I used 'sudo ranger-usersync start' command to run the Ranger UserSync Process in ubuntu 16.04.

["Qiang Zhang (JIRA)" <ji...@apache.org>]

Qiang Zhang created RANGER-1372:
-----------------------------------

             Summary: There are some errors when I used 'sudo ranger-usersync start' command to run the Ranger UserSync Process in ubuntu 16.04.
                 Key: RANGER-1372
                 URL: https://issues.apache.org/jira/browse/RANGER-1372
             Project: Ranger
          Issue Type: Bug
          Components: usersync
    Affects Versions: 0.7.0
            Reporter: Qiang Zhang
            Assignee: Qiang Zhang


There are following errors when I used 'sudo ranger-usersync start' command to run the Ranger UserSync Process in ubuntu 16.04.
Starting Apache Ranger Usersync Service
/usr/bin/ranger-usersync: line 78: /var/run/ranger/usersync.pid: No such file or directory
chown: cannot access '/var/run/ranger/usersync.pid': No such file or directory
chmod: cannot access '/var/run/ranger/usersync.pid': No such file or directory
cat: /var/run/ranger/usersync.pid: No such file or directory
Apache Ranger Usersync Service with pid  has started.

Then the following error would occur when I run 'sudo ranger-usersync stop' command.
Apache Ranger Usersync Service not running

In fact the process was running.

The cause of the error is as follows:
/var/run/ranger directory does not exist when Apache Ranger Usersync Service started. The 'echo $VALUE_OF_PID > ${pidf}' failed. This problem will cause the following errors:
1. /usr/bin/ranger-usersync: line 78: /var/run/ranger/usersync.pid: No such file or directory
2. chown: cannot access '/var/run/ranger/usersync.pid': No such file or directory
3. chmod: cannot access '/var/run/ranger/usersync.pid': No such file or directory
4. cat: /var/run/ranger/usersync.pid: No such file or directory
5. Apache Ranger Usersync Service with pid  has started. The 'pid' has no value.
6. Apache Ranger Usersync Service not running. In fact the process was running.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)