creating IPv4 interface lan2:4 failed; interface ignored

[joseph51]

Hi ,

I am daily getting the following error messages from the syslog .

named.64[28315]: creating IPv4 interface lan2:4 failed; interface ignored
named.64[28315]: creating IPv4 interface lo0 failed; interface ignored
named.64[28315]: creating IPv4 interface lan2:3 failed; interface ignored
named.64[28315]: creating IPv4 interface lan3 failed; interface ignored
named.64[28315]: creating IPv4 interface lan2 failed; interface ignored
named.64[28315]: creating IPv4 interface lan0 failed; interface ignored
named.64[28315]: creating IPv4 interface lan5 failed; interface ignored

Its repeating many times . But when I check in the server its shows everything is up and running

From the cmviewcl -v command all teh interface are showing up

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/0/14/1/0/6/0 lan2
PRIMARY up 0/0/14/1/0/6/1 lan3
PRIMARY up 1/0/14/1/0/6/1 lan5
STANDBY up 1/0/14/1/0/6/0 lan4


Also from lanscan command also everything showing up
root@hostname:/etc/cmcluster : lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/6/1/0/6/0 0x00215ADE0CF0 0 UP lan0 snap0 1 ETHER Yes 119
0/0/6/1/0/6/1 0x00215ADE0CF1 1 UP lan1 snap1 2 ETHER Yes 119
0/0/14/1/0/6/0 0x001E0B838270 2 UP lan2 snap2 3 ETHER Yes 119
0/0/14/1/0/6/1 0x001E0B838271 3 UP lan3 snap3 4 ETHER Yes 119
1/0/14/1/0/6/0 0x00215ADE0C2A 4 UP lan4 snap4 5 ETHER Yes 119
1/0/14/1/0/6/1 0x00215ADE0C2B 5 UP lan5 snap5 6 ETHER Yes 119
LinkAgg0 0x000000000000 900 DOWN lan900 snap900 8 ETHER Yes 119
LinkAgg1 0x000000000000 901 DOWN lan901 snap901 9 ETHER Yes 119
LinkAgg2 0x000000000000 902 DOWN lan902 snap902 10 ETHER Yes 119
LinkAgg3 0x000000000000 903 DOWN lan903 snap903 11 ETHER Yes 119
LinkAgg4 0x000000000000 904 DOWN lan904 snap904 12 ETHER Yes 119
root@Hostname:/etc/cmcluster :

Can some one please tell me why this kind of error messages are coming daily . is there anything wrong in the server

[Matti_Kurkela · Accepted solution]

> named.64[28315]: creating IPv4 interface lan2:4 failed; interface ignored

The beginning of the log messages may indicate they're coming from process "named.64", with PID 28315.

Normally "named" is a DNS server daemon; it should *never* be in the business of configuring NICs at all. But I also don't know why it should have the suffix .64 in its name; this is probably a customized installation of named?

Googling for the error message text tells me this is a fairly common error message from named, and usually means named is failing to set up a port to listen *on* those interfaces. So the wording of the error message is less than clear.

Perhaps you have two copies of named running, using the same configuration? In that case, the first one opens all the ports it needs, and the second one fails because those ports are already in use by the first one. Apparently named does not always stop in that situation, but waits and tries again to reclaim the ports once in a while. Or perhaps some script is trying to restart the second copy of named?

MK

[joseph51]

Yes . I could see that there are two named process running on the system

ps -ef | grep -i named
root 28315 1 0 Jan 13 ? 0:11 /usr/sbin/named.64
root 4438 4393 1 09:42:16 pts/1 0:00 grep -i named
root 25812 1 0 Jan 13 ? 3:17 /usr/sbin/named.64
root 27231 15207 0 Jan 21 pts/4 0:00 cat /etc/named


So to resolve this issue I can kill the process which is running with the PID 28315 right ?
Please clarify me

[Matti_Kurkela]

> So to resolve this issue I can kill the process which is running with the PID 28315 right ?

Yes, that should stop the error messages.

But the issue won't be perfectly solved unless you find out _why_ the second copy of named.64 was started on January 13th.

If it was a sysadmin error, there probably was some reason to restart it.

For example, if named configuration was changed at that day, but someone forgot to stop the old named.64 process before starting the new one, then the old one might still be running an old version of configuration. In that case, you might want to stop the other named.64 process too and restart it, and then verify that named works as it should, paying special attention to the configuration features changed on Jan 13th.

If the extra process was started by some sort of automatic monitoring system, it obviously failed to detect that another named process was already running. In that case, you might want to find out how the monitoring system detects that named needs restarting, and see if you can improve it to prevent a chance of "misfire".

Of course, real life is not always perfect; if you cannot find the cause of the extra named.64 process, you may have to just wait and see if it happens again.

MK

[joseph51]

Thanks for your replay . I killed the process , and now only one namedd process is running .

Issue resolved