Hello ,
We have FreeBSD 5.1 on server.Today our exim is down and error is:
server# /etc/init.d/exim start
exim exim.: Can't open /etc/rc.d/init.d/functions: No such file or directory
Could not create INET socket: Address already in use IO::Socket::INET: Address already in use

Now my /var/log/messages say this :
Jul 20 08:04:36 server named[70804]: could not listen on UDP socket: permission denied
Jul 20 08:04:36 server named[70804]: creating IPv4 interface fxp0 failed; interface ignored
Jul 20 08:04:36 server named[70804]: could not listen on UDP socket: permission denied
Jul 20 08:04:36 server named[70804]: creating IPv4 interface fxp0 failed; interface ignored
Jul 20 08:04:36 server named[70804]: could not listen on UDP socket: permission denied
Jul 20 08:04:36 server named[70804]: creating IPv4 interface lo0 failed; interface ignored
Jul 20 08:04:36 server named[70804]: not listening on any interfaces
What could be problem ?
My named isn't listening to any interfaces at all..
Please help !!!

I can help pm me

Be carefull on who you let in your server!
zeeklancer, Is it possible to explain your fix here, I would like to know myself?

I could if I knew for sure what the probme is, there are many things that could be causing this problem.

Here is something that MIGHT help

http://forums.cpanel.net/showthread.php?t=26532

Hi,

I'm looking at using FreeBSD 5.x on an EV1 server but EV1 only supply 4.x servers at this stage. Can I ask how you managed to get 5.1 on your server, if this is in fact an EV1 server?

Many Thanks,

Techbrat

You can upgradse the current install, or reinstall using your swap parititon.

(install a small version of freebsd on your swap partition then boot to the swap and then install the newer version on the main parititon.

There is a permission problem some place, somebody would have to look around (unless somebody has had the exzact same thing happen before)

I may be wrong but freebsd chroots its named...

This indicates that the SysV init functions file is missing

That looks to me like a Linux startup script, not a FreeBSD startup script .. FreeBSD startup scripts are in /etc/ or /usr/local/etc/rc.d/ and the functions file they use is /usr/local/etc/rc.subr (on my FreeBSD 4.9 box it is) .. or is there a SysV-init package that EV1 installs on it's FreeBSD images? My *BSD install is one I did myself, not an EV1 image ..

The named errors do look like permissions issues. I don't think named is installed in a chroot jail by default on FreeBSD, I think you have to explicitly run the port install for that version or use the jail script yourself for that.



Is the closest port I see related to both named and jail|chroot, so unless he explicitly jailed named, my guess it that it isn't running chrooted.

Found this via google ... looks like the same issue as yours .. this person fixed it by moving the named config from /etc/rc.conf to /etc/rc.local

http://lists.freebsd.org/pipermail/freebsd...ber/059114.html

http://lists.freebsd.org/pipermail/freebsd...ber/059136.html

Looks like I was wrong , the bind install does let you easily specify a chroot setup .. maybe because named isn't reading your configuration parameters correctly it is trying to run itself in a chroot environment and failing to open the fxp interface because you hadn't set up the jail ....