DirectAdmin auto-update to 1.36.0 crashed

Status
Not open for further replies.
L

lowbwtom

Verified User
Joined
Aug 17, 2008
Messages
22
The auto-update kicked in 2 days ago and directadmin has been down ever since. This system had been running without trouble for months. I managed to get DA running again, but now httpd won't start any more. Here's a list of the problems and fixes, so far, restarting the appropriate service(s) between each.

1) libmysqlclient.so.15 not found
(got new file installed, long rigamarole)
2) ioctl can't find the server's ip address for eth0 : No such device
(added ethernet_dev=venet0:0 to directadmin.conf)
3) Syntax error on line 26 of /etc/httpd/conf/ips.conf:
User cannot occur within <VirtualHost> section
(moved user/group statements -- has something overwritten all the config files?)
4) Syntax error on line 7 of /usr/local/directadmin/data/users/admin/httpd.conf:
Port was replaced with Listen in Apache 2.0
(edit httpd.conf, change Port to Listen.)
5) Syntax error on line 22 of /usr/local/directadmin/data/users/admin/httpd.conf:
User cannot occur within <VirtualHost> section
(commented out User/Group statements in VirtualHost sections)
6) (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(totally stumped by this one)

Summary: It looks like the DA update has overwritten many of the configuration files with something that is out of date. the ips.conf and httpd.conf files I fixed were written by DA.

What is wrong with this crazy thing and how do I fix it?
 
back online after 3 days

./build rewrite_confs
seems to fix setup, except changed httpd.conf for server domain so it's feeding from the wrong directory. virtual hosts remained intact. finally, back online again after 3-days down.

It's nice that they list the commands available in the build script. Even nicer would be if there was documentation on what they do and what they are used for. Not all the commands are self-explanatory.

I wonder if this happens with Plesk, too...
 
This is the first time it ever happened to me. All the previous automatic updates worked without any problems. There must be something different about this one. I think it stemmed from the libmysqlclient.so.15 file getting wiped or not properly updated. Some of the steps involved in fixing that may have changed the original configurations. That can happen when you don't really want to make a lifetime occupation of fixing DA and use cookbook solutions you find online, most of which don't work.

I hate it when software tells me something is wrong, but is too stupid to fix it itself.
 
Last edited:
lowbwtom said:
The auto-update kicked in 2 days ago and directadmin has been down ever since. This system had been running without trouble for months. I managed to get DA running again, but now httpd won't start any more. Here's a list of the problems and fixes, so far, restarting the appropriate service(s) between each.

1) libmysqlclient.so.15 not found
(got new file installed, long rigamarole)
2) ioctl can't find the server's ip address for eth0 : No such device
(added ethernet_dev=venet0:0 to directadmin.conf)
3) Syntax error on line 26 of /etc/httpd/conf/ips.conf:
User cannot occur within <VirtualHost> section
(moved user/group statements -- has something overwritten all the config files?)
4) Syntax error on line 7 of /usr/local/directadmin/data/users/admin/httpd.conf:
Port was replaced with Listen in Apache 2.0
(edit httpd.conf, change Port to Listen.)
5) Syntax error on line 22 of /usr/local/directadmin/data/users/admin/httpd.conf:
User cannot occur within <VirtualHost> section
(commented out User/Group statements in VirtualHost sections)
6) (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
(totally stumped by this one)

Summary: It looks like the DA update has overwritten many of the configuration files with something that is out of date. the ips.conf and httpd.conf files I fixed were written by DA.

What is wrong with this crazy thing and how do I fix it?
Click to expand...

For future reference, to fix #1 it's right in the help section: http://help.directadmin.com/item.php?id=236
 
doh. That's where i finally found it. only it's for 64-bit. the 32-bit (most common) version was in fine print and incomplete. there was something else wrong with it too, so that it did not work the first time and had to be diddled with.

I stick by the concept that I should not have to repair DA's internal workings. And I don't see DA taking ownership of the problem.
 
No. I already fixed it myself. Since I've posted this on the forum, they should be aware that they have a problem with their auto-updates. Maybe they will do something about it. If the next one crashes, too, I will turn off the auto-updates.
 
DirectAdmin staff has pointed out many times that these forums are NOT an official support venue, and posting is not the ideal way to bring something to their attention.

The forums are set up to be a self-help community.

Jeff
 
Really. Thank you SO MUCH for setting me on the right path. All praise to thee. Do you see any links to "Support" on this page? No? I rest my case.

I'm done. My problem is solved. I don't want to argue with anyone.
 
Hello,

FYI, a quick email to us would have solved it right away. The problem was with the build of the binaries. We had the MySQL-shared rpm existing on that build system, so the linker linked to the libmysqlclient file. I removed the MySQL-shared rpm on the build system so it doesn't use the linked file, and has the mysql code within the DA binaries. The problem existed for about an hour, at which point it was found and the binaries were fixed and updated.

For anyone with this issue, the simple solution is to grab the new binaries:
http://help.directadmin.com/item.php?id=29

FYI, everyone's system should have MySQL-shared. Our build system is the only case where it doesn't, just so that we ensure our binaries don't link to external files. Installing MySQL-shared (if it's missing), or adding the libmysqlclient file are also options, but the main cause was the DA binaries had changed temporarily.

John
 
Status
Not open for further replies.
Back
Top