watchdog and network connection problems

Traceback (most recent call last):
File "/usr/bin/qtvcp", line 555, in <module>
_qtvcp = QTVCP()
^^^^^^^
File "/usr/bin/qtvcp", line 261, in __init__
window.load_extension(opts.usermod)
File "/usr/lib/python3/dist-packages/qtvcp/qt_makegui.py", line 269, in load_extension
methods, self[obj].handler_module, self[obj].handler_instance = self._load_handlers([handlerpath], self.halcomp, self[obj])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/qtvcp/qt_makegui.py", line 297, in _load_handlers
mod = __import__(basename)
^^^^^^^^^^^^^^^^^^^^
File "/usr/share/qtvcp/panels/test_panel/test_panel_handler.py", line 5, in <module>
from distutils.spawn import find_executable
ModuleNotFoundError: No module named 'distutils'

is the error i am getting with qtdragon

this machine will work for a few days in Axis gui and then stops communicating. Resource temporarily unavailable. no communication lights on the rj45 connector on the mesa 7i96 and unable to ping 10.10.10.10. i didn't change anything. im also having some other communication problems within Axis when it was running. my servo spindle will have a long delay before linuxcnc tells it to turn on. minutes agter i turn it on, it comes on. i checked the wiring. its the same issue ive been having. its not new. a reinstall of the os would be a work around but ultimatley, that doesn't fix anything. i am not getting the watchdog error light(red light on the mesa 7i96s. )

here is ip a;
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether a4:1f:72:67:47:1f brd ff:ff:ff:ff:ff:ff
inet 10.10.10.1/8 brd 10.255.255.255 scope global enp4s0
valid_lft forever preferred_lft forever
inet6 fe80::a61f:72ff:fe67:471f/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 9c:2a:70:32:72:49 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.106/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp3s0
valid_lft 42363sec preferred_lft 42363sec
inet6 2603:7080:e936:2933::12d8/128 scope global dynamic noprefixroute
valid_lft 603964sec preferred_lft 603964sec
inet6 fd00:f405:95cf:605a::12d8/128 scope global dynamic noprefixroute
valid_lft 603964sec preferred_lft 603964sec
inet6 fd00:f405:95cf:605a:bc86:6ca6:e17a:1d65/64 scope global temporary dynamic
valid_lft 603965sec preferred_lft 85084sec
inet6 fd00:f405:95cf:605a:9e2a:70ff:fe32:7249/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604537sec preferred_lft 604537sec
inet6 2603:7080:e936:2933:6b4b:639:ebcd:c3eb/64 scope global temporary dynamic
valid_lft 603965sec preferred_lft 85084sec
inet6 2603:7080:e936:2933:9e2a:70ff:fe32:7249/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604537sec preferred_lft 604537sec
inet6 fe80::9e2a:70ff:fe32:7249/64 scope link noprefixroute
valid_lft forever preferred_lft forever
destination unreachable with ping.

here it is after a reset of the mesa 7i96s

ip a ;
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a4:1f:72:67:47:1f brd ff:ff:ff:ff:ff:ff
inet 10.10.10.1/8 brd 10.255.255.255 scope global enp4s0
valid_lft forever preferred_lft forever
inet6 fe80::a61f:72ff:fe67:471f/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 9c:2a:70:32:72:49 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.106/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp3s0
valid_lft 42120sec preferred_lft 42120sec
inet6 2603:7080:e936:2933::12d8/128 scope global dynamic noprefixroute
valid_lft 603721sec preferred_lft 603721sec
inet6 fd00:f405:95cf:605a::12d8/128 scope global dynamic noprefixroute
valid_lft 603721sec preferred_lft 603721sec
inet6 fd00:f405:95cf:605a:bc86:6ca6:e17a:1d65/64 scope global temporary dynamic
valid_lft 603722sec preferred_lft 84841sec
inet6 fd00:f405:95cf:605a:9e2a:70ff:fe32:7249/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604775sec preferred_lft 604775sec
inet6 2603:7080:e936:2933:6b4b:639:ebcd:c3eb/64 scope global temporary dynamic
valid_lft 603722sec preferred_lft 84841sec
inet6 2603:7080:e936:2933:9e2a:70ff:fe32:7249/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 604775sec preferred_lft 604775sec
inet6 fe80::9e2a:70ff:fe32:7249/64 scope link noprefixroute
valid_lft forever preferred_lft forever
still not able to ping

2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether a4:1f:72:67:47:1f brd ff:ff:ff:ff:ff:ff
inet 10.10.10.1/8 brd 10.255.255.255 scope global enp4s0
valid_lft forever preferred_lft forever
inet6 fe80::a61f:72ff:fe67:471f/64 scope link proto kernel_ll


Try setting the netmask to /24
and disabling IPV6 in the network settings for enp4s0

how do i do that through terminal? i would have to create a new connection to do it through the gui. im not sure, but i think that causes conflicts when you create a connection and have it configured through /etc/network/interfaces.

thank you all you help and patients with me. this would be a considerably longer process without the help of way smarter people than i am.

im getting that red light on the mesa 7i96s again.

here is the results of sudo chrt 99 ping -i .001 -q 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
ping: Warning: time of day goes back (-511999937us), taking countermeasures
ping: Warning: time of day goes back (-511999879us), taking countermeasures
ping: Warning: time of day goes back (-2199023255489us), taking countermeasures

--- 10.10.10.10 ping statistics ---
5924 packets transmitted, 1308 received, +1898 errors, 77.9203% packet loss, time 587511ms
rtt min/avg/max/mdev = 0.000/0.109/8.769/0.401 ms, pipe 12
it seems to be communicating but drops the majority of packests