dpkg: error processing proxmox-ve (--configure):

[nigelr]

Hi,

ProxMox Ve looks amazing.... I ran it up on Virtual machine under fusion on my MacPro and worked great.

I then tried to do the same on my ESXi box and it failed during the install... I then brought down my ESXi box and tried on a new hard disk to install directly and had the same issue...

Server is an Asus RS161-E2
Dual Opteron Processors
4GB ECC memory

THE ISSUE
The machine boots off the installation CD and does the file installs, after that it brings up a screen of final config information, these are some of the last lines...

Creating SSH2 RSA key; this may take some time ...
Creating SSH2 DSA key; this may take some time ...
dpkg: error processing proxmox-ve (--configure):
subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
proxmox-ve


Also, if it helps... With debug on I saw this in the initial screens... I think its unrelated but any info may help
ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ffc00000-0x00000000ffffffff - kernel bug?

I am excited about getting this working on my box (instead of ESXi) and hope someone can shed some light.

Thanks in advance,
Nigel

 

[martin]

Hi,

ProxMox Ve looks amazing.... I ran it up on Virtual machine under fusion on my MacPro and worked great.

I then tried to do the same on my ESXi box and it failed during the install... I then brought down my ESXi box and tried on a new hard disk to install directly and had the same issue...

Server is an Asus RS161-E2
Dual Opteron Processors
4GB ECC memory

THE ISSUE
The machine boots off the installation CD and does the file installs, after that it brings up a screen of final config information, these are some of the last lines...

Creating SSH2 RSA key; this may take some time ...
Creating SSH2 DSA key; this may take some time ...
dpkg: error processing proxmox-ve (--configure):
subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
proxmox-ve


Also, if it helps... With debug on I saw this in the initial screens... I think its unrelated but any info may help
ck804xrom ck804xrom_init_one(): Unable to register resource 0x00000000ffc00000-0x00000000ffffffff - kernel bug?

I am excited about getting this working on my box (instead of ESXi) and hope someone can shed some light.

Thanks in advance,
Nigel

so you got the same problem:

1. install as a VM on esxi
2. install on bare-metal

can you confirm this? if yes, i can try to reproduce it on esxi.

and you got no problems running it on Fusion (on mac osx)?
(without KVM)

 

[nigelr]

Yes... Seems like same issue on bare metal install or under ESXi on the same machine.

Worked great under fusion on the Xeon in the MacPro..

 

[dietmar]

Please verify your installation media (md5sum) - maybe the media is corrupt?

 

[Onyx]

I think I am in the same situation...
I just bought 2 new HP DL320G5's and downloaded the V1.0 ISO today to setup Proxmox
Just as above, all works fine until the end of the setup process. There I see a popup with all the messages, but I can't read all of it because that popup is higher than my screen. All messages look fine.
Last thing I see:
Creating SSH2 RSA key; this may take some time ...
Creating SSH2 DSA key; this may take some time ...
The rest is "under" my screen.

I am also stuck in that screen, there seems to be no way to get out of it, so I have to reset after that.

 

[Onyx]

OK, update on this:
I am now able to see the complete messages. I had to push ctrl+alt+f2 to get in that screen and not alt+f2 as suggested in the install.

This is my output:
Creating SSH2 RSA key; this may take some time ...
Creating SSH2 DSA key; this may take some time ...
invoke-rc.d: action update-cron is unknown, but proceeding anyway
dpkg: error processing proxmox-ve (--configure):
subprocess post-installation script returned error exit status 2
errors were encountered while processing:
proxmox-ve

 

[nigelr]

The attempted install on ESXi was via the ISO file... The bare metal instal was via a cd.. This ISO was proxmox-ve_1.0.iso with MD5 of cdcbd3d765263c157582f69ba24116bb (the ISO worked perfectly on MacPro)

Last night then downloaded proxmox-ve_1.0-3410.iso with an MD5 0838c3623e0d1f7f9accf4e0c9e6bf4b..

This still has the exact same issue..

 

[Onyx]

Problem Solved!

I ran the install again with an original hdd from HP, hoping that would help, but same thing.
Now I watched the console while the install was running, and I noticed some warnings about the time being xxxxxxxxx seconds in the future.
I corrected the time in the bios and installed again, and it worked!
I'm not 100% sure that was the solution because at the same time I also attached a network cable to the second ethernet port of the server.
So either the time settings or the attachment of the second ethernet cable solved this issue.

Thanks!

 

[tom]

The attempted install on ESXi was via the ISO file... The bare metal instal was via a cd.. This ISO was proxmox-ve_1.0.iso with MD5 of cdcbd3d765263c157582f69ba24116bb (the ISO worked perfectly on MacPro)

Last night then downloaded proxmox-ve_1.0-3410.iso with an MD5 0838c3623e0d1f7f9accf4e0c9e6bf4b..

This still has the exact same issue..

I just installed proxmox-ve_1.0-3410.iso on a fresh install of ESXi without problems.

 

[nigelr]

Yep, fixed as well....

The machine is being installed tomorrow so I can't take it down and do a bare metal, although an install on ESXi worked perfectly... (after I changed the date/time)

 

[martin]

Yep, fixed as well....

The machine is being installed tomorrow so I can't take it down and do a bare metal, although an install on ESXi worked perfectly... (after I changed the date/time)

cool, but a strange issue. I tested this on one of your test servers but I could not reproduce the issue. anyway, thanks for going further.

 

[Onyx]

cool, but a strange issue. I tested this on one of your test servers but I could not reproduce the issue. anyway, thanks for going further.

To try to reproduce this, try to set your date in the bios 6 months back

 

[tom]

To try to reproduce this, try to set your date in the bios 6 months back

OK, we got it. the gnu privacy guard does not like this (if the bios date is older than the date of our signed packages).

we will adapt our installer to fix this. in the meantime, just set the correct date in the bios.