Problems in upgrading modified V1.1 to V1.2

[uwetr]

Hi,

I'm running some Proxmox V1.1 boxes and tried to upgrade to V1.2

But somehow I ran into probs with the procedure....

after running "pve-upgrade-1.1-to-1.2" I got the following error:

E: Internal Error, Could not perform immediate configuration (1) on debconf

Actually I need to say that I downloaded/install some addon packages to box (ohhh, pls. don't hurt me ... Software RAID support since it's private use only, so my budget is limited), so it's not a standard installation at all...

Someone here with an idea where to search for the problem and it's solution? Any kind of help is very appreciated!

cheers,
Uwe

 

[tom]

pls post the pve-update.log (same dir).

 

[dietmar]

What happens if you run the script again?

 

[uwetr]

Hi Tom,

pls post the pve-update.log (same dir).

thanks for your quick answer!

Unfortunaletly there's clue in about problem in the update.log.
I found a good hint on a debian-user website:

This magic spell:

dpkg --configure -a

reminded me that I've patched the sysctl.conf for NFS as mentioend in the openvz wiki

after going back to the original verison of sysctl.conf everything seems to be fine again.

Now I'm curious about the the result of "shutdown -r now"...

..BRB, or something went wrong


cheers,
Uwe

 

[amravit]

is version 1.2 already out or this a closed beta test?

regards
amr

 

[uwetr]

Hi,

..BRB, or something went wrong

GREAT! Everything fine now...

After "apt-get install mdadm" (*duckundweg*) and a reboot the V1.2 mounted the SW-RAID without any problems and all VMs are running again.

proxmox2:~# pveversion -v
pve-manager: 1.2-1 (pve-manager/1.2/3982)
qemu-server: 1.0-12
pve-kernel: 2.6.24-6
pve-kvm: 85-1
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.1-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

@ProxMox-Team: Thank you so much for the update!

I do have a personal "whish" for the next release...
Would it be possible to include the latest driver for the Realtek 8111DL onboad gigabyte NIC (very popular now with latest lowcost boards) to the distribution?

cheers,
Uwe

 

[uwetr]

Hi amr,

is version 1.2 already out or this a closed beta test?

it's public already:

http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_1.1_to_1.2

cheers,
Uwe

 

[dietmar]

Would it be possible to include the latest driver for the Realtek 8111DL onboad gigabyte NIC (very popular now with latest lowcost boards) to the distribution?

That product is covered by one or more of the following patents:US5,307,459, US5,434,872, US5,732,094, US6,570,884, US6,115,776, and US6,327,625.

I do not plan to include something protected by patents.

- Dietmar

 

[uwetr]

That product is covered by one or more of the following patents:US5,307,459, US5,434,872, US5,732,094, US6,570,884, US6,115,776, and US6,327,625.

I do not plan to include something protected by patents.

- Dietmar

oops ... so sorry, I didn't know about that issue.

But I do have another Another wish

you amazing vzdump tool offers the feature to exclude pathes of a VM from an backup. That would be great to have a daily backup uf the system itself and it's logfiles but doing the big data on once a week.

Could you add some "exclude" input lines for the backup feature to the webinterface ?


cheers,
Uwe

 

[dietmar]

Could you add some "exclude" input lines for the backup feature to the webinterface ?

I want to keep that config simple. Maybe a simple boolean like:

exclude logs = yes/no (maps to --stdexcludes option)

what do you think?

 

[uwetr]

Hi Dietmar,

I want to keep that config simple. Maybe a simple boolean like:

exclude logs = yes/no (maps to --stdexcludes option)

what do you think?

that won't do the job for me ...
I'm running a humble file server inside my provate LAN.

It offers the SuSe-Distributions from 6.4 to now via Sama.

Since I have all of them on optical medias there is no need to put them into the vzdump.

But it also keeps the user profiles of my samba domain and I would lie to have daily snapshot of the sytem...

cheers,
Uwe

 

[dietmar]

I think I can never create a full featured backup configuration which fits everybodies needs. Simply create you own cron job - that quite easy too.

- Dietmar

 

[uwetr]

I think I can never create a full featured backup configuration which fits everybodies needs. Simply create you own cron job - that quite easy too.

- Dietmar

The existing solution is allready fine!
(and your vzdump is a real killer tool, thank you so much for implementing!)

Pls add just ony one input-editor per backup job (maybe max. 255 characters?) and let the user key in aditional parameters for the vzdump-job.

That's everything need in my eyes.
Everything can passed as a parameter to vzdump afterwards...

cherrs,
Uwe

 

[dietmar]

Pls add just ony one input-editor per backup job (maybe max. 255 characters?) and let the user key in aditional parameters for the vzdump-job.

So far, we do not expose internals anywhere in the web interfaces. Why don't you define your own cron job?

 

[uwetr]

Hi Dietmar,

So far, we do not expose internals anywhere in the web interfaces.

hey, pls. don't get me wrong.

It was only a suggestion to get an even better result from an allready good solution...

If you disagree..so what?

We're only the users of your solution and so we need to follow your rules&ideas, isn't it?

Why don't you define your own cron job?

because I like ProxMox's webinterface, otherwise I could go ahead with my old XEN3 servers.

cheers,
Uwe

 

[dietmar]

hey, pls. don't get me wrong.

It was only a suggestion to get an even better result from an allready good solution...

If you disagree..so what?

don't worry - I am just trying to find out if it is really neccessary ;-)

- Dietmar