Search results

I further audit the dpkg: # dpkg --audit The following packages have been unpacked but not yet configured. They must be configured using dpkg --configure or the configure menu option in dselect for them to work: pve-kernel-4.15 Latest Proxmox VE Kernel Image The following packages are...

Not exactly I know of. However, what I can guess is when trying to reinstall the proxmox-ve after an removing as I stated earlier. Thanks for your input. Here comes the outputs: # apt install pve-manager Reading package lists... Done Building dependency tree Reading state information... Done...

Forgot to mention that the apt sources are also alright: # grep '' /etc/apt/sources.list deb [arch=amd64] http://cdn-fastly.deb.debian.org/debian/ stretch main contrib non-free deb-src [arch=amd64] http://cdn-fastly.deb.debian.org/debian/ stretch main contrib non-free deb [arch=amd64]...

Hi, Proxmox4 (installed on remote server on top of Debian Jessie) was serving well till upgrade in virtual machines started popping out errors making the lxc containers failing to boot. No zfs and ceph and hosting only lxc containers. So I decided to upgrade first to Proxmox5...

Thanks for your input. 1. I guess I already have the DNAT rule in place in line 34 in http://ix.io/3pUe 2. telnet to port 25 of the mailserver (lxc guest) from proxmox host is reachable: root@server2:~# telnet 192.168.25.110 25 Trying 192.168.25.110... Connected to 192.168.25.110. Escape...

@Stoiko Ivanov Thanks for your input. Although it has been a while, but the problem appears everytime I upgrade the system (ubuntu 18.04). This time, can send emails, but not receive! Legends: Proxmox host = server2.domain.tld LXC mailserver = mail.domain.tld From the proxmox host, it works...

Hi, I am running a mailserver (ISPConfig) in a proxmox lxc container which was working fine and stopped working recently all of a sudden. All the ports necessary are open in the proxmox host: # iptables -L | grep smtp ACCEPT tcp -- anywhere 192.168.25.110 tcp dpt:smtp...

@fabian , Thanks for the nifty pointer. But there appears to be a size mismatch, created 12G: # pct config 108 arch: amd64 hostname: hdi.loc memory: 1024 net0: name=eth0,bridge=vmbr0,gw=192.168.63.1,hwaddr=42:E4:13:94:32:93,ip=192.168.63.108/24,type=veth onboot: 0 ostype: ubuntu rootfs...

In my OP (https://forum.proxmox.com/threads/unable-to-parse-directory-volume-name-with-pct-create.55373/), I guess I specified exactly the same to get the errror: --rootfs local:vm-108-disk-1.raw,size=12G Also tried with: --storage local --rootfs local:volume=vm-108-disk-1,size=12G but got...

@sb-jw: Thanks for the pointer. Appending the part with: --storage local --rootfs volume=vm-108-disk-1.raw,size=12G as well as with: --storage local --rootfs volume=vm-108-disk-1,size=12G fails to create the container with the following error: to comply with what pct manpage states...

Hi, Tried to create a lxc container over command line: # pct create 108 local:vztmpl/debian-9.0-standard_9.7-1_amd64.tar.gz --hostname server1.name.dom --cpulimit 1 --cpuunits 1024 --memory 512 --swap 1024 --ostype debian --onboot 1 --net0...

The reportedly failing drive: 2018-06-19 14:26:55 root@SSDRAPIDWEAROUT:[~]:$ smartctl -a /dev/sda smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.4.83-1-pve] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model...

Does not seem so. I posted a new thread at https://forum.proxmox.com/threads/rapid-ssd-wear-out.44681/

Hi, I have two machines (in different locations) which has exactly same hardware as well as proxmox versions (4) running. The first machine was deployed two years ahead of the second one. The first server has more network transactions than the second one. It is strange that smartctl states...

@Nemesiz, Thanks for sharing. Just wanted to know whether you did this in PM4 or PM5? And can you throw some light on 2 above? What is 'e'? It would be nice if you can share a small note on exact commands that you executed to accomplish this setup. Cheers, /z

@dietmar Thanks for an update. I was just reading your reply at https://forum.proxmox.com/threads/dev-pve-data-not-mounted-after-fresh-4-2-install.27220/#post-136966. 1§ CLI issue: However, it makes very inconvenient to figure out data usage for the command line users which is the standard way...

Hi, I cannot say for sure whether this is a feature or a bug? Installed Proxmox 5.1 on a KVM machine with 100GB space allocated, but 'df -h' failed to show up pve-data mounted. The only error message I see: <QUOTE> # dmesg | grep vd [ 0.921700] vda: vda1 vda2 vda3 # dmesg | grep sd [...

SOLVED: root@lhotse:~# lxc-start -F -n 250 --logfile=lxc.log --logpriority=debug unable to open file '/fastboot.tmp.11088' - Disk...

Hi, The pct start failed after an upgrade as follows (only has pve-no-subscription repo enabled. # pct start 250 Job for lxc@250.service failed. See 'systemctl status lxc@250.service' and 'journalctl -xn' for details. command 'systemctl start lxc@250' failed: exit code 1 root@lhotse:~#...

A relevant thread WITHOUT the hwRAID is posted at https://forum.proxmox.com/threads/crashed-proxmox4-reboots-only-to-the-grub-boot-prompt.37568/ for those who are encountering a similar issue, not yet solved till these lines are written. ;)