Web- Service restart on changeView #66
Comments
|
Please provide more logs |
|
I have run the log through a GREP. Does it fit like this? |
|
Can you please check log again and post the full error around that
I think the grep hides the relevant stuff here |
|
No problem. |
|
Ok, a bit mroe but not thaaaaat helpful
|
|
could be connected to http-party/node-http-proxy#579 |
|
Is there anything else I can do to help solve this? |
|
maybe also connected to chimurai/http-proxy-middleware#476 ... @n3roGit notreally ... its not that easy ... |
|
maybe try tonot to load the image thaaaat ofen ? Logs tells you load that file ever 20ms! |
|
Okay but thanks anyway for the quick response! Which file do you mean exactly? |
|
@n3roGit Please try GitHub version ... I tried to add an error handler for a socket ... Version stays same for now, so manually restart web after update please. If an error happens now it should be logged only (info loglevel). In fact the error seems to happen when the server whichis conacted by the proxy is resetting the connection while proxy still reads. See your log "/picture/2/current/" is requested every 20ms ... maybe thats too much for the target server. |
|
Thanks a lot!! I will test that right away! The images come from the slideshow adapter. This is as far as I know still beta. I will deactivate the times and test it. |
|
No leave that high frequenc for the test :-))) Iexpect it will more easy hit when high frequency calls ... |
|
BTW: Grep for "[proxy] Socket Error for" to see if that hit ... (if it does not crash) |
|
I was able to reproduce the problem directly. Unfortunately I don't see an entry with "[proxy] Socket Error for". |
|
Ok, erstmal sicherstellen das es auch die neue Verison ist :-))) Und Du hast web neu gestartet nach der Installation ??? |
|
Log steht auf INFO. |
|
Schade :-( Versuch nochmal neue Github, obwohl ist nicht glaube das es helfen wird |
|
Mist! Montag kann ich die nochmal ziehen und das testen. Ich werde berichten :) |
|
kein stress |
|
Hier das Log mit der aktuellen Github Version: ` 2022-01-25 11:18:24.424 - info: javascript.0 (1892168) script.js.System.z_OLD.Zauberwürfel: Würfel ist gesperrt!!! ` |
|
:-( The the question is why it happens :-( |
|
I told you that I could not really see anything in the log ... :( |
|
All good ... in fact it seems that the system where the request goes to is resetting the connection here and there and this triggers an uncatchable exception on such a proxied connection inside the used proxy library ... so in fact you can really try to reduce the "Number of requests" that they are maybe not done any 20ms .. maybe it is simply "too much" for the device |
|
I have deactivated the slideshow now. It seems to help. Time will tell! Thanks to you! |
|
Ok, maybe really try to lower the frequency |
|
I have now played around a bit. I think it is because of the iFrame from Motioneye. There the video is streamed with 15FPS. I will test it times to 2FPS reduce and keep an eye on. In itself, my server here is more than potent enough to cope with this load. |
|
The "Problem" is that this error is thrown by the used proxy library. in fact somehow the connection gets closed unexpectedly which reading data ... |
|
Unfortunately, I can not get the problem under control. I have reduced the frame rate to 5 FPS and set up a separate web service for each tablet, but the web service still runs in the restart loop. I am really with my Latin at the end. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. |
|
This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions. |
Good day,
I have the phenomenon that my web.1 adapter restarts constantly when I trigger a changeView via script.
After some searching, I strongly suspect that the problem is related to the proxy adapter.
If this is not the case, I am happy to be proven wrong. Maybe you have another idea.
As soon as this is active, the web.1 adapter hangs and restarts often.
I can see the following message in the log:
`
My configuration and versions are as follows:
I recently updated the web adapter from the stabel to the latest available, hoping to fix the problem. Unfortunately, there was no improvement at all.
The text was updated successfully, but these errors were encountered: