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 <terbol...@gmail.com> 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" <motty.c...@gmail.com> 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 <motty.c...@gmail.com> 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
