Search results

  1. D

    OpenVZ backup fails

    This happens every time that I attempt to back up, no matter what compression is chosen...
  2. D

    OpenVZ backup fails

    I have one of my openvz backups that is failing in my schedule. The other ones appear to work fine. I called the backup manually with Gzip, LZO, and NO compression, all of them failed. I called one of my other containers manually, using gzip compression and it worked fine, no issues. Here...
  3. D

    Proxmox 3.0 web ui on port 443 instead of 8006

    Warning! Anyone that uses this needs to carefully work this out, as more research is needed. I had an OpenVZ container running on venet, and for some reason could not wget/connect/lynx to ANYTHING ON PORT 443, which made some of my applications break... after a little bit of trying to figure...
  4. D

    Proxmox 3.0 web ui on port 443 instead of 8006

    Thanks! I tried this and it works great, thanks for the help!
  5. D

    Proxmox 3.0 web ui on port 443 instead of 8006

    I would like to change the webui port on my Proxmox 3.0 installation to port 443, not 8006. I notice it is hardcoded in pveproxy, and changing the port to 443 gives the following error: pveproxyunable to create socket - IO::Socket::INET: Permission denied This appears to be running as...
  6. D

    Changing permissions on bind mount

    Okay, I was wondering if something like that would work, but the bind mounting appeared to be destroying the permission structure for what I had.... So on my NAS I would create 2 users, match their UID's to my CT UID's, set permissions manually on my NAS box, then just export the SMB? Do I...
  7. D

    Changing permissions on bind mount

    Yeah, almost 100% certain this is more of a CIFS/SAMBA issue that I don't have enough knowledge about... Well, for now it is sort of "solved" just giving my users' too much permission (not a huge deal, just have scripts running that I had locked down to specific folders/files for security)...
  8. D

    Changing permissions on bind mount

    All of the information I have found shows that you cannot mount CIFS directly inside of CT, (link shown below). I used that forum post to read all my files, but I have multiple users writing to those files, so needed to chown individual directories so users could write to them. My old method...
  9. D

    Changing permissions on bind mount

    Anyone? I would take ANY solution to mount a SMB/CIFS share from my NAS box to my openvz container that allowed multiple owners (users on the openvz client). I was able to do this before by directly passing an external USB HDD to the container.... but now I have a NAS...
  10. D

    Changing permissions on bind mount

    I have a SMB bind mount to a openvz client: #!/bin/bash mount -o gid=107,uid=107 --bind /mnt/media /var/lib/vz/root/104/mnt/media I am trying to set the owner of the bind mount to a user on the CLIENT. Not sure how to do that, since I get permission denied when I attempt to change it on the...
  11. D

    Backups started failing after resizing LVM

    Too far back for bash history unfortunately... and I honestly can't remember if I resized the partition... which usually means I didn't :( root@proxmox:~# fdisk -l Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280...
  12. D

    Backups started failing after resizing LVM

    I extended the LV /dev/pve/data, if I remember it was a simple pvcreate, then vgextend, then lvextend. root@proxmox:~# lvscan Incorrect metadata area header checksum on /dev/sdb1 at offset 4096 Incorrect metadata area header checksum on /dev/sdb1 at offset 4096 ACTIVE...
  13. D

    Backups started failing after resizing LVM

    I resized my LVM a little bit ago... and now my backups are failing..it appears as if the LVM expansion ran into issues, although everything appears to work. Anyone have any idea how to solve? vzdump 105 103 --quiet 1 --mailto xxxxx@xxxx.com --mode snapshot --compress gzip --storage Backups...
  14. D

    Force port 443 instead of 8006

    For those of you advocating changing my pve-redirect or pve.conf (first off, I don't think editing pve.conf should not work period as there is a redirect), have any of you actually tried that? Because I don't think it works, I delete the re-direct file and edit pve.conf to 443 and still doesn't...
  15. D

    Force port 443 instead of 8006

    Is there an easy way to get proxmox to force a 443 connection all of the way through and not redirect to port 8006?
  16. D

    Restore Error

    Hmmm.. well a reboot of the node appears to have fixed this issue.
  17. D

    Restore Error

    I've tried multiple ID's with multiple OpenVZ backup images, and they are all free (the id box should turn red right?) with no luck.
  18. D

    Restore Error

    I was restoring my VM's on 2.0 via the web interface, and all of my KVM VM's worked fine, so I thought I was in the clear, but my OpenVZ containers (I have 3, tried 2 of them so far), and I get the error "TASK ERROR: can't lock container 101" (or 104). Is there something I am missing?
  19. D

    unable to parse volume ID error restoring from 1.9

    I had the same issue, what I ended up doing was creating a storage dir called Backups in the webui, once you do that a folder called "dump" should be created in that backup folder (if not create one) and put all of the images in there. Then, you can go to your Backups storage, click on content...
  20. D

    LVM storage used for containers

    Thanks, I had tried the lvextend command, but since I don't really understand LVM :D didn't realize I had to resize2fs... after a large amount of research online finally just delete the entire /pve-data LV and created another LV that was the right size from the very beginning and reformatted...