the Syslog was also having a bunch of rrdcached errrors every few minutes along the lines of:
```... illegal attempt to update using time 1336006652 when last update time is 1336039770 (minimum one second step)...```
Odd, as it's a new server i just built, that had the correct time in BIOS...
fresh install of Proxmox 5.4-5 and noticing that the Webgui will log me out after a few minutes. Is there a way to turn off this 'feature'? I'm not having any issue with 5.4-3 on another machine.
Completely re-built and re-installed. Now using a 1TB SSD for OS + VM Disks. Will use a 4TB HDD + 120GB SSD as a totally separate ZFS Pool that I can share over NFS for shared storage accesible on the network.
If I had enough NIC's I'd even separate the storage + normal network. I do have a...
I meant, should I have installed proxmox OS on the SSD, outside of ZFS pool, and then used the HDD for rpool, storing VM disks, etc.
sda is 120GB SSD
sdb is normal spinning HDD 7200rpm
Both are SATA disks
root@proxmox:~# zpool status
scan: scrub repaired 0B in...
I think my proxmox node may not be performing well. According to the man page for pveperf, my FSYNC should be > 200. But I'm getting the below:
CPU BOGOMIPS: 25536.00
HD SIZE: 2451.76 GB (rpool/ROOT/pve-1)
After walking away from the machine for a while and having another go today I've managed to get things running again. I'm still having the error on boot with ZFS mounting failing via Systemd, and systemctl status zfs-mount.service is showing it as failed - but as you say, it seems to...
Hi there proxmoxers,
I'm in a real bind. My usually always stable Proxmox install is completely on it's knees right now.
I have a SSD + Larger HDD. Only 2 VM's ( pfsense, and a Centos VM used to host docker containers for various things ).
There was a power failure here, and upon reboot, my...
I got it working. that cat /etc/network/interface command helped me see the issue.
My default gateway IP recently changed. Have fixed that now via 'ip route change default <new_ip>' and we are back in business.
I've noticed my install of 5.1-32 has started showing some errors in the last few days ( since Nov 25 ).
These are to do with 'apt-get update' failing.
When I run this from the shell via SSH, I get the following output:
root@proxmox:~# apt-get update
Ahh OK, yes, that appears to have fixed the creation of new containers.
Curiously, now reverting my 102.conf back to what it was for rootfs is not working, but I'll dig into the logs and see what is going on. Now it is failing to start. lol.
Thanks so much for the assistance. Much appreciate...
This is what happens:
root@proxmox:/# pct create 105 /var/lib/vz/template/cache/archlinux-base_20170704-1_amd64.tar.gz --rootfs local-zfs:8
mounting container failed
cannot open directory //rpool: No such file or directory