Search results

  1. S

    removing nfs at datacenter level

    I had a very similar experience with CIFS share on datacenter/storage level not unmounting after unchecking "Enabled". Before also filing a bug I will make shure my expectency is correct. A storage/mount has to go after being disabled or undefined. - correct? My current solution is to manually...
  2. S

    Ping with unprivileged user in LXC container / Linux capabilities

    As some people say, root inside a container could be considered "safe" as it's allready running in user context on the host. Sadly the best answer to this on the internet. So in my case of telegraf in a container, run it as root and it is able to ping.
  3. S

    Ping with unprivileged user in LXC container / Linux capabilities

    Same here while trying to get telegraf working using native ping plugin. After setcap, user telegraf inside the container is able to execute ping (legacy, screen scrape). This workaround does not work for telegraf's native ping implementation. Even after also applying setcap to telegraf binary...
  4. S

    VM in a DMZ

    I have to disagree, that an interface/bridge wich just has no IP given, is not listening or reachable via its connected L2 network. Why? By default, the kernel always sticks his plug into a linux-bridge. - Interfaces (vmbrX) still pick up ipv6 adresses if the network it switches announces one...
  5. S

    SSD Wearout S.M.A.R.T - N/A

    PATCH an pve-devel@proxmox.com gesendet.
  6. S

    SSD Wearout S.M.A.R.T - N/A

    Hallo, ich wundere mich gerade über "N/A" Werte in der Wearout-Spalte der Disks-Übersicht auf der Proxmox-Oberfläche. Eigentlich sind die SMART-Werte vorhanden. Ein wenig reverse-engineering und der (Bug) ist gefunden. `get_wear_leveling_info` schaut nach dem Vendor-Namen im Model-String der...
  7. S

    [SOLVED] Failed To Import Pool 'rpool'

    Today I ran in to a similar issue where Proxmox hang at during boot. Syslog statet: Since this is a supermicro server-board with IPMI, sr0 is the remote-media virtual drive where I forgot to unmount the image. I had mounted the remote media from a temporary cifs server wich wasn't reachable...
  8. S

    Soft / interruptible mounts for backup targets

    This is obviously not a Proxmox issue alone but general design issue of cifs and nfs implementation. https://stackoverflow.com/questions/18085868/attempt-to-access-remote-folder-mounted-with-cifs-hangs-when-disconnected/19101647
  9. S

    Backup (Vzdump) fails and hangs forever

    Not only does this bug hang just this backup, this bug slowly kills the host kernel until after a while the entire host is dead because the cifs module somehow stops execution of the kernel itself. I also reported here...
  10. S

    Soft / interruptible mounts for backup targets

    Have the same trouble with my lab servers doing offsite-backups via unreliable connections. If cifs sees fluctuations the kernel is blocked by the hung cifs module entirely. Leaving the server alone a while it doesn't even respond to network traffic anymore. CIFS totally locks up the kernel...
  11. S

    Network Issues - virtio vs e1000

    I had to go back to the e1000. In my case under FreeBSD and years later, virtio does not function properly. See proto://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165059 Neither pfSense nor Kali Linux. VirtIO cost me weeks in debuggig webservers, analyzing tcp packets in deep and ping. Sadly the...
  12. S

    Can't add second node to cluster - "unable to copy ssh ID"

    I had the same issue recently when i reinstalled a slave node. It was then not possible to ssh-copy-id the key from the new node to the cluster master. When executing on the new node: wich is the error pvecm add complained internaly. I got it working with the following steps on the cluster...