Two of my xen servers that have been running for 64 days both have this error when I try to start a domU. It came up because I tried to restart one. This one happened to be only running 5 domUs, so I was able to stop the other four. Then I restarted the xend service. This seemed to clear up the issue. The other server is running double the domUs so it will be harder to do. dom0 has 2048M of ram assigned to it. The rest of the 32GB is for domUs. Anyone know what causes this error? I found one thread that seemed to indicate that dom0 was stuck, but didn''t give any solutions are causes other than restarting. Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
The error is a python based error, as it shows up in many other apps as a python based error as well. So all you have to do is restart the affected python service: in this case it is the python xen manger. sudo restart xend (I am not sure if you were against restarting this service or the whole server 8) James Pifer wrote:> > Two of my xen servers that have been running for 64 days both have this > error when I try to start a domU. It came up because I tried to restart > one. > > This one happened to be only running 5 domUs, so I was able to stop the > other four. Then I restarted the xend service. This seemed to clear up > the issue. The other server is running double the domUs so it will be > harder to do. > > dom0 has 2048M of ram assigned to it. The rest of the 32GB is for domUs. > > Anyone know what causes this error? I found one thread that seemed to > indicate that dom0 was stuck, but didn''t give any solutions are causes > other than restarting. > > Thanks, > James > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- View this message in context: http://old.nabble.com/cannot-release-un-aquired-lock-tp28436488p28867823.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
It seems to a python 2.5 error, because a google search of the error appears in many other apps as well. Until python 2.5 is patched , then changing versions of python or restarting xend is the solution. James Pifer wrote:> > Two of my xen servers that have been running for 64 days both have this > error when I try to start a domU. It came up because I tried to restart > one. > > This one happened to be only running 5 domUs, so I was able to stop the > other four. Then I restarted the xend service. This seemed to clear up > the issue. The other server is running double the domUs so it will be > harder to do. > > dom0 has 2048M of ram assigned to it. The rest of the 32GB is for domUs. > > Anyone know what causes this error? I found one thread that seemed to > indicate that dom0 was stuck, but didn''t give any solutions are causes > other than restarting. > > Thanks, > James > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >-- View this message in context: http://old.nabble.com/cannot-release-un-aquired-lock-tp28436488p28867855.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users