web died after successful print

arhi

@JoergS5 said in web died after successful print:

One possibility is to set a higher debug level for analyzing, but I have not done it yet, so I cannot help how to do it in detail. One can set debug levels for specific modules.

It's not a problem to add additional debug levels but the problem is that I can't reproduce this easily. last two times it happened I added debug + usb but could not reproduce the problem.

JoergS5

@arhi you could try a keep alive program (etc....)

(wrong thought Maybe the httpsessions were full (8 of 8 used) removed)

JoergS5

@arhi what is interesting is that the data cache hit count. Cache data hit count 4294967295 is exactly 32 bit unsigned, maybe reached an upper limit.

arhi

@JoergS5 said in web died after successful print:

@arhi you could try a keep alive program to check whether it is a disconnect problem after long inactivity.

It is not. The long inactivity was before the print, web opened ok and during the print there was activity and it stopped working immediately after the print finished. So no "timeout" to speak of.

You could check M122 before crash, maybe the httpsessions were full (8 of 8 used).

If I can reproduce the problem on demand it would make sense but I can't. All three times it happened the printer was not in use for 3-4 days.

Where do you see 8 out of 8 ?!?!

Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8

??

Do you use additional programs to access the Duet, like monitoring programs, which may use connections?

No program other than web accessed duet in the times the problem happened (normally I do but the rpi4 that host those programs is of-line these days so, no)

JoergS5

@arhi said in web died after successful print:

Where do you see 8 out of 8 ?!?!

Please ignore, this was wrong.

One thing to check is wipe.g

bot

@arhi said in web died after successful print:

[...}
No program other than web accessed duet in the times the problem happened [...]

This got me thinking. What if there is some ping or other mechanism sent to the Duet automatically by some system on your network.

I wonder if mDNS is playing a role. It was disabled on legacy Duets for similar reason.

From the RRF2 Whats_new doc:

[...}

Disabled mdns in legacy Duets because of code quality issues causing reboots, https://forum.duet3d.com/topic/8352/duet-0-6-randomly-reboots/5

[...}

arhi

@JoergS5 the wipe has nothing to do with it but here it is

if !move.axes[0].homed || !move.axes[1].homed 
  echo "X and Y axes not homed, aborting the wipe"
  M99

if state.currentTool < 0
  echo "No tool loaded, aborting the wipe"
  M99

if heat.heaters[tools[state.currentTool].heaters[0]].current < 200
  echo "Extruder too cold, no point wiping, aborting the wipe"
  M99

; Drop all motor currents down
M400
M913 X30 Y30 Z25

M83 

; -135,       -116,             115,   125,
;     ,104....++++++++++++++++++++++....
;         ....++++++++++++++++++++++....
;         ....++++++++++++++++++++++....
;         ....++++++++++++++++++++++....
;     ,63 ..|.++++++++++++++++++++++....
;         ..|.++++++++++++++++++++++....
;         ..|.++++++++++++++++++++++....
;     ,30 ..|.++++++++++++++++++++++....
;         ....++++++++++++++++++++++....
;         ....++++++++++++++++++++++....
;         ....++++++++++++++++++++++....
;    ,-112....++++++++++++++++++++++....
;         ..............................
;         ..............................
;    ,-121..............................


G0 X-115 Y65  F9000

while true
  G0 X-135 Y{65 - iterations * 3} F7000 
  G0 X-115 Y{65 - iterations * 4} F5000
  if iterations == 6
    G1 E-3 F3000
  if iterations == 8
    break

M98 P"park.g"

; Return all motor currents to 100%
M400
M913 X100 Y100 Z100

and the park is

; drop motor curents
M913 X30 Y30 Z25
; go to park position

G0 X-135 Y40 

; restore motor curents
M913 X100 Y100 Z100

as I said, the code itself works ok.. and after everything is finished paneldue and usb work ok, just web is dead

arhi

@bot said in web died after successful print:

@arhi said in web died after successful print:

[...}
No program other than web accessed duet in the times the problem happened [...]

This got me thinking. What if there is some ping or other mechanism sent to the Duet automatically by some system on your network.

But web itself is pinging it non stop (fetching the model json, displaying temperature etc etc)

I wonder if mDNS is playing a role. It was disabled on legacy Duets for similar reason.

dunno, I don't use mDNS as I had issues with it on windows so my router is configured to add entry to local dns to .local.lan or .local.wifi for all dhcp leases so I use ender5.local.lan to access it so local dns, not using mdns at all

Disabled mdns in legacy Duets because of code quality issues causing reboots, https://forum.duet3d.com/topic/8352/duet-0-6-randomly-reboots/5

yeah but no reboot here, the duet runs ok, this time the web died after the print but usb/paneldue worked ok, last time web died in the middle of the print but print finished ok, paneldue was ok, I just could not connect using web.... I was running later on with debug on for few modules but could not reproduce the problem, today it happened again, the only similarity, the printer was idle for few days (not printing, but I did access it via web to check in some config details etc.. and basically the tab with dwc was open most of the time)

JoergS5

@arhi Error 10 Could be that you have a recursion somewhere.

Error 10 is an addition of 0x02 and 0x08 according to
https://duet3d.dozuki.com/Wiki/Error_codes_and_software_reset_codes

arhi

@JoergS5 said in web died after successful print:

@arhi Could be that you have a recursion somewhere

In that case, it would die much faster; but no, no recursion here. I do call same file from multiple places but never recursive

JoergS5

(deleted, not relevant)

arhi

@JoergS5 said in web died after successful print:

@arhi but some overflow is the reset reason of your last reset. Maybe the cash overflow above, or another overflow. For overflow reasons, I only found the recursion as a cause, but maybe you're first for your overflow reason.

Well, the board did not reset! As I wrote, only the HTTP module or NET module died (did not restart, stayed dead), everything else continued to work ok as nothing happens, continued printing, parsing g-code...

JoergS5

@arhi The M122 reset reason is the reason of the reset 131 hours ago. The error 10 could be related to this access error.

arhi

@JoergS5 yup, that M122 happened before the ~130 hours of inactivity

JoergS5

This post is deleted!

arhi

here it comes again, ~12 hours of inactivity, dead 5 minutes after the print finished ?!?!

JoergS5

@arhi what is the M122 please?

arhi

@JoergS5 I didn't do M122 I just rebooted it, turned on debugging on net, web and few others turned on logging on serial port and let it run so it catches log if it happens again as even dc42 did not find anything useful in the m122 last time so .. collecting debug data now

JoergS5

@arhi ok, hope you find something. Good luck!

arhi

@JoergS5 said in web died after successful print:

@arhi ok, hope you find something. Good luck!

I'm not turning the darn debug off till the darn thing dies again so we'll see ..