problem. Can't start directadmin

[urgido]

Hi people.

I have a big problem. I can't start DA.

./directadmin start
Starting DirectAdmin: [ OK ]

but it's down.

/var/log/directadmin/error.log it's empty.

I need help, pls.

 

[urgido]

wrong forum, sorry. Can some moderator move my post? thanks

 

[daveyw]

What do you get

lsof -ni tcp:2222

netstat -nat | grep :2222

 

[urgido]

thanks,

Result:

netstat -nat | grep :2222
tcp 0 0 0.0.0.0:2222 0.0.0.0:* LISTEN

 

[urgido]

may 28 03:21:33 blazer kernel: [ 1033.114295] firewall: *tcp_in blocked* in=eth0 out= mac=00:1b:b9:6b:6f:b4:00:13:5f:31:57:4a:08:00 src=58.160.80.16 dst=66.197.206.178 len=48 t$
may 28 03:21:33 blazer kernel: [ 1033.116713] firewall: *tcp_in blocked* in=eth0 out= mac=00:1b:b9:6b:6f:b4:00:13:5f:31:57:4a:08:00 src=58.160.80.16 dst=66.197.206.180 len=48 t$
may 28 03:21:33 blazer kernel: [ 1033.117526] firewall: *tcp_in blocked* in=eth0 out= mac=00:1b:b9:6b:6f:b4:00:13:5f:31:57:4a:08:00 src=58.160.80.16 dst=66.197.206.181 len=48 t$
may 28 03:21:33 blazer kernel: [ 1033.118337] firewall: *tcp_in blocked* in=eth0 out= mac=00:1b:b9:6b:6f:b4:00:13:5f:31:57:4a:08:00 src=58.160.80.16 dst=66.197.206.179 len=48 t$
may 28 03:21:33 blazer kernel: [ 1033.120702] firewall: *tcp_in blocked* in=eth0 out= mac=00:1b:b9:6b:6f:b4:00:13:5f:31:57:4a:08:00 src=58.160.80.16 dst=66.197.206.183 len=48 t$
may 28 03:21:36 blazer kernel: [ 1036.349411] firewall: *tcp_in blocked* in=eth0 out= mac=00:1b:b9:6b:6f:b4:00:13:5f:31:57:4a:08:00

i use csf lfd

 

[nobaloney]

Turn off your firewall and see if it works then.

Jeff

 

[urgido]

strange problem.

People of other countries can see all my hosted sites but people of my country (Mexico) can't see my hosted sites.

Very strange. I need help, pls


CSF AND LFD STOPPED

-------------
I CAN CONNECT USING IP BUT NOT DNS. example i can connect 85.66.XXX.00 but not mydomain.com

 

[nobaloney]

And we can't help you because you don't want us to know your IP#. Since the problem is with DNS we need to know domain names and what the IP# should be.

Jeff

 

[urgido]

My nameservers are set in godaddy

main 96.9.147.149

some domains:

Ruiverfvv.com
piensahosting.com
enmueblate.mx
grupoiesa.com

nameservers:
Ns1.piensahosting.info -> 96.9.147.149
ns2.piensahosting.info -> 96.9.147.150


tks

 

[nobaloney]

Please do not give us incorrect information; none of those domains are at 69.9.147.149:

$ dig ruiverfvv.com +short
66.197.206.182
$ dig piensahosting.com +short
96.9.147.151
$ dig enmueblate.mx +short
96.9.147.152
$ dig grupoiesa.com +short
96.9.147.153
$

These all work from here. If they don't work from within Mexico then the problem is not with your server but rather some kind of routing issue within Mexico.

Jeff

 

[urgido]

all information is correct, I talk about my main ip. This sites are hosted on my server with differents ips. I have around 28 usable ips.

BTW, Can you see the sites?

 

[nobaloney]

Yes, I can see the sites. That's what I meant when I wrote: These all work from here.

Jeff

 

[urgido]

Closed, solved. Records a deleted by shutdown issue. Regards