Bug 9180 - Named secondary transfer fails.
Named secondary transfer fails.
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
6.2
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-02-07 11:03 EST by David Lawrence
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:47:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Derek Tattersall 2000-02-07 11:03:55 EST
User named (101.102) does not have permission to create entries in
/var/named/sec so the transfer from the master server fails.
Comment 1 Bernhard Rosenkraenzer 2000-02-07 11:24:59 EST
Neither bind nor caching-nameserver create a /var/named/sec directory.
It was probably created by a user before you updated to b1?
Comment 2 Dale Lovelace 2000-02-11 11:23:59 EST
Moved this bug to "All" architectures.

 Linuxconf uses the /var/named/sec directory to store secondaries. I suppose
Linuxconf creates the directory, here are the permissions:

root@bilbo sec]# pwd
/var/named/sec
[root@bilbo sec]# ls -la
total 8
drwxr-xr-x    2 root     root         4096 Feb 11 12:27 ./
drwxr-xr-x    3 root     root         4096 Feb 11 12:27 ../
[root@bilbo sec]#

  Here is the error from /var/log/messages:
Feb 11 12:28:41 bilbo named[28377]: Forwarding source address is [0.0.0.0].1039
Feb 11 12:28:41 bilbo named: named startup succeeded
Feb 11 12:28:41 bilbo named[28378]: group = 234
Feb 11 12:28:41 bilbo named[28378]: user = named
Feb 11 12:28:41 bilbo named[28378]: Ready to answer queries.
Feb 11 12:28:41 bilbo named-xfer[28382]: can't make tmpfile
(sec/test.redhat.com.Xvai9i): Permission denied

  I suppose since named runs as user named, it doesn't have permission. It looks
like named ran as root in 6.1... Should we move this bug to Linuxconf?
Comment 3 Bernhard Rosenkraenzer 2000-02-11 11:49:59 EST
So it's a linuxconf bug... Reassigning.
Comment 4 Brent Fox 2002-06-05 12:13:24 EDT
Closing because we don't ship linuxconf anymore
Comment 5 Red Hat Bugzilla 2006-02-21 13:47:37 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.