1.32.2 to 1.32.3 (centos4.4)

[erohas]

Maybe it's a bug

when i push an update link, it's looks well, then i recieve an email that DA "Has been updated"

but no changes and version is still 1.32.2 (centos 4.4) x 3 servers

but on other server (centos 5.0) DA has been updated success!

[jpetersen]

I can confirm the same issue for CentOS 4.x. I've tried updating manually, and via the link when logged into DA as admin. It doesn't actually appear to be getting updated. Here's an email I sent to support@ earlier:



Hi,

I can't seem to figure out how to update DirectAdmin on this server. I have
tried 2 different methods.

This is the first method I tried, from the shell, as root:

Updating DirectAdmin Manually
http://help.directadmin.com/item.php?id=29


The second method I tried was by:
1. logging into directadmin as "admin"
2. clicking on "Licensing / Updates"
3. clicking "Update DirectAdmin"


Despite my best efforts, I still see this when logged into DirectAdmin:

Server Version 1.32.2
Current Available Version 1.323000



Here's some strings output of some binaries in /usr/local/directadmin
on that same server:
# strings directadmin dataskq | grep 1.32
1.32.2
1.32.2


and here's what I see on a brand new VDS I just built:
# strings directadmin dataskq | grep 1.32
1.32.3
1.32.3

Can you please tell me what I'm missing here? I've searched the forums,
the documentation, and the knowledge base, and I can't for the life of
me figure out what I'm doing wrong. The license is valid:

(license info here)

and I even clicked "Update License" before trying "Update DirectAdmin"
again. No luck.

Any input would be appreciated.

Thanks.



and a followup:



I can verify that when using the method above, that
/usr/local/directadmin/data/task.queue is populated
with the contents below:

[root@host /usr/local/directadmin]# cat data/task.queue
action=update&value=program



The data/task.queue file does disappear within 1 minute
and the cron is run. From /var/log/cron:

Sep 16 17:16:01 host crond[22383]: (root) CMD (/usr/local/directadmin/dataskq)


The permissions on the file appear good as well:

[root@host /usr/local/directadmin]# ls -l data/task.queue
-rw------- 1 diradmin diradmin 28 Sep 16 15:07 data/task.queue


Port 80 is also permitted outbound (which I presume is necessary
for the update work).


Hopefully this extra info can help narrow down what the issue could
be.

Thanks.



I too see the messages in the Message System titled "DirectAdmin has been updated", all of which state the following:



This is an automated message notifying you that the DirectAdmin software has been successfully updated.

To view what has changed, please visit:

http://www.directadmin.com/versions.php



EDIT

More info: this is all that happens when trying to update from inside DA:

From /var/log/directadmin/2008-Sep-16.log:


16/09/2008:17:26:50 x.x.x.x GET /CMD_LICENSE HTTP/1.1 admin


and from /var/log/directadmin/system.log:




2008:09:16-17:27:06: Update of software successfull!
2008:09:16-17:27:06: signal TERM received. Waiting for children to exit
2008:09:16-17:27:06: Clean shutdown successful
2008:09:16-17:27:06: directadmin restarted



There is nothing logged to /var/log/directadmin/{error.log,errortaskq.log,security.log} during the update attempt.

[jpetersen]

Here's the response from DA:



The 4.4 binaries are not updated yet as we had a disk failure for that box.
You can either use the 4.x static binaries, or wait until we fix the 4.4 box and get the release out.


That would explain it :-)

[roly]

my server is currently centos 4.7 but in directadmins licencing/updates section it is showing "compiled on centos 4.4". does anyone know how to update this to reflect the fact i am running 4.7, or is this not important?

thanks in advance

roland

[chatwizrd]

It is not important. It should just be 4.x but whatever works.

[donkeyKICK]

Any idea when this will be fixed? I am having the same issue.

[hklcf]

The 4.4 build system had a disk failure, thus wasn't included.
If you have the ability to change the OS in our system (/clients) you should be able to change the licenses to CentOS 4.x (static) which should work fine.
The 4.4 binaries were dynamic.

Reply from John