Can't start CT, got signal 11

[absolom]

Hello !
After a SSH connexion, I got theses message on login :

-bash: [: too many arguments
-bash: [: =: unary operator expected
-bash: [: =: unary operator expected
-bash: [: too many arguments
-bash: [: too many arguments

So, I made an apt-get update & apt-get upgrade

I saw these message during update :

Traceback (most recent call last):
  File "/usr/bin/apt-listchanges", line 237, in <module>
    main()
  File "/usr/bin/apt-listchanges", line 44, in main
    apt_pkg.init_system()
AttributeError: 'module' object has no attribute 'init_system'

And then, on every command, I got segmentation fault ...

So I stopped the CT and since, I am unable to restart it, I see this :

Starting container ...
Container is mounted
Adding IP address(es): XX.XX.XX.XX
Got signal 11
Setting CPU units: 1000
Setting CPUs: 4
Got signal 11
Container start in progress...

And the CT is stopped ...

Any idea ?

Thanks for your help,

Aurélien.

 

[tom]

Re: Can't start VM, got signal 11

we use CT for containers and VM for KVM virtual machines - please use these naming.

 

[absolom]

Hi, ok, sorry, I edited my post.

 

[absolom]

But no ideas ?