1474164035 J * fstd_ ~fstd@x4e306030.dyn.telefonica.de 1474164489 Q * fstd Ping timeout: 480 seconds 1474164489 N * fstd_ fstd 1474177679 M * Bertl_oO off to bed now ... have a good one everyone! 1474177679 M * Bertl_oO off to bed now ... have a good one everyone! 1474177683 N * Bertl_oO Bertl_zZ 1474185196 J * Ghislain ~aqueos@adsl1.aqueos.com 1474188851 J * bonbons ~bonbons@2001:a18:205:7601:64fa:878e:dfd2:d550 1474193632 J * derjohn_mob ~aj@x590c56c2.dyn.telefonica.de 1474194184 Q * derjohn_mob Ping timeout: 480 seconds 1474194194 J * derjohn_mob ~aj@x590c56c2.dyn.telefonica.de 1474202105 Q * Ghislain Read error: Connection reset by peer 1474207998 N * Bertl_zZ Bertl 1474207999 M * Bertl morning folks! 1474208752 J * Ghislain ~aqueos@adsl1.aqueos.com 1474214208 Q * Ghislain Read error: Connection reset by peer 1474229768 M * Bertl off for now ... bbl 1474229769 N * Bertl Bertl_oO 1474229930 J * nijikon ~root@static.86.95.76.144.clients.your-server.de 1474229957 M * nijikon Hello everyone 1474229991 M * nijikon I'm unable to start my vservers after rsyncing the vservers folder back from backup 1474229999 M * nijikon It looks like when starting the vserver 1474230007 M * nijikon It is unable to mount /proc 1474230032 M * nijikon Using makefile-style concurrent boot in runlevel 3. 1474230032 M * nijikon ERROR: could not open /proc/stat: No such file or directory 1474230032 M * nijikon Starting system logging: syslog-ng[2016-09-18T20:08:50.138835] system(): The kernel message buffer is not readable, please check permissions if this is unintentional.; device='/proc/kmsg', error='No such file or directory (2)' 1474230037 M * nijikon . 1474230039 M * nijikon ERROR: could not open /proc/stat: No such file or directory 1474230042 M * nijikon Starting domain name service...: bind9Warning: cannot open /proc/net/dev (No such file or directory). Limited output. 1474230045 M * nijikon . 1474230047 M * nijikon ERROR: could not open /proc/stat: No such file or directory 1474230050 M * nijikon Starting periodic command scheduler: cron. 1474230052 M * nijikon Can't start system message bus - /proc is not mounted ... failed! 1474230055 M * nijikon I would really appreciate any help 1474230231 M * daniel_hozac_ did you start vprocunhide on your new server? 1474230317 M * nijikon Yes 1474230326 M * nijikon root@s0 ~ # /etc/init.d/vprocunhide stop 1474230326 M * nijikon root@s0 ~ # /etc/init.d/vprocunhide start 1474230328 M * nijikon Fixing /proc entries visibility.... 1474230372 M * nijikon ++ /usr/bin/nice -n 0 /usr/sbin/chbind --silent --secure --nid 40007 --ip x.x.x.x/29 /usr/lib/x86_64-linux-gnu/util-vserver/exec-ulimit /etc/vservers/ns/ulimits /usr/sbin/vtag --create --tag 40007 --silent -- /usr/sbin/vspace --new --default -- /usr/sbin/vcontext --create --silent --xid 40007 -- /usr/sbin/vspace --mount --fs --set -- /usr/sbin/vspace --set --default -- /usr/lib/x86_64-linux-gnu/util-vserv 1474230378 M * nijikon er/exec-remount /proc /sys -- /usr/sbin/vlimit --dir /etc/vservers/ns/rlimits --missingok -- /usr/sbin/vsched --xid self --force -- /usr/lib/x86_64-linux-gnu/util-vserver/vsysctl --xid self --dir /etc/vservers/ns/sysctl --missingok -- /usr/sbin/vuname --xid self --dir /etc/vservers/ns/uts --missingok -- /usr/sbin/vmemctrl --xid self --set -- /usr/sbin/vuname --xid self --set -t context=/etc/vservers/ns -- 1474230384 M * nijikon /usr/sbin/vattribute --set --secure --flag default --flag fakeinit -- /usr/lib/x86_64-linux-gnu/util-vserver/save_ctxinfo /etc/vservers/ns /usr/bin/env -i PATH=/bin:/usr/bin:/sbin:/usr/sbin PREVLEVEL=N RUNLEVEL=3 /usr/sbin/vcontext --migrate-self --endsetup --pivot-root --closefd --silent -- /etc/init.d/rc 3 1474230470 M * nijikon Probably something is messed up in /vservers/ns 1474230483 M * nijikon Cause configuration was on a different disk and that did not change 1474230544 M * daniel_hozac_ could you paste the complete output of the debug start? 1474230575 M * nijikon Sure 1474230576 M * nijikon Sec 1474230976 M * nijikon http://pastebin.com/FDMQPwVS 1474231177 M * daniel_hozac_ and you do have a /proc directory in the guest, and in the guest's fstab? 1474231213 M * nijikon -rw-r--r-- 1 root root 29 Sep 18 22:35 /vservers/ns/proc/mounts 1474231227 M * nijikon root@s0 ~ # cat /etc/vservers/ns/fstab 1474231227 M * nijikon none /proc proc defaults 0 0 1474231227 M * nijikon none /tmp tmpfs size=256m,mode=1777 0 0 1474231228 M * nijikon none /dev/pts devpts gid=5,mode=620 0 0 1474231266 M * nijikon root@s0 ~ # uname -a 1474231266 M * nijikon Linux s0.servercrunch.com 3.18.25-vs2.3.7.4-beng #1 SMP Mon Jan 25 13:33:23 GMT 2016 x86_64 GNU/Linux 1474231269 M * nijikon root@s0 ~ # dpkg -l|grep vser 1474231271 M * nijikon ii libvserver0 0.30.216-pre3126-jessie0.1-1 amd64 dynamic libraries for util-vserver 1474231274 M * nijikon ii linux-image-vserver-3.18-beng 3.18.25-2.3.7.4+jessie1 amd64 A metapackage which installs the latest Linux-Vserver patched 3.18 linux-image package, BenG's build. 1474231278 M * nijikon ii util-vserver 0.30.216-pre3126-jessie0.1-1 amd64 utilities for managing Linux-VServer guests 1474231281 M * nijikon ii util-vserver-core 0.30.216-pre3126-jessie0.1-1 amd64 core utilities of util-vserver 1474231284 M * nijikon ii util-vserver-sysv 0.30.216-pre3126-jessie0.1-1 amd64 initscripts for util-vserver 1474231386 M * daniel_hozac_ did your backup contain a /proc? it's not just an empty directory? 1474231417 M * nijikon This file was just created 1474231422 M * nijikon I mean the mounts file in /proc 1474231441 M * nijikon I removed it so the dir was empty, then when I ran vserver --debug ns start 1474231444 M * nijikon It created the file 1474231469 M * daniel_hozac_ it shouldn't do that... 1474231482 M * nijikon I also tried to create a new vserver and there is the same problem 1474232071 M * nijikon For a clean jessie 1474232073 M * nijikon http://pastebin.com/GXMgjtjh 1474232081 M * nijikon After this was run 1474232084 M * nijikon Now on main fs 1474232093 M * nijikon root@s0 ~ # vserver-stat 1474232093 M * nijikon WARNING: can not access /proc/uptime. Usually, this is caused by procfs-security. Please read the FAQ for more details http://linux-vserver.org/Proc-Security 1474232096 M * nijikon open("/proc/uptime"): No such file or directory 1474232103 M * nijikon root@s0 ~ # w 1474232103 M * nijikon Error: /proc must be mounted 1474232103 M * nijikon To mount /proc at boot you need an /etc/fstab line like: 1474232103 M * nijikon proc /proc proc defaults 1474232105 M * nijikon In the meantime, run "mount proc /proc -t proc" 1474232107 M * nijikon Any idea? 1474232159 M * daniel_hozac_ do you have selinux or systemd enabled or something like that? 1474232190 M * nijikon systemd on mainfs, yes 1474232213 M * daniel_hozac_ that's not going to work. 1474232247 M * nijikon A ha 1474232257 M * nijikon So I need to remove systemd from main fs and everything will work? 1474232263 M * daniel_hozac_ most likely. 1474232302 M * nijikon OK, will do this then http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_a_Debian_jessie/sid_installation 1474232756 M * nijikon This is good 1474232761 M * nijikon It looks like the vserver is starting 1474232771 M * nijikon Quick question cause I can see that the vserver did start 1474232780 M * nijikon But processes like bind, cron, syslog-ng etc 1474232783 M * nijikon Did not start at all 1474232788 M * nijikon Any idea? 1474234003 Q * bonbons Quit: Leaving 1474234515 M * nijikon Nevermind, this is some misconfiguration on my end 1474234526 M * nijikon daniel_hozac_: thanks for your help! 1474236245 Q * nijikon Quit: Lost terminal