On 12/24/05, Herbert Poetzl <herbert@13thfloor.at> wrote:
>
> On Fri, Dec 23, 2005 at 10:29:04PM +0500, Mustafa Abbasi wrote:
> > when i try to start the vserer using
> > vserver sarge start
> > i get this error
> > /proc/uptime can not be accessed. Usually, this is caused by
> > procfs-security. Please read the FAQ for more details
> > http://www.linux-vserver.org/index.php?page=Linux-Vserver+FAQ
> >
> >
> > i went to the link and then tried
> > /etc/init.d/vprocunhide stop
> > /etc/init.d/vprocunhide start
> > i get this error
> > Fixing /proc entries visibility.../proc/net/: Bad address
> > /proc/sys/: Bad address
> > /proc/sys/debug/: Bad address
> > /proc/sys/dev/: Bad address
> > /proc/sysvipc/: Bad address
> > /proc/tty/: Bad address
> > /proc/cmdline: Bad address
> > /proc/cpuinfo: Bad address
> > /proc/crypto: Bad address
> > /proc/devices: Bad address
> > /proc/execdomains: Bad address
> > /proc/filesystems: Bad address
> > /proc/interrupts: Bad address
> > /proc/iomem: Bad address
> > /proc/ioports: Bad address
> > /proc/kcore: Bad address
> > /proc/kmsg: Bad address
> > /proc/loadavg: Bad address
> > /proc/locks: Bad address
> > /proc/meminfo: Bad address
> > /proc/misc: Bad address
> > /proc/modules: Bad address
> > /proc/slabinfo: Bad address
> > /proc/stat: Bad address
> > /proc/swaps: Bad address
> > /proc/uptime: Bad address
> > /proc/version: Bad address
> > ERROR
> >
> > what am i doing wrong.
> > i use ubuntu breezy.
>
> a) make sure that you have a patched kernel and
> (chances are good, but test with testme.sh)
>
> b) make sure that the tools are working properly
> (i.e. build them yourself or at least test them
> with the testme.sh)
>
> > ps i did get a vserver to run in debian sarge but i can't get it to
> > work in ubuntu breezy. installing in ubuntu i did take nore care to
> > satisfy build dependencies before compiling and did compile the kernel
> > more carefully. do i need to recompile the kernel or is the someother
> > problem. i can i access
> > cat /proc/uptime
> > can anyone give any help.
>
> if the issue persists with a 2.01 or 2.1.0 kernel
> and 0.30.209 (mainline) tools, please let me know
> so we can start investigating ...
>
> best,
> Herbert
oh it ok now. i solved it thanks to the good ppl ppl on te vserver irc.
apprently i had installed the debian package as well as the one i compiled.
> my computer is a
> > amd sempron 2400 +
> > MSI km3mv-v
> > 256 mb ram
> >
> > i used this kernel
> > root@ubuntu:~# uname -r
> > 2.6.14.4-vs2.1.0
> >
> > i ran all the commands as root.
>
> > _______________________________________________
> > Vserver mailing list
> > Vserver@list.linux-vserver.org
> > http://list.linux-vserver.org/mailman/listinfo/vserver
>
>
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Sat Dec 24 04:01:11 2005