maxtoid
Cadet
- Joined
- Jun 4, 2020
- Messages
- 3
So I finally made the jump and upgraded to 11.3-U5 to the 12.0 release and at first everything seemed to work fine, or so it seemed for about a week or so. I then tried to upgrade a plugin and found that even though I had upgraded my pools, I had forgotten to upgrade my jails. So I performed the "iocage upgrade JAIL -r 12.1-RELEASE" on each of my base jails (which took quite a bit of work since it broke things like pkg and other issues), but I finally got them all working and upgraded.
Now, seemingly as soon as I finished upgrading the jails, my web UI is completely fried. It will lock up and present you with the "Connecting to TrueNAS ... Make sure the TrueNAS system is powered on and connected to the network." message.
It looks and acts Very similar to this issue: https://www.truenas.com/community/threads/11-3-web-ui-connecting-to-freenas.81969 where even the console access doesn't work (just brings you back to the set of options when you try to select one).
I can get in via ssh, where the logs show all sorts of errors but nothing really helpful... I've posted some of them below. - I'm kind of at a loss where to start here, has anyone else experienced anything similar? I would downgrade to 11.3U5 but I already upgraded the pools so I'm assuming downgrading isn't an option... would a clean install help? Is there a way to preserve the pools if I wipe the OS install and reinstall?
Oddly, while it seems to completely break the host TrueNAS OS, the jails perform fine and are fully accessible/functional. Not running LAG on any of the ports and already confirmed there aren't two NICs on the same subnet. It's really odd.
If I manually reboot it via ssh it works for anywhere from 15-45 minutes before it locks up again.
----------------------------------------------------
errors from middleware.log:
Errors from debug.log:
Errors from daemon.log:
Interestingly, if I do cat /var/log/system - there are a ton of arp messages thinking that the primary NIC IP is moving back and forth between the actual MAC address of the port on the freenas box, and one of the virtual MAC addresses that the jails use. It's not one that's in use by a jail, though, I checked that:
And lastly, I pulled this from the middleware log export from right before I rebooted it manually:
Any thoughts suggestions or insight would be greatly appreciated!
Now, seemingly as soon as I finished upgrading the jails, my web UI is completely fried. It will lock up and present you with the "Connecting to TrueNAS ... Make sure the TrueNAS system is powered on and connected to the network." message.
It looks and acts Very similar to this issue: https://www.truenas.com/community/threads/11-3-web-ui-connecting-to-freenas.81969 where even the console access doesn't work (just brings you back to the set of options when you try to select one).
I can get in via ssh, where the logs show all sorts of errors but nothing really helpful... I've posted some of them below. - I'm kind of at a loss where to start here, has anyone else experienced anything similar? I would downgrade to 11.3U5 but I already upgraded the pools so I'm assuming downgrading isn't an option... would a clean install help? Is there a way to preserve the pools if I wipe the OS install and reinstall?
Oddly, while it seems to completely break the host TrueNAS OS, the jails perform fine and are fully accessible/functional. Not running LAG on any of the ports and already confirmed there aren't two NICs on the same subnet. It's really odd.
If I manually reboot it via ssh it works for anywhere from 15-45 minutes before it locks up again.
----------------------------------------------------
errors from middleware.log:
Code:
[2020/12/01 21:16:13] (WARNING) middlewared._loop_monitor_thread():1404 - Task seems blocked: File "/usr/local/bin/middlewared", line 10, in <module> sys.exit(main()) File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1577, in main Middleware( File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1421, in run self.loop.run_forever() File "/usr/local/lib/python3.8/asyncio/base_events.py", line 570, in run_forever self._run_once() File "/usr/local/lib/python3.8/asyncio/base_events.py", line 1859, in _run_once handle._run() File "/usr/local/lib/python3.8/asyncio/events.py", line 81, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.8/site-packages/aiohttp/web_ws.py", line 281, in send_str await self._writer.send(data, binary=False, compress=compress) File "/usr/local/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 649, in send await self._send_frame(message, WSMsgType.TEXT, compress) File "/usr/local/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 587, in _send_frame message = compressobj.compress(message) [2020/12/01 21:16:58] (WARNING) middlewared._loop_monitor_thread():1404 - Task seems blocked: File "/usr/local/bin/middlewared", line 10, in <module> sys.exit(main()) File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1577, in main Middleware( File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1421, in run self.loop.run_forever() File "/usr/local/lib/python3.8/asyncio/base_events.py", line 570, in run_forever self._run_once() File "/usr/local/lib/python3.8/asyncio/base_events.py", line 1859, in _run_once handle._run() File "/usr/local/lib/python3.8/asyncio/events.py", line 81, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.8/site-packages/aiohttp/web_ws.py", line 281, in send_str await self._writer.send(data, binary=False, compress=compress) File "/usr/local/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 649, in send await self._send_frame(message, WSMsgType.TEXT, compress) File "/usr/local/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 588, in _send_frame message = message + compressobj.flush( [2020/12/01 21:45:34] (WARNING) middlewared._loop_monitor_thread():1404 - Task seems blocked: File "/usr/local/lib/python3.8/site-packages/middlewared/alert/source/ipmi_sel.py", line 151, in check return await self._produce_alerts_for_ipmitool_output(await ipmitool(["-c", "sel", "elist"])) File "/usr/local/lib/python3.8/site-packages/middlewared/alert/source/ipmi_sel.py", line 28, in __call__ result = await run(["ipmitool"] + args, check=False, encoding="utf8", errors="ignore") File "/usr/local/lib/python3.8/site-packages/middlewared/utils/__init__.py", line 53, in run proc = await asyncio.create_subprocess_exec(*args, **kwargs) File "/usr/local/lib/python3.8/asyncio/subprocess.py", line 236, in create_subprocess_exec transport, protocol = await loop.subprocess_exec( File "/usr/local/lib/python3.8/asyncio/base_events.py", line 1630, in subprocess_exec transport = await self._make_subprocess_transport( File "/usr/local/lib/python3.8/asyncio/unix_events.py", line 197, in _make_subprocess_transport transp = _UnixSubprocessTransport(self, protocol, args, shell, File "/usr/local/lib/python3.8/asyncio/base_subprocess.py", line 36, in __init__ self._start(args=args, shell=shell, stdin=stdin, stdout=stdout, File "/usr/local/lib/python3.8/asyncio/unix_events.py", line 789, in _start self._proc = subprocess.Popen( File "/usr/local/lib/python3.8/subprocess.py", line 854, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/local/lib/python3.8/subprocess.py", line 1664, in _execute_child os.close(errpipe_read) [2020/12/01 21:54:47] (WARNING) middlewared._loop_monitor_thread():1404 - Task seems blocked: File "/usr/local/bin/middlewared", line 10, in <module> sys.exit(main()) File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1577, in main Middleware( File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1421, in run self.loop.run_forever() File "/usr/local/lib/python3.8/asyncio/base_events.py", line 570, in run_forever self._run_once() File "/usr/local/lib/python3.8/asyncio/base_events.py", line 1859, in _run_once handle._run() File "/usr/local/lib/python3.8/asyncio/events.py", line 81, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.8/site-packages/aiohttp/web_ws.py", line 281, in send_str await self._writer.send(data, binary=False, compress=compress) File "/usr/local/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 649, in send await self._send_frame(message, WSMsgType.TEXT, compress) File "/usr/local/lib/python3.8/site-packages/aiohttp/http_websocket.py", line 620, in _send_frame self.transport.write(header + message) File "/usr/local/lib/python3.8/asyncio/selector_events.py", line 908, in write n = self._sock.send(data)
Errors from debug.log:
Code:
Dec 1 23:39:20 VAULT kernel: sonewconn: pcb 0xfffff802703065b8: Listen queue overflow: 193 already in queue awaiting acceptance (14 occurrences) Dec 1 23:40:20 VAULT kernel: sonewconn: pcb 0xfffff802703065b8: Listen queue overflow: 193 already in queue awaiting acceptance (13 occurrences) Dec 1 23:41:20 VAULT kernel: sonewconn: pcb 0xfffff802703065b8: Listen queue overflow: 193 already in queue awaiting acceptance (11 occurrences) Dec 1 23:42:20 VAULT kernel: sonewconn: pcb 0xfffff802703065b8: Listen queue overflow: 193 already in queue awaiting acceptance (13 occurrences) Dec 1 23:43:20 VAULT kernel: sonewconn: pcb 0xfffff802703065b8: Listen queue overflow: 193 already in queue awaiting acceptance (10 occurrences) Dec 1 23:44:20 VAULT kernel: sonewconn: pcb 0xfffff802703065b8: Listen queue overflow: 193 already in queue awaiting acceptance (14 occurrences) Dec 1 23:45:20 VAULT kernel: sonewconn: pcb 0xfffff802703065b8: Listen queue overflow: 193 already in queue awaiting acceptance (11 occurrences) Dec 1 23:46:20 VAULT kernel: sonewconn: pcb 0xfffff802703065b8: Listen queue overflow: 193 already in queue awaiting acceptance (9 occurrences) Dec 1 23:47:21 VAULT kernel: sonewconn: pcb 0xfffff802703065b8: Listen queue overflow: 193 already in queue awaiting acceptance (9 occurrences) Dec 1 23:48:21 VAULT kernel: sonewconn: pcb 0xfffff802703065b8: Listen queue overflow: 193 already in queue awaiting acceptance (11 occurrences)
Errors from daemon.log:
Code:
Dec 1 23:22:49 VAULT 1 2020-12-01T23:22:49.068402-05:00 VAULT.vhost.us collectd 4193 - - Traceback (most recent call last): File "/usr/local/lib/collectd_pyplugins/disktemp.py", line 62, in read with Client() as c: File "/usr/local/lib/python3.8/site-packages/middlewared/client/client.py", line 281, in __init__ self._ws.connect() File "/usr/local/lib/python3.8/site-packages/middlewared/client/client.py", line 124, in connect rv = super(WSClient, self).connect() File "/usr/local/lib/python3.8/site-packages/ws4py/client/__init__.py", line 223, in connect bytes = self.sock.recv(128) socket.timeout: timed out Dec 1 23:27:49 VAULT 1 2020-12-01T23:27:49.063753-05:00 VAULT.vhost.us collectd 4193 - - Traceback (most recent call last): File "/usr/local/lib/collectd_pyplugins/disktemp.py", line 62, in read with Client() as c: File "/usr/local/lib/python3.8/site-packages/middlewared/client/client.py", line 281, in __init__ self._ws.connect() File "/usr/local/lib/python3.8/site-packages/middlewared/client/client.py", line 124, in connect rv = super(WSClient, self).connect() File "/usr/local/lib/python3.8/site-packages/ws4py/client/__init__.py", line 223, in connect bytes = self.sock.recv(128) socket.timeout: timed out Dec 1 23:32:49 VAULT 1 2020-12-01T23:32:49.072775-05:00 VAULT.vhost.us collectd 4193 - - Traceback (most recent call last): File "/usr/local/lib/collectd_pyplugins/disktemp.py", line 62, in read with Client() as c: File "/usr/local/lib/python3.8/site-packages/middlewared/client/client.py", line 281, in __init__ self._ws.connect() File "/usr/local/lib/python3.8/site-packages/middlewared/client/client.py", line 124, in connect rv = super(WSClient, self).connect() File "/usr/local/lib/python3.8/site-packages/ws4py/client/__init__.py", line 223, in connect bytes = self.sock.recv(128) socket.timeout: timed out Dec 1 23:37:49 VAULT 1 2020-12-01T23:37:49.060546-05:00 VAULT.vhost.us collectd 4193 - - Traceback (most recent call last): File "/usr/local/lib/collectd_pyplugins/disktemp.py", line 62, in read with Client() as c: File "/usr/local/lib/python3.8/site-packages/middlewared/client/client.py", line 281, in __init__ self._ws.connect() File "/usr/local/lib/python3.8/site-packages/middlewared/client/client.py", line 124, in connect rv = super(WSClient, self).connect() File "/usr/local/lib/python3.8/site-packages/ws4py/client/__init__.py", line 223, in connect bytes = self.sock.recv(128) socket.timeout: timed out Dec 1 23:42:49 VAULT 1 2020-12-01T23:42:49.063308-05:00 VAULT.vhost.us collectd 4193 - - Traceback (most recent call last): File "/usr/local/lib/collectd_pyplugins/disktemp.py", line 62, in read with Client() as c: File "/usr/local/lib/python3.8/site-packages/middlewared/client/client.py", line 281, in __init__ self._ws.connect() File "/usr/local/lib/python3.8/site-packages/middlewared/client/client.py", line 124, in connect rv = super(WSClient, self).connect() File "/usr/local/lib/python3.8/site-packages/ws4py/client/__init__.py", line 223, in connect bytes = self.sock.recv(128) socket.timeout: timed out Dec 1 23:47:49 VAULT 1 2020-12-01T23:47:49.068544-05:00 VAULT.vhost.us collectd 4193 - - Traceback (most recent call last): File "/usr/local/lib/collectd_pyplugins/disktemp.py", line 62, in read with Client() as c: File "/usr/local/lib/python3.8/site-packages/middlewared/client/client.py", line 281, in __init__ self._ws.connect() File "/usr/local/lib/python3.8/site-packages/middlewared/client/client.py", line 124, in connect rv = super(WSClient, self).connect() File "/usr/local/lib/python3.8/site-packages/ws4py/client/__init__.py", line 223, in connect bytes = self.sock.recv(128) socket.timeout: timed out
Interestingly, if I do cat /var/log/system - there are a ton of arp messages thinking that the primary NIC IP is moving back and forth between the actual MAC address of the port on the freenas box, and one of the virtual MAC addresses that the jails use. It's not one that's in use by a jail, though, I checked that:
Code:
Nov 30 13:11:09 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 16:13:18 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Nov 30 16:33:18 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 16:53:18 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Nov 30 17:13:18 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 17:33:18 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 17:53:18 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 18:13:18 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 18:33:19 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 18:53:19 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Nov 30 19:13:19 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 19:33:19 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 19:53:19 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 20:13:19 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 20:33:19 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 20:53:20 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 21:13:20 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 21:33:19 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 21:53:19 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Nov 30 22:13:19 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 22:33:30 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Nov 30 23:53:30 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Dec 1 00:13:30 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 00:33:30 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 00:53:30 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 01:13:30 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 01:17:49 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 02:13:31 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 03:53:31 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 04:13:31 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 04:33:31 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 05:33:32 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Dec 1 05:53:32 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 06:13:32 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 06:33:32 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 07:13:32 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Dec 1 07:18:06 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 09:53:33 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 10:33:30 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Dec 1 10:53:33 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 11:13:33 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 11:33:33 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Dec 1 11:53:33 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 12:00:00 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 13:13:33 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 15:44:32 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 16:24:34 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Dec 1 16:44:34 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 17:04:34 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 17:24:34 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 17:35:02 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 18:04:34 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Dec 1 18:15:08 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 18:44:34 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Dec 1 19:04:34 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 19:24:34 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 19:44:34 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 20:14:26 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 20:23:04 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 20:43:08 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 21:43:15 VAULT kernel: arp: 10.0.1.10 moved from 00:25:90:bc:c2:7b to 02:25:90:55:0c:82 on epair0b Dec 1 21:58:29 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b Dec 1 23:24:13 VAULT kernel: arp: 10.0.1.10 moved from 02:25:90:55:0c:82 to 00:25:90:bc:c2:7b on epair0b
And lastly, I pulled this from the middleware log export from right before I rebooted it manually:
Code:
[2020/12/01 20:22:14] (WARNING) builtins.add_bind_interfaces():116 - IP address [172.16.5.10] is no longer in use and should be removed from SMB configuration. [2020/12/01 20:22:14] (WARNING) builtins.add_bind_interfaces():116 - IP address [10.0.1.10] is no longer in use and should be removed from SMB configuration. [2020/12/01 20:22:14] (WARNING) builtins.add_bind_interfaces():116 - IP address [172.16.10.10] is no longer in use and should be removed from SMB configuration.
Any thoughts suggestions or insight would be greatly appreciated!