The backup failed (uplink -p4
) last Sunday 9th of December
:
root-node-1 | 214GiB 0:55:08 [89.9MiB/s] [66.5MiB/s] [> ] 5% ETA 15:40:42
root-node-1 | failed to upload part 213: uplink: encryption: metaclient: manager closed: closed: read tcp 172.19.0.3:42882->34.172.100.72:7777: read: connection reset by peer
root-node-1 | error getting reader for part 215: context canceled
root-node-1 | failed to upload part 212: uplink: failed to upload enough pieces (needed at least 80 but got 72)
root-node-1 | failed to upload part 214: uplink: context canceled
root-node-1 | 215GiB 0:55:11 [66.5MiB/s] [66.5MiB/s] [> ] 5%
root-node-1 |
And today (16 December 2023):
root-node-1 | 24.6GiB 0:07:15 [62.5MiB/s] [57.9MiB/s] [> ] 0% ETA 19:07:57
root-node-1 | 25.0GiB 0:07:20 [76.3MiB/s] [58.1MiB/s] [> ] 0% ETA 19:03:45
root-node-1 | failed to upload part 15: uplink: metaclient: manager closed: closed: read tcp 172.19.0.3:55320->34.172.100.72:7777: read: con
nection reset by peer
root-node-1 | error getting reader for part 25: context canceled
root-node-1 | failed to upload part 23: uplink: encryption: context canceled
root-node-1 | failed to upload part 24: uplink: context canceled
root-node-1 | 25.0GiB 0:07:21 [58.0MiB/s] [58.0MiB/s] [> ] 0%
So Iāve restarted it again with uplink -p 2
now.
Good point!
Though we are not using the firewall on our MikroTik router.
[admin@MikroTik] > /ip/firewall/connection/print
<nothing>
[admin@MikroTik] > /ip/firewall/filter/print
Flags: X - disabled, I - invalid; D - dynamic
[admin@MikroTik] > /ip/firewall/nat/print
Flags: X - disabled, I - invalid; D - dynamic
[admin@MikroTik] > /ip/firewall/mangle/print
Flags: X - disabled, I - invalid; D - dynamic
[admin@MikroTik] > /ip/firewall/raw/print
Flags: X - disabled, I - invalid; D - dynamic
[admin@MikroTik] >
[admin@MikroTik] > /ip/firewall/connection/tracking/print
enabled: auto
active-ipv4: no
active-ipv6: no
tcp-syn-sent-timeout: 5s
tcp-syn-received-timeout: 5s
tcp-established-timeout: 1d
tcp-fin-wait-timeout: 10s
tcp-close-wait-timeout: 10s
tcp-last-ack-timeout: 10s
tcp-time-wait-timeout: 10s
tcp-close-timeout: 10s
tcp-max-retrans-timeout: 5m
tcp-unacked-timeout: 5m
loose-tcp-tracking: yes
udp-timeout: 10s
udp-stream-timeout: 3m
icmp-timeout: 10s
generic-timeout: 10m
max-entries: 28672
total-entries: 0
AFAIK, the connection tracking feature primarily comes into play when the router needs to keep track of the state of network connections, which is typically necessary for certain types of firewall rules.
We donāt use Firewall so the connection tracking limitation can be ignored I guess, nor we have QoS. We have pretty much default and very simple MikroTik router config.
So it might be anything else I guess (e.g. FW/SW/HW, cables, or ISP/upstream issues).
The temperature is less than 80Ā°C which should not be a concern for MikroTik CRS326-24S+2Q+ we have. And the network load is 0% despite it being making the backup right now with Storjās uplink
at this very moment.