Search results

top - 11:23:21 up 15 days, 6 min, 1 user, load average: 1.59, 3.34, 3.82 Tasks: 281 total, 4 running, 187 sleeping, 0 stopped, 0 zombie %Cpu(s): 19.2 us, 14.8 sy, 0.0 ni, 65.3 id, 0.2 wa, 0.0 hi, 0.5 si, 0.0 st KiB Mem : 8039432 total, 3806792 free, 3787720 used, 444920...

Hello, My installation is made with 2 nodes. They are not very powerful and will be replaced soon with much more powerful one. My problem is that on one of the nodes i have permanently a high system charge and can't figure out why. Here is the sum up of the host. Average cpu usage is around...

Finally i umounted my partition and with fdisk i destroyed and recreated it at 349G (wasn't possible at 350G). Then i resized the fs. the only weird thing is that parted doesn't see the right size (375G).

Hello, I have a vm with a boot disk on lvm-local. I have attached a second disk to the host (by uuid) On the disk i created a lv in which i created a second disk for my guest. The physical disk is a 937Gb The guest disk was 282Gb I resized it to 350Gb. --- Logical volume --- LV Name...

The share has been properly unmounted and snmpd daemon can normally read the buffer. snmpwalk is ok and i guess in 5 minutes i will see the host in my nms.

here is the output of mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=3965716k,nr_inodes=991429,mode=755) devpts on /dev/pts type devpts...

I may have an idea. I run strace on the host. I run snmpwalk in another shell. This host is not responsive to snmp. Snmpwalk returns dozen of lines and hangs until time out The last line of the trace is: statfs("/mnt/pve/TS639", Where /mnt/pve/TS639 is the mount point of nfs shared storage...

in the journal i see an error on boths hosts which is not time related to the message in the nms. the error is: inetNetToMediaTable:_add_or_update_arpentry: unsupported address type, len = 0 I didn't find other examples of this error. It seems linked to a change in the bridge config which...

I finally got it working with ........ a reboot but only for a few days. This night my 2 nodes were unreachable by snmp. I tried to stop/start snmpd daemon. I tried to kill snmpd and restart. I tried to restart networking.service. When i restarted networking all my guests on the host became...

I migrate the container to another host. Even when i try snmpwalk from proxmox host itself i get a timeout. I don't think it's related to librenms. It also has no problem to get data from a procurve switch, a qnap nas or a debian vm on the host.

I made some changes in my snmp config. I copied from https://www.svennd.be/how-to-install-snmp-service-on-proxmox/ Now i see that there is something listening on port 161. with ss -au i can see that Recv-Q is growing which means that there is no service which reads data from the socket. It stops...

I try to setup librenms monitoring server in a lxc container. I can monitor my switch, a qnap nas, a vm but i'm unable to get it working for a proxmox host. i installed snmpd with a standard debian conf. The service start without problem and is active. But when i try snmpwalk from proxmox host...

I extended the metadata pool. I understood that it has to be around 1% of thinpool. lvextend --poolmetadatasize +4.9G vgdocker/lvdocker lvs -a vgdocker LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvdocker vgdocker...

the vm-106-disk-0 is already resized. It shows 282Gib and 11,35% mapped In the guest i only see 32Gib lvs- a vgdocker LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvdocker vgdocker twi-aotz-- 498.00g 6.43...

thanks for your answer. I'll dig to see how to resize metadata pool (i thought it was done automatically). I know that i have to resize /dev/sdb1 but i don't know how. Resize2fs tells me the size il already correct. here is the result of lvdisplay on the host: lvdisplay vgdocker --- Logical...

Hi, I added a disk to a host (1TB) I added a lvm thinpool on that disk intially 100G. I added to a guest a raw disk on that thinpool. Initially the size of the disk was 32G. Ineed more room on that raw disk. I resized the thin pool to 498G. I resized the disk to 282G. With dmesg i see that the...

Hi, Thank you for your answer, so i'll go for thin pool. Unfortunately i can't do it with the gui. I have a disk (/dev/sdb). I created a pv: pvdocker then a vg: vgdocker But in the gui, on node level when i want to create a thinpool i can't because it says there are no unused disk. Edit: I...

Hello, I'm relatively new to proxmox. I'm using it for my personnal needs and to experiment new things. I was using esxi 5.5 but i wanted to experiment live migration and other stuff (not available with the free license). So i decided to move on to proxmox. I started with one host to test. I...