Recent content by Okumba

Solved, was not a problem of proxmox (for more information see updated first post). Moderators can delete this thread. Sorry for the inconvenience caused.

-

Hello, the problem of the sudden increase from ~ 0-3 % cpu usage to 12.5% per KVM VM was caused by another server in the dataserver. Our system got all its traffic which was then transfered to the VMs. We could observe around 4,000 to 10,000 connections with a bandwith of 1.5 - 3 MB/s. This was...

Thank you Fabian.

Hi, might be a stupid question but still: After installing proxmox ontop of a debian jessie based on the wiki, I entered our subscription and added the /etc/apt/sources.list.d/pve-enterprise.list Can I or should I remove the /etc/apt/sources.list.d/pve-install-repo.list which is still listing...

thank you, used the wiki article and tested it, works wonderful.

I would like to ask this too, is Proxmox 4.1 compatible with fail2ban?

thank you.

Hm... i am just stupid I guess the old backup is deleted only on success? (Would be nice if someone can confirm) If that is so, then my backup simply fails cause of not enuff space. The backup will be ~ 60 GB where my df -h shows [...] /dev/mapper/vg1-backup 296G 242G 39G 87%...

Hi, the scheduled backup was running for months without problems. Since 2 weeks i get the following error while using the scheduled backup. "vma_queue_write: write error - Broken pipe". vzdump 200 --quiet 1 --mode snapshot --mailto REMOVED --compress lzo --storage backup 200: Apr 09...

running fsck fixes it in so far that i can mount the vda again, but the main part of data then is "recovered" to the lost+found folder... i guess i cannot do anything now to recover the data of the raw image file?

old server is running again from power outtage... i cannot start the vm on the old nor on the new server, seems the filesystem of the raw image file is corrupted. any advice but running fsck?