Manuel, I would suggest disabling any chroot-related functionality for the Dovecot components which are malfunctioning in this way. A portion of the LX emulation is still performed in userspace, requiring access to certain system libraries which are traditionally located in the /native mount point. Any actions occurring after a chroot which need fresh access to those resources will fail, causing errors in line with what you observed.
Moving all of the LX emulation into kernel space (thus eliminating these chroot-related difficulties) is an eventual goal of the project, but there is still much to do on that front. With regards, -Patrick On 15 February 2016 at 15:59, <[email protected]> wrote: > Hi everyone, > > we have a lx zone (debian-8, 20160204, 445d04f4-cad6-11e5-a1a0-9f6c0ce02707). > We tried to setup dovecot in it, but so far without success. Here are the > relevant pieces from the syslog: > > dovecot: anvil: Error: ld.so.1: lx_brand.so.1: fatal: lib socket.so.1: open > failed: No such file or directory > dovecot: anvil: Error: ld.so.1: lx_brand.so.1: fatal: relocation error: file > /native/usr/lib/amd64/lx_brand.so.1: symbol accept: referenced symbol not > found > dovecot: anvil: Fatal: master: service(anvil): child 4366 1 killed with > signal 9 > > libsocket is present, find / -name libsocket.so.1: > /native/usr/lib/amd64/libsocket.so.1 > /native/usr/lib/libsocket.so.1 > /native/lib/amd64/libsocket.so.1 > /native/lib/libsocket.so.1 > > Does anybody have an idea? > > I checked the compatibility sheet for lx zones, dovecot is not listed. So > maybe this is a known issue/limitation? > > Thank you a lot! > > Cheers > Manuel > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
