Did you recently update tomcat? I've seen it happen where if you update tomcat it will stop the cloudstack service and start the generic tomcat service therefore giving 404 errors.
On Mon, Aug 11, 2014 at 2:32 PM, mo <m...@daoenix.com> wrote: > it would appear that you must start management first & then agent? I did > so, ad I am back online. > > Still would like to know if there is a particular process to start up. > > On August 11, 2014 at 5:08:45 PM, mo (m...@daoenix.com) wrote: > > > > On August 11, 2014 at 4:17:16 PM, mo (m...@daoenix.com) wrote: > > This is one of the errors I mentioned: > > Unable to connect to remote: is there a server running on port 8250 > > Also this one. > > https://gist.github.com/anonymous/ea821c3e00d9b2baa7b6 > > - Mo > > On August 11, 2014 at 4:05:23 PM, mo (m...@daoenix.com) wrote: > > Hello, > > Curious, I am getting this message, it’s worked for 10 days without issue. > No reboots or changes really made by me. > > > Rebooting agent / management resolves it. Agent log shows it cannot > connect, but no firewall rules have been altered. > > > Any information would be appreciated. > > - Mo
