DA not working after upgrading to 1.293

If the httpd.conf files need rewriting, type:
Code: 
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
echo "action=rewrite&value=ips" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq d
John
 
We just encountered our first real problem with this upgrade

The file /etc/httpd/conf/ips.conf was completely munged with one users partial httpd.conf file appended to it. Not sure HOW that could have happened, but it took apache right offline (obviously).

A simple edit repaired the file (just deleted the erroneous lines), but it definately caught our attention.
 
Are the issues with this update restricted to CentOS 4 or other OS's as well? Just want to know what OS's are effected before we update, a list off all effected OS's would be great.

Thanks
 
There was 1 corrupted update.tar.gz file.
If your *license* is set to centOS 4.4, and you updated within 24 hours of the release, then you'd need to get a new update.tar.gz (see page 1). Not all 4.4 machines use 4.4. license. Some have the 4.1 license which worked fine. Either way, all OS's will be fine now as it was quickly fixed once identified.

Also, if apache went down, then make sure you have the fixed update.tar.gz, then run the echo commands (page 1 again) to rewrite the ips.conf and httpd.conf files. You'll know if your update.tar.gz is bad by logging into DA and looking at the enhanced skin. You'll have the header repeated many times vertically.

The issue was caused by a network file system error that didn't show up as an error when compressing the the package, else the packaging system would have complained.

John
 
Thanks John... that seems to have fixed the issue.

Ironically, there's several machines with the exact same config (updated at the same time) - only one was affected. I guess I owe some uptime credits to customers.

Thanks for the quick fix
 
Obviously issues like this are never good, but I still stand that updating/upgrading/managing DirectAdmin boxes is by far the least stressful part of my job.

We finally ditched our last Plesk box a few months ago and I've never been happier. I look forward to new DirectAdmin releases, where I dread seeing new Plesk and cPanel releases.

Good work guys.
 
Phantium, there is no reason for that :) The archive has been fixed and there are no bugs now.
 
For anyone who is paranoid, you can backup your update.tar.gz before updating:
Code: 
cd /usr/local/directadmin
cp update.tar.gz update.tar.gz.backup
Then use the manual update procedure. If there are any problems, just extract the update.tar.gz.backup, and run "./directadmin p", then restart DA and you're back to normal.

But... as smtalk mentioned, the issue is gone now ;)

John
 
If I try to update from DA Licensing/Updates section, everytime I see that 1.29.2 is staying instead of being upgraded to 1.29.3

Also, I'm getting this error while trying to do manual update.
[root@helios directadmin]# wget -O update.tar.gz https://www.directadmin.com/cgi-bin/daupdate?uid=[nnnn]\&lid=[nnnnn]
--08:53:07-- https://www.directadmin.com/cgi-bin/daupdate?uid=[nnnn]&lid=[nnnnn]
=> `update.tar.gz'
Resolving www.directadmin.com... 66.51.122.131
Connecting to www.directadmin.com|66.51.122.131|:443... connected.
Segmentation fault
Click to expand...
 
The moral of the story. Never have auto updates checked in DA either.
 
DirectAdmin Support said:
what OS are you trying to update?

For wget, try recompiling:
http://help.directadmin.com/item.php?id=119

John
Click to expand...

CentOS 4.4 32bit

Tried to recompile wget 1.10.2 as suggested, but fails. A snippet of errors is as below :

make[1]: Entering directory `/wget-1.10.2/po'
file=./`echo bg | sed 's,.*/,,'`.gmo \
&& rm -f $file && PATH=../src:$PATH msgfmt -o $file bg.po
/bin/sh: msgfmt: command not found
make[1]: *** [bg.gmo] Error 127
make[1]: Leaving directory `/wget-1.10.2/po'
make: *** [install.mo] Error 2
Click to expand...

After a little research, I found that msgfmt is a part of gettext package...but need help to solve this.

BTW, recently I had updated OpenSSL to 0.9.8e
 
You must log in or register to reply here.
Back
Top