Error migrating from 1.5 to 1.6?

[Juan Carmona]

Hi guys

We are getting the following error when try to reconnect to proxmox via http.

May be the process update can take a long long time? We launch it 20 minutes ago...

Help? :-S

Thanks in advance,

Juan Carmona
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, postmaster@antispam.intra.cerdanyola.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.
[19571]ERR: 24: Error in Perl code: Can't locate object method "clusterinfo" via package "Proxmox::Config::System" at /var/www/proxmox/base.epl line 13.
[19571]ERR: 24: Error in Perl code: Can't call method "nav_rule" on an undefined value at /var/www/proxmox/base.epl line 166.
[19571]ERR: 24: Error in Perl code: Can't call method "nav_config" on an undefined value at /var/www/proxmox/base.epl line 170.
[19571]ERR: 24: Error in Perl code: Can't call method "nav_admin" on an undefined value at /var/www/proxmox/base.epl line 173.
[19571]ERR: 24: Error in Perl code: Failed to locate method (ping) in class (Proxmox::ConfigServer) at /usr/share/perl5/SOAP/Lite.pm line 2337.

Apache/1.3.33 Ben-SSL/1.55 (Debian GNU/Linux) mod_perl/1.29 HTML::Embperl 1.3.6 [Tue Oct 31 11:53:04 2006]

 

[martin]

Hi guys

We are getting the following error when try to reconnect to proxmox via http.

May be the process update can take a long long time? We launch it 20 minutes ago...

Help? :-S

Thanks in advance,

Juan Carmona
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, postmaster@antispam.intra.cerdanyola.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.
[19571]ERR: 24: Error in Perl code: Can't locate object method "clusterinfo" via package "Proxmox::Config::System" at /var/www/proxmox/base.epl line 13.
[19571]ERR: 24: Error in Perl code: Can't call method "nav_rule" on an undefined value at /var/www/proxmox/base.epl line 166.
[19571]ERR: 24: Error in Perl code: Can't call method "nav_config" on an undefined value at /var/www/proxmox/base.epl line 170.
[19571]ERR: 24: Error in Perl code: Can't call method "nav_admin" on an undefined value at /var/www/proxmox/base.epl line 173.
[19571]ERR: 24: Error in Perl code: Failed to locate method (ping) in class (Proxmox::ConfigServer) at /usr/share/perl5/SOAP/Lite.pm line 2337.

Apache/1.3.33 Ben-SSL/1.55 (Debian GNU/Linux) mod_perl/1.29 HTML::Embperl 1.3.6 [Tue Oct 31 11:53:04 2006]

hi,
please login vial ssh and restart apache:

/etc/init.d/apache-ssl restart

if this does not help, reboot.

If you system is under load, it coud take considerable long as we changed a view things in the database structure.

best regards,
martin

 

[Juan Carmona]

Hi Martin

Before we restart services o reboot the mail gateway... The htpp logon screen shows the actual version as 1.5, not 1.6. May be the update process is running at all.

We wait for one hour before restart services.

Thanks in advance,

Juan Carmona

 

[Juan Carmona]

After restart apache the error we are getting is as follows

FYI

Best regards,

Juan Carmona

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, postmaster@--- and inform them of the time the error occurred, and anything you might have done that may have caused the error.

[20839]ERR: 24: Error in Perl code: Failed to locate method (ping) in class (Proxmox::ConfigServer) at /usr/share/perl5/SOAP/Lite.pm line 2337.

Apache/1.3.33 Ben-SSL/1.55 (Debian GNU/Linux) mod_perl/1.29 HTML::Embperl 1.3.6 [Tue Oct 31 12:44:12 2006]

 

[dietmar]

Version 1.6 is a major database upgrade, and converting the old database can take a long time if you have a slow maschine and a large database?

I recomment to stop/block incomming mail traffic (on the firewall) until the database update is finished - this will speed up the upgrade process. A reboot will not solve the problem)

