Multi Server Setup

[Prorva]

Hello,

We have 2 DA

1. FreeBSD 6.2-RELEASE-p4 in Jail (No firewall)

2. FreeBSD 6.2-RELEASE-p6 in Jail (No firewall)

On both: security.jail.allow_raw_sockets: 1

When I tried to setup Multi Server Setup DA,
I've received the following message:

error binding datagram socket
Unable to open a socket

Any ideas ?

Thanks.

 

[marcvh]

My apologies in advance for bumping an old thread, but we are experiencing the same problem.

We are able to setup sockets on our jailed server itsself, but the directadmin daemon doesn't seem able to.

Some extra info:
- FreeBSD 7.0-RELEASE
- DirectAdmin v1.32.3

Any suggestions?

 

[scsi]

Does your interface match the one in /usr/local/directadmin/conf/directadmin.conf

You would probably have better luck posting on freebsd.org forums as the error is specific to freebsd and not directadmin.

 

[marcvh]

Does your interface match the one in /usr/local/directadmin/conf/directadmin.conf

Yes, it does.

You would probably have better luck posting on freebsd.org forums as the error is specific to freebsd and not directadmin.

We applied some suggestions from FreeBSD such as setting jail_socket_unixiproute_only to no, but without success.

We also tried to open a datagram socket through a C program on the console, which worked:

fmh236# ./datagram
Socket port #55233

The origin from the error is directadmin:

fmh236# pwd
/usr/local/directadmin
fmh236# strings directadmin | egrep "error binding datagram socket|Unable to open a socket"
Unable to open a socket
Unable to download %s.  Unable to open a socket
error binding datagram socket: 
fmh236#

The exact error is slightly different then the one the topic starter wrote:

error binding datagram socket: Invalid argument
Unable to open a socket

I'm curious how DirectAdmin tries to open datagram sockets because we can't reproduce the error in any way on the commandline. Only DirectAdmin inside a FreeBSD jail seems affected. All of our jailed hosts have this problem, and none of the 'normal' ones do.

 

[scsi]

Well you probably should email directadmin support and ask because no one is going to know the answer except for them.