LXC problem with network | Proxmox v4 Beta4 | DEV look here! (VIDEO)

[sigxcpu]

Same useless information (to me) like I have when they fail to start.
I didn't manage to see anything, but the recommentation is to start it like this:

lxc-start -n 104 -- /sbin/init --debug --verbose


This should show you the container's init debug log. That should be the most valuable piece of information because init fails, but to me it didn't show anything at all. Maybe you are luckier than me.

 

[Egner]

Same useless information (to me) like I have when they fail to start.
I didn't manage to see anything, but the recommentation is to start it like this:

lxc-start -n 104 -- /sbin/init --debug --verbose


This should show you the container's init debug log. That should be the most valuable piece of information because init fails, but to me it didn't show anything at all. Maybe you are luckier than me.

root@tc01-c-h:~# lxc-start -n 104 -- /sbin/init --debug --verbose
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.

cat /var/log/lxc/104.log


lxc-start 1444219042.957 ERROR lxc_start - start.c:start:1252 - No such file or directory - failed to exec ib/lxc 104
lxc-start 1444219042.957 ERROR lxc_sync - sync.c:__sync_wait:51 - invalid sequence number 1. expected 4
lxc-start 1444219042.957 ERROR lxc_start - start.c:__lxc_start:1172 - failed to spawn '104'
lxc-start 1444219048.359 ERROR lxc_start_ui - lxc_start.c:main:344 - The container failed to start.
lxc-start 1444219048.359 ERROR lxc_start_ui - lxc_start.c:main:346 - To get more details, run the container in foreground mode.
lxc-start 1444219048.359 ERROR lxc_start_ui - lxc_start.c:main:348 - Additional information can be obtained by setting the --logfile and --logpriority options.

I have like you no luck at all.

 

[sigxcpu]

that failed to exec "ib/lxc" looks suspicious. Let's hope it is just a message error, not a path error (shouild be "lib" there?).

try
lxc-start -n 104 -l debug -F -- /sbin/init --debug --verbose

that should attempt to start the container in the foreground along with debugging.

 

[Egner]

I have do this things before like u do.

But they are not like giving u any good answer

root@tc01-c-h:~# lxc-start -n 104 -l debug -F -- /sbin/init --debug --verbose
systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
Detected virtualization 'lxc'.
Detected architecture 'x86-64'.


Welcome to Debian GNU/Linux 8 (jessie)!


Set hostname to <tc02-vm-c>.
Failed to install release agent, ignoring: No such file or directory
Failed to create root cgroup hierarchy: No such file or directory
Failed to allocate manager object: No such file or directory

 

[sigxcpu]

That is exactly what I've got yesterday on an upstart (not systemd) based container. Switched to a systemd install and it worked

The real issue is that init does not spit any debug messages. Maybe they are in container's syslog:
pct enter 104
tail -n 1000 /var/log/syslog

 

[Egner]

Here is the debug log btw : http://pastebin.com/t9qNNcHK

And here is the syslog file : http://pastebin.com/fcv8Uurg

 

[sigxcpu]

In syslog it looks like it did a lot of stuff actually. Do you still have 3 processes started only?

And btw, if this is systemd, you can run systemctl --failed to see what services failed and systemctl status <service name> to see why.


Also, after container starts (sort of) and pct enter 104, please run dpkg -l | grep systemd. Your warnings/errors are found in a bug between 218 and 219 releases.

LE: it is above: 215

Here is a discussion about that: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766216

Running jessie containers in jessie hosts (proxmox is jessie)

Here is a possible solution: https://wiki.debian.org/LXC#Incompatibility_with_systemd

 

[Egner]

Yes there is still just 3 processes running still under the virtual machine.

Yes debian 8 is build on systemd, but the command systemctl --failed is not working at all.

root@tc02-vm-c:~# dpkg -l | grep systemd
ii libsystemd0:amd64 215-17+deb8u1 amd64 systemd utility library
ii systemd 215-17+deb8u1 amd64 system and service manager
ii systemd-sysv 215-17+deb8u1 amd64 system and service manager - SysV links

And this is not an upgrade, this is a finish debian 8 template, and i have also be looking in to that page today.

i have also try this
lxc.autodev = 1
lxc.kmsg = 0

 

[sigxcpu]

That page says to

[COLOR=black]apt-get install sysvinit-core

. Did you try that?[/COLOR]

 

[tom]

which template do you use?

you should use:
http://download.proxmox.com/images/system/debian-8.0-standard_8.0-1_amd64.tar.gz

this one is NOT using systemd.

 

[Egner]

which template do you use?

yes i will try your template out!

 

[Egner]

you should use:
http://download.proxmox.com/images/system/debian-8.0-standard_8.0-1_amd64.tar.gz

this one is NOT using systemd.[/QUOTE]


Update : Yes the problem is now located to systemd, i have now a new installed template from proxmox and now everything seems working just i should.

I recreate the problem on one node, and then i try to move a old (vm) that works on the other node with systemd. and after i move the server to that node that not working atm with systemd the server is not started with systemd scripts. But if i take my new created container from proxmox and move over to the same node the server went online.

So to anyone here, do NOT use a template from OpenVZ website like i do!! and you will properly getting the same type of problems that i has

I will keep this updated if there is something that will comes up, by so far i will just wait some days and see have things going.

But anyway this will help others with the same problem.

i will give a big thanks to : Tom,sigxcpu and wbumiller that help me so much with this

/Best regards
Egner