[3.4rc1] 6HC + SBC DWC "Network error"
-
After upgrading a test machine to 3.4rc1 on a 6HC + SBC, we are seeing a lot of "Network errors" when editing / creating / deleting / listing files. Clearing the error and trying again always results in success. See screenshot below. What I can say is that it's only happening on 3.4rc1, never happened before on the other 3.4 betas, and is now regularly happening.
-
@oozebot I haven't observed any unexpected network errors on my machine. Can you please check the JS console or the network tab (both acccessible via F12) for potential errors?
Duet software engineer
-
@chrishamm - yes, many errors. I'll see if I can figure out how to export this if you think it would be helpful.
-
@chrishamm FYI - the error counter for app.79c76c3a.js is just constantly increasing..
-
@oozeBot Thanks.
- HTTP code 404 for rr_connect is nothing to worry about, it can be ignored
- HTTP code 503 and the WS errors mean DCS/DWS were not started, you'd have to check the popup to see why
- ERR_NAME_NOT_RESOLVED means that your browser cannot find the DNS/mDNS entry any more. Perhaps the machine rebooted?
- HTTP code 404 in the middle means the requested /sys/jobs/jobs folder wasn't found. Are you using M505?
- HTTP code 409 means the target folder/file for a move requests already exists
I'm going to fix the last few errors in 3.4-rc2.
-
@chrishamm Thanks. Here is a bit more info. I'll see what else I can capture if they keep occurring.
- The 503 errors were from a reboot earlier today
- The ERR_NAME_NOT_RESOLVED is curious as we haven't had any other DNS related issues
- The 404 (in the middle) is one of concern as that is one where it couldn't write a file I was editing, but did save just fine on a second try. No, we don't use M505
- The 409 was me testing to try to recreate the issue
