Hi group.
I've got Bind working fine with kernel 2.4.25 but now i've installed 2.6 and
it doesn't start.
I get this message in logs:

Starting BIND: /usr/sbin/named
named: capset failed: Operation not permitted

Can anyone help me?

Thanks in advance,

Nuno Paquete

Nuno Paquete wrote:
> Hi group.
> I've got Bind working fine with kernel 2.4.25 but now i've installed 2.6 and
> it doesn't start.
> I get this message in logs:
>
> Starting BIND: /usr/sbin/named
> named: capset failed: Operation not permitted
>
> Can anyone help me?

Bind-9 won't run if there is a error in the configuration files.
If you missed a dot "." somewhere it won't run.

--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.26 SMP i686 (GCC) 3.3.4
Uptime:8 days, 23:21, 1 user, load average: 1.02, 1.01, 1.00

David wrote:

> Nuno Paquete wrote:
>> Hi group.
>> I've got Bind working fine with kernel 2.4.25 but now i've installed 2.6
>> and it doesn't start.
>> I get this message in logs:
>>
>> Starting BIND: /usr/sbin/named
>> named: capset failed: Operation not permitted
>>
>> Can anyone help me?
>
> Bind-9 won't run if there is a error in the configuration files.
> If you missed a dot "." somewhere it won't run.
>

As I said before when i startup with kernel 2.4.25 it is OK, so the
configuration file must be ok, because if it won't it never should run.

Any more ideas?

Nuno Paquete.

Nuno Paquete wrote:

> Hi group.
> I've got Bind working fine with kernel 2.4.25 but now i've installed 2.6
> and it doesn't start.
> I get this message in logs:
>
> Starting BIND: /usr/sbin/named
> named: capset failed: Operation not permitted

Hi!
Try checking so that you have given the correct rwx to it all. Looks like
you haven't given the read/write rights to the directory/files.

Mike

On Wed, 23 Jun 2004 16:23:22 +0100, Nuno Paquete wrote:
> Starting BIND: /usr/sbin/named
> named: capset failed: Operation not permitted

# modprobe capability ; named ; echo 'it works!'
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

Le 23.06.2004 18:40, Nuno Paquete a écrit :
> David wrote:
>
>
>>Nuno Paquete wrote:
>>
>>>Hi group.
>>>I've got Bind working fine with kernel 2.4.25 but now i've installed 2.6
>>>and it doesn't start.
>>>I get this message in logs:
>>>
>>>Starting BIND: /usr/sbin/named
>>>named: capset failed: Operation not permitted
>>>
>>>Can anyone help me?
>>
>>Bind-9 won't run if there is a error in the configuration files.
>>If you missed a dot "." somewhere it won't run.
>>
>
>
> As I said before when i startup with kernel 2.4.25 it is OK, so the
> configuration file must be ok, because if it won't it never should run.
>
> Any more ideas?
>
> Nuno Paquete.

I've googled for "capset failed: Operation not permitted" and i find two
relevants pages :
One said to recompile bind: http://www.jvds.com/wiki/database/CapSetFailed

the other said is a miss configuration in the 2.6 kernel:
http://www.uwsg.iu.edu/hypermail/lin...03.2/1228.html

If that help ...

/dev/rob0 wrote:

> On Wed, 23 Jun 2004 16:23:22 +0100, Nuno Paquete wrote:
>> Starting BIND: /usr/sbin/named
>> named: capset failed: Operation not permitted
>
> # modprobe capability ; named ; echo 'it works!'

That's it. Thanks.
Now, how can I be sure that this works next time the system starts up?

Nuno Paquete.

On Wed, 23 Jun 2004 20:00:15 +0100,
Nuno Paquete <nmp@ispgaya.pt> wrote:

[ modprobe capability ]

> Now, how can I be sure that this works next time the system starts up?

One way would be to add the modprobe command to the bind_start function
in /etc/rc.d/rc.bind, just before named is started. (There may be a
smarter way, I'm not familar with bind.)


--
Mark Hill <mrhil@gmail.com>

On Wed, 23 Jun 2004 20:00:15 +0100, Nuno Paquete wrote:
> Now, how can I be sure that this works next time the system starts up?

You need The Book:
http://slackware.com/book/
http://slackbook.lizella.net/

I bet that one's in the FAQ as well, but I didn't look to see.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply