Search results

I have use Monit, but I need to know maybe a field of "Load avg" on each VPS list? NB: I know I can use M/Monit but this is not my concern

When Proxmox Load Average show 150 then I can not determine which VPS caused this high load since all VPS CPU < 90%. Is this a way to show load of each VPS so I can see where the 150 come from? NB: currently, I must use enter to each VPS then run #top command 1 by 1

Great Juan ... I just recheck that #top command reported right load, but WHM/CPanel (Home »System Health »Process Manager) still report node load instead :rolleyes:

# pveversion pve-manager/5.4-13/aee6f0ec (running kernel: 4.15.18-18-pve) # # apt-get upgrade lxcfs Reading package lists... Done Building dependency tree Reading state information... Done lxcfs is already the newest version (3.0.3-pve1). I have edited "ExecStart=/usr/bin/lxcfs -l...

~# smartctl -a /dev/nvme0n1 smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.18-12-pve] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: V-GEN03SM19EG1TP3X4IT Serial Number...

If Proxmox using NVME hang (all icons grayed) then I do hard restart, then vps (in my case LXC) will back to several days ago. So any websites in VPS will back to several days ago. How to avoid this? NB: Proxmox 5.4.3 VPS created on secondary disk using NVME with ext4 file system

I have try Balloon with 5.000/10.000 RAM then stop/start VM but still overload displayed on Proxmox, ram starting 0.5 % then increase near to 92%. Also has been trying with balloon min/max 10.000/10.000 but no luck.

Yes ... Balloon Service already ran in Windows. Below is the screenshot of Proxmox Summary and VM inside.

Here is my config: # cat 2016.conf agent: 1 balloon: 0 bootdisk: virtio0 cores: 2 memory: 4096 name: win2016 net0: virtio=D6:6C:AF:A7:96:4D,bridge=vmbr2 numa: 0 onboot: 1 ostype: win10 sata0: local-data:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K scsihw: virtio-scsi-pci smbios1...

KVM must reports RAM inside VM, this behavior works fine on WinXP, Win 2003, Win7 and Win2008. Abnormal RAM report only happen on Win 2012 and Win 2016 (maybe Win 10 also), even I have installed Balloon Service & Qemu-Agent.

Even I already installed latest version of virtio-win iso (virtio-win-0.1.141.iso then virtio-win-0.1.171.iso) Proxmox still report RAM usage is 90%, even inside Windows only use 1GB. Here is my settings: Proxmox 5.3.8 dan guest Win 2016 RAM Ballon=0 HDD and NIC using VirtIO Ballon Service...

Is there a way Proxmox Backup still run but ignore invalid files? Bacause Backup will failed if found even only 1 failed/corrupted/invalid file.

No error on mount. Since this VPS used for hosting then my last change is backup all files then move to new VPS, but I must prepare a long time because data size was nearly 80GB. Is there a way Proxmox Backup ignore invalid files?

# pct stop 3256 # mount /mnt/data/images/3256/vm-3256-disk-1.raw /mnt/test/ Change to that folder then: # rm 1538852941.M550773P24916\,S\=1532\,W\=1561 rm: cannot remove '1538852941.M550773P24916,S=1532,W=1561': Bad message #

When I try to backup ... I found INFO: tar: ./home/mail/new/1538852941.M550773P24916,S=1532,W=1561: Cannot stat: Bad message Try to delete this file but error ... Cannot stat: Bad message. Event I manually mount the file of this Container, I still can not delete this Corrupted File. How to...

# mke2fs -n /mnt/data/images/3256/vm-3256-disk-1.raw mke2fs 1.43.4 (31-Jan-2017) /mnt/data/images/3256/vm-3256-disk-1.raw contains a ext4 file system created on Thu Jun 14 09:34:18 2018 Proceed anyway? (y,N) y Creating filesystem with 39845888 4k blocks and 9961472 inodes Filesystem...

I try to resize a container, TASK OK but with error: Image resized. e2fsck 1.43.4 (31-Jan-2017) MMP interval is 10 seconds and total wait time is 42 seconds. Please wait... The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it...

Check the I/O Delay, you may show Total Disk Read and Total Disk Write, if to high will cause server hang. Also check CPU and Server load for a month (set Proxmox chart to "month maximum").

- How often the server hang? Every certain of time? - When Server hang, can you see the Monitor? Usually Monitor display the last error - In my experience, such error can only fix by replaced with another server. Because h/w test only test a h/w functional not h/w stabilization in certain period.

One of my LXC has very high TOTAL DISK READ, while Total Disk Write is normal. This LXC has 9 TB Total Disk Read while other VPS only several GB. How to know which process doing this high disk write? I'm using latest Proxmox 5.3-5.