Search results

After I resize again then fixed!

# pct fsck 36165 fsck from util-linux 2.25.2 /mnt/sda1/images/36165/vm-36165-disk-1.raw: clean, 369528/6553600 files, 8523021/26214400 blocks root@ids-094110:~# pct start 36165 lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details...

root@ids-094110:~# pct fsck 36165 cannot run fsck on active container root@ids-094110:~# pveversion -v proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve) pve-manager: 4.1-1 (running version: 4.1-1/2f9650d4) pve-kernel-4.2.6-1-pve: 4.2.6-26 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 0.17.2-1...

1. CT is ON ---------------- Resizing CT from 100 GB to 200 GB, Proxmox UI failed message: Image resized. resize2fs 1.42.12 (29-Aug-2014) resize2fs: Permission denied to resize filesystem Filesystem at /dev/loop0 is mounted on /tmp; on-line resizing required old_desc_blocks = 7, new_desc_blocks...

Use the Bare-metal installation.see: https://pve.proxmox.com/wiki/Quick_installation

More details please? What is the tool to generate the certificate (unfortunately pvecm updatecerts has no option to read certain file config).

Still find how to check the method I think using existing certificate from other Server will cause security issue? Becase verify the certificate's name against host will failed?

I think https://www.startssl.com/ is free for first year only? A self signed is enough for me because our Proxmox Server only access by our API.

The "hostname -f" result is FQDN, but "pvecm updatecerts --force" still generate a short hostname certificate. I have checked /etc/hosts. Any idea to fix this issue?

How to force "pvecm updatecerts" to use FQDN, I try "pvecm updatecerts --force" but still the Hostname used. Should I manually use openssl? Note: this case happen after I change Hostname then run pvecm updatecerts --force, the result is just the Hostname not FQDN.

Right, on installation there are options to choose: Debian or Proxmox. Choose Proxmox instead.

I do reinstall, and just aware that Hetzner also provided Proxmox beside Debian. Use built in Proxmox image then Proxmox API PHP works fine.

Right, above code running well on other Data Centers, I have use it for hundreds servers. Unfortunately, Hetzner does not help, I have open Ticket to Hezner but they told me to ask to forum.

http://pve.proxmox.com/pve2-api-doc/ Look at: nodes/qemu/{vmid}/config -- ide[n]

This script below works fine on several server but only server from Hetzner doesn't. <?php require_once("pve2_api.class.php"); $pve2 = new PVE2_API("my-server-ip", "root", "pam", "my-password"); if ($pve2->login()) { foreach ($pve2->get_node_list() as $node_name) {...

Dear, My kern.log file very2 large, I found 99% entry was: kernel: ip_set_hash_net: disagrees about version of symbol module_layout Any idea to fix this? # pveversion -v proxmox-ve-2.6.32: 3.4-166 (running kernel: 2.6.32-37-pve) pve-manager: 3.4-11 (running version: 3.4-11/6502936f)...

I manage hundred IPs so it is not possible to do it manually, use DCHP instead. Install DHCP Server is very simple: #apt-get install isc-dhcp-server edit /etc/dhcp/dhcpd.conf, to specify your available IPs Inside VM set to DHCP. I install the DHCP on Proxmox node. Read this tutorial for...

Try this, inside your VPS: #hostname hosting.domain.com Then edit /etc/sysconfig/network: HOSTNAME=hosting DOMAINNAME=domain.com Change to: HOSTNAME=hosting.domain.com

what is your monitor resolution? have you replace with another monitor cable? this usually happen when you use old LCD monitor, replace with new LED or use old CRT mnonitor.

Server Manager: For most Provider, you must go to their Server Manager then Add Virtual MAC to your IP Edit your VPS-- replace existing with Virtual MAC from step #1 Stop then Start the VM Inside Windows VM: Make sure Remote Desktop = Enable (Windows -- Properties) Add RDC to Windows...