Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Cloudera Community

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Who agreed with this topic

Permissions on /var/lib/<directory> causing services to fail.

avatar
author-rank Ranjandas
Explorer

Created on ‎01-20-2017 08:29 PM - edited ‎09-16-2022 03:55 AM

I am setting up a CDH (5.8) Cluster with Cloudera Manager and Parcels. Most of the services are installed and running fine with an exception of HDFS HTTPFS role and Oozie. I am using a custom parcel directory on the agents  and also I am running SELinux in Enforcing mode (Please dont ask me to put it to permissive 🙂 ).

 

Both has similar isssue where its trying to move some files (related to tomcat) from the parcel's directory to /var/lib/<directory>.

 

When I checked the permissions of the directories in /var/lib I could see that most of the directories are created without any permissions set on them.

 

 

$ ls -l /var/lib/ | grep ^d-
d---------.  2 root         root            6 Jan 13 00:28 flume-ng
d---------.  2 root         root            6 Jan 13 00:28 hadoop-hdfs
d---------.  2 root         root            6 Jan 13 00:28 hadoop-httpfs
d---------.  2 root         root            6 Jan 13 00:28 hadoop-kms
d---------.  2 root         root            6 Jan 13 00:28 hadoop-mapreduce
d---------.  2 root         root            6 Jan 13 00:28 hadoop-yarn
d---------.  2 root         root            6 Jan 13 00:28 hbase
d---------.  2 root         root            6 Jan 13 00:28 hive
d---------.  2 root         root            6 Jan 13 00:28 impala
d---------.  2 root         root            6 Jan 13 00:29 kafka
d---------.  2 root         root            6 Jan 13 00:28 llama
d---------.  2 root         root            6 Jan 13 00:28 oozie
d---------.  2 root         root            6 Jan 13 00:28 sentry
d---------.  2 root         root            6 Jan 13 00:28 solr
d---------.  2 root         root            6 Jan 13 00:28 spark
d---------.  2 root         root            6 Jan 13 00:28 sqoop
d---------.  2 root         root            6 Jan 13 00:28 sqoop2
d---------.  2 root         root            6 Jan 13 00:28 zookeeper

 

 

Is this expected?

 

For Oozie, I changed the permission of /var/lib/oozie to 700 and changed the ownership to oozie:oozie fixed the issue.

 

What would be the reason for this permission issue and how could be this fixed.

 

Thanks in advance.

7,711
1
Who agreed with this topic