Update problem

S

streamservice

Verified User
Joined
Dec 14, 2005
Messages
173
Location
The Netherlands
Hello,

When I update DirectAdmin (version 1.28.1) to the newest version all new options will be enabled) it doesn't update the version number. This isn't really nice and I would like an option to fix this problem.
 
At me the same problem
*** An error has occurred while trying to update the license file ***

and this:
*** An error has occurred while trying to update the software ***
This is an automated message notifying you that an error has occurred while trying to update the software.
The generated error message is as follows:

Error restoring file /usr/local/directadmin/update.tar.gz :
gzip: stdin: not in gzip format
/bin/tar: Child returned status 1
/bin/tar: Error exit delayed from previous errors
: tar returned error code 512<br>


What to do?
 
streamservice,

It did update properly on our servers on which we've run it, and it does show the latest version.

When you click on Licensing / Updates what does it show? If it still shows the old version, try the update again.

igorek,

The error messages shows that the server got a bad update.tar.gz file. Try opening it with a text editor; it probably has a plaintext error message in it that will tell you what went wrong.

If not, then contact DA support staff.

Jeff
 
igorek,

The error messages shows that the server got a bad update.tar.gz file. Try opening it with a text editor; it probably has a plaintext error message in it that will tell you what went wrong.

If not, then contact DA support staff.

Jeff [/B]
Click to expand...

hm...

[root@sv directadmin]# cat update.tar.gz
* You are not allowed to run this program *

[root@sv directadmin]#
 
Presuming you were logged in to either the control panel as admin or the shell as root, and you got that message, then you should probably contact support.

Jeff
 
jlasman said:
streamservice,

It did update properly on our servers on which we've run it, and it does show the latest version.

When you click on Licensing / Updates what does it show? If it still shows the old version, try the update again.

igorek,

The error messages shows that the server got a bad update.tar.gz file. Try opening it with a text editor; it probably has a plaintext error message in it that will tell you what went wrong.

If not, then contact DA support staff.

Jeff
Click to expand...

I did it many times, but all the times there was no error message.
http://[serverip]:2222/CMD_LICENSE?update=program logged in as "admin".

Using the message system I can see the message below:
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

It is completely updated for so far I can see, only the version number isn't updated.
 
Well this just beats everything .... :)

In Licensing / Updates I see the following

Code: 
DirectAdmin Values 

Compiled for                     Redhat Enterprise 4.0 
Server Version                   1.27.4 
Current Available Version        1.286000 
Last Updated                     Tue Jul 25 09:04:32 2006  

Update DirectAdmin

When I click "Update DirectAdmin" it takes a couple of seconds and then replies with .....

Code: 
You already have the most recent version of the program


How do I solve this problem?

Regards,
 
resolveit said:
Well this just beats everything .... :)
Click to expand...
I'm not sure I'd recommend this to just anyone, Onno, but I bet you can follow this suggestion and tell us what you find:

Check the skin to see where the variable comes from that shows the wrong number.

Look in the file the wrong number is coming from and see what it says. Look at it's timestamp to see when it was last updated.

I don't have any idea why this is happening for some folk and not others. My guess is you use the same OS Distribution I use, so let's presume it's not an OS Distribution issue. How about an issue of what the old version was? I don't see how that could happen.

Perhaps DA support staff can give us some idea.

Jeff
 
Hello,

My guess is that you actually already have the latest version of DA on disk. However, this new version isn't active because DA didn't get restarted.. so first restart DA and I'm guessing the new version will pop up ;)

/etc/init.d/directadmin restart

or

/usr/local/etc/rc.d/directadmin restart
(for freebsd)

Check your version manually:

cd /usr/local/directadmin
./directadmin v

If you actually still have an old version, update manually:
http://help.directadmin.com/item.php?id=29

John
 
The operating system I use: Debian 3.1

When I do a check manually on the version it shows the correct version, how is it possible that it still shows an older version in DirectAdmin (even after 5 restarts off DirectAdmin)?

I only use the enhanced skin and that skin shouldn't be any problem for so far I know.

EDIT:
I solved this problem using the options below:
- Login to ssh as root (if needed use su root)
- Find in the Service Monitor page off DirectAdmin the PID numbers used by DirectAdmin (for example: directadmin (pid 4794 4800 4816 4820 5002 5007 ))
- Remember this numbers (you normally only need the first number, in this case 4794)
- Go back to ssh
- Give the following commands in ssh (don't copy the comments between ( and ) to let it work):
-- cd /usr/local/directadmin
-- ./directadmin v (looks if DirectAdmin has the correct version number, if not -> manually update DirectAdmin using the howto for manually updating DirectAdmin)
-- kill [pid] (where [pid] is the number found in DirectAdmin, in this case 4794)
-- ./directadmin (looks if the version number is changed)
-- /etc/init.d/directadmin restart (DirectAdmin should be started with the correct version number)

Login to DirectAdmin (normally port 2222) to check if the problem is fixed.

Only used 1 time on a Debian 3.1 server with DirectAdmin version 1.28.6 (current version).

Onno if you have still questions after this short howto for updating the version number you can also contact me by e-mail of phone (you should be able to find this on www.streamservice.nl/?page=contact, because I think you are from resolve-it.nl)
 
Last edited:
streamservice,

Isn't that the same as what DA Support said? I don't see anything except you restarting DirectAdmin.

You can restart DA from the control panel. You can also restart it from the shell a bit easier; the following is the command for systems which use the init.d directory (i.e, RedHat and some others):

# service directadmin restart

Jeff
 
If the pid file ever becomes "off" the restart command will try to restart a process that might not exist. The manual way to restart DA would be:
Code: 
cd /usr/local/directadmin
killall -9 directadmin
./directadmin d
Which shouldn't ever have any problems working ;) We can't use killall in the boot script because the script is also named directadmin, so it would end up commiting suicide in the "stop" portion of the restart... the script would have killed itself before DA starts up again, hence we use pid files (freebsd/debian anyway, rehats have smart built-in functions for restarting)

John
 
You must log in or register to reply here.
Back
Top