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:[email protected]] Sent: Friday, August 19, 2011 1:37 PM To: makhan Cc: [email protected] 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 <[email protected]> wrote: > /srv/cloud/one/var/.lock _______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
