Search results

  1. S

    Cannot open /proc/stat: Transport endpoint is not connected

    Bump: Is there any solution for this error? The error appears 2-3x a week after the last upgrade. The problem is: I can not even restart single services:
  2. S

    Cannot open /proc/stat: Transport endpoint is not connected

    As workaround rebooting the LXC-containers helped. I will monitor if the error will come back again. Edit: I mentioned, that the error appears even after rebooting the host machine. So I have to shutdown every machine and turn it on again.
  3. S

    Cannot open /proc/stat: Transport endpoint is not connected

    Hello, since a few seconds I can not use htop or top in my LXC-containers: Same problem on reloading php5-fpm This is the syslog This is my PVE version What can I do here?
  4. S

    Failed to reset devices.list on /lxc/

    Hello, unfortunately I'm getting a lot of errors like these ones in my debian 8 LXC-container: Any idea how to solve this?
  5. S

    IOTOP on LXC

    Hello, unfortunately I can not use iotop on proxmox-lxc-container and debian 8 template. This is the output: Does anybody know how to fix that?
  6. S

    LXC -> IPSET 6+?

    Hello, I would like to use a new firewall-extension for PLESK on a Proxmox-LXC. Now the support of the firewall-extension wrote me this message: Good question. Does it? Do you have any experiences with that?
  7. S

    Proxmox and LXC: Set noatime for LXC-guests

    Hello, I would like to use noatime-attibute to improve disk-performance on my PVE-Server: On the host I could change /etc/fstab to # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more...
  8. S

    LXC: Services restart says "No Space Left On Device"

    Hello, If I want to restart any service on any LXC-container on my proxmox-node, I'm getting the error: No space left on device This is the df -h and df -i output of the container: /dev/loop3 394G 3,8G 370G 2% / none 100K 0 100K 0% /dev cgroup 12K...
  9. S

    Proxmox 4: Wrong networking-settings in containers after reboot

    Hello, I mention that my LXC guests are automatically set up with post-up ip route add 8x.xxx.148.1 dev eth0 post-up ip route add default via 8x.xxx.148.1 pre-down ip route del default via 8x.xxx.148.1 pre-down ip route del 8x.xxx.148.1 dev eth0 these...
  10. S

    LXC: Failed to talk to init daemon

    Hello, after rebooting my system I'm getting on all LXC-Containers errors like this: Edit: Solved by rebooting main system
  11. S

    LXC -> Create template from existing container?

    Hi Dietmar, well, if I use "Backup" and try to restore that backup, I can only replace the existing machine. I am not able to create a new one from backup.
  12. S

    LXC -> Create template from existing container?

    Hello there :-) Is there any possibility to create a template from an existing LXC-Container or simply clone one? Thanks in advance :-)
  13. S

    VPS is randomly crashing without "warning" before

    Okay, I'll run atop and free for some hours now and will have a look what happens next time it crashes.
  14. S

    VPS is randomly crashing without "warning" before

    Hi there, well, it's not one box that is affected. It's one box at the same time. But all boxes have these problems on different time.
  15. S

    VPS is randomly crashing without "warning" before

    Hi manu, thanks for your answer. Well, but wouldn't be all boxes slow on this moment? All boxes are working fine, but only this one is stuck. The last problems (with different VPS) were on: - 2 am (friday) - 6 am (sunday) - 9 am (today - monday)
  16. S

    VPS is randomly crashing without "warning" before

    Hi there, I'm using Proxmox to get some VPS which are running Debian 7.8 with LAMP. Now for any reason, I don't get why, these boxes are freezing randomly. If they do I can not connect via SSH. All services are down. If I connect via VNC I can see, that there is an error message like `kernel...