Cura: [4.6.1] Monitor print status not updated, S3, network

[C-Seebacher]

Application version
4.6.1

Platform
Win10

Printer
Ultomahe S3, LAN

Reproduction steps
After a while teh monitor starts is not updated any more. Web interface is ok

Screenshot(s)

Web interface is OK. Cura Monitor stopped working.

Actual results
Progress bar halted, moitor tab shows not updates any more

[rburema]

Could you attach the logs? The template is quite clear on that, and I think they could be of help in this case.

The log can be found in the user folder (see here for details on how to access those) or you can click on 'show configuration folder' in the help menu within Cura itself.

[C-Seebacher]

Hi Remco, her is the logfile. Sorry quite large. Problem should be in there more than once.

Is that the correct reply? I am not so familiar with github.
Best Regards,
Christian

Am 12.06.2020 um 09:34 schrieb Remco Burema:
>

Could you attach the logs? The template is quite clear on that, and I think they could be of help in this case.

The log can be found in the user folder (see here
https://github.com/Ultimaker/Cura/wiki/Cura-Preferences-and-Settings-Locations for details on how to access those)
or you can click on 'show configuration folder' in the help menu within Cura itself.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Ultimaker/Cura/issues/7914#issuecomment-643120002, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADTMLDU5HU5XPCQM2SHPBA3RWHK7RANCNFSM4N2TIEOQ.

>

Dr. Christian Seebacher
TILL I.D. GmbH
Am Klopferspitz 19a
82152 Martinsried
Tel [phone]
Geschäftsführer: Dr. Rainer Uhl
HRB 129399 Amtsgericht München
USt.-IdNr. DE 205045721

[fieldOfView]

Is that the correct reply?

Unfortunately, no. Though you can send in answers via email, all attachments are scrubbed. Please use the github.com webinterface to post files, or insert a link to the file you meant to attach (eg via dropbox, google drive, etc).

[C-Seebacher]

Ok her is log

cura.zip

[rburema]

Thank you.

Hm, it seems Cura has problems contacting the printer:

Error transferring http://192.168.1.96/cluster-api/v1/printers - server replied: Gateway Time-out
Error transferring http://192.168.1.96/cluster-api/v1/materials - server replied: Gateway Time-out
Error transferring http://192.168.1.96/cluster-api/v1/print_jobs - server replied: Gateway Time-out
Error transferring http://192.168.1.96/cluster-api/v1/printers - server replied: Gateway Time-out
Error transferring http://192.168.1.96/cluster-api/v1/print_jobs - server replied: Gateway Time-out
Error transferring http://192.168.1.96/cluster-api/v1/printers - server replied: Gateway Time-out
Error transferring http://192.168.1.96/cluster-api/v1/print_jobs - server replied: SERVICE UNAVAILABLE
Error transferring http://192.168.1.96/cluster-api/v1/printers - server replied: SERVICE UNAVAILABLE
Error transferring http://192.168.1.96/cluster-api/v1/printers - server replied: SERVICE UNAVAILABLE
Error transferring http://192.168.1.96/cluster-api/v1/print_jobs - server replied: SERVICE UNAVAILABLE
Error transferring http://192.168.1.96/cluster-api/v1/print_jobs - server replied: SERVICE UNAVAILABLE

But that doesn't explain why the web-interface _is_ able to contact the service. I'll discuss it with the team next week.

In the meantime, maybe @ChrisTerBeke has any ideas?

[ChrisTerBeke]

The APIs on the printer give timeouts if the printer is too busy doing other stuff (like printing, or handling other requests). The API process has a lower priority to prevent printing quality issues. To fully debug this, we'd also need the logs from the printer itself.

[no-response[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.