error samba AD provisioning into lxc container

fieraf

Member
May 30, 2016
34
0
6
47
H've configured a copntainer for installing samba4 AD, but not work

Code:
process_usershare_file: share name unknown service (snum == -1) contains invalid characters (any of %<>*?|/\+=;:",)
xattr_tdb_removexattr() failed to get vfs_handle->data!
process_usershare_file: share name unknown service (snum == -1) contains invalid characters (any of %<>*?|/\+=;:",)
Security context active token stack underflow!
PANIC (pid 19164): Security context active token stack underflow!
BACKTRACE: 44 stack frames:
 #0 /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0(log_stack_trace+0x1a) [0x7f0fac09f71a]
 #1 /usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0(smb_panic_s3+0x20) [0x7f0fac09f7f0]
 #2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f0fbcfcbf1f]
 #3 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(sec_ctx_active_token+0x6a) [0x7f0fa8e603da]
 #4 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(try_chown+0xa9) [0x7f0fa8e6bd69]
 #5 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(set_nt_acl+0x1fd) [0x7f0fa8e6bfbd]
 #6 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(+0x1ce5c1) [0x7f0fa8f2e5c1]
 #7 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(smb_vfs_call_fset_nt_acl+0x2d) [0x7f0fa8e645cd]
 #8 /usr/lib/x86_64-linux-gnu/samba/vfs/acl_xattr.so(+0x2389) [0x7f0f95dae389]
 #9 /usr/lib/x86_64-linux-gnu/samba/vfs/acl_xattr.so(+0x4416) [0x7f0f95db0416]
 #10 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(smb_vfs_call_fset_nt_acl+0x2d) [0x7f0fa8e645cd]
 #11 /usr/lib/python2.7/dist-packages/samba/samba3/smbd.so(+0x2334) [0x7f0fa928b334]
 #12 /usr/bin/python2.7(PyEval_EvalFrameEx+0x6da2) [0x4cada2]
 #13 /usr/bin/python2.7(PyEval_EvalCodeEx+0x255) [0x4c2765]
 #14 /usr/bin/python2.7(PyEval_EvalFrameEx+0x6099) [0x4ca099]
 #15 /usr/bin/python2.7(PyEval_EvalFrameEx+0x5d8f) [0x4c9d8f]
 #16 /usr/bin/python2.7(PyEval_EvalCodeEx+0x255) [0x4c2765]
 #17 /usr/bin/python2.7(PyEval_EvalFrameEx+0x6099) [0x4ca099]
 #18 /usr/bin/python2.7(PyEval_EvalCodeEx+0x255) [0x4c2765]
 #19 /usr/bin/python2.7(PyEval_EvalFrameEx+0x6099) [0x4ca099]
 #20 /usr/bin/python2.7(PyEval_EvalCodeEx+0x255) [0x4c2765]
 #21 /usr/bin/python2.7() [0x4de8b8]
 #22 /usr/bin/python2.7(PyObject_Call+0x43) [0x4b0cb3]
 #23 /usr/bin/python2.7(PyEval_EvalFrameEx+0x2ad1) [0x4c6ad1]
 #24 /usr/bin/python2.7(PyEval_EvalCodeEx+0x255) [0x4c2765]
 #25 /usr/bin/python2.7() [0x4de6fe]
 #26 /usr/bin/python2.7(PyObject_Call+0x43) [0x4b0cb3]
 #27 /usr/bin/python2.7(PyEval_EvalFrameEx+0x2ad1) [0x4c6ad1]
 #28 /usr/bin/python2.7(PyEval_EvalCodeEx+0x255) [0x4c2765]
 #29 /usr/bin/python2.7() [0x4de6fe]
 #30 /usr/bin/python2.7(PyObject_Call+0x43) [0x4b0cb3]
 #31 /usr/bin/python2.7(PyEval_EvalFrameEx+0x2ad1) [0x4c6ad1]
 #32 /usr/bin/python2.7(PyEval_EvalCodeEx+0x255) [0x4c2765]
 #33 /usr/bin/python2.7() [0x4de6fe]
 #34 /usr/bin/python2.7(PyObject_Call+0x43) [0x4b0cb3]
 #35 /usr/bin/python2.7(PyEval_EvalFrameEx+0x2ad1) [0x4c6ad1]
 #36 /usr/bin/python2.7(PyEval_EvalCodeEx+0x255) [0x4c2765]
 #37 /usr/bin/python2.7(PyEval_EvalCode+0x19) [0x4c2509]
 #38 /usr/bin/python2.7() [0x4f1def]
 #39 /usr/bin/python2.7(PyRun_FileExFlags+0x82) [0x4ec652]
 #40 /usr/bin/python2.7(PyRun_SimpleFileExFlags+0x191) [0x4eae31]
 #41 /usr/bin/python2.7(Py_Main+0x68a) [0x49e14a]
 #42 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f0fbdf91830]
 #43 /usr/bin/python2.7(_start+0x29) [0x49d9d9]
Can not dump core: corepath not set up

Can you help-me?
it's a problema of the container?

Tahnks
 
Can you recreate a container as priviledged, and see if that problems happens again ?
 
Sorry My mistake, I've not installed a package before samba
post closed
Many thanks
 
Hi !

I'm sorry, this post is closed since a long time, but I have exactly the same problem. Can you tell me wich package you have missed please ?

Thank you !
 
I'd like to confirm that the proposed solution (changing the option "unprivileged container" from "yes" to "no") made the error go away in my case.

(I stumbled upon this thread, after encountering the same error message: "Security context active token stack underflow")

Note: my scenario was attempting to setup a container based on the template "Turn Key Linux Domain Controller" (debian-10-turnkey-domain-controller).
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!