[Bug 532415] New: bind-9.5.0p2 - the working directory is not writable? (chroot)
http://bugzilla.novell.com/show_bug.cgi?id=532415 User revealed@freakmail.de added comment http://bugzilla.novell.com/show_bug.cgi?id=532415#c438045 Summary: bind-9.5.0p2 - the working directory is not writable? (chroot) Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: 32bit OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: revealed@freakmail.de QAContact: qa@suse.de Found By: --- Created an attachment (id=313941) --> (http://bugzilla.novell.com/attachment.cgi?id=313941) named.conf User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-1.2 Firefox/3.5.2 I got this in /var/log/messages: # named[3868]: the working directory is not writable So i went and set Ownership for /var/lib/named to "named.named" recursiveley. This fixed the message. But: SuSEconfig reports: (Snippet) # setting /var/lib/named/dev/null to root:root 0666. (wrong owner/group # named:named) # /var/lib/named/dev/null: don't know what to do with that type of file # setting /var/lib/named/dev/random to root:root 0666. (wrong owner/group # named:named) # /var/lib/named/dev/random: don't know what to do with that type of file # ERROR: not all operations were successful. So i set them manually according to the values stated by permissions.d? # named chroot (#438045) This solved that message too. But my guess that these permissions might still not be the proper ones. For example these ones changed from alone only due to rebooting once and restarting named: #/var/lib/named/proc Reproducible: Always Steps to Reproduce: 1. Install named and enable chroot in sysconfig 2. chkconfig named on 3. rcnamed start 4. ls -l /var/lib/named 5. grep "working directory is not writable" /var/log/messages Actual Results: I dont know how to set the permissions properly. Expected Results: Persmissions should be set properly from alone or maybe by permissions.d? Will attach the named.conf (cacheing only) Can you please help on this? A suggestion could be a named file for permissions.d, please?? Many Thanks for your help! Greetings, R -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=532415 User revealed@freakmail.de added comment http://bugzilla.novell.com/show_bug.cgi?id=532415#c1 --- Comment #1 from revealed revealed <revealed@freakmail.de> 2009-08-19 05:22:12 MDT --- I posted this problem in this forum, too: http://www.linux-club.de/viewtopic.php?f=51&t=104967&p=646154 Thats why i opened this one here. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=532415 shuang qiu <sqiu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sqiu@novell.com AssignedTo|bnc-team-screening@forge.pr |ug@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=532415 User ug@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=532415#c2 Uwe Gansert <ug@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #2 from Uwe Gansert <ug@novell.com> 2009-10-01 08:19:44 MDT --- the message is a false alert in the bind code. It's called a bit too early. Moving the permissions check a bit will solve the message too and it's fixed upstream too already. You can ignore that. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=532415 User revealed@freakmail.de added comment http://bugzilla.novell.com/show_bug.cgi?id=532415#c3 --- Comment #3 from revealed revealed <revealed@freakmail.de> 2009-10-01 08:37:06 MDT --- Thanks you :) Greetings, R -- Configure bugmail: http://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=532415 https://bugzilla.novell.com/show_bug.cgi?id=532415#c4 dev001x _ <pgngw+dev001+novell.com@f-m.fm> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |pgngw+dev001+novell.com@f-m | |.fm Component|Network |Network Platform|32bit |All AssignedTo|ug@novell.com |bnc-team-screening@forge.pr | |ovo.novell.com Resolution|WONTFIX | Product|openSUSE 11.1 |openSUSE 11.3 Target Milestone|--- |Final OS/Version|openSUSE 11.1 |openSUSE 11.3 --- Comment #4 from dev001x _ <pgngw+dev001+novell.com@f-m.fm> 2010-11-15 16:18:45 UTC --- (In reply to comment #2)
the message is a false alert in the bind code. It's called a bit too early. Moving the permissions check a bit will solve the message too and it's fixed upstream too already. You can ignore that.
rather than opening a _new_ bug, reopening this one ... i'm seeing the same ERROR with bind9 built/installed from src tarball (bind-9.7.2-P2), and exec from a chroot in /var/lib/named. the chroot includes required devices ... ls -al /var/lib/named/dev/ total 8 drwxr-xr-x 2 named named 4096 2010-11-09 07:45 ./ drwx------ 8 named named 4096 2010-10-18 19:06 ../ srw-rw-rw- 1 root root 0 2010-11-09 07:45 log crw-rw-rw- 1 named named 1, 3 2010-10-18 18:47 null crw-rw-rw- 1 named named 1, 8 2010-10-18 18:47 random crw-rw-rw- 1 named named 1, 9 2010-10-18 18:47 urandom but at, zypper up on exec of 'SuSEconfig', i get the previously reported permission errors for 2 of the 3 devices, .. Additional rpm output: Starting SuSEconfig, the SuSE Configuration Tool... Running module permissions only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.permissions... /var/lib/named/dev/null: don't know what to do with that type of file /var/lib/named/dev/random: don't know what to do with that type of file ERROR: not all operations were successful. Checking permissions and ownerships - using the permissions files /etc/permissions /etc/permissions.easy /etc/permissions.d/mail-server /etc/permissions.d/postfix /etc/permissions.local setting /var/lib/named/dev/null to root:root 0666. (wrong owner/group named:named) setting /var/lib/named/dev/random to root:root 0666. (wrong owner/group named:named) setting /usr/bin/wall to root:tty 2755. (wrong permissions 0755) setting /usr/bin/write to root:tty 2755. (wrong permissions 0755) Finished. sounds like it's an ignorable error, per your earlier comments, but you'd mentioned it was "fixed upstream". do you have a reference for that fix? thanks. -- 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=532415 https://bugzilla.novell.com/show_bug.cgi?id=532415#c Xinli Niu <xlniu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED CC| |xlniu@novell.com AssignedTo|bnc-team-screening@forge.pr |ug@novell.com |ovo.novell.com | -- 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=532415 https://bugzilla.novell.com/show_bug.cgi?id=532415#c5 Uwe Gansert <ug@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME --- Comment #5 from Uwe Gansert <ug@novell.com> 2010-11-23 13:49:09 UTC --- that error has nothing to do with the bug I was talking about above. Please open a new bug if you see that issue with SUSE RPMs -- 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=532415 https://bugzilla.novell.com/show_bug.cgi?id=532415#c6 Peer Heinlein <p.heinlein@heinlein-support.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |p.heinlein@heinlein-support | |.de --- Comment #6 from Peer Heinlein <p.heinlein@heinlein-support.de> 2012-03-11 10:58:39 UTC --- Just FYI: Dies behavior still exists in OpenSUSE 12.1 having bind 9.7. Standard-Installations, no special moditifcations: Mar 11 11:52:55 clustertest1 named[23056]: the working directory is not writable -- 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=532415 https://bugzilla.novell.com/show_bug.cgi?id=532415#c7 --- Comment #7 from Uwe Gansert <ug@suse.com> 2012-03-12 14:57:31 UTC --- yes but that's okay. You can ignore that. bind can really not write into that dir and does not have to. -- 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