[opensuse] libreoffice and NFS ?
I'm hoping someone might recognise the situation - the fileserver has not been touched for at least a year, yet since the last couple of days, multiple clients are having problems when trying to save libreoffice documents. They can read etc, but as soon as you try to save, there's a sharing or permissions issue of some sort. Only with libreoffice, other apps have no issue. Does that ring a bell with anyone? -- Per Jessen, Zürich (7.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 2014-11-20 08:41, Per Jessen wrote:
Does that ring a bell with anyone?
I have been reading similar comments since many years.
In this case something changed, I just need to pin down what it was. To my knowledge it wasn't the server, and although some clients were changed, it also affects those that were not changed. -- Per Jessen, Zürich (7.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I had this issue not long ago on my NAS at home. I had to mount the NFS share with the nolock parameter and libreoffice has had no trouble saving to the NFS share since. On 20 November 2014 12:10, Per Jessen <per@computer.org> wrote:
Carlos E. R. wrote:
On 2014-11-20 08:41, Per Jessen wrote:
Does that ring a bell with anyone?
I have been reading similar comments since many years.
In this case something changed, I just need to pin down what it was. To my knowledge it wasn't the server, and although some clients were changed, it also affects those that were not changed.
-- Per Jessen, Zürich (7.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Paul Groves wrote:
I had this issue not long ago on my NAS at home. I had to mount the NFS share with the nolock parameter and libreoffice has had no trouble saving to the NFS share since.
I've read about that too, but I don't understand how this has suddenly become a problem. I'll see if it makes a difference. What I don't understand - why is it only open/libreoffice that has this problem ?? -- Per Jessen, Zürich (7.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Paul Groves wrote:
I had this issue not long ago on my NAS at home. I had to mount the NFS share with the nolock parameter and libreoffice has had no trouble saving to the NFS share since.
I've read about that too, but I don't understand how this has suddenly become a problem. I'll see if it makes a difference. What I don't understand - why is it only open/libreoffice that has this problem ??
Well, after having googled quite a bit, it would appear that open/libre office has an issue with file locking. I first tried altering the "soffice" script to not enable file locking, but it seems a better option to add "nolock" to /etc/fstab instead. Interestingly, it wasn't sufficient to remount with nolock. -- Per Jessen, Zürich (7.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/11/14 07:55, Per Jessen wrote:
Per Jessen wrote:
Paul Groves wrote:
I had this issue not long ago on my NAS at home. I had to mount the NFS share with the nolock parameter and libreoffice has had no trouble saving to the NFS share since.
I've read about that too, but I don't understand how this has suddenly become a problem. I'll see if it makes a difference. What I don't understand - why is it only open/libreoffice that has this problem ??
Well, after having googled quite a bit, it would appear that open/libre office has an issue with file locking. I first tried altering the "soffice" script to not enable file locking, but it seems a better option to add "nolock" to /etc/fstab instead. Interestingly, it wasn't sufficient to remount with nolock.
When you open a lo doc, it creates a hidden lockfile in the same folder as the doc. If you then try to open it elsewhere, it tells you. Nice. Maybe what you are seeing is a conflict between what lo does internally and what nfs does? IOW if you want the locking, you have it anyway, so no hrm turning it off at fs level. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn wrote:
On 21/11/14 07:55, Per Jessen wrote:
Per Jessen wrote:
Paul Groves wrote:
I had this issue not long ago on my NAS at home. I had to mount the NFS share with the nolock parameter and libreoffice has had no trouble saving to the NFS share since.
I've read about that too, but I don't understand how this has suddenly become a problem. I'll see if it makes a difference. What I don't understand - why is it only open/libreoffice that has this problem ??
Well, after having googled quite a bit, it would appear that open/libre office has an issue with file locking. I first tried altering the "soffice" script to not enable file locking, but it seems a better option to add "nolock" to /etc/fstab instead. Interestingly, it wasn't sufficient to remount with nolock.
When you open a lo doc, it creates a hidden lockfile in the same folder as the doc. If you then try to open it elsewhere, it tells you. Nice.
Yes, that is a nice feature.
Maybe what you are seeing is a conflict between what lo does internally and what nfs does?
I'm beginning to think so, yeah.
IOW if you want the locking, you have it anyway, so no hrm turning it off at fs level.
Ah, I see, thanks. -- Per Jessen, Zürich (7.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Agreed. When I started using opensuse at 12.3 it worked fine for months then suddenly this issue and I have had to mount my NFS share with nolock ever since. On 20 November 2014 17:24, Per Jessen <per@computer.org> wrote:
Paul Groves wrote:
I had this issue not long ago on my NAS at home. I had to mount the NFS share with the nolock parameter and libreoffice has had no trouble saving to the NFS share since.
I've read about that too, but I don't understand how this has suddenly become a problem. I'll see if it makes a difference. What I don't understand - why is it only open/libreoffice that has this problem ??
-- Per Jessen, Zürich (7.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 21/11/14 17:59, Paul Groves wrote:
Agreed. When I started using opensuse at 12.3 it worked fine for months then suddenly this issue and I have had to mount my NFS share with nolock ever since.
On 20 November 2014 17:24, Per Jessen <per@computer.org> wrote:
Paul Groves wrote:
I had this issue not long ago on my NAS at home. I had to mount the NFS share with the nolock parameter and libreoffice has had no trouble saving to the NFS share since.
I've read about that too, but I don't understand how this has suddenly become a problem. I'll see if it makes a difference. What I don't understand - why is it only open/libreoffice that has this problem ??
Hi again If you want NFS to handle the locking, comment the following lines: SAL_ENABLE_FILE_LOCKING=1 export SAL_ENABLE_FILE_LOCKING and restart both the nfs and lo. HTH, L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
lynn wrote:
On 21/11/14 17:59, Paul Groves wrote:
Agreed. When I started using opensuse at 12.3 it worked fine for months then suddenly this issue and I have had to mount my NFS share with nolock ever since.
On 20 November 2014 17:24, Per Jessen <per@computer.org> wrote:
Paul Groves wrote:
I had this issue not long ago on my NAS at home. I had to mount the NFS share with the nolock parameter and libreoffice has had no trouble saving to the NFS share since.
I've read about that too, but I don't understand how this has suddenly become a problem. I'll see if it makes a difference. What I don't understand - why is it only open/libreoffice that has this problem ??
Hi again If you want NFS to handle the locking, comment the following lines: SAL_ENABLE_FILE_LOCKING=1 export SAL_ENABLE_FILE_LOCKING and restart both the nfs and lo.
Yes, I saw that mentioned too, but I think I'd rather change /etc/fstab (on every client) instead of the soffice script. -- Per Jessen, Zürich (7.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 23/11/14 09:20, Per Jessen wrote:
lynn wrote:
On 21/11/14 17:59, Paul Groves wrote:
Agreed. When I started using opensuse at 12.3 it worked fine for months then suddenly this issue and I have had to mount my NFS share with nolock ever since.
On 20 November 2014 17:24, Per Jessen <per@computer.org> wrote:
Paul Groves wrote:
I had this issue not long ago on my NAS at home. I had to mount the NFS share with the nolock parameter and libreoffice has had no trouble saving to the NFS share since.
I've read about that too, but I don't understand how this has suddenly become a problem. I'll see if it makes a difference. What I don't understand - why is it only open/libreoffice that has this problem ??
Hi again If you want NFS to handle the locking, comment the following lines: SAL_ENABLE_FILE_LOCKING=1 export SAL_ENABLE_FILE_LOCKING and restart both the nfs and lo.
Yes, I saw that mentioned too, but I think I'd rather change /etc/fstab (on every client) instead of the soffice script.
That's OK if you don't use nfs for anything else. We had many meetings over this. In the end cifs was the only way to go as we have windows boxes working on microsoft office too although we'd recommend it on a unix only network too. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-23 09:20, Per Jessen wrote:
Yes, I saw that mentioned too, but I think I'd rather change /etc/fstab (on every client) instead of the soffice script.
fstab affects any other program using the share. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2014-11-23 09:20, Per Jessen wrote:
Yes, I saw that mentioned too, but I think I'd rather change /etc/fstab (on every client) instead of the soffice script.
fstab affects any other program using the share.
Good point, thanks Carlos and Lynn. -- Per Jessen, Zürich (7.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-20 13:10, Per Jessen wrote:
Carlos E. R. wrote:
I have been reading similar comments since many years.
Yes, the issues I read about were related to file locks, IIRC.
In this case something changed, I just need to pin down what it was. To my knowledge it wasn't the server, and although some clients were changed, it also affects those that were not changed.
Run a "zypper ps" on the server, to check if there are pending updates to be applied. Try restart the daemon, then. If not, the entire server. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 20 November 2014 08:41, Per Jessen <per@computer.org> wrote:
I'm hoping someone might recognise the situation - the fileserver has not been touched for at least a year, yet since the last couple of days, multiple clients are having problems when trying to save libreoffice documents. They can read etc, but as soon as you try to save, there's a sharing or permissions issue of some sort. Only with libreoffice, other apps have no issue.
what LibreOffice version? There were some bugs related to open or save files in a network sharing (and fixed). Try to check with an updated LibreOffice version. If it doesn't work, try to open a bug report or write here. I'll try to help you. Best, Marina -- Marina Latini http://www.fsugitalia.org http://www.libreitalia.it http://www.libreoffice.org openSUSE Advocate: deneb_alpha -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carlos E. R. -
lynn -
Marina Latini -
Paul Groves -
Per Jessen