Marcus, Thanks for the feedback, but I don't believe it was this specific issue as I'm running a code from github and as you know my folder structure is very different.
Can someone please try pulling latest code, install with nonoss and try to login? Thanks ilya -----Original Message----- From: Marcus Sorensen [mailto:shadow...@gmail.com] Sent: Thursday, February 14, 2013 5:18 PM To: cloudstack-dev@incubator.apache.org Subject: Re: [ISSUE]ACS 4.1 code from today (02/14) broke login auth So, this was happening previously because the cloud user's home was not right. I saw this yesterday and the management server was throwing an exception when trying to generate ssh keys in /var/lib/cloud/management, which didn't exist. The new path is /var/cloudstack/management. So what may be happening is that people are now being bitten by everything being changed to match the package installs. I'll bet you have /var/lib/cloud/management/.ssh but not /var/cloudstack/management/.ssh On Thu, Feb 14, 2013 at 2:46 PM, Musayev, Ilya <imusa...@webmd.net> wrote: > ACS 4.1 code from today (02/14) broke login auth > > I get an error at login prompt "The given command does not exist or its not > available for the user" > > 2013-02-14 16:40:12,633 DEBUG [cloud.api.ApiServlet] > (2087715408@qtp-44855217-5:null) ===START=== 10.46.40.109 -- POST > null > 2013-02-14 16:40:12,639 DEBUG [cloud.user.AccountManagerImpl] > (2087715408@qtp-44855217-5:null) Attempting to log in user: admin in > domain 1 > 2013-02-14 16:40:12,640 DEBUG [server.auth.MD5UserAuthenticator] > (2087715408@qtp-44855217-5:null) Retrieving user: admin > 2013-02-14 16:40:12,659 DEBUG [cloud.user.AccountManagerImpl] > (2087715408@qtp-44855217-5:null) User: admin in domain 1 has > successfully logged in > 2013-02-14 16:40:12,689 DEBUG [cloud.api.ApiServlet] > (2087715408@qtp-44855217-5:null) ===END=== 10.46.40.109 -- POST null > 2013-02-14 16:40:12,709 DEBUG [cloud.api.ApiServlet] > (2087715408@qtp-44855217-5:null) ===START=== 10.46.40.109 -- GET > command=listCapabilities&response=json&sessionkey=MHQ4BNzDLCxRyhBtAzRE > vVWsJw0%3D&_=1360878012706 > 2013-02-14 16:40:12,729 DEBUG [cloud.api.ApiServer] > (2087715408@qtp-44855217-5:null) The given command:listCapabilities > does not exist or it is not available for user with id:2 > 2013-02-14 16:40:12,732 DEBUG [cloud.api.ApiServlet] > (2087715408@qtp-44855217-5:null) ===END=== 10.46.40.109 -- GET > command=listCapabilities&response=json&sessionkey=MHQ4BNzDLCxRyhBtAzRE > vVWsJw0%3D&_=1360878012706 > 2013-02-14 16:40:12,746 DEBUG [cloud.api.ApiServlet] > (2087715408@qtp-44855217-5:null) ===START=== 10.46.40.109 -- GET > command=listSwifts&response=json&sessionkey=MHQ4BNzDLCxRyhBtAzREvVWsJw > 0%3D&_=1360878012744 > 2013-02-14 16:40:12,766 DEBUG [cloud.api.ApiServer] > (2087715408@qtp-44855217-5:null) The given command:listSwifts does not > exist or it is not available for user with id:2 > 2013-02-14 16:40:12,769 DEBUG [cloud.api.ApiServlet] > (2087715408@qtp-44855217-5:null) ===END=== 10.46.40.109 -- GET > command=listSwifts&response=json&sessionkey=MHQ4BNzDLCxRyhBtAzREvVWsJw > 0%3D&_=1360878012 > >
