directadmin server problem

felosi

Well-Known Member
#1
Since I upgraded the other night I been getting random shutdowns for no reaosn at all. Server just stops. Upon looking at the logs for the last shutdown here is what it has

2008-06-01 02:09:18.773 [ERROR] HttpListener::start(): Can't listen at address adminListener: Address already in use!
2008-06-01 02:09:18.773 [ERROR] HttpServer::addListener(adminListener) failed to create new listener
2008-06-01 02:09:18.773 [ERROR] [config:admin:listener:adminListener] failed to start listener on address *:7080!
2008-06-01 02:09:18.773 [ERROR] [config:admin:listener] No listener is available for admin virtual host!
2008-06-01 02:09:18.774 [ERROR] Fatal error in configuration, exit!
2008-06-01 02:09:19.001 [NOTICE] [Child: 1008] Start shutting down gracefully ...
2008-06-01 02:09:19.001 [INFO] Stop listener 127.0.0.1:443.
2008-06-01 02:09:19.001 [INFO] Stop listener 127.0.0.1:80.
2008-06-01 02:09:19.001 [INFO] Stop listener 89.248.163.100:443.

Any idea why it would just shut down like that out of nowhere when its been up all day?
 

felosi

Well-Known Member
#2
I notice another problem too but its before this version. Sometimes lshttpd makes too many processes for itself. For example a one core license restarts or something and then has 2 root processes and 2 apache process and its very hard to kill the processes, they do not die immediately. Not sure if this is really a problem or not but I figured id point it out
 

felosi

Well-Known Member
#3
oh wow, since I had to come in and startt it back up tonight its killing itself every few minutes. Here is usual log entries

008-06-01 02:34:59.929 [NOTICE] [Child: 7501] Setup swapping space...
2008-06-01 02:34:59.929 [NOTICE] [Child: 7501] LiteSpeed/3.3.13 Enterprise starts successfully!
2008-06-01 02:35:00.100 [NOTICE] [AutoUpdate] Checking for new releases...
2008-06-01 02:35:00.114 [INFO] [HTAccess] Updating configuration from [/home/freak/domains/warezfreak.org/public_html/.htaccess]
2008-06-01 02:35:00.561 [INFO] [AutoUpdate] No new update.
2008-06-01 02:35:00.718 [INFO] [APVH_www.warezfreak.orgSuphp:] pid list size: 1
2008-06-01 02:35:00.718 [INFO] [APVH_www.warezfreak.orgSuphp:] add child process pid: 7505
2008-06-01 02:35:01.138 [INFO] [HTAccess] Updating configuration from [/home/killer/domains/killerguides.com/public_html/.htaccess]
2008-06-01 02:35:01.140 [INFO] [APVH_www.killerguides.comSuphp:] pid list size: 1
2008-06-01 02:35:01.140 [INFO] [APVH_www.killerguides.comSuphp:] add child process pid: 7509
2008-06-01 02:35:01.475 [INFO] [HTAccess] Updating configuration from [/home/killer/domains/killerguides.com/public_html/images/.htaccess]
2008-06-01 02:35:01.483 [NOTICE] Server Restart Request via Signal...
2008-06-01 02:35:01.483 [NOTICE] [Child: 7501] Start shutting down gracefully ...
 

felosi

Well-Known Member
#4
it keeps on doing this
2008-06-01 02:40:25.838 [NOTICE] Server Restart Request via Signal...

Im gonna roll back and see if it helps.

Nothing is giving it signal, its just doing it
 

felosi

Well-Known Member
#6
yep new version is a dud with directadmin. I just tried to setup a vps with it today, brand new vps, is doing the same thing

Installing the .12 version fixed issue in both situations
 
Last edited:

hadyabed

Active Member
#7
I'm also having this problem, lshttpd crashes and Apache starts up ever since the upgrade. What gives?
-Hady Abed
 
Last edited:

felosi

Well-Known Member
#8
well if you have apache off in the directadmin service monitor it should not start back.

I tried this though every which way, using the apache wrapper and everything with the monitor, it still done it. Only solution was to downgrade to the version before the latest. I would have normally written this off as freak occurence but its happened on 2 servers when I was posting in this thread and I went to setup a vps today and it was a brand new fresh vps - done the same thing. Would just quit out of nowhere and not start back
 

hadyabed

Active Member
#9
Yeah - this is happening on two of my DirectAdmin VPSes. Apache is off in the DirectAdmin service monitor but for some reason it starts right when lshttpd crashes, even though it's off in chkconfig too. Oh well - for now, I've downgraded back to 3.3.12 until a fix becomes available.
-Hady Abed
 
Top