Search results

  1. F

    [SOLVED] kern.log, syslog and messages growing too big

    Hi, Finally we bought a new, branded, nic and replaced the one added by the reseller (rtl8169 chip on unbranded nic) and all the problems disappeared. That was a hardware problem. I could not even suspect a certified dell reseller adding an unbranded nic on original dell desktop. Thank you all.
  2. F

    [SOLVED] kern.log, syslog and messages growing too big

    I was nearly certain that the problem comes from the second nic card, but lspc -v returned: 00:1c.0 PCI bridge: Intel Corporation Device a293 (rev f0) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 122 Bus: primary=00, secondary=01, subordinate=01...
  3. F

    [SOLVED] kern.log, syslog and messages growing too big

    Hi, First I thought that the pve no subscription channel has some kernel debugging enabled that filled my root device in less than two days of non continual usage, but even dmesg is listing some errors intead of the usual boot and peripheral information. My logs are bloated of repeated messages...
  4. F

    Monitoring Proxmox VE in harsh environment

    Hi, I am setting up a poc with an embedded proxmox computer on a rail vehicule (harsh environement with heat and dust) and would like to monitor especially cpu temperature and fan speed. What should I add in /etc/pve/status.cfg which actually contains the following lines: influxdb: server...
  5. F

    Error: command 'systemctl start pve-container@114' failed: exit code 1

    this is a server with proxmox 5.1 which I didn't update since 270+ days. I configured /etc/pve/status.cfg to send to an influxdb, updated and rebooted it. After reading this forum, I added the no subscription apt repo and did another update which solved my problem. Before that, I was using only...
  6. F

    Error: command 'systemctl start pve-container@114' failed: exit code 1

    Hello, same problem here. There seems no 2.1.1-3 lxc-pve available. How did you upgrade to it ? TIA
  7. F

    Undelete mount point

    Another problem arised. I have mounted a subdirectory of /opt as an external mount point (which I haven't backed up) and knwo, I am unable to restore from the main container backup. Is there any way to bypass the mounting of the external moint point during restore ? TIA
  8. F

    Undelete mount point

    I have moved all my important data from inside the container to an external mount point. I also marked the mount point to not be backed up. Know I deleted my container to test a restore procedure and then remebered that I am not backing up this "data" mount point. Could I restore it ? or will it...
  9. F

    Big proxmox installations

    Thanks for the information, Could you tell me what are the specs of these servers ? Especially the ratio Number VMs/cpu ? Shared storage ? Multipath links in the previous is true ? Interconnexion bandwith ? Cost of the whole solution ? Tia.
  10. F

    Big proxmox installations

    Hello, We are in the process of migrating our legacy vendro-locked virtualization platform and would like to know if anyone is using proxmox VE at a large scale ? Number of nodes and VMs ? Hardware configs ? Also, has anyone made a comparisson of how much it would cost to host all nodes...
  11. F

    Proxmox VE is 10 years old!

    Happy Birthday and thanks to all proxmox team. I hope to see more proxmox installations accross the world.
  12. F

    Error: command 'systemctl start pve-container@114' failed: exit code 1

    If you don't have a subscription to the proxmox repo then you have to enable the "no sbscription" repo to get any update for Proxmox packages.
  13. F

    Error: command 'systemctl start pve-container@114' failed: exit code 1

    root@pve-10-101:~# pveversion -v proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve) pve-manager: 5.1-41 (running version: 5.1-41/0b958203) pve-kernel-4.13.13-2-pve: 4.13.13-32 libpve-http-server-perl: 2.0-8 lvm2: 2.02.168-pve6 corosync: 2.4.2-pve3 libqb0: 1.0.1-1 pve-cluster: 5.0-19 qemu-server...
  14. F

    Error: command 'systemctl start pve-container@114' failed: exit code 1

    Hello, Yesterday, I updated my proxmox test server via apt-get dist-upgrade and rebooted. After what, none of the containers starts. From cli, I tried to start one in foreground and this is what i got: root@pve-10-101:~# /usr/bin/lxc-start -n 114 -F -lDEBUG -o /dev/shm/err.log --logpriority...
  15. F

    lxc_conf - conf.c:lxc_create_network:2888 - failed to create netdev

    Thank you fabian, I did as you said and received a message about no candidate for package proxmox-ve, I updated sources.list to use pvetest and have a taste of 5.1, then did as you said. After some several reboot, I run an apt upgrade followed by another reboot. Now, I can access the webgui on...
  16. F

    lxc_conf - conf.c:lxc_create_network:2888 - failed to create netdev

    Thank you Alwin, i read that document before doing the upgrade, just added '-y' to automate answers, as I did to upgrade from 4.3 to 4.4 and as I usually do.
  17. F

    lxc_conf - conf.c:lxc_create_network:2888 - failed to create netdev

    Hi, I have just upgraded one of my proxmoxve nodes from 4.4 to 5.0 whith the following command: apt-get update && apt-get dist-upgrade -y && sed -i 's/jessie/stretch/g' /etc/apt/sources.list && sed -i 's/jessie/stretch/g' /etc/apt/sources.list.d/pve-enterprise.list && echo "deb...