Search results

Those look pretty good. We could also try adding a little load on the disks and check the metrics. You can install the fio tool with apt install fio and run the following command fio --randrepeat=1 --ioengine=libaio --gtod_reduce=1 --name=test --filename=test --bs=4k --iodepth=64 --size=4G...

I would check two things for the zfs: What is the configured ashift. You can find it with zdb | grep ashift Do you have enabled the LZ4 compression on zfs? Also on what governor cpu frequency are you running? cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors cat...

That's not something that would reboot the server. It is informing you that kernel has change the sample rating. If nothing on the logs, the reboot could be due to power loss maybe?

You can check the currently conntrack objects and the limit with: cat /proc/sys/net/netfilter/nf_conntrack_count cat /proc/sys/net/netfilter/nf_conntrack_max This is not a hardware issue but it seems that you are hitting the limits that are set for nf_conntrack

@LnxBil That's a good point and i agree that it may seems like misused resources, but the idea of the swap is to keep systems healthy and not to be used as a ram tradeoff. Think of all those pages that kernel read on boot from disk, passed to ram and then none of those are going to be used...

A more simple soiution would be to setup the smartd daemon to run short and long tests and have it email to you any inconsistencies that it may find. Having an output with counters will need more work, but having the daemon check those counters and inform you when a {short,long} check fail is...

High swap usage is not a bad thing. Under normal operations kernel may decide to move things to swap to keep more ram available. Also high swap does not mean slower systems, if those memory pages are not accessed frequently. I have been using this command to find what is using most of the swap...

There are a lot of guides on internet to accomplish what you are asking, but most of times CPU is not the bottleneck. Would you like to elaborate more on what is the issue you encounter and maybe some metrics?

Hardware RAID and ZFS will not work. ZFS by design is managing the disks itself, so it needs to know about the disk devices and not the device that hardware RAID will make available. Personally i would disable the hardware raid setup and configure ZFS from scratch on the new server (also RAID5...

Are you trying on the https or the http?

I would check if the systemd services are enabled for the zfs with systemctl list-unit-files. On my machines i have enabled: zfs-import-cache.service enabled zfs-import-scan.service disabled zfs-mount.service enabled zfs-share.service...

I would remove the no_root_squash option ( which is not a bad thing to remove https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/security_guide/sect-security_guide-securing_nfs-do_not_use_the_no_root_squash_option ), remount the nfs storage and try again

You can follow the routed setup from this link https://wiki.hetzner.de/index.php/Netzkonfiguration_Debian/en#Routed_.28brouter.29

So it seems that you don't have the correct permissions. Are you using an nfs storage for the proxmox-backups directory? If so can you share the /etc/exports file from the nfs server and the /etc/fstab of the nfs client?

Does this completes successfully on both nodes? lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- touch /mnt/pve/proxmox-backups/testfile

This seems like a permissions problem with your /mnt/pve/proxmox-backups. The backup is running as the unprivileged user who has no permissions to write on that path. The privileged containers are not running as a mapped uid/gid. Try to set a more broad permissions on the backup directory and...

I have upgraded to proxmox 6 with the new kernel and the issue is fixed

Just had the same issue. I'm running lxc and docker containers. Freshly pulled "alpine:latest" and tried to install git which gets killed during installation root@wkr1:~# docker run -ti --rm alpine:latest /bin/sh / # apk update fetch...