Search results

Obviously something is not quite right. Mir's reply made me remember that I indeed updated some packages and rsyslogd was one of them.

Worked!! So I take that rsyslogd was somehow in a half-awake state and needed to be brought back fresh.. Are the PVE devs aware of this? Thanks Mir for the suggestion! It worked !

Hello my PVE node has decided to display "no content" and a blank page instead of the syslog messages that you usually can see under syslog tab of the WebGUI.. Not sure when this started to happen, but first time I saw this (about 2 weeks ago) at that time I thought that the syslog was...

Re: Getting started with PVE storage model - software RAID5 array and storage concept aenima99x I am sorry I couldnt reply earlier.. I am constantly trying to find time to post on these forums but life is getting in the way ;) I have decided to go down the separate storage server...

Ok I'm kindly bumping this thread because 60 views and not a single reply, I'd like to know why. Is this thread to general and vague and not specific enough? Too complicated to reply?

Hello all, I am seeking advices from experienced proxmox users in regards to reconfiguring my proxmox node to be the most resilient possible. I am not looking to upgrade my hardware and I am not looking to cluster, I will continue to use a single standalone node. I am mainly interested in...

Overloaded I dont think so but aound the time it was "slow" and these errors (or rather warnings) appeared in the console (syslog), the node was performing some SMART tests on the drives, I could hear them scratch away so intensely... I will keep an eye on that but if someone can provide more...

Yes, these lines are exactly what's recommended to do on pfsense's wiki. If you look at my thread, you will see several errors: WARNING: VM 100 qmp command 'balloon' failed - got timeout WARNING: unable to connect to VM 101 socket - timeout after 31 retries WARNING: unable to connect to VM 100...

I just opened my own thread on this error... Have you found a cause for this error? Is this serious??? I saw these errors since I enabled memory ballooning on a pfsense VM with virtio. I am worried so I would like to know if you got to the bottom of this. thanks!!

Hello, I was using my proxmox node and found my pfsense VM to be suspiciously slow / unresponsive, when I decided to look in PVE's syslog and saw these: Jun 3 22:58:08 proxmox pvestatd[3603]: VM 100 qmp command failed - VM 100 qmp command 'balloon' failed - got timeout Jun 3 22:58:08...

Dietmar, I did uncomment the drives before starting the VM. I tried like 3 or 4 times. Thats why I could see that on one shot, the VM halted because one of the LV was not found, and with the other shot it was the other LV.. Now that you mention that backup comments out the other drives...

Thank you Dietmar for replying. I am just not understanding your repsonse. Yes, I have excluded the drive from being backed up but that shouldnt mean the drive is no longer available to the VM upon restoration? Especially using the UUID of the drive to mount it in the VM.. Also, I have tried...

Update: I updated pVE with the latest packages (as found under updates tab), rebooted the node and started the VM back up again, it worked fine this time... I am concerned about this... What could I provide to the PVE devs so we can get to the bottom of this???

Hello, I am in a bit of severe trouble here so I hope I can have help from you guys.. I have this CentOS VM that I backed up twice to a small backup storage of 300GB.. What I didnt realize when I backed up the VM a second time is that the backup storage was running low on space but...

Found the problem. The backup was really 13TB (!) because of what I explained in my previous post. I added ",backup=no" at the end of the lines of the VHD's in the VMID.conf and I could backup the VM. Perhaps I missed that proxmox was backing up all HD's by default but this is what it does...

According to ls -l the VM is 128GB (which rings a bell and seems familiar) 128849018880 = 128.8GB Backup has 211GB left.. Should be enough to store a backup of 128GB The VM that is failing to backup (other than its main VHD) has also two drives assignment. One is a software RAID passed to...

Lets move our discussions to my dedicated thread if you dont mind. I didnt mean to hijack the OP's thread and now its getting difficult to know who is replying to who.. http://forum.proxmox.com/threads/18395-Cannot-backup-VM-Operation-not-permitted

Although I think you may be replying to the OP, I will still weigh in with this: No, there are no other VM's being backed up at that time.. More importantly, the backup is mounted on the same node (locally) as the running VM's and I have only one node. Just backed up 6 other VM's witout...

Just found your thread.... Missed it during a pre-post search on this forum.. Have you found a solution yet? I am having the same (or VERY similar) problem, I also think this should be considered seriously since its critical IMO. My thread is at...

Hello Using proxmox 3.2-1/1933730b, I am trying to make a backup of a VM (KVM) using the local node's backup resource, and it fails every time with : ERROR: job failed with err -1 - Operation not permitted INFO: aborting backup job INFO: stopping kvm after backup task ERROR: Backup of...