[
https://issues.apache.org/jira/browse/AMBARI-9227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288429#comment-14288429
]
jun aoki commented on AMBARI-9227:
----------------------------------
[~vitthal_gogate],
1. ambari-server start fails when it is executed as "non-root" user. Just to
clarify.
2. I'm open to move the check to ambari-server setup.
3. My suggestion is (as you also concerns) not to change the limit
automatically and blindly, but to halts startup if the limit does not meet
Ambari's qualification with a friendly message where users know they have to
configure limits.conf.
> ambari-server startup with non-root user causes a ulimit error Operation not
> permitted.
> ---------------------------------------------------------------------------------------
>
> Key: AMBARI-9227
> URL: https://issues.apache.org/jira/browse/AMBARI-9227
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: jun aoki
> Priority: Minor
> Fix For: 2.0.0
>
>
> When you are starting ambari-server with non-root users (you can set so
> during amari-server setup (1)), it attempts to modify ulimit -n (the max open
> files to ) 10000 by default, you get a permission error. (2)
> Bad thing is the server process is started "successfully" without actually
> effecting the max number of open file descriptor. (some non user friendly
> error is shown though)
> Our customers tend to run applications with an non-root user so we'd like to
> clean up here a bit.
> The challenge is, ulimit is a bash command like 'cd', and only root can
> execute. See (3) to find ulimit behavior.
> My possible solution is
> 1. if root user, do the current behavior
> 2. if non-root, then the startup checks ulimit -a and if the current max
> number meets the requirement, if it does not meet, the server startup halts.
> End users have to fix through limits.conf.
> Let me know if this works.
> (1) setup to customize ambari daemon user
> {code}
> bash-4.1# ambari-server setup
> Using python /usr/bin/python2.6
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'disabled'
> Customize user account for ambari-server daemon [y/n] (n)? y
> Enter user account for ambari-server daemon (root):pivotal
> {code}
> (2) permission error
> {code}
> bash-4.1# ambari-server start
> Using python /usr/bin/python2.6
> Starting ambari-server
> Ambari Server running with 'root' 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.
> {code}
> (3)
> {code}
> [root@node1 init.d]# where ulimit
> -bash: where: command not found
> [root@node1 init.d]# sudo ulimit
> sudo: ulimit: command not found
> [root@node1 init.d]# ulimit
> unlimited
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
