Jasonhorne.co

When i try to connect from my client I receive the following log entry. Not sure how there could be mod mismatch as I copied the entire world folder from my client where it was before to the server. [13Jan2025 20:20:33.404] [Netty Client IO #3/ERROR] [net.minecraft.network.Connection/]: Exception caught in connection java.net.SocketException: Connection reset at java.base/sun.nio.ch.SocketChannelImpl.throwConnectionReset(Unknown Source) ~[?:?] at java.base/sun.nio.ch.SocketChannelImpl.read(Unknown Source) ~[?:?] at MC-BOOTSTRAP/[email protected]/io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:254) ~[netty-buffer-4.1.97.Final.jar%23147!/:4.1.97.Final] at MC-BOOTSTRAP/[email protected]/io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) ~[netty-buffer-4.1.97.Final.jar%23147!/:4.1.97.Final] at MC-BOOTSTRAP/[email protected]/io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:357) ~[netty-transport-4.1.97.Final.jar%23154!/:4.1.97.Final] at MC-BOOTSTRAP/[email protected]/io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151) ~[netty-transport-4.1.97.Final.jar%23154!/:4.1.97.Final] at MC-BOOTSTRAP/[email protected]/io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788) ~[netty-transport-4.1.97.Final.jar%23154!/:4.1.97.Final] at MC-BOOTSTRAP/[email protected]/io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724) ~[netty-transport-4.1.97.Final.jar%23154!/:4.1.97.Final] at MC-BOOTSTRAP/[email protected]/io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650) ~[netty-transport-4.1.97.Final.jar%23154!/:4.1.97.Final] at MC-BOOTSTRAP/[email protected]/io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) ~[netty-transport-4.1.97.Final.jar%23154!/:4.1.97.Final] at MC-BOOTSTRAP/[email protected]/io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.97.Final.jar%23149!/:4.1.97.Final] at MC-BOOTSTRAP/[email protected]/io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.97.Final.jar%23149!/:4.1.97.Final] at java.base/java.lang.Thread.run(Unknown Source) [?:?] [13Jan2025 20:20:33.464] [Netty Client IO #3/ERROR] [net.minecraft.CrashReport/]: Negative index in crash report handler (13/21) [13Jan2025 20:20:33.473] [Netty Client IO #3/FATAL] [net.neoforged.neoforge.common.NeoForgeMod/]: Preparing crash report with UUID 8d3e84df-b267-4bd2-9c02-b42cd16ffd94 [13Jan2025 20:20:33.504] [Render thread/WARN] [net.neoforged.neoforge.client.gui.ModMismatchDisconnectedScreen/]: Channel [sophisticatedcore:sound_stop_notification] failed to connect: Channel of mod "Sophisticated Core" failed to connect: This channel is missing on the server side, but required on the client! [13Jan2025 20:20:33.504] [Render thread/WARN] [net.neoforged.neoforge.client.gui.ModMismatchDisconnectedScreen/]: Channel [enderio:vat_dump_tank] failed to connect: Channel of mod "Ender IO" failed to connect: This channel is missing on the server side, but required on the client! [13Jan2025 20:20:33.504] [Render thread/WARN] [net.neoforged.neoforge.client.gui.ModMismatchDisconnectedScreen/]: Channel [enderio:vat_move_tank] failed to connect: Channel of mod "Ender IO" failed to connect: This channel is missing on the server side, but required on the client! [13Jan2025 20:20:33.711] [Render thread/WARN] [net.minecraft.client.multiplayer.ClientCommonPacketListenerImpl/]: Client disconnected with reason: Internal Exception: java.net.SocketException: Connection reset

The server is now getting an IP address and I can ping it but I still cant access the web GUI. Just says refused to connect.

I already removed all other cables but the one. The server isnt getting an IP address at all. The nic isnt showing any IP address assigned to it.

I turned off bonding on my NIC and on my switch and now I can no longer reach the web GUI nor the OS GUI. The NIC isn't getting an IP address, I've tried enabling DHCP and using a static IP with no change in networks.cfg file. When I try the local GUI it says it cant connect to the localhost. I've read the other posts with this same issue and I've waited for a good amount of time with no change. Diag logs attached. Any help is appreciated. vault-diagnostics-20230420-2038.zip

Yes the parity sync was still in progress when I took diags. I did that because even if I have all the dockers stopped the parity sync speed is still around 10MBs. So I didn't see a reason to stop it as it doesn't increase the speed.

I tried letting it run with all dockers stopped but the speed was the same so if the speed is the same might as well have the dockers running. But I will stop them all until it's done. I've have the tips amd tweaks plugin and followed that exact thread before.

My server performance is not what it should be considering my hardware. Just navigating around the interface is very slow or sometimes takes 10 minutes to load a page. A server restart fixes it for a very short period of time, so I'm thinking something is filling up but I can tell what. My mover and parity performance is extremely slow as well, also get "execution error a lot when starting or stopping dockers". I've looked at a bunch of other threads but its doesn't seem to be one specific issue causing these issues. So I'm here posting my diags to see if someone had the time to help me out. I do appreciate it. Setup: Dell R730XD 12 3.5 bay CPU: 2 E5-2699 v3 18 core RAM: 128gb A-Tech 2Rx4 PC4 2400mhz ECC Reg Drives: 1 16tb Exos (parity) 1 16tb Exos (array) 3 10tb WD Ironwolf Pro Reds (array) 4 6tb WD NASware (array) 2 2.5inch 1tb Dell Constellation in cache pool raid0 (temporary and need to remove this cache drive) 2 1tb Crucial P2 NVME m.2 drives in cache pool raid0 (for main cache) Dell H730P Mini configured to HBA (non IT mode) NVIDIA QUARDRO P200 vault-diagnostics-20221114-1510.zip

I followed the steps here but when I start the stack my grafana webui never loads and my server log just loops this. Guide https://github.com/HStep20/Ultimate-Unraid-Dashboard-Guide Log: Nov 2 17:27:39 Vault kernel: docker0: port 5(veth8fdf633) entered blocking state Nov 2 17:27:39 Vault kernel: docker0: port 5(veth8fdf633) entered disabled state Nov 2 17:27:39 Vault kernel: device veth8fdf633 entered promiscuous mode Nov 2 17:27:42 Vault kernel: eth0: renamed from veth24cf354 Nov 2 17:27:42 Vault kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8fdf633: link becomes ready Nov 2 17:27:42 Vault kernel: docker0: port 5(veth8fdf633) entered blocking state Nov 2 17:27:42 Vault kernel: docker0: port 5(veth8fdf633) entered forwarding state Nov 2 17:27:42 Vault kernel: docker0: port 5(veth8fdf633) entered disabled state Nov 2 17:27:42 Vault kernel: veth24cf354: renamed from eth0 Nov 2 17:27:43 Vault kernel: docker0: port 5(veth8fdf633) entered disabled state Nov 2 17:27:43 Vault kernel: device veth8fdf633 left promiscuous mode Nov 2 17:27:43 Vault kernel: docker0: port 5(veth8fdf633) entered disabled state Nov 2 17:27:58 Vault kernel: docker0: port 5(veth564d5dc) entered blocking state Nov 2 17:27:58 Vault kernel: docker0: port 5(veth564d5dc) entered disabled state Nov 2 17:27:58 Vault kernel: device veth564d5dc entered promiscuous mode Nov 2 17:28:01 Vault kernel: eth0: renamed from vethf453cd6 Nov 2 17:28:01 Vault kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth564d5dc: link becomes ready Nov 2 17:28:01 Vault kernel: docker0: port 5(veth564d5dc) entered blocking state Nov 2 17:28:01 Vault kernel: docker0: port 5(veth564d5dc) entered forwarding state Nov 2 17:28:02 Vault avahi-daemon[28394]: Joining mDNS multicast group on interface veth564d5dc.IPv6 with address fe80::4c56:d2ff:fe3e:a7ce. Nov 2 17:28:02 Vault avahi-daemon[28394]: New relevant interface veth564d5dc.IPv6 for mDNS. Nov 2 17:28:02 Vault avahi-daemon[28394]: Registering new address record for fe80::4c56:d2ff:fe3e:a7ce on veth564d5dc.*. Nov 2 17:28:03 Vault kernel: vethf453cd6: renamed from eth0 Nov 2 17:28:03 Vault kernel: docker0: port 5(veth564d5dc) entered disabled state Nov 2 17:28:04 Vault avahi-daemon[28394]: Interface veth564d5dc.IPv6 no longer relevant for mDNS. Nov 2 17:28:04 Vault avahi-daemon[28394]: Leaving mDNS multicast group on interface veth564d5dc.IPv6 with address fe80::4c56:d2ff:fe3e:a7ce. Nov 2 17:28:04 Vault kernel: docker0: port 5(veth564d5dc) entered disabled state Nov 2 17:28:04 Vault kernel: device veth564d5dc left promiscuous mode Nov 2 17:28:04 Vault kernel: docker0: port 5(veth564d5dc) entered disabled state Nov 2 17:28:04 Vault avahi-daemon[28394]: Withdrawing address record for fe80::4c56:d2ff:fe3e:a7ce on veth564d5dc. Nov 2 17:28:42 Vault kernel: docker0: port 5(veth1ece80b) entered blocking state Nov 2 17:28:42 Vault kernel: docker0: port 5(veth1ece80b) entered disabled state Nov 2 17:28:42 Vault kernel: device veth1ece80b entered promiscuous mode Nov 2 17:28:45 Vault kernel: eth0: renamed from vethd0586ec Nov 2 17:28:45 Vault kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1ece80b: link becomes ready Nov 2 17:28:45 Vault kernel: docker0: port 5(veth1ece80b) entered blocking state Nov 2 17:28:45 Vault kernel: docker0: port 5(veth1ece80b) entered forwarding state Nov 2 17:28:46 Vault kernel: vethd0586ec: renamed from eth0 Nov 2 17:28:46 Vault kernel: docker0: port 5(veth1ece80b) entered disabled state Nov 2 17:28:47 Vault kernel: docker0: port 5(veth1ece80b) entered disabled state Nov 2 17:28:47 Vault kernel: device veth1ece80b left promiscuous mode Nov 2 17:28:47 Vault kernel: docker0: port 5(veth1ece80b) entered disabled state