- Dietmar

 

[dietmar]

Ok, this looks like the database upgrade is still in progress.

- Dietmar

 

[Juan Carmona]

Hello

Well, we wait after lunchtime to get any decission. The system is running but the only part that is in trouble is the web interface.
We give a chance to the 'slow' database upgrade process.

Best regards,

Juan Carmona

 

[Juan Carmona]

Well... After reset the proxmox server we have no SSH nor http connection.
Console shows the following message:

Sync Proxmox configuration

And the system is 'halted'. Responds to ping but no way to connect it!

Help?

Best regards,

Juan Carmona

 

[dietmar]

You can try again to reboot by turning power on/off. If that does not help you need to reinstall if we can't connect via ssh (use the 1.6 iso image).

- Dietmar

 

[Juan Carmona]

Hi

We reset the server and reinstall the 1.6 version but the init load console locks at

Sync Proxmox configuration

Best regards,

Juan

 

[dietmar]

Please open tcp port 2703 on the firewall

Hi Juan,

I guess we found the problem. You need to enable the Razor Port on the
firewall. Else Razor registration takes infinite time.

So please enable port 2703 from proxmox to internet and test again.

- Dietmar

 

[Juan Carmona]

Hi there

The upgrade was made successfully after open the port 2703 for Razor.

Thanks to Dietmar, Martin and all the staff for the quality of support.

Best regards,

Juan Carmona

 

[ahoyer2]

We're experiencing the same problem that Juan reported. The error that we got when running the upgrade was:

DBD:g::db do failed: ERROR: duplicate key violates unique constraint "cgreylist_pkey"
dpkg: error processing proxmox-mailgateway (--install):

At the end of the upgrade it says:

Analyzing/Upgrading existing Databases...DBD:g::db do failed: ERROR: duplicate key violates unique constraint "cgreylist_pkey"
dpkg: error processing proxmox-mailgateway (--install):
subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
proxmox-mailgateway
error during install

A reboot brought the server back online, but one of the pages is still failing:

statistics/general fails with a [3048]ERR: 24: Error in Perl code: DBD:g::db do failed: ERROR: column "mtime" of relation "dailystat" does not exist

Is there a way to verify that the installation is stable? Also, our outgoing ports are open at the firewall so port 2703 is accessible to the proxmox server.

 

[Juan Carmona]

Hi there

As Dietmar says our case was resolved by open the 2703 port at firewall. All due to a razor2 registration issue.

Best regards,

Juan

 

[dietmar]

We're experiencing the same problem that Juan reported. The error that we got when running the upgrade was:

DBD:g::db do failed: ERROR: duplicate key violates unique constraint "cgreylist_pkey"
dpkg: error processing proxmox-mailgateway (--install):

Please try to install the servicepack again. If you give us ssh access we can debug directly on your server (send login data to 'dietmar@proxmox.com')

 

[dietmar]

We're experiencing the same problem that Juan reported. The error that we got when running the upgrade was:

DBD:g::db do failed: ERROR: duplicate key violates unique constraint "cgreylist_pkey"
dpkg: error processing proxmox-mailgateway (--install):

Just a guess, but did you update during the server receives mail?

 

[ahoyer2]

Dietmar,

Yes, the server was still receiving external e-mail during the upgrade. I'll close the incoming port temporarily while re-applying the update. Thanks,

Alex.

 

[ahoyer2]

Hi Dietmar,

I applied the servicepack again, but got more errors. I reverted to the VM that was running before the upgrade (I had a backup), closed incoming e-mail ports and this time the upgrade had no problems. I would suggest putting a note on the servicepack download that the proxmox server should not be receiving e-mails during the upgrade.

Thanks for your help,

Alex

 

[dietmar]

I would suggest putting a note on the servicepack download that the proxmox server should not be receiving e-mails during the upgrade.

Thanks for that hint.

- Dietmar