The times I've had problems with this have been due to not having sudo access for the cloud user.
Make sure you have the following in sudoers: cloud ALL = NOPASSWD : ALL On 8 June 2013 10:18, Er Krishna <[email protected]> wrote: > On 8 Jun 2013 20:45, "Er Krishna" <[email protected]> wrote: > > > > Plz search on net . It may be a problem reated with database > connectivity. On line entry in some configuration file. > > > > On 8 Jun 2013 20:43, "Nehal J. Wani" <[email protected]> wrote: > >> > >> I successfully installed cloudstack 4.0.2 on CentOS 6.4. > >> > >> When I opened localhost:8080/client and entered admin:password, I got > the > >> error: Invalid username/password. > >> > >> The file /var/log/cloud/management/access_log.2013-06-08.txt > >> says: > >> 10.1.39.195 - - [08/Jun/2013:20:34:52 +0530] "POST /client/api HTTP/1.1" > >> 404 1057 > >> > >> When I visit the URL localhost:8080/client/api, I get the error: > >> > >> HTTP Status 404 - Servlet apiServlet is not available > >> ------------------------------ > >> > >> *type* Status report > >> > >> *message* *Servlet apiServlet is not available* > >> > >> *description* *The requested resource (Servlet apiServlet is not > available) > >> is not available.* > >> ------------------------------ > >> Apache Tomcat/6.0.24 > >> > >> and in the very beginning, when I restart my cloud-management-service, > I > >> get the error: > >> > >> HTTP Status 500 - > >> ------------------------------ > >> > >> *type* Exception report > >> > >> *message*** > >> > >> *description* *The server encountered an internal error () that > prevented > >> it from fulfilling this request.* > >> > >> *exception* > >> > >> javax.servlet.ServletException: Error instantiating servlet class > >> com.cloud.api.ApiServlet > >> > > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > >> > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > >> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > >> > > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > >> > > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > >> > > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) > >> > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > >> > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > >> java.lang.Thread.run(Thread.java:722) > >> > >> *root cause* > >> > >> com.cloud.utils.exception.CloudRuntimeException: ApiServer not > initialized > >> com.cloud.api.ApiServlet.<init>(ApiServlet.java:55) > >> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > >> > > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > >> > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > >> java.lang.reflect.Constructor.newInstance(Constructor.java:525) > >> java.lang.Class.newInstance0(Class.java:372) > >> java.lang.Class.newInstance(Class.java:325) > >> > > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) > >> > org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555) > >> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) > >> > > org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889) > >> > > org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721) > >> > > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274) > >> > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > >> > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > >> java.lang.Thread.run(Thread.java:722) > >> > >> *note* *The full stack trace of the root cause is available in the > Apache > >> Tomcat/6.0.24 logs.* > >> ------------------------------ > >> Apache Tomcat/6.0.24 > >> > >> I have tried executing the command cloud-setup-databases and > >> cloud-setup-management and also checked in the cloud database, user > table > >> that the md5 hash of password is indeed that of 'password'. Where am I > >> going wrong? > >> > >> Thanking You, > >> Nehal J. Wani > >> UG2, BTech CS+MS(CL) > >> IIIT-Hyderabad > >> http://commanlinewani.blogspot.com >
