Michael Huang

i have similar issue reported intermittently. Do you find the issue? or other errors, such as NIC reboot?

Thanks. i think i found where the problem is. looks like the depend lib is missing or apparmor is missing, so it cannot create te-browserbot pod. anyway, i will use ubuntu instead.

recently, i noticed thousandeyes/enterprise-agent on my docker unstable. in the log, i notice following errors: Jul 31 14:45:38 Tower kernel: eth0: renamed from veth59412e0 Jul 31 14:45:46 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 31 14:45:46 Tower kernel: te-bbot-ipv4: port 1(veth6624a102) entered blocking state Jul 31 14:45:46 Tower kernel: te-bbot-ipv4: port 1(veth6624a102) entered disabled state Jul 31 14:45:46 Tower kernel: device veth6624a102 entered promiscuous mode Jul 31 14:45:47 Tower kernel: te-bbot-ipv4: port 1(veth6624a102) entered blocking state Jul 31 14:45:47 Tower kernel: te-bbot-ipv4: port 1(veth6624a102) entered forwarding state Jul 31 14:45:48 Tower kernel: te-bbot-ipv4: port 1(veth6624a102) entered disabled state Jul 31 14:45:48 Tower kernel: device veth6624a102 left promiscuous mode Jul 31 14:45:48 Tower kernel: te-bbot-ipv4: port 1(veth6624a102) entered disabled state Jul 31 14:45:49 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 31 14:45:49 Tower kernel: te-bbot-ipv4: port 1(vethf2ca2d71) entered blocking state Jul 31 14:45:49 Tower kernel: te-bbot-ipv4: port 1(vethf2ca2d71) entered disabled state Jul 31 14:45:49 Tower kernel: device vethf2ca2d71 entered promiscuous mode Jul 31 14:45:49 Tower kernel: te-bbot-ipv4: port 1(vethf2ca2d71) entered blocking state Jul 31 14:45:49 Tower kernel: te-bbot-ipv4: port 1(vethf2ca2d71) entered forwarding state Jul 31 14:45:49 Tower kernel: te-bbot-ipv4: port 1(vethf2ca2d71) entered disabled state Jul 31 14:45:49 Tower kernel: device vethf2ca2d71 left promiscuous mode Jul 31 14:45:49 Tower kernel: te-bbot-ipv4: port 1(vethf2ca2d71) entered disabled state Jul 31 14:45:50 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready so looks like the port is always flapping. i has been worked for several months without this error, even on latest or old version. and all others docker has no such issue. BTW, my docker is using br1 which is eth1. eth0 has no cable on it. and here is command to build docker: docker run \ --hostname='mk-TE' \ --memory=2g \ --memory-swap=2g \ --detach=true \ --tty=true \ --shm-size=512M \ -e TEAGENT_ACCOUNT_TOKEN=d812398jkjfadf38cgiap70s349cxfkl1qm \. (i removed some digit here) -e TEAGENT_INET=4 \ -v '/mnt/user/ThousandEyes/thousandeyes/mk-TE/te-agent':/var/lib/te-agent \ -v '/mnt/user/ThousandEyes/thousandeyes/mk-TE/te-browserbot':/var/lib/te-browserbot \ -v '/mnt/user/ThousandEyes/thousandeyes/mk-TE/log/':/var/log/agent \ --cap-add=NET_ADMIN \ --cap-add=SYS_ADMIN \ --name 'mk-TE' \ --net='br1' \ --ip='10.0.0.30' \ --restart=unless-stopped \ --expose=49152/udp \ --expose=49153/udp \ --expose=49153/tcp \ --publish=49152:49152/udp \ --publish=49153:49153/udp \ --publish=49153:49153/tcp \tower-diagnostics-20220731-1528.zip thousandeyes/enterprise-agent:latest /sbin/my_init

i try to install ThousandEyes on my docker but when doing ./configure, i get error "Applying apparmor config./configure_docker.sh: line 171: apparmor_parser: command not found". so i notice unraid does not have apparmor installed, so it cannot finish the configure. so how show i install the apparmor on my unraid? i am using Unraid 6.10.3. i remember it should work with old version, such as 6.9.x Thanks. btw, if you want to try, here is the command to configure seccomp & apparmor profiles for docker: curl -Os https://downloads.thousandeyes.com/bbot/configure_docker.sh chmod +x configure_docker.sh sudo ./configure_docker.sh from the script, it need to run follow two command but failed due to no apparmor installed. cp -f "/var/docker/configs/te-apparmor.cfg" "/etc/apparmor.d/te-apparmor.cfg" apparmor_parser -r -W /etc/apparmor.d/te-apparmor.cfg