HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz wrote: > Hello, > I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the > following error: > HTTP Status 404 - > -- > > *type* Status report > > *message* > > *description* *The requested resource () is not available.* > -- > Apache Tomcat/6.0.24 > > Thanks for your support, > Motty > -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
I tried to attached the management-server.log file but is too big. In Catalina.out I see the following error: Oct 08, 2014 7:23:08 AM org.apache.catalina.startup.Catalina start SEVERE: Catalina.start: LifecycleException: service.getName(): "Catalina"; Protocol handler start failed: java.net.BindException: Address already in use :8080 at org.apache.catalina.connector.Connector.start(Connector.java:1087) at org.apache.catalina.core.StandardService.start(StandardService.java:531) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:593) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Oct 08, 2014 7:23:08 AM org.apache.catalina.startup.Catalina start INFO: Server startup in 77 ms Oct 08, 2014 7:23:21 AM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-8080 Oct 08, 2014 7:23:22 AM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Oct 08, 2014 7:23:22 AM org.apache.catalina.connector.MapperListener destroy WARNING: Error unregistering MBeanServerDelegate java.lang.NullPointerException at org.apache.catalina.connector.MapperListener.destroy(MapperListener.java:176) at org.apache.catalina.connector.Connector.stop(Connector.java:1128) at org.apache.catalina.core.StandardService.stop(StandardService.java:593) at org.apache.catalina.core.StandardServer.stop(StandardServer.java:744) at org.apache.catalina.startup.Catalina.stop(Catalina.java:643) at org.apache.catalina.startup.Catalina.start(Catalina.java:618) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Oct 08, 2014 7:23:22 AM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080 Oct 08, 2014 7:23:22 AM org.apache.catalina.connector.Connector stop SEVERE: Coyote connector has not been started On Wed, Oct 8, 2014 at 6:53 AM, motty cruz wrote: > I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank > page no errors > > any ideas? > > On Wed, Oct 8, 2014 at 6:34 AM, motty cruz wrote: > >> Hello, >> I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the >> following error: >> HTTP Status 404 - >> -- >> >> *type* Status report >> >> *message* >> >> *description* *The requested resource () is not available.* >> -- >> Apache Tomcat/6.0.24 >> >> Thanks for your support, >> Motty >> > > > > -- > Thanks for your support, > Motty > -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev "motty cruz" følgende: > I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank > page no errors > > any ideas? > > On Wed, Oct 8, 2014 at 6:34 AM, motty cruz wrote: > > > Hello, > > I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the > > following error: > > HTTP Status 404 - > > -- > > > > *type* Status report > > > > *message* > > > > *description* *The requested resource () is not available.* > > -- > > Apache Tomcat/6.0.24 > > > > Thanks for your support, > > Motty > > > > > > -- > Thanks for your support, > Motty >
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management:[ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management:[ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber wrote: > You shouldnt start tomcat, cloudstack will do that for you. > > Shutdown tomcat and kill any acs related java processes. Then you start > cloudstack-management service and post the logs if it fails > > Erii > 8. okt. 2014 15:53 skrev "motty cruz" følgende: > > > I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank > > page no errors > > > > any ideas? > > > > On Wed, Oct 8, 2014 at 6:34 AM, motty cruz wrote: > > > > > Hello, > > > I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the > > > following error: > > > HTTP Status 404 - > > > -- > > > > > > *type* Status report > > > > > > *message* > > > > > > *description* *The requested resource () is not available.* > > > -- > > > Apache Tomcat/6.0.24 > > > > > > Thanks for your support, > > > Motty > > > > > > > > > > > -- > > Thanks for your support, > > Motty > > > -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
should I revert the upgrade? if you think I should. Do you know the steps to revert? I really need this cluster up and running. Thanks for your help!. -Motty On Wed, Oct 8, 2014 at 9:29 AM, motty cruz wrote: > Hi Erik, > > I did as you suggested : > [root@blaze home]# pkill java > [root@blaze home]# service cloudstack-management status > cloudstack-management dead but pid file exists > The pid file locates at /var/run/cloudstack-management.pid and lock file > at /var/lock/subsys/cloudstack-management. > Starting cloudstack-management will take care of them or you can > manually clean up. > [root@blaze home]# service cloudstack-management stop > Stopping cloudstack-management:[ OK ] > [root@blaze home]# service cloudstack-management start > Starting cloudstack-management:[ OK ] > [root@blaze home]# service cloudstack-management status > cloudstack-management (pid 3853) is running... > [root@blaze home]# service cloudstack-management status > cloudstack-management (pid 3853) is running... > [root@blaze home]# > > I can't attached the management-server.log apache.org complained about > it. > > On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber wrote: > >> You shouldnt start tomcat, cloudstack will do that for you. >> >> Shutdown tomcat and kill any acs related java processes. Then you start >> cloudstack-management service and post the logs if it fails >> >> Erii >> 8. okt. 2014 15:53 skrev "motty cruz" følgende: >> >> > I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank >> > page no errors >> > >> > any ideas? >> > >> > On Wed, Oct 8, 2014 at 6:34 AM, motty cruz >> wrote: >> > >> > > Hello, >> > > I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the >> > > following error: >> > > HTTP Status 404 - >> > > -- >> > > >> > > *type* Status report >> > > >> > > *message* >> > > >> > > *description* *The requested resource () is not available.* >> > > -- >> > > Apache Tomcat/6.0.24 >> > > >> > > Thanks for your support, >> > > Motty >> > > >> > >> > >> > >> > -- >> > Thanks for your support, >> > Motty >> > >> > > > > -- > Thanks for your support, > Motty > -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev "motty cruz" følgende: > Hi Erik, > > I did as you suggested : > [root@blaze home]# pkill java > [root@blaze home]# service cloudstack-management status > cloudstack-management dead but pid file exists > The pid file locates at /var/run/cloudstack-management.pid and lock file at > /var/lock/subsys/cloudstack-management. > Starting cloudstack-management will take care of them or you can > manually clean up. > [root@blaze home]# service cloudstack-management stop > Stopping cloudstack-management:[ OK ] > [root@blaze home]# service cloudstack-management start > Starting cloudstack-management:[ OK ] > [root@blaze home]# service cloudstack-management status > cloudstack-management (pid 3853) is running... > [root@blaze home]# service cloudstack-management status > cloudstack-management (pid 3853) is running... > [root@blaze home]# > > I can't attached the management-server.log apache.org complained about it. > > On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber wrote: > > > You shouldnt start tomcat, cloudstack will do that for you. > > > > Shutdown tomcat and kill any acs related java processes. Then you start > > cloudstack-management service and post the logs if it fails > > > > Erii > > 8. okt. 2014 15:53 skrev "motty cruz" følgende: > > > > > I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank > > > page no errors > > > > > > any ideas? > > > > > > On Wed, Oct 8, 2014 at 6:34 AM, motty cruz > wrote: > > > > > > > Hello, > > > > I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the > > > > following error: > > > > HTTP Status 404 - > > > > -- > > > > > > > > *type* Status report > > > > > > > > *message* > > > > > > > > *description* *The requested resource () is not available.* > > > > -- > > > > Apache Tomcat/6.0.24 > > > > > > > > Thanks for your support, > > > > Motty > > > > > > > > > > > > > > > > -- > > > Thanks for your support, > > > Motty > > > > > > > > > -- > Thanks for your support, > Motty >
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber wrote: > Post the log on pastebin, also post the output of > > netstat -anlp > ps aux > > Erik > 8. okt. 2014 18:30 skrev "motty cruz" følgende: > > > Hi Erik, > > > > I did as you suggested : > > [root@blaze home]# pkill java > > [root@blaze home]# service cloudstack-management status > > cloudstack-management dead but pid file exists > > The pid file locates at /var/run/cloudstack-management.pid and lock file > at > > /var/lock/subsys/cloudstack-management. > > Starting cloudstack-management will take care of them or you can > > manually clean up. > > [root@blaze home]# service cloudstack-management stop > > Stopping cloudstack-management:[ OK ] > > [root@blaze home]# service cloudstack-management start > > Starting cloudstack-management:[ OK ] > > [root@blaze home]# service cloudstack-management status > > cloudstack-management (pid 3853) is running... > > [root@blaze home]# service cloudstack-management status > > cloudstack-management (pid 3853) is running... > > [root@blaze home]# > > > > I can't attached the management-server.log apache.org complained about > it. > > > > On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber wrote: > > > > > You shouldnt start tomcat, cloudstack will do that for you. > > > > > > Shutdown tomcat and kill any acs related java processes. Then you start > > > cloudstack-management service and post the logs if it fails > > > > > > Erii > > > 8. okt. 2014 15:53 skrev "motty cruz" følgende: > > > > > > > I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a > blank > > > > page no errors > > > > > > > > any ideas? > > > > > > > > On Wed, Oct 8, 2014 at 6:34 AM, motty cruz > > wrote: > > > > > > > > > Hello, > > > > > I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the > > > > > following error: > > > > > HTTP Status 404 - > > > > > -- > > > > > > > > > > *type* Status report > > > > > > > > > > *message* > > > > > > > > > > *description* *The requested resource () is not available.* > > > > > -- > > > > > Apache Tomcat/6.0.24 > > > > > > > > > > Thanks for your support, > > > > > Motty > > > > > > > > > > > > > > > > > > > > > -- > > > > Thanks for your support, > > > > Motty > > > > > > > > > > > > > > > -- > > Thanks for your support, > > Motty > > > -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - > From: "motty cruz" > To: users@cloudstack.apache.org > Sent: Wednesday, 8 October, 2014 6:34:29 PM > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS > 4.4.1 > Thanks Erik, > here is the output of netstat -anlp > http://pastebin.com/raw.php?i=CJn9i9ci > ps aux > http://pastebin.com/raw.php?i=uSDJJUDH > management-server.log > http://pastebin.com/raw.php?i=sSs63jRi > Thanks for your support > Motty > On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber > wrote: > > Post the log on pastebin, also post the output of > > > > netstat -anlp > > ps aux > > > > Erik > > 8. okt. 2014 18:30 skrev "motty cruz" > > følgende: > > > > > Hi Erik, > > > > > > I did as you suggested : > > > [root@blaze home]# pkill java > > > [root@blaze home]# service cloudstack-management status > > > cloudstack-management dead but pid file exists > > > The pid file locates at /var/run/cloudstack-management.pid and > > > lock file > > at > > > /var/lock/subsys/cloudstack-management. > > > Starting cloudstack-management will take care of them or you can > > > manually clean up. > > > [root@blaze home]# service cloudstack-management stop > > > Stopping cloudstack-management: [ OK ] > > > [root@blaze home]# service cloudstack-management start > > > Starting cloudstack-management: [ OK ] > > > [root@blaze home]# service cloudstack-management status > > > cloudstack-management (pid 3853) is running... > > > [root@blaze home]# service cloudstack-management status > > > cloudstack-management (pid 3853) is running... > > > [root@blaze home]# > > > > > > I can't attached the management-server.log apache.org complained > > > about > > it. > > > > > > On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber > > > wrote: > > > > > > > You shouldnt start tomcat, cloudstack will do that for you. > > > > > > > > Shutdown tomcat and kill any acs related java processes. Then > > > > you start > > > > cloudstack-management service and post the logs if it fails > > > > > > > > Erii > > > > 8. okt. 2014 15:53 skrev "motty cruz" > > > > følgende: > > > > > > > > > I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm > > > > > getting a > > blank > > > > > page no errors > > > > > > > > > > any ideas? > > > > > > > > > > On Wed, Oct 8, 2014 at 6:34 AM, motty cruz > > > > > > > > wrote: > > > > > > > > > > > Hello, > > > > > > I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm > > > > > > getting the > > > > > > following error: > > > > > > HTTP Status 404 - > > > > > > -- > > > > > > > > > > > > *type* Status report > > > > > > > > > > > > *message* > > > > > > > > > > > > *description* *The requested resource () is not available.* > > > > > > -- > > > > > > Apache Tomcat/6.0.24 > > > > > > > > > > > > Thanks for your support, > > > > > > Motty > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Thanks for your support, > > > > > Motty > > > > > > > > > > > > > > > > > > > > > -- > > > Thanks for your support, > > > Motty > > > > > > -- > Thanks for your support, > Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky wrote: > I've had a similar issue when upgrading, but I can't remember exactly how > I solved it. I think everything should be in the logs, it was pretty > straightforward and quick as far as I remember. > > Andrei > > P.S. to revert back you simply stop acs and usage server, restore your > database from backups and install the previous acs version. If you've > updated any clients, make sure you revert them back as well. > > - Original Message - > > > From: "motty cruz" > > To: users@cloudstack.apache.org > > Sent: Wednesday, 8 October, 2014 6:34:29 PM > > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS > > 4.4.1 > > > Thanks Erik, > > here is the output of netstat -anlp > > http://pastebin.com/raw.php?i=CJn9i9ci > > > ps aux > > http://pastebin.com/raw.php?i=uSDJJUDH > > > management-server.log > > http://pastebin.com/raw.php?i=sSs63jRi > > > Thanks for your support > > Motty > > > On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber > > wrote: > > > > Post the log on pastebin, also post the output of > > > > > > netstat -anlp > > > ps aux > > > > > > Erik > > > 8. okt. 2014 18:30 skrev "motty cruz" > > > følgende: > > > > > > > Hi Erik, > > > > > > > > I did as you suggested : > > > > [root@blaze home]# pkill java > > > > [root@blaze home]# service cloudstack-management status > > > > cloudstack-management dead but pid file exists > > > > The pid file locates at /var/run/cloudstack-management.pid and > > > > lock file > > > at > > > > /var/lock/subsys/cloudstack-management. > > > > Starting cloudstack-management will take care of them or you can > > > > manually clean up. > > > > [root@blaze home]# service cloudstack-management stop > > > > Stopping cloudstack-management: [ OK ] > > > > [root@blaze home]# service cloudstack-management start > > > > Starting cloudstack-management: [ OK ] > > > > [root@blaze home]# service cloudstack-management status > > > > cloudstack-management (pid 3853) is running... > > > > [root@blaze home]# service cloudstack-management status > > > > cloudstack-management (pid 3853) is running... > > > > [root@blaze home]# > > > > > > > > I can't attached the management-server.log apache.org complained > > > > about > > > it. > > > > > > > > On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber > > > > wrote: > > > > > > > > > You shouldnt start tomcat, cloudstack will do that for you. > > > > > > > > > > Shutdown tomcat and kill any acs related java processes. Then > > > > > you start > > > > > cloudstack-management service and post the logs if it fails > > > > > > > > > > Erii > > > > > 8. okt. 2014 15:53 skrev "motty cruz" > > > > > følgende: > > > > > > > > > > > I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm > > > > > > getting a > > > blank > > > > > > page no errors > > > > > > > > > > > > any ideas? > > > > > > > > > > > > On Wed, Oct 8, 2014 at 6:34 AM, motty cruz > > > > > > > > > > wrote: > > > > > > > > > > > > > Hello, > > > > > > > I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm > > > > > > > getting the > > > > > > > following error: > > > > > > > HTTP Status 404 - > > > > > > > -- > > > > > > > > > > > > > > *type* Status report > > > > > > > > > > > > > > *message* > > > > > > > > > > > > > > *description* *The requested resource () is not available.* > > > > > > > -- > > > > > > > Apache Tomcat/6.0.24 > > > > > > > > > > > > > > Thanks for your support, > > > > > > > Motty > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Thanks for your support, > > > > > > Motty > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Thanks for your support, > > > > Motty > > > > > > > > > > -- > > Thanks for your support, > > Motty > -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Management server log is missing ERROR statements in what you've posted. Please include the full log file. On 10/8/14, 12:23 PM, motty cruz wrote: I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: "motty cruz" To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev "motty cruz" følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev "motty cruz" følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Hello ilya, I was not able to post the entire log file is too big, here is the error msg I see at 6:21 am. http://pastebin.com/raw.php?i=dWxDmR91 Thanks, Motty On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev wrote: > Management server log is missing ERROR statements in what you've posted. > Please include the full log file. > > On 10/8/14, 12:23 PM, motty cruz wrote: > >> I am looking in the logs but I can't see to find exactly the error causing >> this issue. >> I still getting this error: >> HTTP Status 404 - >> -- >> >> *type* Status report >> >> *message* >> >> *description* *The requested resource () is not available.* >> -- >> Apache Tomcat/6.0.24 >> >> On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky >> wrote: >> >> I've had a similar issue when upgrading, but I can't remember exactly how >>> I solved it. I think everything should be in the logs, it was pretty >>> straightforward and quick as far as I remember. >>> >>> Andrei >>> >>> P.S. to revert back you simply stop acs and usage server, restore your >>> database from backups and install the previous acs version. If you've >>> updated any clients, make sure you revert them back as well. >>> >>> - Original Message - >>> >>> From: "motty cruz" >>>> To: users@cloudstack.apache.org >>>> Sent: Wednesday, 8 October, 2014 6:34:29 PM >>>> Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS >>>> 4.4.1 >>>> Thanks Erik, >>>> here is the output of netstat -anlp >>>> http://pastebin.com/raw.php?i=CJn9i9ci >>>> ps aux >>>> http://pastebin.com/raw.php?i=uSDJJUDH >>>> management-server.log >>>> http://pastebin.com/raw.php?i=sSs63jRi >>>> Thanks for your support >>>> Motty >>>> On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber >>>> wrote: >>>> >>>>> Post the log on pastebin, also post the output of >>>>> >>>>> netstat -anlp >>>>> ps aux >>>>> >>>>> Erik >>>>> 8. okt. 2014 18:30 skrev "motty cruz" >>>>> følgende: >>>>> >>>>> Hi Erik, >>>>>> >>>>>> I did as you suggested : >>>>>> [root@blaze home]# pkill java >>>>>> [root@blaze home]# service cloudstack-management status >>>>>> cloudstack-management dead but pid file exists >>>>>> The pid file locates at /var/run/cloudstack-management.pid and >>>>>> lock file >>>>>> >>>>> at >>>>> >>>>>> /var/lock/subsys/cloudstack-management. >>>>>> Starting cloudstack-management will take care of them or you can >>>>>> manually clean up. >>>>>> [root@blaze home]# service cloudstack-management stop >>>>>> Stopping cloudstack-management: [ OK ] >>>>>> [root@blaze home]# service cloudstack-management start >>>>>> Starting cloudstack-management: [ OK ] >>>>>> [root@blaze home]# service cloudstack-management status >>>>>> cloudstack-management (pid 3853) is running... >>>>>> [root@blaze home]# service cloudstack-management status >>>>>> cloudstack-management (pid 3853) is running... >>>>>> [root@blaze home]# >>>>>> >>>>>> I can't attached the management-server.log apache.org complained >>>>>> about >>>>>> >>>>> it. >>>>> >>>>>> On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber >>>>>> wrote: >>>>>> >>>>>> You shouldnt start tomcat, cloudstack will do that for you. >>>>>>> >>>>>>> Shutdown tomcat and kill any acs related java processes. Then >>>>>>> you start >>>>>>> cloudstack-management service and post the logs if it fails >>>>>>> >>>>>>> Erii >>>>>>> 8. okt. 2014 15:53 skrev "motty cruz" >>>>>>> følgende: >>>>>>> >>>>>>> I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm >>>>>>>> getting a >>>>>>>> >>>>>>> blank >>>>> >>>>>> page no errors >>>>>>>> >>>>>>>> any ideas? >>>>>>>> >>>>>>>> On Wed, Oct 8, 2014 at 6:34 AM, motty cruz >>>>>>>> >>>>>>>> >>>>>>> wrote: >>>>>> >>>>>>> Hello, >>>>>>>>> I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm >>>>>>>>> getting the >>>>>>>>> following error: >>>>>>>>> HTTP Status 404 - >>>>>>>>> -- >>>>>>>>> >>>>>>>>> *type* Status report >>>>>>>>> >>>>>>>>> *message* >>>>>>>>> >>>>>>>>> *description* *The requested resource () is not available.* >>>>>>>>> -- >>>>>>>>> Apache Tomcat/6.0.24 >>>>>>>>> >>>>>>>>> Thanks for your support, >>>>>>>>> Motty >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Thanks for your support, >>>>>>>> Motty >>>>>>>> >>>>>>>> >>>>>> >>>>>> -- >>>>>> Thanks for your support, >>>>>> Motty >>>>>> >>>>>> -- >>>> Thanks for your support, >>>> Motty >>>> >>> >> >> > -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
can I run "cloudstack-setup-management" would this help? I try to find the meaning of this command, On Wed, Oct 8, 2014 at 1:04 PM, motty cruz wrote: > Hello ilya, > I was not able to post the entire log file is too big, > > here is the error msg I see at 6:21 am. > http://pastebin.com/raw.php?i=dWxDmR91 > > > Thanks, > Motty > > On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < > ilya.mailing.li...@gmail.com> wrote: > >> Management server log is missing ERROR statements in what you've posted. >> Please include the full log file. >> >> On 10/8/14, 12:23 PM, motty cruz wrote: >> >>> I am looking in the logs but I can't see to find exactly the error >>> causing >>> this issue. >>> I still getting this error: >>> HTTP Status 404 - >>> -- >>> >>> *type* Status report >>> >>> *message* >>> >>> *description* *The requested resource () is not available.* >>> -- >>> Apache Tomcat/6.0.24 >>> >>> On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky >>> wrote: >>> >>> I've had a similar issue when upgrading, but I can't remember exactly >>>> how >>>> I solved it. I think everything should be in the logs, it was pretty >>>> straightforward and quick as far as I remember. >>>> >>>> Andrei >>>> >>>> P.S. to revert back you simply stop acs and usage server, restore your >>>> database from backups and install the previous acs version. If you've >>>> updated any clients, make sure you revert them back as well. >>>> >>>> - Original Message - >>>> >>>> From: "motty cruz" >>>>> To: users@cloudstack.apache.org >>>>> Sent: Wednesday, 8 October, 2014 6:34:29 PM >>>>> Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS >>>>> 4.4.1 >>>>> Thanks Erik, >>>>> here is the output of netstat -anlp >>>>> http://pastebin.com/raw.php?i=CJn9i9ci >>>>> ps aux >>>>> http://pastebin.com/raw.php?i=uSDJJUDH >>>>> management-server.log >>>>> http://pastebin.com/raw.php?i=sSs63jRi >>>>> Thanks for your support >>>>> Motty >>>>> On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber >>>>> wrote: >>>>> >>>>>> Post the log on pastebin, also post the output of >>>>>> >>>>>> netstat -anlp >>>>>> ps aux >>>>>> >>>>>> Erik >>>>>> 8. okt. 2014 18:30 skrev "motty cruz" >>>>>> følgende: >>>>>> >>>>>> Hi Erik, >>>>>>> >>>>>>> I did as you suggested : >>>>>>> [root@blaze home]# pkill java >>>>>>> [root@blaze home]# service cloudstack-management status >>>>>>> cloudstack-management dead but pid file exists >>>>>>> The pid file locates at /var/run/cloudstack-management.pid and >>>>>>> lock file >>>>>>> >>>>>> at >>>>>> >>>>>>> /var/lock/subsys/cloudstack-management. >>>>>>> Starting cloudstack-management will take care of them or you can >>>>>>> manually clean up. >>>>>>> [root@blaze home]# service cloudstack-management stop >>>>>>> Stopping cloudstack-management: [ OK ] >>>>>>> [root@blaze home]# service cloudstack-management start >>>>>>> Starting cloudstack-management: [ OK ] >>>>>>> [root@blaze home]# service cloudstack-management status >>>>>>> cloudstack-management (pid 3853) is running... >>>>>>> [root@blaze home]# service cloudstack-management status >>>>>>> cloudstack-management (pid 3853) is running... >>>>>>> [root@blaze home]# >>>>>>> >>>>>>> I can't attached the management-server.log apache.org complained >>>>>>> about >>>>>>> >>>>>> it. >>>>>> >>>>>>> On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber >>>>>>> wrote: >>>>>>> >>>>>>> You shouldnt start tomcat, cloudstack will do that for you. >>>>>>>> >>>>>>>> Shutdown tomcat and kill any acs related java processes. Then >>>>>>>> you start >>>>>>>> cloudstack-management service and post the logs if it fails >>>>>>>> >>>>>>>> Erii >>>>>>>> 8. okt. 2014 15:53 skrev "motty cruz" >>>>>>>> følgende: >>>>>>>> >>>>>>>> I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm >>>>>>>>> getting a >>>>>>>>> >>>>>>>> blank >>>>>> >>>>>>> page no errors >>>>>>>>> >>>>>>>>> any ideas? >>>>>>>>> >>>>>>>>> On Wed, Oct 8, 2014 at 6:34 AM, motty cruz >>>>>>>>> >>>>>>>>> >>>>>>>> wrote: >>>>>>> >>>>>>>> Hello, >>>>>>>>>> I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm >>>>>>>>>> getting the >>>>>>>>>> following error: >>>>>>>>>> HTTP Status 404 - >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>>> *type* Status report >>>>>>>>>> >>>>>>>>>> *message* >>>>>>>>>> >>>>>>>>>> *description* *The requested resource () is not available.* >>>>>>>>>> -- >>>>>>>>>> Apache Tomcat/6.0.24 >>>>>>>>>> >>>>>>>>>> Thanks for your support, >>>>>>>>>> Motty >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Thanks for your support, >>>>>>>>> Motty >>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Thanks for your support, >>>>>>> Motty >>>>>>> >>>>>>> -- >>>>> Thanks for your support, >>>>> Motty >>>>> >>>> >>> >>> >> > > > -- > Thanks for your support, > Motty > -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
How did you upgrade exactly? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "motty cruz" > To: users@cloudstack.apache.org > Sent: Wednesday, 8 October, 2014 22:31:57 > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > can I run "cloudstack-setup-management" would this help? I try to find the > meaning of this command, > > On Wed, Oct 8, 2014 at 1:04 PM, motty cruz wrote: > >> Hello ilya, >> I was not able to post the entire log file is too big, >> >> here is the error msg I see at 6:21 am. >> http://pastebin.com/raw.php?i=dWxDmR91 >> >> >> Thanks, >> Motty >> >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < >> ilya.mailing.li...@gmail.com> wrote: >> >>> Management server log is missing ERROR statements in what you've posted. >>> Please include the full log file. >>> >>> On 10/8/14, 12:23 PM, motty cruz wrote: >>> >>>> I am looking in the logs but I can't see to find exactly the error >>>> causing >>>> this issue. >>>> I still getting this error: >>>> HTTP Status 404 - >>>> -- >>>> >>>> *type* Status report >>>> >>>> *message* >>>> >>>> *description* *The requested resource () is not available.* >>>> -- >>>> Apache Tomcat/6.0.24 >>>> >>>> On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky >>>> wrote: >>>> >>>> I've had a similar issue when upgrading, but I can't remember exactly >>>>> how >>>>> I solved it. I think everything should be in the logs, it was pretty >>>>> straightforward and quick as far as I remember. >>>>> >>>>> Andrei >>>>> >>>>> P.S. to revert back you simply stop acs and usage server, restore your >>>>> database from backups and install the previous acs version. If you've >>>>> updated any clients, make sure you revert them back as well. >>>>> >>>>> - Original Message - >>>>> >>>>> From: "motty cruz" >>>>>> To: users@cloudstack.apache.org >>>>>> Sent: Wednesday, 8 October, 2014 6:34:29 PM >>>>>> Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS >>>>>> 4.4.1 >>>>>> Thanks Erik, >>>>>> here is the output of netstat -anlp >>>>>> http://pastebin.com/raw.php?i=CJn9i9ci >>>>>> ps aux >>>>>> http://pastebin.com/raw.php?i=uSDJJUDH >>>>>> management-server.log >>>>>> http://pastebin.com/raw.php?i=sSs63jRi >>>>>> Thanks for your support >>>>>> Motty >>>>>> On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber >>>>>> wrote: >>>>>> >>>>>>> Post the log on pastebin, also post the output of >>>>>>> >>>>>>> netstat -anlp >>>>>>> ps aux >>>>>>> >>>>>>> Erik >>>>>>> 8. okt. 2014 18:30 skrev "motty cruz" >>>>>>> følgende: >>>>>>> >>>>>>> Hi Erik, >>>>>>>> >>>>>>>> I did as you suggested : >>>>>>>> [root@blaze home]# pkill java >>>>>>>> [root@blaze home]# service cloudstack-management status >>>>>>>> cloudstack-management dead but pid file exists >>>>>>>> The pid file locates at /var/run/cloudstack-management.pid and >>>>>>>> lock file >>>>>>>> >>>>>>> at >>>>>>> >>>>>>>> /var/lock/subsys/cloudstack-management. >>>>>>>> Starting cloudstack-management will take care of them or you can >>>>>>>> manually clean up. >>>>>>>> [root@blaze home]# service cloudstack-management stop >>>>>>>> Stopping cloudstack-management: [ OK ] >>>>>>>> [root@blaze home]# service cloudstack-management start >>>>>>>> Starting cloudstack-management: [ OK ] >>>>>>>> [root@blaze home]# service cloudstack-management stat
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
I can't revert the upgrade because the cloudstack.repo point to directory with two version 4.4.0 and 4.4.1 please help!! here is the link to management-server.log http://pastebin.com/raw.php?i=6cuXJd3S Thanks On Wed, Oct 8, 2014 at 2:31 PM, motty cruz wrote: > can I run "cloudstack-setup-management" would this help? I try to find the > meaning of this command, > > On Wed, Oct 8, 2014 at 1:04 PM, motty cruz wrote: > >> Hello ilya, >> I was not able to post the entire log file is too big, >> >> here is the error msg I see at 6:21 am. >> http://pastebin.com/raw.php?i=dWxDmR91 >> >> >> Thanks, >> Motty >> >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < >> ilya.mailing.li...@gmail.com> wrote: >> >>> Management server log is missing ERROR statements in what you've posted. >>> Please include the full log file. >>> >>> On 10/8/14, 12:23 PM, motty cruz wrote: >>> >>>> I am looking in the logs but I can't see to find exactly the error >>>> causing >>>> this issue. >>>> I still getting this error: >>>> HTTP Status 404 - >>>> -- >>>> >>>> *type* Status report >>>> >>>> *message* >>>> >>>> *description* *The requested resource () is not available.* >>>> -- >>>> Apache Tomcat/6.0.24 >>>> >>>> On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky >>> > >>>> wrote: >>>> >>>> I've had a similar issue when upgrading, but I can't remember exactly >>>>> how >>>>> I solved it. I think everything should be in the logs, it was pretty >>>>> straightforward and quick as far as I remember. >>>>> >>>>> Andrei >>>>> >>>>> P.S. to revert back you simply stop acs and usage server, restore your >>>>> database from backups and install the previous acs version. If you've >>>>> updated any clients, make sure you revert them back as well. >>>>> >>>>> - Original Message - >>>>> >>>>> From: "motty cruz" >>>>>> To: users@cloudstack.apache.org >>>>>> Sent: Wednesday, 8 October, 2014 6:34:29 PM >>>>>> Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS >>>>>> 4.4.1 >>>>>> Thanks Erik, >>>>>> here is the output of netstat -anlp >>>>>> http://pastebin.com/raw.php?i=CJn9i9ci >>>>>> ps aux >>>>>> http://pastebin.com/raw.php?i=uSDJJUDH >>>>>> management-server.log >>>>>> http://pastebin.com/raw.php?i=sSs63jRi >>>>>> Thanks for your support >>>>>> Motty >>>>>> On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber >>>>>> wrote: >>>>>> >>>>>>> Post the log on pastebin, also post the output of >>>>>>> >>>>>>> netstat -anlp >>>>>>> ps aux >>>>>>> >>>>>>> Erik >>>>>>> 8. okt. 2014 18:30 skrev "motty cruz" >>>>>>> følgende: >>>>>>> >>>>>>> Hi Erik, >>>>>>>> >>>>>>>> I did as you suggested : >>>>>>>> [root@blaze home]# pkill java >>>>>>>> [root@blaze home]# service cloudstack-management status >>>>>>>> cloudstack-management dead but pid file exists >>>>>>>> The pid file locates at /var/run/cloudstack-management.pid and >>>>>>>> lock file >>>>>>>> >>>>>>> at >>>>>>> >>>>>>>> /var/lock/subsys/cloudstack-management. >>>>>>>> Starting cloudstack-management will take care of them or you can >>>>>>>> manually clean up. >>>>>>>> [root@blaze home]# service cloudstack-management stop >>>>>>>> Stopping cloudstack-management: [ OK ] >>>>>>>> [root@blaze home]# service cloudstack-management start >>>>>>>> Starting cloudstack-management: [ OK ] >>>>>>>> [root@blaze home]# service cloudstack-management status &g
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Hi Nux, I follow this steps to upgrade http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4/upgrade/upgrade-4.4.html here is my cloudstack.repo [cloudstack] name=cloudstack baseurl=http://cloudstack.apt-get.eu/rhel/4.4/ enabled=1 gpgcheck=0 cloudstack.repo (END) Thanks for your help! On Wed, Oct 8, 2014 at 2:40 PM, Nux! wrote: > How did you upgrade exactly? > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - > > From: "motty cruz" > > To: users@cloudstack.apache.org > > Sent: Wednesday, 8 October, 2014 22:31:57 > > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > > > can I run "cloudstack-setup-management" would this help? I try to find > the > > meaning of this command, > > > > On Wed, Oct 8, 2014 at 1:04 PM, motty cruz wrote: > > > >> Hello ilya, > >> I was not able to post the entire log file is too big, > >> > >> here is the error msg I see at 6:21 am. > >> http://pastebin.com/raw.php?i=dWxDmR91 > >> > >> > >> Thanks, > >> Motty > >> > >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < > >> ilya.mailing.li...@gmail.com> wrote: > >> > >>> Management server log is missing ERROR statements in what you've > posted. > >>> Please include the full log file. > >>> > >>> On 10/8/14, 12:23 PM, motty cruz wrote: > >>> > >>>> I am looking in the logs but I can't see to find exactly the error > >>>> causing > >>>> this issue. > >>>> I still getting this error: > >>>> HTTP Status 404 - > >>>> -- > >>>> > >>>> *type* Status report > >>>> > >>>> *message* > >>>> > >>>> *description* *The requested resource () is not available.* > >>>> -- > >>>> Apache Tomcat/6.0.24 > >>>> > >>>> On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky < > and...@arhont.com> > >>>> wrote: > >>>> > >>>> I've had a similar issue when upgrading, but I can't remember exactly > >>>>> how > >>>>> I solved it. I think everything should be in the logs, it was pretty > >>>>> straightforward and quick as far as I remember. > >>>>> > >>>>> Andrei > >>>>> > >>>>> P.S. to revert back you simply stop acs and usage server, restore > your > >>>>> database from backups and install the previous acs version. If you've > >>>>> updated any clients, make sure you revert them back as well. > >>>>> > >>>>> - Original Message - > >>>>> > >>>>> From: "motty cruz" > >>>>>> To: users@cloudstack.apache.org > >>>>>> Sent: Wednesday, 8 October, 2014 6:34:29 PM > >>>>>> Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS > >>>>>> 4.4.1 > >>>>>> Thanks Erik, > >>>>>> here is the output of netstat -anlp > >>>>>> http://pastebin.com/raw.php?i=CJn9i9ci > >>>>>> ps aux > >>>>>> http://pastebin.com/raw.php?i=uSDJJUDH > >>>>>> management-server.log > >>>>>> http://pastebin.com/raw.php?i=sSs63jRi > >>>>>> Thanks for your support > >>>>>> Motty > >>>>>> On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber > >>>>>> wrote: > >>>>>> > >>>>>>> Post the log on pastebin, also post the output of > >>>>>>> > >>>>>>> netstat -anlp > >>>>>>> ps aux > >>>>>>> > >>>>>>> Erik > >>>>>>> 8. okt. 2014 18:30 skrev "motty cruz" > >>>>>>> følgende: > >>>>>>> > >>>>>>> Hi Erik, > >>>>>>>> > >>>>>>>> I did as you suggested : > >>>>>>>> [root@blaze home]# pkill java > >>>>>>>> [root@blaze home]# service cloudstack-management status > >>>>>>>> cloudstack-
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Motty, The error you see about not being able to connect to a host on port 9090 is normal when the management server is starting. There must be another error or warning somewhere. Please try the steps below to shrink the log file to manageable size and upload the file to some file sharing site if paste bin restricts you. service cloudstack-management stop cat /dev/null > /var/log/cloudstack/management/management-server.log service cloudstack-management start wait 10 minutes upload the whole file or contents of it to google drive or something similar. What is your umask is set to? Regards ilya On 10/8/14, 1:04 PM, motty cruz wrote: Hello ilya, I was not able to post the entire log file is too big, here is the error msg I see at 6:21 am. http://pastebin.com/raw.php?i=dWxDmR91 Thanks, Motty On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev wrote: Management server log is missing ERROR statements in what you've posted. Please include the full log file. On 10/8/14, 12:23 PM, motty cruz wrote: I am looking in the logs but I can't see to find exactly the error causing this issue. I still getting this error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky wrote: I've had a similar issue when upgrading, but I can't remember exactly how I solved it. I think everything should be in the logs, it was pretty straightforward and quick as far as I remember. Andrei P.S. to revert back you simply stop acs and usage server, restore your database from backups and install the previous acs version. If you've updated any clients, make sure you revert them back as well. - Original Message - From: "motty cruz" To: users@cloudstack.apache.org Sent: Wednesday, 8 October, 2014 6:34:29 PM Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 Thanks Erik, here is the output of netstat -anlp http://pastebin.com/raw.php?i=CJn9i9ci ps aux http://pastebin.com/raw.php?i=uSDJJUDH management-server.log http://pastebin.com/raw.php?i=sSs63jRi Thanks for your support Motty On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber wrote: Post the log on pastebin, also post the output of netstat -anlp ps aux Erik 8. okt. 2014 18:30 skrev "motty cruz" følgende: Hi Erik, I did as you suggested : [root@blaze home]# pkill java [root@blaze home]# service cloudstack-management status cloudstack-management dead but pid file exists The pid file locates at /var/run/cloudstack-management.pid and lock file at /var/lock/subsys/cloudstack-management. Starting cloudstack-management will take care of them or you can manually clean up. [root@blaze home]# service cloudstack-management stop Stopping cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management start Starting cloudstack-management: [ OK ] [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# service cloudstack-management status cloudstack-management (pid 3853) is running... [root@blaze home]# I can't attached the management-server.log apache.org complained about it. On Wed, Oct 8, 2014 at 9:07 AM, Erik Weber wrote: You shouldnt start tomcat, cloudstack will do that for you. Shutdown tomcat and kill any acs related java processes. Then you start cloudstack-management service and post the logs if it fails Erii 8. okt. 2014 15:53 skrev "motty cruz" følgende: I restarted tomcat6 /etc/init.d/tomcat6 restart now I'm getting a blank page no errors any ideas? On Wed, Oct 8, 2014 at 6:34 AM, motty cruz wrote: Hello, I just upgrade Cloudstack from 4.4.0 to 4.4.1, now I'm getting the following error: HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty -- Thanks for your support, Motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Motty, Here's a repo that still has 4.4.0 http://cloudstack.apt-get.eu/rhel/4.4/ You could try to yum downgrade to 4.4.0 and restore your DB. Do take backups before you do that.. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "motty cruz" > To: users@cloudstack.apache.org > Sent: Wednesday, 8 October, 2014 23:31:00 > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > Hi Nux, > I follow this steps to upgrade > > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4/upgrade/upgrade-4.4.html > > here is my cloudstack.repo > > [cloudstack] > name=cloudstack > baseurl=http://cloudstack.apt-get.eu/rhel/4.4/ > enabled=1 > gpgcheck=0 > cloudstack.repo (END) > > Thanks for your help! > > > On Wed, Oct 8, 2014 at 2:40 PM, Nux! wrote: > >> How did you upgrade exactly? >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro >> >> - Original Message - >> > From: "motty cruz" >> > To: users@cloudstack.apache.org >> > Sent: Wednesday, 8 October, 2014 22:31:57 >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 >> >> > can I run "cloudstack-setup-management" would this help? I try to find >> the >> > meaning of this command, >> > >> > On Wed, Oct 8, 2014 at 1:04 PM, motty cruz wrote: >> > >> >> Hello ilya, >> >> I was not able to post the entire log file is too big, >> >> >> >> here is the error msg I see at 6:21 am. >> >> http://pastebin.com/raw.php?i=dWxDmR91 >> >> >> >> >> >> Thanks, >> >> Motty >> >> >> >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < >> >> ilya.mailing.li...@gmail.com> wrote: >> >> >> >>> Management server log is missing ERROR statements in what you've >> posted. >> >>> Please include the full log file. >> >>> >> >>> On 10/8/14, 12:23 PM, motty cruz wrote: >> >>> >> >>>> I am looking in the logs but I can't see to find exactly the error >> >>>> causing >> >>>> this issue. >> >>>> I still getting this error: >> >>>> HTTP Status 404 - >> >>>> -- >> >>>> >> >>>> *type* Status report >> >>>> >> >>>> *message* >> >>>> >> >>>> *description* *The requested resource () is not available.* >> >>>> -- >> >>>> Apache Tomcat/6.0.24 >> >>>> >> >>>> On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky < >> and...@arhont.com> >> >>>> wrote: >> >>>> >> >>>> I've had a similar issue when upgrading, but I can't remember exactly >> >>>>> how >> >>>>> I solved it. I think everything should be in the logs, it was pretty >> >>>>> straightforward and quick as far as I remember. >> >>>>> >> >>>>> Andrei >> >>>>> >> >>>>> P.S. to revert back you simply stop acs and usage server, restore >> your >> >>>>> database from backups and install the previous acs version. If you've >> >>>>> updated any clients, make sure you revert them back as well. >> >>>>> >> >>>>> - Original Message - >> >>>>> >> >>>>> From: "motty cruz" >> >>>>>> To: users@cloudstack.apache.org >> >>>>>> Sent: Wednesday, 8 October, 2014 6:34:29 PM >> >>>>>> Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS >> >>>>>> 4.4.1 >> >>>>>> Thanks Erik, >> >>>>>> here is the output of netstat -anlp >> >>>>>> http://pastebin.com/raw.php?i=CJn9i9ci >> >>>>>> ps aux >> >>>>>> http://pastebin.com/raw.php?i=uSDJJUDH >> >>>>>> management-server.log >> >>>>>> http://pastebin.com/raw.php?i=sSs63jRi >> >>>>>> Thanks for your support >> >>>>>&g
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
very grateful, for your help, I did a backup of database, I apologize for the this but I can't think of the command to restore MySQL backup. Thank you very much. On Wed, Oct 8, 2014 at 3:35 PM, Nux! wrote: > Motty, > > Here's a repo that still has 4.4.0 > http://cloudstack.apt-get.eu/rhel/4.4/ > > You could try to yum downgrade to 4.4.0 and restore your DB. > > Do take backups before you do that.. > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - > > From: "motty cruz" > > To: users@cloudstack.apache.org > > Sent: Wednesday, 8 October, 2014 23:31:00 > > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > > > Hi Nux, > > I follow this steps to upgrade > > > > > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4/upgrade/upgrade-4.4.html > > > > here is my cloudstack.repo > > > > [cloudstack] > > name=cloudstack > > baseurl=http://cloudstack.apt-get.eu/rhel/4.4/ > > enabled=1 > > gpgcheck=0 > > cloudstack.repo (END) > > > > Thanks for your help! > > > > > > On Wed, Oct 8, 2014 at 2:40 PM, Nux! wrote: > > > >> How did you upgrade exactly? > >> > >> -- > >> Sent from the Delta quadrant using Borg technology! > >> > >> Nux! > >> www.nux.ro > >> > >> - Original Message - > >> > From: "motty cruz" > >> > To: users@cloudstack.apache.org > >> > Sent: Wednesday, 8 October, 2014 22:31:57 > >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS > 4.4.1 > >> > >> > can I run "cloudstack-setup-management" would this help? I try to find > >> the > >> > meaning of this command, > >> > > >> > On Wed, Oct 8, 2014 at 1:04 PM, motty cruz > wrote: > >> > > >> >> Hello ilya, > >> >> I was not able to post the entire log file is too big, > >> >> > >> >> here is the error msg I see at 6:21 am. > >> >> http://pastebin.com/raw.php?i=dWxDmR91 > >> >> > >> >> > >> >> Thanks, > >> >> Motty > >> >> > >> >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < > >> >> ilya.mailing.li...@gmail.com> wrote: > >> >> > >> >>> Management server log is missing ERROR statements in what you've > >> posted. > >> >>> Please include the full log file. > >> >>> > >> >>> On 10/8/14, 12:23 PM, motty cruz wrote: > >> >>> > >> >>>> I am looking in the logs but I can't see to find exactly the error > >> >>>> causing > >> >>>> this issue. > >> >>>> I still getting this error: > >> >>>> HTTP Status 404 - > >> >>>> -- > >> >>>> > >> >>>> *type* Status report > >> >>>> > >> >>>> *message* > >> >>>> > >> >>>> *description* *The requested resource () is not available.* > >> >>>> -- > >> >>>> Apache Tomcat/6.0.24 > >> >>>> > >> >>>> On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky < > >> and...@arhont.com> > >> >>>> wrote: > >> >>>> > >> >>>> I've had a similar issue when upgrading, but I can't remember > exactly > >> >>>>> how > >> >>>>> I solved it. I think everything should be in the logs, it was > pretty > >> >>>>> straightforward and quick as far as I remember. > >> >>>>> > >> >>>>> Andrei > >> >>>>> > >> >>>>> P.S. to revert back you simply stop acs and usage server, restore > >> your > >> >>>>> database from backups and install the previous acs version. If > you've > >> >>>>> updated any clients, make sure you revert them back as well. > >> >>>>> > >> >>>>> - Original Message - > >> >>>>> > >> >>>>> From: "motty cruz" > >> >>
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Motty, Roughly it's like this: mysql -ucsuser -pcspass csdb < csdb.sql, the same for cloud_usage and cloudbridge (though these are less critical) PhpMyAdmin or Webmin can be helpful it you are not good with the command line. It's also possible you will have to drop those databases or the tables within altogether to make sure your backup is used and nothing extra. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "motty cruz" > To: users@cloudstack.apache.org > Sent: Wednesday, 8 October, 2014 23:38:34 > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > very grateful, for your help, > > I did a backup of database, I apologize for the this but I can't think of > the command to restore MySQL backup. > > Thank you very much. > > On Wed, Oct 8, 2014 at 3:35 PM, Nux! wrote: > >> Motty, >> >> Here's a repo that still has 4.4.0 >> http://cloudstack.apt-get.eu/rhel/4.4/ >> >> You could try to yum downgrade to 4.4.0 and restore your DB. >> >> Do take backups before you do that.. >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro >> >> ----- Original Message ----- >> > From: "motty cruz" >> > To: users@cloudstack.apache.org >> > Sent: Wednesday, 8 October, 2014 23:31:00 >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 >> >> > Hi Nux, >> > I follow this steps to upgrade >> > >> > >> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4/upgrade/upgrade-4.4.html >> > >> > here is my cloudstack.repo >> > >> > [cloudstack] >> > name=cloudstack >> > baseurl=http://cloudstack.apt-get.eu/rhel/4.4/ >> > enabled=1 >> > gpgcheck=0 >> > cloudstack.repo (END) >> > >> > Thanks for your help! >> > >> > >> > On Wed, Oct 8, 2014 at 2:40 PM, Nux! wrote: >> > >> >> How did you upgrade exactly? >> >> >> >> -- >> >> Sent from the Delta quadrant using Borg technology! >> >> >> >> Nux! >> >> www.nux.ro >> >> >> >> - Original Message - >> >> > From: "motty cruz" >> >> > To: users@cloudstack.apache.org >> >> > Sent: Wednesday, 8 October, 2014 22:31:57 >> >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS >> 4.4.1 >> >> >> >> > can I run "cloudstack-setup-management" would this help? I try to find >> >> the >> >> > meaning of this command, >> >> > >> >> > On Wed, Oct 8, 2014 at 1:04 PM, motty cruz >> wrote: >> >> > >> >> >> Hello ilya, >> >> >> I was not able to post the entire log file is too big, >> >> >> >> >> >> here is the error msg I see at 6:21 am. >> >> >> http://pastebin.com/raw.php?i=dWxDmR91 >> >> >> >> >> >> >> >> >> Thanks, >> >> >> Motty >> >> >> >> >> >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < >> >> >> ilya.mailing.li...@gmail.com> wrote: >> >> >> >> >> >>> Management server log is missing ERROR statements in what you've >> >> posted. >> >> >>> Please include the full log file. >> >> >>> >> >> >>> On 10/8/14, 12:23 PM, motty cruz wrote: >> >> >>> >> >> >>>> I am looking in the logs but I can't see to find exactly the error >> >> >>>> causing >> >> >>>> this issue. >> >> >>>> I still getting this error: >> >> >>>> HTTP Status 404 - >> >> >>>> ------ >> >> >>>> >> >> >>>> *type* Status report >> >> >>>> >> >> >>>> *message* >> >> >>>> >> >> >>>> *description* *The requested resource () is not available.* >> >> >>>> -- >> >> >>>> Apache Tomcat/6.0.24 >> >> >>>> >> >> >>>> On Wed, Oct 8, 2014 at 12:09 PM, Andrei
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Hi ilya, here is the management-server.log as you suggest, I waited 10 minutes http://pastebin.com/raw.php?i=AiYXmxSU my umask 002 cat /etc/profile Thank you very much. On Wed, Oct 8, 2014 at 3:32 PM, ilya musayev wrote: > Motty, > > The error you see about not being able to connect to a host on port 9090 > is normal when the management server is starting. There must be another > error or warning somewhere. > > Please try the steps below to shrink the log file to manageable size and > upload the file to some file sharing site if paste bin restricts you. > > service cloudstack-management stop > cat /dev/null > /var/log/cloudstack/management/management-server.log > service cloudstack-management start > > wait 10 minutes > upload the whole file or contents of it to google drive or something > similar. > > What is your umask is set to? > > Regards > ilya > > On 10/8/14, 1:04 PM, motty cruz wrote: > >> Hello ilya, >> I was not able to post the entire log file is too big, >> >> here is the error msg I see at 6:21 am. >> http://pastebin.com/raw.php?i=dWxDmR91 >> >> >> Thanks, >> Motty >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < >> ilya.mailing.li...@gmail.com> >> wrote: >> >> Management server log is missing ERROR statements in what you've posted. >>> Please include the full log file. >>> >>> On 10/8/14, 12:23 PM, motty cruz wrote: >>> >>> I am looking in the logs but I can't see to find exactly the error >>>> causing >>>> this issue. >>>> I still getting this error: >>>> HTTP Status 404 - >>>> -- >>>> >>>> *type* Status report >>>> >>>> *message* >>>> >>>> *description* *The requested resource () is not available.* >>>> -- >>>> Apache Tomcat/6.0.24 >>>> >>>> On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky >>> > >>>> wrote: >>>> >>>> I've had a similar issue when upgrading, but I can't remember exactly >>>> how >>>> >>>>> I solved it. I think everything should be in the logs, it was pretty >>>>> straightforward and quick as far as I remember. >>>>> >>>>> Andrei >>>>> >>>>> P.S. to revert back you simply stop acs and usage server, restore your >>>>> database from backups and install the previous acs version. If you've >>>>> updated any clients, make sure you revert them back as well. >>>>> >>>>> - Original Message - >>>>> >>>>> From: "motty cruz" >>>>> >>>>>> To: users@cloudstack.apache.org >>>>>> Sent: Wednesday, 8 October, 2014 6:34:29 PM >>>>>> Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS >>>>>> 4.4.1 >>>>>> Thanks Erik, >>>>>> here is the output of netstat -anlp >>>>>> http://pastebin.com/raw.php?i=CJn9i9ci >>>>>> ps aux >>>>>> http://pastebin.com/raw.php?i=uSDJJUDH >>>>>> management-server.log >>>>>> http://pastebin.com/raw.php?i=sSs63jRi >>>>>> Thanks for your support >>>>>> Motty >>>>>> On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber >>>>>> wrote: >>>>>> >>>>>> Post the log on pastebin, also post the output of >>>>>>> >>>>>>> netstat -anlp >>>>>>> ps aux >>>>>>> >>>>>>> Erik >>>>>>> 8. okt. 2014 18:30 skrev "motty cruz" >>>>>>> følgende: >>>>>>> >>>>>>> Hi Erik, >>>>>>> >>>>>>>> I did as you suggested : >>>>>>>> [root@blaze home]# pkill java >>>>>>>> [root@blaze home]# service cloudstack-management status >>>>>>>> cloudstack-management dead but pid file exists >>>>>>>> The pid file locates at /var/run/cloudstack-management.pid and >>>>>>>> lock file >>>>>>>> >>>>>>>> at >>>>>>> >>>>>>> /var/lock/subsys/cloudstack-management. >>>>>>>> Starting cloud
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
I tried to downgrade, here is the command that I used: yum downgrade cloudstack-management now I'm getting this errors: ---> Package cloudstack-management.x86_64 0:4.4.1-NONOSS_1.el6 will be erased --> Finished Dependency Resolution Error: Package: cloudstack-awsapi-4.4.1-NONOSS_1.el6.x86_64 (@cloudstack) Requires: cloudstack-management = 4.4.1 Removing: cloudstack-management-4.4.1-NONOSS_1.el6.x86_64 (@cloudstack) cloudstack-management = 4.4.1-NONOSS_1.el6 Downgraded By: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 (cloudstack) cloudstack-management = 4.4.0-NONOSS_3.el6 Error: Package: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 (cloudstack) Requires: cloudstack-awsapi = 4.4.0 Installed: cloudstack-awsapi-4.4.1-NONOSS_1.el6.x86_64 (@cloudstack) cloudstack-awsapi = 4.4.1-NONOSS_1.el6 Available: cloudstack-awsapi-4.4.0-NONOSS_3.el6.x86_64 (cloudstack) cloudstack-awsapi = 4.4.0-NONOSS_3.el6 Error: Package: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 (cloudstack) Requires: cloudstack-common = 4.4.0 Installed: cloudstack-common-4.4.1-NONOSS_1.el6.x86_64 (@cloudstack) cloudstack-common = 4.4.1-NONOSS_1.el6 Available: cloudstack-common-4.4.0-NONOSS_3.el6.x86_64 (cloudstack) cloudstack-common = 4.4.0-NONOSS_3.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@blaze home]# please help! On Wed, Oct 8, 2014 at 3:35 PM, Nux! wrote: > Motty, > > Here's a repo that still has 4.4.0 > http://cloudstack.apt-get.eu/rhel/4.4/ > > You could try to yum downgrade to 4.4.0 and restore your DB. > > Do take backups before you do that.. > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - > > From: "motty cruz" > > To: users@cloudstack.apache.org > > Sent: Wednesday, 8 October, 2014 23:31:00 > > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > > > Hi Nux, > > I follow this steps to upgrade > > > > > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4/upgrade/upgrade-4.4.html > > > > here is my cloudstack.repo > > > > [cloudstack] > > name=cloudstack > > baseurl=http://cloudstack.apt-get.eu/rhel/4.4/ > > enabled=1 > > gpgcheck=0 > > cloudstack.repo (END) > > > > Thanks for your help! > > > > > > On Wed, Oct 8, 2014 at 2:40 PM, Nux! wrote: > > > >> How did you upgrade exactly? > >> > >> -- > >> Sent from the Delta quadrant using Borg technology! > >> > >> Nux! > >> www.nux.ro > >> > >> - Original Message - > >> > From: "motty cruz" > >> > To: users@cloudstack.apache.org > >> > Sent: Wednesday, 8 October, 2014 22:31:57 > >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS > 4.4.1 > >> > >> > can I run "cloudstack-setup-management" would this help? I try to find > >> the > >> > meaning of this command, > >> > > >> > On Wed, Oct 8, 2014 at 1:04 PM, motty cruz > wrote: > >> > > >> >> Hello ilya, > >> >> I was not able to post the entire log file is too big, > >> >> > >> >> here is the error msg I see at 6:21 am. > >> >> http://pastebin.com/raw.php?i=dWxDmR91 > >> >> > >> >> > >> >> Thanks, > >> >> Motty > >> >> > >> >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < > >> >> ilya.mailing.li...@gmail.com> wrote: > >> >> > >> >>> Management server log is missing ERROR statements in what you've > >> posted. > >> >>> Please include the full log file. > >> >>> > >> >>> On 10/8/14, 12:23 PM, motty cruz wrote: > >> >>> > >> >>>> I am looking in the logs but I can't see to find exactly the error > >> >>>> causing > >> >>>> this issue. > >> >>>> I still getting this error: > >> >>>> HTTP Status 404 - > >> >>>> -- > >> >>>> > >> >>>> *type* Status report > >> >>>> > >> >>>> *message* > >> >>>> > >> >>>> *descri
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Try: yum downgrade cloudstack-\* -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "motty cruz" > To: users@cloudstack.apache.org > Sent: Thursday, 9 October, 2014 14:53:07 > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > I tried to downgrade, here is the command that I used: yum downgrade > cloudstack-management now I'm getting this errors: > ---> Package cloudstack-management.x86_64 0:4.4.1-NONOSS_1.el6 will be > erased > --> Finished Dependency Resolution > Error: Package: cloudstack-awsapi-4.4.1-NONOSS_1.el6.x86_64 (@cloudstack) > Requires: cloudstack-management = 4.4.1 > Removing: cloudstack-management-4.4.1-NONOSS_1.el6.x86_64 > (@cloudstack) > cloudstack-management = 4.4.1-NONOSS_1.el6 > Downgraded By: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 > (cloudstack) > cloudstack-management = 4.4.0-NONOSS_3.el6 > Error: Package: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 (cloudstack) > Requires: cloudstack-awsapi = 4.4.0 > Installed: cloudstack-awsapi-4.4.1-NONOSS_1.el6.x86_64 > (@cloudstack) > cloudstack-awsapi = 4.4.1-NONOSS_1.el6 > Available: cloudstack-awsapi-4.4.0-NONOSS_3.el6.x86_64 > (cloudstack) > cloudstack-awsapi = 4.4.0-NONOSS_3.el6 > Error: Package: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 (cloudstack) > Requires: cloudstack-common = 4.4.0 > Installed: cloudstack-common-4.4.1-NONOSS_1.el6.x86_64 > (@cloudstack) > cloudstack-common = 4.4.1-NONOSS_1.el6 > Available: cloudstack-common-4.4.0-NONOSS_3.el6.x86_64 > (cloudstack) > cloudstack-common = 4.4.0-NONOSS_3.el6 > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest > [root@blaze home]# > > please help! > > On Wed, Oct 8, 2014 at 3:35 PM, Nux! wrote: > >> Motty, >> >> Here's a repo that still has 4.4.0 >> http://cloudstack.apt-get.eu/rhel/4.4/ >> >> You could try to yum downgrade to 4.4.0 and restore your DB. >> >> Do take backups before you do that.. >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro >> >> - Original Message - >> > From: "motty cruz" >> > To: users@cloudstack.apache.org >> > Sent: Wednesday, 8 October, 2014 23:31:00 >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 >> >> > Hi Nux, >> > I follow this steps to upgrade >> > >> > >> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4/upgrade/upgrade-4.4.html >> > >> > here is my cloudstack.repo >> > >> > [cloudstack] >> > name=cloudstack >> > baseurl=http://cloudstack.apt-get.eu/rhel/4.4/ >> > enabled=1 >> > gpgcheck=0 >> > cloudstack.repo (END) >> > >> > Thanks for your help! >> > >> > >> > On Wed, Oct 8, 2014 at 2:40 PM, Nux! wrote: >> > >> >> How did you upgrade exactly? >> >> >> >> -- >> >> Sent from the Delta quadrant using Borg technology! >> >> >> >> Nux! >> >> www.nux.ro >> >> >> >> - Original Message - >> >> > From: "motty cruz" >> >> > To: users@cloudstack.apache.org >> >> > Sent: Wednesday, 8 October, 2014 22:31:57 >> >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS >> 4.4.1 >> >> >> >> > can I run "cloudstack-setup-management" would this help? I try to find >> >> the >> >> > meaning of this command, >> >> > >> >> > On Wed, Oct 8, 2014 at 1:04 PM, motty cruz >> wrote: >> >> > >> >> >> Hello ilya, >> >> >> I was not able to post the entire log file is too big, >> >> >> >> >> >> here is the error msg I see at 6:21 am. >> >> >> http://pastebin.com/raw.php?i=dWxDmR91 >> >> >> >> >> >> >> >> >> Thanks, >> >> >> Motty >> >> >> >> >> >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < >> >> >> ilya.mailing.li...@gmail.com> wrote: >> >> >> >> >> >>> Management server log is m
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Thanks that worked! I was able to downgrade packages to cloudstack-management-4.4.0 but I still getting same error message. I am going to loose my sense, HTTP Status 404 - -- *type* Status report *message* *description* *The requested resource () is not available.* -- Apache Tomcat/6.0.24 Please help! On Thu, Oct 9, 2014 at 7:08 AM, Nux! wrote: > Try: > > yum downgrade cloudstack-\* > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - > > From: "motty cruz" > > To: users@cloudstack.apache.org > > Sent: Thursday, 9 October, 2014 14:53:07 > > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > > > I tried to downgrade, here is the command that I used: yum downgrade > > cloudstack-management now I'm getting this errors: > > ---> Package cloudstack-management.x86_64 0:4.4.1-NONOSS_1.el6 will be > > erased > > --> Finished Dependency Resolution > > Error: Package: cloudstack-awsapi-4.4.1-NONOSS_1.el6.x86_64 (@cloudstack) > > Requires: cloudstack-management = 4.4.1 > > Removing: cloudstack-management-4.4.1-NONOSS_1.el6.x86_64 > > (@cloudstack) > > cloudstack-management = 4.4.1-NONOSS_1.el6 > > Downgraded By: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 > > (cloudstack) > > cloudstack-management = 4.4.0-NONOSS_3.el6 > > Error: Package: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 > (cloudstack) > > Requires: cloudstack-awsapi = 4.4.0 > > Installed: cloudstack-awsapi-4.4.1-NONOSS_1.el6.x86_64 > > (@cloudstack) > > cloudstack-awsapi = 4.4.1-NONOSS_1.el6 > > Available: cloudstack-awsapi-4.4.0-NONOSS_3.el6.x86_64 > > (cloudstack) > > cloudstack-awsapi = 4.4.0-NONOSS_3.el6 > > Error: Package: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 > (cloudstack) > > Requires: cloudstack-common = 4.4.0 > > Installed: cloudstack-common-4.4.1-NONOSS_1.el6.x86_64 > > (@cloudstack) > > cloudstack-common = 4.4.1-NONOSS_1.el6 > > Available: cloudstack-common-4.4.0-NONOSS_3.el6.x86_64 > > (cloudstack) > > cloudstack-common = 4.4.0-NONOSS_3.el6 > > You could try using --skip-broken to work around the problem > > You could try running: rpm -Va --nofiles --nodigest > > [root@blaze home]# > > > > please help! > > > > On Wed, Oct 8, 2014 at 3:35 PM, Nux! wrote: > > > >> Motty, > >> > >> Here's a repo that still has 4.4.0 > >> http://cloudstack.apt-get.eu/rhel/4.4/ > >> > >> You could try to yum downgrade to 4.4.0 and restore your DB. > >> > >> Do take backups before you do that.. > >> > >> -- > >> Sent from the Delta quadrant using Borg technology! > >> > >> Nux! > >> www.nux.ro > >> > >> - Original Message - > >> > From: "motty cruz" > >> > To: users@cloudstack.apache.org > >> > Sent: Wednesday, 8 October, 2014 23:31:00 > >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS > 4.4.1 > >> > >> > Hi Nux, > >> > I follow this steps to upgrade > >> > > >> > > >> > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4/upgrade/upgrade-4.4.html > >> > > >> > here is my cloudstack.repo > >> > > >> > [cloudstack] > >> > name=cloudstack > >> > baseurl=http://cloudstack.apt-get.eu/rhel/4.4/ > >> > enabled=1 > >> > gpgcheck=0 > >> > cloudstack.repo (END) > >> > > >> > Thanks for your help! > >> > > >> > > >> > On Wed, Oct 8, 2014 at 2:40 PM, Nux! wrote: > >> > > >> >> How did you upgrade exactly? > >> >> > >> >> -- > >> >> Sent from the Delta quadrant using Borg technology! > >> >> > >> >> Nux! > >> >> www.nux.ro > >> >> > >> >> - Original Message - > >> >> > From: "motty cruz" > >> >> > To: users@cloudstack.apache.org > >> >> > Sent: Wednesday, 8 October, 2014 22:31:57 > >> >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS > >> 4.4.1 > >> >> > &g
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
What I would do next is to restore /etc/cloudstack on the management server from the backups and also the DB. To be 100% sure you are using the old one, just drop the DBs and restore from backups. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "motty cruz" > To: users@cloudstack.apache.org > Sent: Thursday, 9 October, 2014 15:46:50 > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > Thanks that worked! I was able to downgrade packages to > cloudstack-management-4.4.0 but I still getting same error message. > > I am going to loose my sense, > > HTTP Status 404 - > -- > > *type* Status report > > *message* > > *description* *The requested resource () is not available.* > -- > Apache Tomcat/6.0.24 > > Please help! > > On Thu, Oct 9, 2014 at 7:08 AM, Nux! wrote: > >> Try: >> >> yum downgrade cloudstack-\* >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro >> >> - Original Message ----- >> > From: "motty cruz" >> > To: users@cloudstack.apache.org >> > Sent: Thursday, 9 October, 2014 14:53:07 >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 >> >> > I tried to downgrade, here is the command that I used: yum downgrade >> > cloudstack-management now I'm getting this errors: >> > ---> Package cloudstack-management.x86_64 0:4.4.1-NONOSS_1.el6 will be >> > erased >> > --> Finished Dependency Resolution >> > Error: Package: cloudstack-awsapi-4.4.1-NONOSS_1.el6.x86_64 (@cloudstack) >> > Requires: cloudstack-management = 4.4.1 >> > Removing: cloudstack-management-4.4.1-NONOSS_1.el6.x86_64 >> > (@cloudstack) >> > cloudstack-management = 4.4.1-NONOSS_1.el6 >> > Downgraded By: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 >> > (cloudstack) >> > cloudstack-management = 4.4.0-NONOSS_3.el6 >> > Error: Package: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 >> (cloudstack) >> > Requires: cloudstack-awsapi = 4.4.0 >> > Installed: cloudstack-awsapi-4.4.1-NONOSS_1.el6.x86_64 >> > (@cloudstack) >> > cloudstack-awsapi = 4.4.1-NONOSS_1.el6 >> > Available: cloudstack-awsapi-4.4.0-NONOSS_3.el6.x86_64 >> > (cloudstack) >> > cloudstack-awsapi = 4.4.0-NONOSS_3.el6 >> > Error: Package: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 >> (cloudstack) >> > Requires: cloudstack-common = 4.4.0 >> > Installed: cloudstack-common-4.4.1-NONOSS_1.el6.x86_64 >> > (@cloudstack) >> > cloudstack-common = 4.4.1-NONOSS_1.el6 >> > Available: cloudstack-common-4.4.0-NONOSS_3.el6.x86_64 >> > (cloudstack) >> > cloudstack-common = 4.4.0-NONOSS_3.el6 >> > You could try using --skip-broken to work around the problem >> > You could try running: rpm -Va --nofiles --nodigest >> > [root@blaze home]# >> > >> > please help! >> > >> > On Wed, Oct 8, 2014 at 3:35 PM, Nux! wrote: >> > >> >> Motty, >> >> >> >> Here's a repo that still has 4.4.0 >> >> http://cloudstack.apt-get.eu/rhel/4.4/ >> >> >> >> You could try to yum downgrade to 4.4.0 and restore your DB. >> >> >> >> Do take backups before you do that.. >> >> >> >> -- >> >> Sent from the Delta quadrant using Borg technology! >> >> >> >> Nux! >> >> www.nux.ro >> >> >> >> - Original Message - >> >> > From: "motty cruz" >> >> > To: users@cloudstack.apache.org >> >> > Sent: Wednesday, 8 October, 2014 23:31:00 >> >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS >> 4.4.1 >> >> >> >> > Hi Nux, >> >> > I follow this steps to upgrade >> >> > >> >> > >> >> >> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4/upgrade/upgrade-4.4.html >> >> > >> >> > here is my cloudstack.repo >> >> > >> >> > [cloudstack] >> >> > name=cloudstack >> >> > baseurl=http://cloudstack.apt-get
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Thank you very much Nux, that was the trick, here is what I did to fixed it: mysql -u root -pmypassword -e "DROP DATABASE cloud" mysql -u root -pmypassword -e "CREATE DATABASE cloud" mysql -u root -pmypassword -h localhost cloud < cloud-backup_2014-10-08.sql now successfully downgrade to Cloudstack-Managment 4.4.0, Thank you all for your help and your support, I was under intensive heat, you guys helped me very much. -Motty On Thu, Oct 9, 2014 at 7:49 AM, Nux! wrote: > What I would do next is to restore /etc/cloudstack on the management > server from the backups and also the DB. To be 100% sure you are using the > old one, just drop the DBs and restore from backups. > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - > > From: "motty cruz" > > To: users@cloudstack.apache.org > > Sent: Thursday, 9 October, 2014 15:46:50 > > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > > > Thanks that worked! I was able to downgrade packages to > > cloudstack-management-4.4.0 but I still getting same error message. > > > > I am going to loose my sense, > > > > HTTP Status 404 - > > -- > > > > *type* Status report > > > > *message* > > > > *description* *The requested resource () is not available.* > > -- > > Apache Tomcat/6.0.24 > > > > Please help! > > > > On Thu, Oct 9, 2014 at 7:08 AM, Nux! wrote: > > > >> Try: > >> > >> yum downgrade cloudstack-\* > >> > >> -- > >> Sent from the Delta quadrant using Borg technology! > >> > >> Nux! > >> www.nux.ro > >> > >> - Original Message - > >> > From: "motty cruz" > >> > To: users@cloudstack.apache.org > >> > Sent: Thursday, 9 October, 2014 14:53:07 > >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS > 4.4.1 > >> > >> > I tried to downgrade, here is the command that I used: yum downgrade > >> > cloudstack-management now I'm getting this errors: > >> > ---> Package cloudstack-management.x86_64 0:4.4.1-NONOSS_1.el6 will be > >> > erased > >> > --> Finished Dependency Resolution > >> > Error: Package: cloudstack-awsapi-4.4.1-NONOSS_1.el6.x86_64 > (@cloudstack) > >> > Requires: cloudstack-management = 4.4.1 > >> > Removing: cloudstack-management-4.4.1-NONOSS_1.el6.x86_64 > >> > (@cloudstack) > >> > cloudstack-management = 4.4.1-NONOSS_1.el6 > >> > Downgraded By: > cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 > >> > (cloudstack) > >> > cloudstack-management = 4.4.0-NONOSS_3.el6 > >> > Error: Package: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 > >> (cloudstack) > >> > Requires: cloudstack-awsapi = 4.4.0 > >> > Installed: cloudstack-awsapi-4.4.1-NONOSS_1.el6.x86_64 > >> > (@cloudstack) > >> > cloudstack-awsapi = 4.4.1-NONOSS_1.el6 > >> > Available: cloudstack-awsapi-4.4.0-NONOSS_3.el6.x86_64 > >> > (cloudstack) > >> > cloudstack-awsapi = 4.4.0-NONOSS_3.el6 > >> > Error: Package: cloudstack-management-4.4.0-NONOSS_3.el6.x86_64 > >> (cloudstack) > >> > Requires: cloudstack-common = 4.4.0 > >> > Installed: cloudstack-common-4.4.1-NONOSS_1.el6.x86_64 > >> > (@cloudstack) > >> > cloudstack-common = 4.4.1-NONOSS_1.el6 > >> > Available: cloudstack-common-4.4.0-NONOSS_3.el6.x86_64 > >> > (cloudstack) > >> > cloudstack-common = 4.4.0-NONOSS_3.el6 > >> > You could try using --skip-broken to work around the problem > >> > You could try running: rpm -Va --nofiles --nodigest > >> > [root@blaze home]# > >> > > >> > please help! > >> > > >> > On Wed, Oct 8, 2014 at 3:35 PM, Nux! wrote: > >> > > >> >> Motty, > >> >> > >> >> Here's a repo that still has 4.4.0 > >> >> http://cloudstack.apt-get.eu/rhel/4.4/ > >> >> > >> >> You could try to yum downgrade to 4.4.0 and restore your DB. > >> >> > >> >> Do take backups before you do that.. > >> >> > >>
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
I generally experience this if there is a wrong configuration setting. Did you change anything before upgrading? Erik 9. okt. 2014 00:49 skrev "motty cruz" følgende: > Hi ilya, > here is the management-server.log as you suggest, I waited 10 minutes > http://pastebin.com/raw.php?i=AiYXmxSU > > my umask 002 > cat /etc/profile > > Thank you very much. > > On Wed, Oct 8, 2014 at 3:32 PM, ilya musayev > > wrote: > > > Motty, > > > > The error you see about not being able to connect to a host on port 9090 > > is normal when the management server is starting. There must be another > > error or warning somewhere. > > > > Please try the steps below to shrink the log file to manageable size and > > upload the file to some file sharing site if paste bin restricts you. > > > > service cloudstack-management stop > > cat /dev/null > /var/log/cloudstack/management/management-server.log > > service cloudstack-management start > > > > wait 10 minutes > > upload the whole file or contents of it to google drive or something > > similar. > > > > What is your umask is set to? > > > > Regards > > ilya > > > > On 10/8/14, 1:04 PM, motty cruz wrote: > > > >> Hello ilya, > >> I was not able to post the entire log file is too big, > >> > >> here is the error msg I see at 6:21 am. > >> http://pastebin.com/raw.php?i=dWxDmR91 > >> > >> > >> Thanks, > >> Motty > >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < > >> ilya.mailing.li...@gmail.com> > >> wrote: > >> > >> Management server log is missing ERROR statements in what you've > posted. > >>> Please include the full log file. > >>> > >>> On 10/8/14, 12:23 PM, motty cruz wrote: > >>> > >>> I am looking in the logs but I can't see to find exactly the error > >>>> causing > >>>> this issue. > >>>> I still getting this error: > >>>> HTTP Status 404 - > >>>> -- > >>>> > >>>> *type* Status report > >>>> > >>>> *message* > >>>> > >>>> *description* *The requested resource () is not available.* > >>>> -- > >>>> Apache Tomcat/6.0.24 > >>>> > >>>> On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky < > and...@arhont.com > >>>> > > >>>> wrote: > >>>> > >>>> I've had a similar issue when upgrading, but I can't remember > exactly > >>>> how > >>>> > >>>>> I solved it. I think everything should be in the logs, it was pretty > >>>>> straightforward and quick as far as I remember. > >>>>> > >>>>> Andrei > >>>>> > >>>>> P.S. to revert back you simply stop acs and usage server, restore > your > >>>>> database from backups and install the previous acs version. If you've > >>>>> updated any clients, make sure you revert them back as well. > >>>>> > >>>>> - Original Message - > >>>>> > >>>>> From: "motty cruz" > >>>>> > >>>>>> To: users@cloudstack.apache.org > >>>>>> Sent: Wednesday, 8 October, 2014 6:34:29 PM > >>>>>> Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS > >>>>>> 4.4.1 > >>>>>> Thanks Erik, > >>>>>> here is the output of netstat -anlp > >>>>>> http://pastebin.com/raw.php?i=CJn9i9ci > >>>>>> ps aux > >>>>>> http://pastebin.com/raw.php?i=uSDJJUDH > >>>>>> management-server.log > >>>>>> http://pastebin.com/raw.php?i=sSs63jRi > >>>>>> Thanks for your support > >>>>>> Motty > >>>>>> On Wed, Oct 8, 2014 at 10:00 AM, Erik Weber > >>>>>> wrote: > >>>>>> > >>>>>> Post the log on pastebin, also post the output of > >>>>>>> > >>>>>>> netstat -anlp > >>>>>>> ps aux > >>>>>>> > >>>>>>> Erik > >>>>>>> 8. okt. 2014 18:30 skrev "motty
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Erik, I did not change anything before or after upgrading Cloudstack-management 4.4.0. I followed the steps below to the exact words. http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.1/upgrade/upgrade-4.4.html now I believe it was an issue with the Database, maybe the scheme was not upgraded? I am running database on a different server. Any ideas? I really would like to upgrade to latest package to be able to use Windows templates. at this moment I can't create instances from windows templates. Thanks Motty On Thu, Oct 9, 2014 at 8:06 AM, Erik Weber wrote: > I generally experience this if there is a wrong configuration setting. > > Did you change anything before upgrading? > > Erik > 9. okt. 2014 00:49 skrev "motty cruz" følgende: > > > Hi ilya, > > here is the management-server.log as you suggest, I waited 10 minutes > > http://pastebin.com/raw.php?i=AiYXmxSU > > > > my umask 002 > > cat /etc/profile > > > > Thank you very much. > > > > On Wed, Oct 8, 2014 at 3:32 PM, ilya musayev < > ilya.mailing.li...@gmail.com > > > > > wrote: > > > > > Motty, > > > > > > The error you see about not being able to connect to a host on port > 9090 > > > is normal when the management server is starting. There must be another > > > error or warning somewhere. > > > > > > Please try the steps below to shrink the log file to manageable size > and > > > upload the file to some file sharing site if paste bin restricts you. > > > > > > service cloudstack-management stop > > > cat /dev/null > /var/log/cloudstack/management/management-server.log > > > service cloudstack-management start > > > > > > wait 10 minutes > > > upload the whole file or contents of it to google drive or something > > > similar. > > > > > > What is your umask is set to? > > > > > > Regards > > > ilya > > > > > > On 10/8/14, 1:04 PM, motty cruz wrote: > > > > > >> Hello ilya, > > >> I was not able to post the entire log file is too big, > > >> > > >> here is the error msg I see at 6:21 am. > > >> http://pastebin.com/raw.php?i=dWxDmR91 > > >> > > >> > > >> Thanks, > > >> Motty > > >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < > > >> ilya.mailing.li...@gmail.com> > > >> wrote: > > >> > > >> Management server log is missing ERROR statements in what you've > > posted. > > >>> Please include the full log file. > > >>> > > >>> On 10/8/14, 12:23 PM, motty cruz wrote: > > >>> > > >>> I am looking in the logs but I can't see to find exactly the error > > >>>> causing > > >>>> this issue. > > >>>> I still getting this error: > > >>>> HTTP Status 404 - > > >>>> -- > > >>>> > > >>>> *type* Status report > > >>>> > > >>>> *message* > > >>>> > > >>>> *description* *The requested resource () is not available.* > > >>>> -- > > >>>> Apache Tomcat/6.0.24 > > >>>> > > >>>> On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky < > > and...@arhont.com > > >>>> > > > >>>> wrote: > > >>>> > > >>>> I've had a similar issue when upgrading, but I can't remember > > exactly > > >>>> how > > >>>> > > >>>>> I solved it. I think everything should be in the logs, it was > pretty > > >>>>> straightforward and quick as far as I remember. > > >>>>> > > >>>>> Andrei > > >>>>> > > >>>>> P.S. to revert back you simply stop acs and usage server, restore > > your > > >>>>> database from backups and install the previous acs version. If > you've > > >>>>> updated any clients, make sure you revert them back as well. > > >>>>> > > >>>>> - Original Message - > > >>>>> > > >>>>> From: "motty cruz" > > >>>>> > > >>>>>> To: users@cloudstack.apache.org > > >>>>&
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Motty, On which hypervisor are you on? I've never had problems with Windows templates (on kvm). -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "motty cruz" > To: users@cloudstack.apache.org > Sent: Thursday, 9 October, 2014 16:11:12 > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > Erik, I did not change anything before or after upgrading > Cloudstack-management 4.4.0. I followed the steps below to the exact words. > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.1/upgrade/upgrade-4.4.html > > now I believe it was an issue with the Database, maybe the scheme was not > upgraded? I am running database on a different server. Any ideas? I really > would like to upgrade to latest package to be able to use Windows > templates. at this moment I can't create instances from windows templates. > > Thanks > Motty > > On Thu, Oct 9, 2014 at 8:06 AM, Erik Weber wrote: > >> I generally experience this if there is a wrong configuration setting. >> >> Did you change anything before upgrading? >> >> Erik >> 9. okt. 2014 00:49 skrev "motty cruz" følgende: >> >> > Hi ilya, >> > here is the management-server.log as you suggest, I waited 10 minutes >> > http://pastebin.com/raw.php?i=AiYXmxSU >> > >> > my umask 002 >> > cat /etc/profile >> > >> > Thank you very much. >> > >> > On Wed, Oct 8, 2014 at 3:32 PM, ilya musayev < >> ilya.mailing.li...@gmail.com >> > > >> > wrote: >> > >> > > Motty, >> > > >> > > The error you see about not being able to connect to a host on port >> 9090 >> > > is normal when the management server is starting. There must be another >> > > error or warning somewhere. >> > > >> > > Please try the steps below to shrink the log file to manageable size >> and >> > > upload the file to some file sharing site if paste bin restricts you. >> > > >> > > service cloudstack-management stop >> > > cat /dev/null > /var/log/cloudstack/management/management-server.log >> > > service cloudstack-management start >> > > >> > > wait 10 minutes >> > > upload the whole file or contents of it to google drive or something >> > > similar. >> > > >> > > What is your umask is set to? >> > > >> > > Regards >> > > ilya >> > > >> > > On 10/8/14, 1:04 PM, motty cruz wrote: >> > > >> > >> Hello ilya, >> > >> I was not able to post the entire log file is too big, >> > >> >> > >> here is the error msg I see at 6:21 am. >> > >> http://pastebin.com/raw.php?i=dWxDmR91 >> > >> >> > >> >> > >> Thanks, >> > >> Motty >> > >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < >> > >> ilya.mailing.li...@gmail.com> >> > >> wrote: >> > >> >> > >> Management server log is missing ERROR statements in what you've >> > posted. >> > >>> Please include the full log file. >> > >>> >> > >>> On 10/8/14, 12:23 PM, motty cruz wrote: >> > >>> >> > >>> I am looking in the logs but I can't see to find exactly the error >> > >>>> causing >> > >>>> this issue. >> > >>>> I still getting this error: >> > >>>> HTTP Status 404 - >> > >>>> -- >> > >>>> >> > >>>> *type* Status report >> > >>>> >> > >>>> *message* >> > >>>> >> > >>>> *description* *The requested resource () is not available.* >> > >>>> -- >> > >>>> Apache Tomcat/6.0.24 >> > >>>> >> > >>>> On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky < >> > and...@arhont.com >> > >>>> > >> > >>>> wrote: >> > >>>> >> > >>>> I've had a similar issue when upgrading, but I can't remember >> > exactly >> > >>>> how >> > >>>> >> > >>>>> I solved it. I think
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Nux, I am using XenServer 6.2, everything seem to be working fine except Windows Server 2012 templates. I have a testing cluster made up of personal PC, XenServer 6.2 ACS 4.40 using NFS as primary and secondary storage and windows server 2012 templates work like a charm, that is the reason I decided to upgrade. Thanks, Motty On Thu, Oct 9, 2014 at 8:36 AM, Nux! wrote: > Motty, > > On which hypervisor are you on? I've never had problems with Windows > templates (on kvm). > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - > > From: "motty cruz" > > To: users@cloudstack.apache.org > > Sent: Thursday, 9 October, 2014 16:11:12 > > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > > > Erik, I did not change anything before or after upgrading > > Cloudstack-management 4.4.0. I followed the steps below to the exact > words. > > > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.1/upgrade/upgrade-4.4.html > > > > now I believe it was an issue with the Database, maybe the scheme was not > > upgraded? I am running database on a different server. Any ideas? I > really > > would like to upgrade to latest package to be able to use Windows > > templates. at this moment I can't create instances from windows > templates. > > > > Thanks > > Motty > > > > On Thu, Oct 9, 2014 at 8:06 AM, Erik Weber wrote: > > > >> I generally experience this if there is a wrong configuration setting. > >> > >> Did you change anything before upgrading? > >> > >> Erik > >> 9. okt. 2014 00:49 skrev "motty cruz" følgende: > >> > >> > Hi ilya, > >> > here is the management-server.log as you suggest, I waited 10 minutes > >> > http://pastebin.com/raw.php?i=AiYXmxSU > >> > > >> > my umask 002 > >> > cat /etc/profile > >> > > >> > Thank you very much. > >> > > >> > On Wed, Oct 8, 2014 at 3:32 PM, ilya musayev < > >> ilya.mailing.li...@gmail.com > >> > > > >> > wrote: > >> > > >> > > Motty, > >> > > > >> > > The error you see about not being able to connect to a host on port > >> 9090 > >> > > is normal when the management server is starting. There must be > another > >> > > error or warning somewhere. > >> > > > >> > > Please try the steps below to shrink the log file to manageable size > >> and > >> > > upload the file to some file sharing site if paste bin restricts > you. > >> > > > >> > > service cloudstack-management stop > >> > > cat /dev/null > /var/log/cloudstack/management/management-server.log > >> > > service cloudstack-management start > >> > > > >> > > wait 10 minutes > >> > > upload the whole file or contents of it to google drive or something > >> > > similar. > >> > > > >> > > What is your umask is set to? > >> > > > >> > > Regards > >> > > ilya > >> > > > >> > > On 10/8/14, 1:04 PM, motty cruz wrote: > >> > > > >> > >> Hello ilya, > >> > >> I was not able to post the entire log file is too big, > >> > >> > >> > >> here is the error msg I see at 6:21 am. > >> > >> http://pastebin.com/raw.php?i=dWxDmR91 > >> > >> > >> > >> > >> > >> Thanks, > >> > >> Motty > >> > >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < > >> > >> ilya.mailing.li...@gmail.com> > >> > >> wrote: > >> > >> > >> > >> Management server log is missing ERROR statements in what you've > >> > posted. > >> > >>> Please include the full log file. > >> > >>> > >> > >>> On 10/8/14, 12:23 PM, motty cruz wrote: > >> > >>> > >> > >>> I am looking in the logs but I can't see to find exactly the > error > >> > >>>> causing > >> > >>>> this issue. > >> > >>>> I still getting this error: > >> > >>>> HTTP Status 404 - > >> > >>>> -
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Motty, Sorry, Xenserver is a bit out of my territory as I have none to test on. Perhaps some other people can chip in. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "motty cruz" > To: users@cloudstack.apache.org > Sent: Thursday, 9 October, 2014 16:43:55 > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > Nux, > > I am using XenServer 6.2, everything seem to be working fine except Windows > Server 2012 templates. I have a testing cluster made up of personal PC, > XenServer 6.2 ACS 4.40 using NFS as primary and secondary storage and > windows server 2012 templates work like a charm, that is the reason I > decided to upgrade. > > Thanks, > Motty > > > On Thu, Oct 9, 2014 at 8:36 AM, Nux! wrote: > >> Motty, >> >> On which hypervisor are you on? I've never had problems with Windows >> templates (on kvm). >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro >> >> - Original Message ----- >> > From: "motty cruz" >> > To: users@cloudstack.apache.org >> > Sent: Thursday, 9 October, 2014 16:11:12 >> > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 >> >> > Erik, I did not change anything before or after upgrading >> > Cloudstack-management 4.4.0. I followed the steps below to the exact >> words. >> > >> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.1/upgrade/upgrade-4.4.html >> > >> > now I believe it was an issue with the Database, maybe the scheme was not >> > upgraded? I am running database on a different server. Any ideas? I >> really >> > would like to upgrade to latest package to be able to use Windows >> > templates. at this moment I can't create instances from windows >> templates. >> > >> > Thanks >> > Motty >> > >> > On Thu, Oct 9, 2014 at 8:06 AM, Erik Weber wrote: >> > >> >> I generally experience this if there is a wrong configuration setting. >> >> >> >> Did you change anything before upgrading? >> >> >> >> Erik >> >> 9. okt. 2014 00:49 skrev "motty cruz" følgende: >> >> >> >> > Hi ilya, >> >> > here is the management-server.log as you suggest, I waited 10 minutes >> >> > http://pastebin.com/raw.php?i=AiYXmxSU >> >> > >> >> > my umask 002 >> >> > cat /etc/profile >> >> > >> >> > Thank you very much. >> >> > >> >> > On Wed, Oct 8, 2014 at 3:32 PM, ilya musayev < >> >> ilya.mailing.li...@gmail.com >> >> > > >> >> > wrote: >> >> > >> >> > > Motty, >> >> > > >> >> > > The error you see about not being able to connect to a host on port >> >> 9090 >> >> > > is normal when the management server is starting. There must be >> another >> >> > > error or warning somewhere. >> >> > > >> >> > > Please try the steps below to shrink the log file to manageable size >> >> and >> >> > > upload the file to some file sharing site if paste bin restricts >> you. >> >> > > >> >> > > service cloudstack-management stop >> >> > > cat /dev/null > /var/log/cloudstack/management/management-server.log >> >> > > service cloudstack-management start >> >> > > >> >> > > wait 10 minutes >> >> > > upload the whole file or contents of it to google drive or something >> >> > > similar. >> >> > > >> >> > > What is your umask is set to? >> >> > > >> >> > > Regards >> >> > > ilya >> >> > > >> >> > > On 10/8/14, 1:04 PM, motty cruz wrote: >> >> > > >> >> > >> Hello ilya, >> >> > >> I was not able to post the entire log file is too big, >> >> > >> >> >> > >> here is the error msg I see at 6:21 am. >> >> > >> http://pastebin.com/raw.php?i=dWxDmR91 >> >> > >> >> >> > >> >> >> > >> Thanks, >> >> > >> Motty >> >> > >> On Wed, Oct 8, 2014 at 1
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Motty, Also, 4.4.1 was not yet released AFAIK, wait until it is. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "motty cruz" > To: users@cloudstack.apache.org > Sent: Thursday, 9 October, 2014 16:11:12 > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > Erik, I did not change anything before or after upgrading > Cloudstack-management 4.4.0. I followed the steps below to the exact words. > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.1/upgrade/upgrade-4.4.html > > now I believe it was an issue with the Database, maybe the scheme was not > upgraded? I am running database on a different server. Any ideas? I really > would like to upgrade to latest package to be able to use Windows > templates. at this moment I can't create instances from windows templates. > > Thanks > Motty > > On Thu, Oct 9, 2014 at 8:06 AM, Erik Weber wrote: > >> I generally experience this if there is a wrong configuration setting. >> >> Did you change anything before upgrading? >> >> Erik >> 9. okt. 2014 00:49 skrev "motty cruz" følgende: >> >> > Hi ilya, >> > here is the management-server.log as you suggest, I waited 10 minutes >> > http://pastebin.com/raw.php?i=AiYXmxSU >> > >> > my umask 002 >> > cat /etc/profile >> > >> > Thank you very much. >> > >> > On Wed, Oct 8, 2014 at 3:32 PM, ilya musayev < >> ilya.mailing.li...@gmail.com >> > > >> > wrote: >> > >> > > Motty, >> > > >> > > The error you see about not being able to connect to a host on port >> 9090 >> > > is normal when the management server is starting. There must be another >> > > error or warning somewhere. >> > > >> > > Please try the steps below to shrink the log file to manageable size >> and >> > > upload the file to some file sharing site if paste bin restricts you. >> > > >> > > service cloudstack-management stop >> > > cat /dev/null > /var/log/cloudstack/management/management-server.log >> > > service cloudstack-management start >> > > >> > > wait 10 minutes >> > > upload the whole file or contents of it to google drive or something >> > > similar. >> > > >> > > What is your umask is set to? >> > > >> > > Regards >> > > ilya >> > > >> > > On 10/8/14, 1:04 PM, motty cruz wrote: >> > > >> > >> Hello ilya, >> > >> I was not able to post the entire log file is too big, >> > >> >> > >> here is the error msg I see at 6:21 am. >> > >> http://pastebin.com/raw.php?i=dWxDmR91 >> > >> >> > >> >> > >> Thanks, >> > >> Motty >> > >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < >> > >> ilya.mailing.li...@gmail.com> >> > >> wrote: >> > >> >> > >> Management server log is missing ERROR statements in what you've >> > posted. >> > >>> Please include the full log file. >> > >>> >> > >>> On 10/8/14, 12:23 PM, motty cruz wrote: >> > >>> >> > >>> I am looking in the logs but I can't see to find exactly the error >> > >>>> causing >> > >>>> this issue. >> > >>>> I still getting this error: >> > >>>> HTTP Status 404 - >> > >>>> -- >> > >>>> >> > >>>> *type* Status report >> > >>>> >> > >>>> *message* >> > >>>> >> > >>>> *description* *The requested resource () is not available.* >> > >>>> -- >> > >>>> Apache Tomcat/6.0.24 >> > >>>> >> > >>>> On Wed, Oct 8, 2014 at 12:09 PM, Andrei Mikhailovsky < >> > and...@arhont.com >> > >>>> > >> > >>>> wrote: >> > >>>> >> > >>>> I've had a similar issue when upgrading, but I can't remember >> > exactly >> > >>>> how >> > >>>> >> > >>>>> I solved it. I think everything should be in the logs, it was >> prett
Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Nux, thanks for your suggestion, I will wait until the official release. Thank you! Motty On Thu, Oct 9, 2014 at 9:22 AM, Nux! wrote: > Motty, > > Also, 4.4.1 was not yet released AFAIK, wait until it is. > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - > > From: "motty cruz" > > To: users@cloudstack.apache.org > > Sent: Thursday, 9 October, 2014 16:11:12 > > Subject: Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1 > > > Erik, I did not change anything before or after upgrading > > Cloudstack-management 4.4.0. I followed the steps below to the exact > words. > > > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.4.1/upgrade/upgrade-4.4.html > > > > now I believe it was an issue with the Database, maybe the scheme was not > > upgraded? I am running database on a different server. Any ideas? I > really > > would like to upgrade to latest package to be able to use Windows > > templates. at this moment I can't create instances from windows > templates. > > > > Thanks > > Motty > > > > On Thu, Oct 9, 2014 at 8:06 AM, Erik Weber wrote: > > > >> I generally experience this if there is a wrong configuration setting. > >> > >> Did you change anything before upgrading? > >> > >> Erik > >> 9. okt. 2014 00:49 skrev "motty cruz" følgende: > >> > >> > Hi ilya, > >> > here is the management-server.log as you suggest, I waited 10 minutes > >> > http://pastebin.com/raw.php?i=AiYXmxSU > >> > > >> > my umask 002 > >> > cat /etc/profile > >> > > >> > Thank you very much. > >> > > >> > On Wed, Oct 8, 2014 at 3:32 PM, ilya musayev < > >> ilya.mailing.li...@gmail.com > >> > > > >> > wrote: > >> > > >> > > Motty, > >> > > > >> > > The error you see about not being able to connect to a host on port > >> 9090 > >> > > is normal when the management server is starting. There must be > another > >> > > error or warning somewhere. > >> > > > >> > > Please try the steps below to shrink the log file to manageable size > >> and > >> > > upload the file to some file sharing site if paste bin restricts > you. > >> > > > >> > > service cloudstack-management stop > >> > > cat /dev/null > /var/log/cloudstack/management/management-server.log > >> > > service cloudstack-management start > >> > > > >> > > wait 10 minutes > >> > > upload the whole file or contents of it to google drive or something > >> > > similar. > >> > > > >> > > What is your umask is set to? > >> > > > >> > > Regards > >> > > ilya > >> > > > >> > > On 10/8/14, 1:04 PM, motty cruz wrote: > >> > > > >> > >> Hello ilya, > >> > >> I was not able to post the entire log file is too big, > >> > >> > >> > >> here is the error msg I see at 6:21 am. > >> > >> http://pastebin.com/raw.php?i=dWxDmR91 > >> > >> > >> > >> > >> > >> Thanks, > >> > >> Motty > >> > >> On Wed, Oct 8, 2014 at 12:34 PM, ilya musayev < > >> > >> ilya.mailing.li...@gmail.com> > >> > >> wrote: > >> > >> > >> > >> Management server log is missing ERROR statements in what you've > >> > posted. > >> > >>> Please include the full log file. > >> > >>> > >> > >>> On 10/8/14, 12:23 PM, motty cruz wrote: > >> > >>> > >> > >>> I am looking in the logs but I can't see to find exactly the > error > >> > >>>> causing > >> > >>>> this issue. > >> > >>>> I still getting this error: > >> > >>>> HTTP Status 404 - > >> > >>>> -- > >> > >>>> > >> > >>>> *type* Status report > >> > >>>> > >> > >>>> *message* > >> > >>>> > >> > >>>> *description* *The requested resour
