[
https://issues.apache.org/jira/browse/AMBARI-9663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14323301#comment-14323301
]
Hudson commented on AMBARI-9663:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1784 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1784/])
AMBARI-9663. Modifying the ambari server to run as a sudo root account prints
error on start (aonishuk) (aonishuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=46fbae9eb84ab09b6d4cae0e37e9dbde64b2543a)
* ambari-server/src/test/python/TestAmbariServer.py
* ambari-server/src/main/python/ambari_server_main.py
> Modifying the ambari server to run as a sudo root account prints error on
> start
> -------------------------------------------------------------------------------
>
> Key: AMBARI-9663
> URL: https://issues.apache.org/jira/browse/AMBARI-9663
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.0.0
>
>
> During ambari-server setup, changed the daemon to run as ec2-user (which is a
> user that can sudo to root).
>
>
>
> Customize user account for ambari-server daemon [y/n] (n)? y
> Enter user account for ambari-server daemon (root):ec2-user
>
> On ambari-server start, a ulimit message is printed. Not sure if it causes an
> issues.
>
>
>
> [root@ip-10-233-119-156 yum.repos.d]# ambari-server start
> Using python /usr/bin/python2.6
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server start....sh: line 0: ulimit: open files: cannot modify
> limit: Operation not permitted
> ................
> Ambari Server 'start' completed successfully.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
