Bug #14427
closed
LLDPD & LADVD permissions with RAM Disks
0%
Description
LLDPD cannot enable agent-x support with RAM Disks enabled
May 27 10:55:19 lldpd 3881 Warning: Failed to connect to the agentx master agent ([NIL]):
May 27 10:55:19 lldpd 3298 cannot connect to /var/agentx/master: No such file or directory
creating the directory does not resolve the issue
May 27 10:59:04 lldpd 3881 Warning: Failed to connect to the agentx master agent ([NIL]):
May 27 10:59:04 lldpd 3298 cannot connect to /var/agentx/master: Socket operation on non-socket
LADVD will not even start following a reboot, even though it was previously enabled and running. Starts and works fine with RAM Disks disabled
failed to open /var/run/ladvd.sock: No such file or directory
if this needs two separate reports lmk
Updated by
Updated by Grzegorz Krzystek over 1 year ago
Jordan Greene wrote:
LLDPD cannot enable agent-x support with RAM Disks enabled
May 27 10:55:19 lldpd 3881 Warning: Failed to connect to the agentx master agent ([NIL]):
May 27 10:55:19 lldpd 3298 cannot connect to /var/agentx/master: No such file or directorycreating the directory does not resolve the issue
May 27 10:59:04 lldpd 3881 Warning: Failed to connect to the agentx master agent ([NIL]):
May 27 10:59:04 lldpd 3298 cannot connect to /var/agentx/master: Socket operation on non-socketLADVD will not even start following a reboot, even though it was previously enabled and running. Starts and works fine with RAM Disks disabled
failed to open /var/run/ladvd.sock: No such file or directoryif this needs two separate reports lmk
similar thing is with NUT
after reboot when /var is in ram /var/db/nut is owned by uucp:uucp , while should be owned by nut:nut.