AnsweredAssumed Answered

MapR installation: Unable to read warden.conf

Question asked by lappie on Jun 30, 2015
Latest reply on Jul 2, 2015 by lappie
While installing MapR two of our nodes get stuck on 60% at the installation. I get the following error message:
Starting WARDEN, logging to /opt/mapr/logs/warden.log. . Error: warden can not be started. See /opt/mapr/logs/warden.log for details

Warden.conf on the failed nodes shows us this:
no jobtracker to stop
chown: cannot access `/opt/mapr/hadoop/hadoop-0.20.2/logs/*': No such file or directory
chown: cannot access `/opt/mapr/hadoop/hadoop-2.5.1/logs/*': No such file or directory
Header: hostName: slave1.hadoop1cluster, Time Zone: Australian Eastern Standard Time (New South Wales), processName: warden, processId: 11132, MapR Build Version:
2015-07-01 11:35:10,863 ERROR com.mapr.warden.WardenMain main [main]: /opt/mapr/conf/warden.conf (Permission denied)
Exception in thread "main" Could not load properties file : /opt/mapr/conf/warden.conf
        at com.mapr.warden.WardenMain.main(
/etc/init.d/mapr-warden: line 232: kill: (11362) - No such process
Warden start failed
Error: warden can not be started. See /opt/mapr/logs/warden.log for details

Looking at the conf-files it seems that warden.conf cannot be accessed because it is owned by root, while almost all files are owned by admin/mapr:
-r--r--r-- 1 admin mapr  811 Jul  1 11:34 ssl_truststore
-rw------- 1 root  root 6135 Jul  1 11:34 warden.conf
-rw-r--r-- 1 admin mapr 6019 Mar 27 05:59 warden.conf.2015-07-01.11-33
-rw-r--r-- 1 admin mapr  114 Jul  1 11:34 web.conf

Using *chown* on it won't help, because it is removed when I restart the installation and put back with the owner set to root again.

When I chown warden.conf to admin/mapr and start it manually warden does work. However, this does not help us getting further in the installation-process.

Any ideas what causes this permission issue?