Hey, here is my LibreOffice Online setup https://git.project-insanity.org/snippets/13 I am trying to package it for ArchLinux! Loolwsd prints several errors when starting: https://git.project-insanity.org/snippets/14 It's similar to this: kit-11301-11301 19:27:30.869672 [ loolkit ] ERR link("/usr/lib/libreoffice/program/libavmedialo.so", "/var/lib/lool/child-roots/11301/lo/program/libavmedialo.so") failed. Will copy. (errno: File exists)| kit/Kit.cpp:152 Best regards, Jonas
This issue seems to be fixed in the latest version of libreoffice-online 2.0.3 and libreoffice (sdk) 5.3
Ups sorry, no its still present
Updated build scripts: https://aur.archlinux.org/cgit/aur.git/tree/?h=libreoffice-online Updated to libreoffice-online 2.0.3 Updated to libreoffice-sdk 5.3 Heres my loolwsd.xml: https://git.project-insanity.org/snippets/15 Bug still present ...
This bug was never confirmed. Moving back to UNCONFIRMED
Does this still occur with a current version?
Occurring for me with version 2.1.2 (in a custom-built Debian package). E.g.: kit-01386-01384 23:12:14.288949 [ loolkit ] ERR link("/usr/lib/libreoffice/program/libwriterperfectlo.so", "/srv/lool/child-roots/NGpdMlZ91uLmyV8q/lo/program/libwriterperfectlo.so") failed. Will copy. (errno: File exists)| kit/Kit.cpp:156 kit-01386-01384 23:12:14.305384 [ loolkit ] ERR link("/usr/lib/libreoffice/program/libunoidllo.so", "/srv/lool/child-roots/NGpdMlZ91uLmyV8q/lo/program/libunoidllo.so") failed. Will copy. (errno: File exists)| kit/Kit.cpp:156 The whole thing ends with a SIGSEGV: kit-01386-01384 23:12:16.456667 [ loolkit ] INF Process is ready.| kit/Kit.cpp:1768 kit-01386-01386 23:12:16.456727 [ loolkit ] SIG Fatal signal received: SIGSEGV Backtrace 1386: /usr/bin/loolforkit(_ZN7SigUtil13dumpBacktraceEv+0x64) [0x55c4779837b4] /usr/bin/loolforkit(+0x99c86) [0x55c477984c86] /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0) [0x7ff60098f0c0] /usr/bin/loolforkit(_Z10lokit_mainRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES6_S6_S6_S6_bbb+0x1972) [0x55c477936e82] /usr/bin/loolforkit(+0x3dcff) [0x55c477928cff] /usr/bin/loolforkit(main+0xd67) [0x55c47790ba77] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7ff6005ff2b1] /usr/bin/loolforkit(_start+0x2a) [0x55c47790ceba] kit-01386-01386 23:12:16.457287 [ loolkit ] SIG SIGSYS trapped with code: 1 and context 140735910328512 kit-01386-01386 23:12:16.457381 [ loolkit ] SIG seccomp trapped signal, un-authorized sys-call: 62 Backtrace 1386: /usr/bin/loolforkit(_ZN7SigUtil13dumpBacktraceEv+0x64) [0x55c4779837b4] /usr/bin/loolforkit(+0x8b1c8) [0x55c4779761c8] /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0) [0x7ff60098f0c0] /lib/x86_64-linux-gnu/libc.so.6(kill+0x7) [0x7ff6006122e7] /usr/bin/loolforkit(+0x99c94) [0x55c477984c94] /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0) [0x7ff60098f0c0] /usr/bin/loolforkit(_Z10lokit_mainRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES6_S6_S6_S6_bbb+0x1972) [0x55c477936e82] /usr/bin/loolforkit(+0x3dcff) [0x55c477928cff] /usr/bin/loolforkit(main+0xd67) [0x55c47790ba77] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7ff6005ff2b1] /usr/bin/loolforkit(_start+0x2a) [0x55c47790ceba] One thing I'm noticing is that both OP and I are putting the files in a non-standard location. The default is `/opt/lool`; I'm putting mine under `/srv/lool` and OP looks to be putting his in `/var/lib/lool`. Perhaps related? Hope this helps!
Same error for me on debian stretch (loolwsd 2.1.2-14). It may be timing related, since I'm running loolwsd in a VM on a slow/small CPU. When I move /opt/lool/{child-roots,systemtemplate} and /usr/lib/libreoffice into a common tmpfs and adjust "loolwsd.service" correspondingly, then I'm no longer seeing those log messages and everything works fine.
Let's set it to confirmed, then. It's probably related to linking not being possible over different partitions.