[one-users] Cannot start oned after upgrading to 3.0
Tino Vazquez
tinova at opennebula.org
Fri Aug 19 05:16:31 PDT 2011
Hi,
Please era the oned.log and try running "oned" by hand.
Any output (from the command line, or from the log)?
Regards,
-Tino
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org | @tinova79
2011/8/19 makhan <makhanmail at gmail.com>:
> Hi Tino,
>
> No, unfortunately it doesn't solve the problem. If I don't remove the .lock
> file manually it just says 'Stale .lock detected. Erasing it.'. So that's
> not where I would look for the problem.
> Wouldn't also concentrate on 'one', but 'oned' instead. If I remember
> correctly from previous versions what 'one' basically does is run 'mm_sched'
> and 'oned'. 'mm_sched' starts without a problem, but 'oned' doesn't'.
>
> Any other ideas?
>
> Regards,
> -Maciej
>
> -----Original Message-----
> From: Tino Vazquez [mailto:tinova at opennebula.org]
> Sent: Friday, August 19, 2011 1:37 PM
> To: makhan
> Cc: users at lists.opennebula.org
> Subject: Re: [one-users] Cannot start oned after upgrading to 3.0
>
> Hi,
>
> Try a "one stop; one start". If that doesn't fix it, try erasing
> /srv/cloud/one/var/.lock and doing a "one start" again.
>
> Regards,
>
> -Tino
>
> --
> Constantino Vázquez Blanco, MSc
> OpenNebula Major Contributor
> www.OpenNebula.org | @tinova79
>
>
>
> On Fri, Aug 19, 2011 at 1:13 PM, makhan <makhanmail at gmail.com> wrote:
>> /srv/cloud/one/var/.lock
>
>
More information about the Users
mailing list