[Bug 893787] New: Pulseaudio does not work with homes on NFS4 mounts
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c0 Summary: Pulseaudio does not work with homes on NFS4 mounts Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai@suse.com ReportedBy: lars.behrens@pi.uka.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Trying to use pulseaudio with home directories on (root_squashed) NFS4 mounts fails. This must be due to not being having sufficient permission to write into users ~, because of root_squash option on the exporting server. Everything works with a local-only user and also if one moves pulse out of ~ via e.g.: export PULSE_CONFIG_PATH=/var/tmp/pulse/pulse-${USER}/.pulse export PULSE_STATE_PATH=/var/tmp/pulse/pulse-${USER}/.pulse export PULSE_RUNTIME_PATH=/var/tmp/pulse/pulse-${USER}/runtime I hardly can believe that we are the only ones stumbling over that so either there is a bug somewhere or some misconfiguration on our side, but that SUSE is freshly installed. Reproducible: Always Steps to Reproduce: 1. Mount ~ from NFS4 2. start pulseaudio: ~$ pulseaudio E: [pulseaudio] core-util.c: Failed to create secure directory (/home/foo/bar/.pulse): Remote I/O error 3. Actual Results: pulseaudio does not work Expected Results: pulseaudio should work -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |lars.behrens@pi.uka.de --- Comment #1 from Takashi Iwai <tiwai@suse.com> 2014-09-01 11:31:47 UTC --- Don't you have $XDG_RUNTIME_DIR environment variable set? As default (unless $PULSE_RUNTIME_PATH is set), $XDG_RUNTIME_DIR/pulse is used for a runtime directory. On my system, $XDG_RUNTIME_DIR is set to /run/user/XXX, so it's on tmpfs. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c2 --- Comment #2 from Lars Behrens <lars.behrens@pi.uka.de> 2014-09-01 13:13:14 UTC --- Didn't touch it, default seems set: ~$ echo $XDG_RUNTIME_DIR /run/user/1261 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c3 --- Comment #3 from Takashi Iwai <tiwai@suse.com> 2014-09-01 13:41:44 UTC --- OK, and do you set other PULSE_* varialbes? If yes, unset them. And remove ~/.pulse directory once if it's present. The recent PA version prefers ~/.config/pulse over ~/.pulse. ~/.pulse is used only if it was created beforehand just for backward compatibility. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c4 Lars Behrens <lars.behrens@pi.uka.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lars.behrens@pi.uka.de --- Comment #4 from Lars Behrens <lars.behrens@pi.uka.de> 2014-09-01 14:15:12 UTC --- No, PuLSE_* are all unset (I mean during testing, for making pulse work I use the settings mentioned in the bugreport) Deleting the dircetories in ~ u mentioned, didn't help: ~$ pactl info Connection failure: Connection refused pa_context_connect() failed: Connection refused Might be of interest that .config/pulse/cookie gets created. (Is there a way to reply via mail, without the need to always log in here?) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> 2014-09-01 14:17:19 UTC --- The more interesting error message would be the one from pulseaudio daemon itself. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c6 --- Comment #6 from Takashi Iwai <tiwai@suse.com> 2014-09-01 14:18:20 UTC --- Also, make sure that you have no ~/.pulse* files, too. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c7 --- Comment #7 from Lars Behrens <lars.behrens@pi.uka.de> 2014-09-01 14:28:52 UTC --- I assume by pulseaudio daemon you mean: ~$ pulseaudio E: [pulseaudio] core-util.c: Failed to create secure directory (/home/pcs/lars/.config/pulse): Remote I/O error Funny thing is that directory already exists like I said above. No other pulse stuff in ~: ~$ find ~ -name "*pulse*" /home/pcs/lars/.config/pulse -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c8 --- Comment #8 from Takashi Iwai <tiwai@suse.com> 2014-09-01 14:38:17 UTC --- Thanks. So the problem remains and shows the very same error. It means that NFS returns -EREMOTEIO error at handling an existing directory somehow. Likely a problem kernel NFS code, supposing that this didn't happen in the past. (You didn't see this in the older kernels, right?) Could you run pulseaudio with strace and check which syscall hits this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c9 --- Comment #9 from Lars Behrens <lars.behrens@pi.uka.de> 2014-09-01 15:14:43 UTC --- Sorry no experience with previous SUSE versions, on Ubuntu up to now. But if it helps I would try with an older one. Last lines of strace: ---------------------------------------------------------------------- lstat("/run/user/1261/pulse", {st_mode=S_IFDIR|0700, st_size=40, ...}) = 0 stat("/home/pcs/lars", {st_mode=S_IFDIR|0701, st_size=126976, ...}) = 0 getuid() = 1261 access("/home/pcs/lars/.pulse", F_OK) = -1 ENOENT (No such file or directory) umask(077) = 022 mkdir("/home/pcs/lars/.config/pulse", 0700) = -1 EEXIST (File exists) umask(022) = 077 open("/home/pcs/lars/.config/pulse", O_RDONLY|O_NOCTTY|O_NOFOLLOW|O_CLOEXEC) = 4 fstat(4, {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0 getuid() = 1261 getgid() = 201 fchown(4, 1261, 201) = -1 EREMOTEIO (Remote I/O error) close(4) = 0 rmdir("/home/pcs/lars/.config/pulse") = -1 ENOTEMPTY (Directory not empty) prctl(PR_GET_NAME, 0xb44500, 0xb44500, 0x7f26d2ea7620, 0x2) = 0 ioctl(2, SNDCTL_TMR_TIMEBASE or SNDRV_TIMER_IOCTL_NEXT_DEVICE or TCGETS, {B38400 opost isig icanon echo ...}) = 0 write(2, "E: [pulseaudio] core-util.c: \33[1"..., 123) = 123 close(3) = 0 exit_group(1) = ? +++ exited with 1 +++ ---------------------------------------------------------------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c10 --- Comment #10 from Takashi Iwai <tiwai@suse.com> 2014-09-01 15:20:32 UTC --- What happens if you run a command like: chown lars:user /home/pcs/lars/.config/pulse ? (suppose your user id is "lars" and group id is "user") -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c11 --- Comment #11 from Lars Behrens <lars.behrens@pi.uka.de> 2014-09-01 15:42:05 UTC --- Aha: ~$ chown 1261:201 /home/pcs/lars/.config/pulse chown: changing ownership of '/home/pcs/lars/.config/pulse': Remote I/O error Same with non-numeric ids or any other created file, file can be written and delete though. Everything normal on lokal file system like /tmp. Ok some nfs/nss/idampd problem? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c12 --- Comment #12 from Takashi Iwai <tiwai@suse.com> 2014-09-01 15:51:33 UTC --- I suppose it's an issue of NFS. To be sure, could you try the older kernel? I've gathered some in OBS home:tiwai:kernel:* project, e.g. home:tiwai:kernel:3.15. Get a package from http:/download.opensuse.org/repositories/home:/tiwai:/kernel:/3.15/ and install it like zypper in --oldpackage kernel-desktop-3.15*.rpm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c13 --- Comment #13 from Lars Behrens <lars.behrens@pi.uka.de> 2014-09-02 09:57:53 UTC --- No luck, same behavior with kernel-desktop-3.15.8-1.1 and even with kernel-desktop-3.8.9-1.61.x86_64 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c14 --- Comment #14 from Lars Behrens <lars.behrens@pi.uka.de> 2014-09-02 09:58:41 UTC --- kernel-desktop-3.15.8-1.1.x86_64 that is -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c15 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nfbrown@suse.com --- Comment #15 from Takashi Iwai <tiwai@suse.com> 2014-09-02 10:08:26 UTC --- OK, so the behavior is consistent and it's no regression. In one side, it's a good news. This makes me wonder whether it's rather a setup problem of NFS server side. Adding Neil to Cc for a better clue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c16 --- Comment #16 from Neil Brown <nfbrown@suse.com> 2014-09-02 10:49:23 UTC --- The error message seems to suggest that the server is returning NFS4ERR_SERVERFAULT rather than NFS4ERR_ACCESS like it should. What OS/kernel is the server running. Can you capture a tcpdump trace while the failure happens and attach that? tcpdump -i INTERFACE -s 0 -w /tmp/dump.pcap or similar. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c17 --- Comment #17 from Lars Behrens <lars.behrens@pi.uka.de> 2014-09-02 13:04:21 UTC --- Server is Debian Squeeze (6.0.10) nfs 1.2.2 Kernel 2.6.32-5 No problems With Ubuntu 12.04 clients so far (kernel 3.2). In the client's tcpdump the only thing which looks supicious at first glance is: 43 1.515130 $SERVER_IP $CLIENT_IP NFS 134 V4 Reply (Call In 42) SETATTR Status: Unknown error: 4261412863 Don't wanna reveal our network traffic here, if you need the tcpdump will send it to nfbrown@suse.com if that's ok? Nothing eye-catching on the server. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c18 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|lars.behrens@pi.uka.de | Resolution| |INVALID --- Comment #18 from Neil Brown <nfbrown@suse.com> 2014-09-03 01:22:50 UTC --- That "Unknown error" is the problem. 4261412863 is 0xFDFFFFFF which is -3 in the wrong byte-order. '3' is ESRCH, which is a little surprising. Definitely a server-side bug though. (downloads Debian kernel patch .... looked through -stable branch...) Oh. 2.6.32-stable contains: commit 63d059e73ff4574b79bd8aa252b5fc00b6326ddf Author: NeilBrown <neilb@suse.de> Date: Wed Feb 16 13:08:35 2011 +1100 nfsd: correctly handle return value from nfsd_map_name_to_* commit 47c85291d3dd1a51501555000b90f8e281a0458e upstream. These functions return an nfs status, not a host_err. So don't try to convert before returning. This is a regression introduced by 3c726023402a2f3b28f49b9d90ebf9e71151157d; I fixed up two of the callers, but missed these two. But it does *not* contain that patch which introduced the regression. If you fix a bug without introducing the bug first.. that ain't good. You should probably report the bug to Debian. I'll report it to -stable. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=893787 https://bugzilla.novell.com/show_bug.cgi?id=893787#c19 --- Comment #19 from Lars Behrens <lars.behrens@pi.uka.de> 2014-09-03 07:36:03 UTC --- Ok. Neill and Takashi thank you for helping! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com