3.1.6 (b2773) Crash today

This is a new one for me. Thanks for the screen shot. I will get this into a bug and onto development.

Thanks Chris.

Let me know what you find out. The console won't connect to the show server at all right now. All I can do is log into Hog3PC as a client to run. Any insight would be greatly appreciated.

J

If you look in the control panel under the network tab on the failing H3 client does the console report any number greater than 0 for RX errors, TX errors, RX drops or TX drops?

Remind me again what are you using as your server. H3PC?

Normally the console is the server, but when it wouldn't connect, I ended up having to use an old PC and Hog3PC to get it to run last night.

I'll check the RX/TX errors today when I get in.

There isn't an issue with it when it's connected as a client. It's only an issue when it runs as the server and won't connect to the show server.

The screenshot was a crash when the console was the server, not a client. Setting it up as a client was the only way to make it through last night.

So normally the H3 is the server and normally there is no client?

Correct.

Normal setup:

HogNet:
H3
DP8000
Exp. Wing
Playback Wing

Artnet:
DP2000 (in Artnet mode)
DHCP Router for Artnet network
21 Pathport Nodes in Artnet mode

There is an old PC kept under FOH for using remote focus, but is not normally connected to the network (as in this case, it was not setup)

"Fix" for H3 not connecting was to put the Hog3PC into server mode and connect the Hog3 as a client.

Hope this helps Chris...let me know if you need further information.

Yes Jon,

That information does help a lot. Let me know about the send/receive errors when you get in and we'll see if this is rooted in hardware or software.

Got in and went to check the TX/RX errors but the console (client) was completely frozen (we left it all on last night). Wouldn't respond to mouse, touch screens, pig-open-backspace, nothing.

Did a reboot and could only get an "X" on the right touchscreen.

Server is still running on Hog3PC with no problems. On the server there are no TX/RX errors or drops reported.

EDIT:
Performing a full ISO currently to see if it comes back.

ISO completed. Console still failed to start show server. Cannot start a new show either.

I pulled up the Control panel and it's showing:
RX Packets: 6334
TX Packets: 1664
RX Errors: 0
TX Errors: 10
RX Drops: 0
TX Drops: 0

I then tried putting it back in Client mode to connect to the server Hog3PC. Clicked on Use Custom IP settings and the system completely froze again.

Had to do a hard reset on the main power switch. Upon reboot, went back into the control panel and setup for client mode (server off, etc). Connected to Hog3PC server with no problems.

RX Packets: 8401
TX Packets: 1604
RX Errors: 0
TX Errors: 0
RX Drops: 0
TX Drops: 0

???????? :confused::confused::confused: ???????

I really don't like seeing those 10 TX errors. One a properly functioning network you should have almost no errors and you're getting nearly 1% with errors. That's bad news.

Try using different cables, and a different port on the switch. Try a different switch if you have one. Also make sure you don't have a duplex mismatch between the two ends of the link.

What kind of switch are you using? Can you see packet error statistics on the switch?

Eric,

This is a permanent system (of 8 years). And, as long as I'm connected as a CLIENT, I have 0 TX errors. It's only when I try and start the show server from the main console that I get the errors. Currently, I'm still sitting at 0 errors while logged in as a client.

Current path (and it doesn't change from server to client, just settings in the console).

Hog 3 - Ethernet Jack at FOH - Cat6 in conduit - patch panel at FOH rack - 6" Patch cable from Patch panel to switch

Switch is USR 100/1000 Mbps 16-port Smart Switch
Firmware: 2.00.08-1109
Currently reading no RX/TX errors.

Swapped console back to show server - will not connect to show server.
Tried putting in a temporary Cat6 cable directly from Hog 3 to switch (different port). Still will not connect to show sever. It now shows (don't fall over) 437 TX errors out of 5757 TX packets but only on the HOG3! The USR page still shows no TX errors so it's not making it to the switch.

Switch it back to client setup and it reads 0 RX/TX errors again.
:dunno::dunno::dunno::dunno:

(And, just so you know, this is a BRAND NEW motherboard from HES installed last Thursday by HES repair center)

Brad has my number if you want to call me...

I have now left it running in client mode for 30 minutes with 0 TX errors.

I shut down and switched back to server and immediately have 430 errors.

It seems to be when I put the console back on as the DHCP server is when the issues start. (And yes, I completely disconnected Hog3PC from the system when I enable DHCP on the console)

No other cabling, switch port, patch cables change in the changeover.

Things are not looking good for that desk. You just got it back from us about a week ago? Let us know how the ISO goes.

The ISO was after between post 9 and post 10. All of the latest was POST-ISO.

Motherboard was from Austin. Repairs done thru local HES Service Center. Could it be a bad motherboard????

Heres the latest from today's testing.

Tried turning off DHCP and starting show - 6 attempts to contact to show server failed
Tried turning DHCP back on and starting show - 6 attempts to contact show server failed
Tried creating s brand new show with DHCP on - failed as soon as I hit continue after selecting the library and locked at a black "X" on the right screen and splash on the left. Had to hard restart the console.
Boot time was VERY long - approximately 4:30. *Sat at the black "x" for quite a while and I thought it was dead. Finally got to the start screen after just letting it sit.
Connected Hog3PC back up. Set the main console to #2 and turned off "run server" hit apply. Immediately, I was able to connect to the Hog3PC show as a client with no problems. No TX/RX errors or drops.

So back to the original question....can this be related to the new motherboard!? Do I need to get it swapped back out??!