On Sun, 21 Dec 2014, 16:42:58 +0100, Achim Gratz wrote:
Basil Chupin writes:
connect() failed on local socket: No such file or directory Internal cluster locking initialisation failed. WARNING: Falling back to local file-based locking. Volume Groups with the clustered attribute will be inaccessible. Found openSUSE 13.1 (x86_64) on /dev/sda4 done
Now, I don't know what the above means but I suspect that it has something to do with Tumbleweed stuffing up my desktop's grub menu (which I had to replace my re-installing 13.1).
No, it means that LVM is set up incorrectly. Do an
lvmconf --disable-cluster
and this message should be gone. But other than being annoying it shouldn't be a problem AFAIK.
I have just "zypper dup"'ed several machines here and got a hung when installing the "lvm2" package; running pstree in a separate window showed rpm and an install script running as the only _active_ processes. The install script tried to restart several services, but that apparently lead to a hang: /usr/bin/systemctl try-restart lvm2-lvmetad.service blk-availability.service lvm2-monitor.service lvm2-lvmetad.socket >/dev/null 2>&1 || : I'm not sure, why this could hang the whole upgrade, but (smoothly) killing the script resulted in a smooth continuation of the whole upgrade process ran further ;) FWIW, the presets for LVM configuration appear to be wrong in any case; even on my 13.1 system, "locking_type" is set to 3 which means, that the built-in clustered locking should be used... hmm, even on a non-clustered setup :( According to "lvm.conf (5)", "1 is the default", but it gets set to 3 instead...
Regards, Achim.
Cheers. l8er manfred