Novell Home

My Favorites

Close

Please to see your favorites.

Starting name server BIND Unable to lock file /etc/nam.conf

This document (7011945) is provided subject to the disclaimer at the end of this document.

Environment

Novell Open Enterprise Server 11 (OES 11) Linux
Novell Open Enterprise Server 2 (OES 2) Linux
novell-named

Situation

novell-named fails to start
unable to start novell-named

Attempting to start the novell-named daemon fails with:

Starting name server BIND Unable to lock file /etc/nam.conf. 
Permission denied

Resolution

Go into yast and modify the Novell AppArmor profile.

1.  yast2 -> novell apparmor -> Edit Profile
2.  Select "/opt/novell/named/bin/novell-named"
3.  Select "Add Entry" -> "File"
4.  Enter /etc/nam.conf in the field
5.  Select "read" and "lock" for the permissions tab
6.  Click ok / done




Cause

The named dameon needs to be able to read / lock the /etc/nam.conf. AppArmor prevents this unless you specify the right.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7011945
  • Creation Date:13-MAR-13
  • Modified Date:13-MAR-13
    • NovellOpen Enterprise Server

Did this document solve your problem? Provide Feedback