cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From motty cruz <motty.c...@gmail.com>
Subject Re: HTTP Status 404 - just upgraded from ACS 4.4.0 to ACS 4.4.1
Date Wed, 08 Oct 2014 21:58:54 GMT
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 <motty.cruz@gmail.com> 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 <motty.cruz@gmail.com> 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.lists@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 <andrei@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" <motty.cruz@gmail.com>
>>>>>> 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 <terbolous@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Post the log on pastebin, also post the output of
>>>>>>>
>>>>>>> netstat -anlp
>>>>>>> ps aux
>>>>>>>
>>>>>>> Erik
>>>>>>> 8. okt. 2014 18:30 skrev "motty cruz" <motty.cruz@gmail.com>
>>>>>>> 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 <terbolous@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.cruz@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.cruz@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
>>>>>>>>
>>>>>>>>  --
>>>>>> Thanks for your support,
>>>>>> Motty
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>> --
>> Thanks for your support,
>> Motty
>>
>
>
>
> --
> Thanks for your support,
> Motty
>



-- 
Thanks for your support,
Motty

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message