[Lxc-users] errors

[Serge Hallyn]

Quoting Tamas Papp (tompos at martos.bme.hu):
> On 05/23/2013 07:34 PM, Serge Hallyn wrote:
> > Quoting Tamas Papp (tompos at martos.bme.hu):
> >> On 05/23/2013 03:39 PM, Tamas Papp wrote:
> >>> On 05/23/2013 03:35 PM, Stéphane Graber wrote:
> >>>> That looks like broken locking, though Serge would know for sure.
> >>>> You may want to try clearing /dev/shm/*lxc* and see if that fixes the
> >>>> problem (not usually recommended as those locks are there for a reason).
> >>> OK.
> >>>
> >>> At this moment I'm trying to reproduce the problem on a test machine, but still no "luck".
> >>>
> >>> I'll let you know, as soon as I have something.
> >> Well, I still was success in this.
> >>
> >> No I have 3 other system with the symptoms (FUTEX_WAIT, segfaults).
> >>
> >> Regerding to lock file, I renamed /dev/shm/sem.lxcapi.jcb-vmc02 and it's recreated automatically. It
> >> is still there, no changes.
> > I'm in the process of replacing those locks.  In the meantime, the
> > /dev/shm/sem.* files are removed when things exit normally, but
> > if you kill a lxc-* command while it is holding the lock, you
> > may have to remove it manually.  If the commands are still running,
> > then of course they should still be there, as the intent is to keep
> > two programs which are both doing c->set_config_item("lxc.rootfs", x)
> > from overwiting each other.
> >
> > I'll try to get the replacement for that ready for staging by
> > tomorrow night.
> 
> FYI, now it works fine now with 0.9.0.0~staging~20130523-0240-0ubuntu1~ppa1~precise1 .
> For this I had to stop all containers then start them again.

Ok - I suspect what was happening was that every lxc-ls was
segfaulting while holding the semaphore, then the next lxc-*
action using the api would hang.

> Thanks for you help guys,
> tamas
> 
> ps.: Can I expect similar "bugs" from these changes, like this was?

Not sure what you mean.

-serge