Re: [Vserver] sparc vserver issues

Matt Kulka wrote:
> Hi,
>
> The following is also in prettier form at http://www.lqx.net/~matt/
> sparc-vserver
>
> I have a few issues with vserver on sparc. Namely, permission denied
> errors (which are pretty broad) when trying to su or when cron tries
> to run a crontab (even a root crontab). Also, when stopping the
> vserver with nfs points mounted, a kernel error is generated. The
> former issues are #1 and #2 while the latter issue is #3.
>
> Platform: Sun T2000 (8-core, 1ghz, 8GB RAM)
> Kernel: Linux 2.6.19-vs2.3.0.6-gentoo #3 SMP Mon Jan 22 19:09:52 MST
> 2007 sparc64 sun4v UltraSparc T1 (Niagara) GNU/Linux
> Installed Versions:
>
> sys-libs/glibc-2.3.6-r5 USE="nptl nptlonly -build -erandom -glibc-
> compat20 -glibc-omitfp (-hardened) (-multilib) -nls -profile (-
> selinux)" 0 kB
> dev-libs/dietlibc-0.30-r2 USE="-debug" 0 kB
> sys-cluster/util-vserver-0.30.212-r1 USE="-bash-completion" 0 kB
>
> Issue #1:
> In the vserver, the cron daemon starts but is unable to run any
> crontabs. The result of it trying is:
> Jan 23 13:00:01 cron[15618]: Permission denied
> in /var/log/messages. This is certainly related to issue #2.
>
> Issue #2:
> In the vserver, su is unable to change to any user. Doing so results
> in the following error
>
> su: Permission denied
>
> The following is shown in /var/log/messages:
> Jan 23 13:26:27 su[6123]: Successful su for dude by root
> Jan 23 13:26:27 su[6123]: + pts/2 root:dude
> Jan 23 13:26:27 su(pam_unix)[6123]: session opened for user dude by
> (uid=0)
> Jan 23 13:26:27 su[6123]: pam_open_session: Permission denied
>
> A log of strace for su - can be found at http://www.lqx.net/~matt/
> sparc-vserver/su.log

Try lowering the limits in your guest's /etc/security/limits.conf,
alternatively remove pam_limits.so from your pam configuration to see if
that fixes it.

> Issue #3:
> The vserver is unable to be shutdown cleanly due to mounted nfs
> mounts. Stopping the vserver produces this error message:

This is a known mainline problem. I've notified (who I think are) the
correct people, hopefully we'll get a fix soon.

> /usr/lib/util-vserver/vserver.functions: line 895: 8230 Segmentation
> fault $_VWAIT --timeout "$VSHELPER_SYNC_TIMEOUT" --status-fd 3
> "$2" >>$_is_tmpdir/out 2>$_is_tmpdir/err 3>$_is_tmpdir/fifo
> internal error: 'vwait' exited with an unexpected status ''; I will
> try to continue but be prepared for unexpected events.
>
> and this in the kernel messages:
>
> [ 1071.769529] Unable to handle kernel NULL pointer dereference
> [ 1071.769555] tsk->{mm,active_mm}->context = 0000000000001f09
> [ 1071.769570] tsk->{mm,active_mm}->pgd = fffff801fcd4e000
> [ 1071.769586] \|/ ____ \|/
> [ 1071.769593] "@'/ .. \`@"
> [ 1071.769600] /_| \__/ |_\
> [ 1071.769607] \__U_/
> [ 1071.769672] vserver(6161[#0]): Oops [#1]
> [ 1071.769690] TSTATE: 0000004411f01600 TPC: 00000000007182b0 TNPC:
> 00000000007182b4 Y: 00000000 Not tainted
> [ 1071.769724] TPC: <_spin_lock_irq+0xc/0x1c>
> [ 1071.769739] g0: 0000000000000004 g1: 0000000000000000 g2:
> 0000000000200200 g3: 00000000007b6fa0
> [ 1071.769763] g4: fffff801fdc54960 g5: fffff80003d53340 g6:
> fffff801f83cc000 g7: 00000000007b6fa0
> [ 1071.769783] o0: 0000000000000a08 o1: 00000000000000fa o2:
> 0000000000000004 o3: 0000000000000000
> [ 1071.769805] o4: 0000000000000072 o5: 0000000000000000 sp:
> fffff801f83cf081 ret_pc: 0000000000548620
> [ 1071.769827] RPC: < lockd_down+0xe4/0x10c>
> [ 1071.769843] l0: 00000000008c1c00 l1: 00000000008e3800 l2:
> 00000000007b4fc0 l3: fffff801fff9c0c0
> [ 1071.769867] l4: fffff801fdc54a38 l5: fffff801f83cfdc0 l6:
> fffff801fdc54ab0 l7: 0000000000000000
> [ 1071.769887] i0: 00000000007b6c00 i1: 0000000000827f00 i2:
> 0000000000000000 i3: 0000000000000001
> [ 1071.769911] i4: 0000000000200200 i5: fffff801fdcf77d8 i6:
> fffff801f83cf141 i7: 00000000005215dc
> [ 1071.769938] I7: < nfs_free_server+0x98/0x110>
> [ 1071.769950] Caller[00000000005215dc]: nfs_free_server+0x98/0x110
> [ 1071.769972] Caller[00000000004ac554]: deactivate_super+0x50/0x6c
> [ 1071.770000] Caller[00000000004c22f0]: release_mounts+0x8c/0xa4
> [ 1071.770023] Caller[00000000004c24b0]: __put_namespace+0x64/0x78
> [ 1071.770044] Caller[000000000046f890]: free_nsproxy+0x34/0x78
> [ 1071.770070] Caller[000000000045a1dc]: do_exit+0x8ac/0x960
> [ 1071.770094] Caller[000000000045a364]: do_group_exit+0x9c/0xa0
> [ 1071.770114] Caller[0000000000406c94]: linux_sparc_syscall32+0x3c/0x40
> [ 1071.770144] Caller[0000000000025360]: 0x25368
> [ 1071.770165] Instruction DUMP: 81c3e008 01000000 9190200f
> 8143e00a 0ac040d0 01000000 81c3e008 01000000
> [ 1071.770209] Fixing recursive fault but reboot is needed!
>
> After this point, as it says, a reboot is needed. The vserver fails
> to start again. With no nfs shares mounted, the vserver shutdown
> cleanly.
>
> Any help is appreciated..
>
> Matt Kulka
> Easynews - Usenet Made Easy!
> http://www.easynews.com
> mkulka@easynews.com

-- 
Daniel Hokka Zakrisson
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver