Search results

Thank you Tom! works good now.

Hi, Since the Proxmox v4 was stable i have some problem with the aptitude so i belive that i have to remove any of the repositorys in my sources.list? starting apt-get update Ign http://ftp.se.debian.org jessie InRelease Hit http://ftp.se.debian.org jessie Release.gpg Hit...

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. 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...

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...

Here is the debug log btw : http://pastebin.com/t9qNNcHK And here is the syslog file : http://pastebin.com/fcv8Uurg

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)...

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...

Here u go i was not allowed to upload it here http://pastebin.com/28Sf6y6W

Here is some additional loggfiles from the container

Well i have the same issue, if i create a container with a different distro like Ubuntu the same problem is appear. And i want to running Debian and not Ubuntu. But if you just restart the nodes a couple of times everything just start working like it should and the init.d/system.d scripts works...

For me is it just 3 services that shows up :-)

Hi and good morning Wolfgang, Here is the results, i also try to restart the network services from the terminal. Here is that one with ifconfig -a here is that one with ip addr Services restart with failure. Let me know if you need something more. /Best regards Egner

Hi, I have recreate the issue on node 1 now after one reboot. Here is a picture on the /etc/network/interfaces on the LXC container there the network not working. And the /etc/network/interface seems legit. #Picure 1. #Picture 2. #Picture 3. Let me know if you need something. /Best...

Hi, yes thats right the LXC container are not applied the ip to the guest. Well, to be honest, you are not manage to get in to the lxc container if they not providing any network so to answer that question isn't easy then ;( If there isn't any backdoor or so in the the container like openvz...

No becouse i'm using untagged vlan for the management so that is irrelevant. here is my switch configuration: interface Gi1/0/2 description "BLADE-2-IP-CONNECT" switchport mode trunk switchport trunk native vlan 801 switchport trunk allowed vlan 801,1338 exit The network is just tagged for...

Hi Wolfgang, My physical nodes are using one tagged vlan in a combination of untagged vlan. For the eth1 (combination of untagged and tagged vlan on same port) The untagged traffic is for the management network that i manage the cluster via. The tagged traffic is vlan1338 that provide NFS...

Hi Proxmox, Now is it time to give you a more information about this problem that i'm forcing and probably that will saving others with same problem this questions. First of all, i have using Proxmox v4 since it was Beta1 and it seems there is some issues just regarding the LXC containers. And...

I using the latest BIOS but the server is still quite old. What server version do you have?

But i try that, but after i force the server in to my hosts file and reboot it seems work like normal again. I have also fix that you want me to do! Thanks!