named-xfer exited with signal 1
2007-12-25 10:00:00
error message "named-xfer exited with signal 1" in regard to DNS
services. Results were somewhat inconclusive, however, I appears
to me that it's simply an innocuous bug with Sun's DNS code.
I received only 4 replies. I don't understand why more people don't
see this error. Maybe because most people don't want to be a Secondary
Authoritative Server for a domain.
Our domain .er.usgs.gov represents Eastern Region of U.S. Geological
Survey of the Federal Gov't. We are actually The Center For Coastal
Geology which is a subset of the Eastern Region. As such, we don't
have authority over the .er.usgs.gov domain and there is no
cfcg.er.usgs.gov domain (although I wish there were). So I set our
server up as a Secondary so that it would receive authoritative copies
of the DNS tables for Eastern Region. Those circumstances are,
apparently, somewhat unusual, and the source of the bug. I guess most
people either have control over their domain and are Primary servers or
simply rely on the Primary servers from above and run Caching
(Non-authoritative) servers locally.
If you run a Secondary server locally and get this error message you can
safely ignore it, although it's quite annoying.
If you want to see the 4 replies they are at the bottom.
Thanks for the help.
Regards,
dan
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| _/ _/ _/_/_/_/ _/_/_/ _/_/_/_/ | Dan Penrod - Unix Administrator |
| _/ _/ _/ _/ _/ | USGS Center for Coastal Geology |
| _/ _/ _/_/_/_/ _/ _/_/ _/_/_/_/ | St. Petersburg, FL 33701 |
| _/ _/ _/ _/ _/ _/ | (813)893-3100 ext.3043 |
|_/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ | penrod@whiplash.er.usgs.gov |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Claus Assmann <ca@informatik.uni-kiel.de> replies...
>> Anyone else ever gotten this?
>
>Not this one, but last time I got an error from named the data on the
>main DNS server was corrupt (typing error...). Have you checked it?
Seems logical... I dumped the tables using the "kill -INT `cat /etc/named.pid`"
syntax. The table was, of course, H U G E ! I couldn't see anything
unusual there before I passed out with annuis. Besides, I suspect the
error wouldn't be found in the tables but in the original flat files.
I don't know... I didn't see anything particularly odd (it is DNS of course).
+++
Richard Savage <Richard.Savage@videotron.net> replies...
>I got a similar problem with one of our client who was running a NT server
>with a "record too short" messages
>
>I don't know if this will help but in our case, the problem was that our
>client (who was primary for his domain) had a xfernets entry in his
>named.boot file and the adress he autorized wasn't our (we are secondary
>for them) so he remove it, everything is now OK and the message stopped.
>
>Of course, you can use xfernet... just put the good adresss ... :-)
xferwhat?! I've never heard of xfernet, nor was it mentioned in the
O'Reilly DNS book. Must be an NT thing.
+++
Marina.Daniels@ccd.tas.gov.au (Marina Daniels) replies...
> I get the following message continuously (see the timestamp) on my dns
> machine running solaris 2.4 (Its a sun 5).
> I rang Sun and they said it was an open bug quite a while ago
> The machine functions correctly but it is quite irritating.
>
>Apr 17 07:41:58 falcon named[16190]: named-xfer exited with signal 1
>Apr 17 08:11:55 falcon named[16190]: named-xfer exited with signal 1
>Apr 17 08:11:55 falcon named[16190]: named-xfer exited with signal 1
Quite so! I'm not holding my breath for a solution.
+++
Geert.Devos@ping.be (Geert Devos (org. : Graphidec-Belgium)) replies...
>What version of SunSolve are you running?
>
>I looked up your messages and your bug ID in SunSolve 2.8, and they both
>return the same thing. But it says "5.4, 1.0_a_plus, sol2.4_hw11_94", no
>word about sol2.4_x86.
>
>It doesn't state a solution either, nor does it state a release date.
Yea, I know, I've got an old SunSolve (V2.6.4) and my boss won't pay up
for support. Ya do what ya can with what ya got. ;-)
Anyway, there you go... known bug, no fix.
Thanks guys, I greatly appreciate the feedback. It's things like this
that make you think you're crazy (or drive you there).
Origanl query below...
+++
I write...
Dear Managers:
I just set up a new DNS server on our site. I decided to make it
a secondary server which gets its tables from a DNS server at
headquarters. The server does appear to work well. However, I'm
getting this nasty message on the console and /var/adm/messages...
.
.
.
Apr 16 11:41:29 newwayback named-xfer[10034]: record too short from 130.11.48.2,
zone er.usgs.gov.hosts
Apr 16 11:41:29 newwayback named[10009]: named-xfer exited with signal 1
Apr 16 11:56:30 newwayback named-xfer[10051]: record too short from 130.11.48.2,
zone er.usgs.gov.hosts
Apr 16 11:56:30 newwayback named[10009]: named-xfer exited with signal 1
.
.
.
Sunsolve describes a very very similar bug (#1200678) but for sol2.4_x86.
I'm running 2.4 on a SPARCserver 20. The bug description doesn't name
a solution but suggests it's innocuous.
Anyone else ever gotten this?
Thanks,
dan
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| _/ _/ _/_/_/_/ _/_/_/ _/_/_/_/ | Dan Penrod - Unix Administrator |
| _/ _/ _/ _/ _/ | USGS Center for Coastal Geology |
| _/ _/ _/_/_/_/ _/ _/_/ _/_/_/_/ | St. Petersburg, FL 33701 |
| _/ _/ _/ _/ _/ _/ | (813)893-3100 ext.3043 |
|_/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/_/ | penrod@whiplash.er.usgs.gov |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Comments
Got something to say?
You must be logged in to post a comment.
