Apache OpenOffice (AOO) Bugzilla – Issue 113330
ooo hangs on opening documents on nfs filesystems
Last modified: 2011-03-17 12:02:27 UTC
ooo320m12 build 9483 from ubuntu lucid oowriter cannot open any document residing on nfs share. I can view and select a document in oowriter open selector dialog but after clicking open, oowriter locks and we have to kill it with SIGKILL to get rid of it (SIGTERM is not sufficient) open works fine in local disks and iSCSI shares. ubuntu bug : https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/577038
Framework issue.
p92: Is locking enabled & working in your mounted home?
My home is on a local dir. Documents are on a NFS mounted dir. Btw what do you mean by "locking enabled & working" ? How do I check that ? my NFS entry in fstab is : synology:/volume1/PC /mnt/pc nfs _netdev,nouser,auto,rw,dev,exec,suid 0 0 Mount: synology:/volume1/PC on /mnt/pc type nfs (rw,addr=192.168.0.2) I have investigated more and found that if I launch openoffice with the script oowriter locks on the splash screen : $ /usr/lib/openoffice/program/soffice -writer "/mnt/pc/proposition de mise en oeuvre de pci-pra.odt" + test -z /home/pascal + FILE_LOCKING=auto + OPENGL_SUPPORT=no + [ -f /etc/openoffice/soffice.sh ] + . /etc/openoffice/soffice.sh + FILE_LOCKING=auto + OPENGL_SUPPORT=no + [ -z ] + home_on_nfs -writer /mnt/pc/proposition de mise en oeuvre de pci-pra.odt + stat -f -c %T /home/pascal + return 1 + [ 1 = 0 ] + file_on_nfs -writer /mnt/pc/proposition de mise en oeuvre de pci-pra.odt + continue + [ -f /mnt/pc/proposition de mise en oeuvre de pci-pra.odt ] + stat -f -c %T /mnt/pc/proposition de mise en oeuvre de pci-pra.odt + return 0 + [ 0 = 0 ] + SAL_ENABLE_FILE_LOCKING=0 + export SAL_ENABLE_FILE_LOCKING + STAR_ENABLE_FILE_LOCKING=0 + export STAR_ENABLE_FILE_LOCKING + [ -z ] + SAL_NOOPENGL=true + export SAL_NOOPENGL + [ LINUX = LINUX -a INTEL = POWERPC ] + pwd + sd_cwd=/home/pascal + [ -h /usr/lib/openoffice/program/soffice ] + dirname /usr/lib/openoffice/program/soffice + cd /usr/lib/openoffice/program + pwd + sd_prog=/usr/lib/openoffice/program + cd /home/pascal + basename /usr/lib/openoffice/program/soffice + sd_binary=soffice.bin + sd_pagein_args=@pagein-common + sd_pagein_args=@pagein-common @pagein-writer + break + /usr/lib/openoffice/program/../basis-link/program/pagein -L/usr/lib/openoffice/program/../basis-link/program @pagein-common @pagein-writer + [ -x /usr/lib/openoffice/program/../basis-link/ure-link/bin/javaldx ] + /usr/lib/openoffice/program/../basis-link/ure-link/bin/javaldx -env:INIFILENAME=vnd.sun.star.pathname:/usr/lib/openoffice/program/redirectrc + my_path=/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/client:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64 + [ -n /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/client:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64 ] + LD_LIBRARY_PATH=/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/client:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64 + export LD_LIBRARY_PATH + unset XENVIRONMENT + [ -f /etc/adabasrc ] + PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games + export PATH + PYTHONPATH=/usr/lib/openoffice/program/../basis-link/program + export PYTHONPATH + [ -writer = -nologo -o -writer = -no-oosplash ] + [ /mnt/pc/proposition = -nologo -o /mnt/pc/proposition = -no-oosplash ] + [ de = -nologo -o de = -no-oosplash ] + [ mise = -nologo -o mise = -no-oosplash ] + [ en = -nologo -o en = -no-oosplash ] + [ oeuvre = -nologo -o oeuvre = -no-oosplash ] + [ de = -nologo -o de = -no-oosplash ] + [ pci-pra.odt = -nologo -o pci-pra.odt = -no-oosplash ] + [ soffice.bin = soffice.bin -a -x /usr/lib/openoffice/program/oosplash.bin ] + [ != y ] + sd_binary=oosplash.bin + trap kill -9 $! TERM + wait 31713 + /usr/lib/openoffice/program/oosplash.bin -writer /mnt/pc/proposition de mise en oeuvre de pci-pra.odt But if I launch oowriter directly from /usr/lib/openoffice/program/oosplash.bin -writer "/mnt/pc/proposition de mise en oeuvre de pci-pra.odt" I experience no lock and oowriter gui is even A LOT MORE responsive than usual especially when in the file selector where it is usually very very slow to display directory contents !
+ SAL_ENABLE_FILE_LOCKING=0 + export SAL_ENABLE_FILE_LOCKING + STAR_ENABLE_FILE_LOCKING=0 + export STAR_ENABLE_FILE_LOCKING seems to disable the locking & cause trouble... Can you please try to change the script so that it does not set the above to 0, and try again? ccheney: The script is Ubuntu-specific, correct?
Sorry but this change nothing, still the same lock on open. $ ooffice -writer /mnt/pc/proposition\ de\ mise\ en\ oeuvre\ de\ pci-pra.odt + test -z /home/pascal + FILE_LOCKING=auto + OPENGL_SUPPORT=no + [ -f /etc/openoffice/soffice.sh ] + . /etc/openoffice/soffice.sh + FILE_LOCKING=auto + OPENGL_SUPPORT=no + [ -z ] + home_on_nfs -writer /mnt/pc/proposition de mise en oeuvre de pci-pra.odt + stat -f -c %T /home/pascal + return 1 + [ 1 = 0 ] + file_on_nfs -writer /mnt/pc/proposition de mise en oeuvre de pci-pra.odt + continue + [ -f /mnt/pc/proposition de mise en oeuvre de pci-pra.odt ] + stat -f -c %T /mnt/pc/proposition de mise en oeuvre de pci-pra.odt + return 0 + [ 0 = 0 ] + SAL_ENABLE_FILE_LOCKING=0 + export SAL_ENABLE_FILE_LOCKING + STAR_ENABLE_FILE_LOCKING=0 + export STAR_ENABLE_FILE_LOCKING + SAL_ENABLE_FILE_LOCKING=1 + export SAL_ENABLE_FILE_LOCKING + STAR_ENABLE_FILE_LOCKING=1 + export STAR_ENABLE_FILE_LOCKING + [ -z ] + SAL_NOOPENGL=true + export SAL_NOOPENGL + [ LINUX = LINUX -a INTEL = POWERPC ] + pwd + sd_cwd=/home/pascal + [ -h /usr/lib/openoffice/program/soffice ] + dirname /usr/lib/openoffice/program/soffice + cd /usr/lib/openoffice/program + pwd + sd_prog=/usr/lib/openoffice/program + cd /home/pascal + basename /usr/lib/openoffice/program/soffice + sd_binary=soffice.bin + sd_pagein_args=@pagein-common + sd_pagein_args=@pagein-common @pagein-writer + break + /usr/lib/openoffice/program/../basis-link/program/pagein -L/usr/lib/openoffice/program/../basis-link/program @pagein-common @pagein-writer + [ -x /usr/lib/openoffice/program/../basis-link/ure-link/bin/javaldx ] + /usr/lib/openoffice/program/../basis-link/ure-link/bin/javaldx -env:INIFILENAME=vnd.sun.star.pathname:/usr/lib/openoffice/program/redirectrc + my_path=/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/client:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64 + [ -n /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/client:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64 ] + LD_LIBRARY_PATH=/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/client:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/native_threads:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64 + export LD_LIBRARY_PATH + unset XENVIRONMENT + [ -f /etc/adabasrc ] + PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games + export PATH + PYTHONPATH=/usr/lib/openoffice/program/../basis-link/program + export PYTHONPATH + [ -writer = -nologo -o -writer = -no-oosplash ] + [ /mnt/pc/proposition = -nologo -o /mnt/pc/proposition = -no-oosplash ] + [ de = -nologo -o de = -no-oosplash ] + [ mise = -nologo -o mise = -no-oosplash ] + [ en = -nologo -o en = -no-oosplash ] + [ oeuvre = -nologo -o oeuvre = -no-oosplash ] + [ de = -nologo -o de = -no-oosplash ] + [ pci-pra.odt = -nologo -o pci-pra.odt = -no-oosplash ] + [ soffice.bin = soffice.bin -a -x /usr/lib/openoffice/program/oosplash.bin ] + [ != y ] + sd_binary=oosplash.bin + trap kill -9 $! TERM + wait 29281 + /usr/lib/openoffice/program/oosplash.bin -writer /mnt/pc/proposition de mise en oeuvre de pci-pra.odt + [ 0 -eq 79 ] + exit $ ps -ef | grep off pascal 29284 1 1 20:49 pts/1 00:00:00 /usr/lib/openoffice/program/soffice.bin -writer /mnt/pc/proposition de mise en oeuvre de pci-pra.odt -splash-pipe=5 $ kill -9 29284
Created attachment 70893 [details] the script that launch ooo
It would be useful to provide a strace of the soffice.bin process. The summary is misleading; a more correct summary would be "OOo hangs when opening a document on a nfs filesystem". (Without having a strace to look at, we don't know if it actually succeeds in opening (in the OS sense) but then hangs when reading it, or what it is that happens. Also, the "share" term comes from Windows and should not be misused for NFS mounts in my opinion. Also, let's call the user visible phenomenon a "hang" and not overuse the term "lock". Locking in the POSIX and NFS sense might be involved, or not.)
reassigned
.
Created attachment 75318 [details] strace while trying to open a file on nfs filesystem
As Go_oo does not exist anymore, this issue can be closed.