cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-8633) Cannot login due to an error in starting 'cloudStackLifeCycle' bean
Date Wed, 15 Jul 2015 07:06:04 GMT


ASF GitHub Bot commented on CLOUDSTACK-8633:

Github user wilderrodrigues commented on the pull request:
    @bhaisaab @DaanHoogland @remibergsma could you have a look at this?
    Wasn't ACS management-server supposed to be executed as SUDO? If I'm right, there is no
need to change the file permission so drastically.
    In that case, @sanju1010 , you need to be sudo to run it. AFAIK we all run our ACS environments,
prod and tests, as sudo.

> Cannot login due to an error in starting 'cloudStackLifeCycle' bean
> -------------------------------------------------------------------
>                 Key: CLOUDSTACK-8633
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.6.0
>            Reporter: Raja Pullela
>            Priority: Blocker
> Using Master builds, MS logs shows following error – 
> “management-server.log:org.springframework.context.ApplicationContextException: Failed
to start bean 'cloudStackLifeCycle'; nested exception is
Failed to inject generated public key into systemvm iso sudo: /etc/sudoers.d/cloudstack-management
is mode 0755, should be 0440sudo: sorry, you must have a tty to run sudo”
> After modifying the permissions – MS works fine. 
> Apparently, this is related to a check that was done some time back…
> commit 870e1898eb28039fafaaeb8e50a7039f626f912c

This message was sent by Atlassian JIRA

View raw message