Error with Automatic Update

(K Dennis) #1

I am seeing this error using the Automatic Update Script.

    Your system is backed up to ./squiz_matrix3-2012-10-07_18-12-backup.tar.gz
    
    [ OK ]
    Check out new code, using tag "mysource_4-10-1"             [ Checking out MySource Matrix Core... ][ FAILED checking out MySource Matrix Core ]
    Unknown host public-cvs.squiz.net.
    *ERROR* Could not check out code from CVS (failed cmd: "cvs -d ':pserver:anonymous@public-cvs.squiz.net:/home/public/core' co -d 'mysource_4-10-1' -r mysource_4-10-1 -P mysource_matrix 2>&1")
    [ Error ]

I am running this command: php /root/automatic_upgrades/matrix_upgrade.php --verbose /var/www/squiz_matrix3 mysource_4-10-2

and I am upgrading from 4-8-2.

the error occurs after reaching this milestone:

Upgrade to 4.10.0 complete.



Can anyone suggest a way to overcome this problem, please?

(Chris Smith) #2

Hi,

[quote]

I am seeing this error using the Automatic Update Script.


    Your system is backed up to ./squiz_matrix3-2012-10-07_18-12-backup.tar.gz
    
    [ OK ]
    Check out new code, using tag "mysource_4-10-1"             [ Checking out MySource Matrix Core... ][ FAILED checking out MySource Matrix Core ]
    Unknown host public-cvs.squiz.net.
    *ERROR* Could not check out code from CVS (failed cmd: "cvs -d ':pserver:anonymous@public-cvs.squiz.net:/home/public/core' co -d 'mysource_4-10-1' -r mysource_4-10-1 -P mysource_matrix 2>&1")
    [ Error ]

I am running this command: php /root/automatic_upgrades/matrix_upgrade.php --verbose /var/www/squiz_matrix3 mysource_4-10-2

and I am upgrading from 4-8-2.

the error occurs after reaching this milestone:

Upgrade to 4.10.0 complete.



Can anyone suggest a way to overcome this problem, please?

[/quote]



I just tested it from a server outside our network (so not in our firewalls etc) and it worked fine.



Can you make sure you're allowing outgoing connections on port 2401 ?

(K Dennis) #3

Thank You Chris Smith,

[quote]Can you make sure you're allowing outgoing connections on port 2401 ?[/quote]



Port 2401, was indeed the cause. After port 2401 was opened the update completed without a hitch.