forked from stefanix/LasaurApp
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SYN flooding issue #20
Comments
Hallo Philip,
folgende Vermutung nach weiterer Diagnose gestern abend:
Die serielle Kommunikation zwischen Industrie-PC und Ardunio bleibt in einem synchronen Teil des Python-Scriptes hängen. Dadurch, dass das Python-Script der Webserver ist, können keine weiteren Verbindungen aufgebaut/entgegengenommen werden, es kommt dann mit weiteren unbeantworteten SYN-Paketen zu den SYN-Flood-Meldungen.
Ich hatte gestern abend als der Lasercutter nochmal hing, den Industrie-PC alleine restartet (Kabel vom Netzteil abgezogen), dann hat zwar wieder das Python-Script reagiert, Kommunikation über den COM-Port war jedoch immer noch nicht möglich. Das Python-Script hängt dann jedoch an einer anderen Stelle fest, und kann weiterlaufen.
Die Abbrüche kommen meist, wenn ein größerer Job mittels Pause unterbrochen wird, so auch wieder gestern bei Eduard.
Gruß
Wolfgang
…------
In Antwort auf die folgende Mail
From: Philip-Caroli <[email protected]>
To: fablab-ka/LasaurApp <[email protected]>
Cc: Subscribed <[email protected]>
Subject: [fablab-ka/LasaurApp] SYN flooding issue (#20)
Date: Mon, 14 Aug 2017 18:02:05 +0000 (UTC)
Shortly before lasaurapp-crash, these lines aer in the journalctl:
Aug 14 19:37:02 lasersaur run.sh[794]: ...............................................................................................................
Aug 14 19:38:34 lasersaur run.sh[794]: ...............................................................................................................
Aug 14 19:38:59 lasersaur kernel: TCP: request_sock_TCP: Possible SYN flooding on port 80. Sending cookies. Check SNMP counters.
Aug 14 19:39:34 lasersaur run.sh[794]: ...............................................................................................................
Aug 14 19:39:34 lasersaur systemd[1]: lasaurapp.service: Main process exited, code=exited, status=142/n/a
Aug 14 19:39:34 lasersaur systemd[1]: lasaurapp.service: Unit entered failed state.
Aug 14 19:39:34 lasersaur systemd[1]: lasaurapp.service: Failed with result 'exit-code'.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/fablab-ka/LasaurApp","title":"fablab-ka/LasaurApp","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/fablab-ka/LasaurApp"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"SYN flooding issue (#20)"}],"action":{"name":"View Issue","url":"#20"}}}
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Shortly before lasaurapp-crash, these lines aer in the journalctl:
Aug 14 19:37:02 lasersaur run.sh[794]: ...............................................................................................................
Aug 14 19:38:34 lasersaur run.sh[794]: ...............................................................................................................
Aug 14 19:38:59 lasersaur kernel: TCP: request_sock_TCP: Possible SYN flooding on port 80. Sending cookies. Check SNMP counters.
Aug 14 19:39:34 lasersaur run.sh[794]: ...............................................................................................................
Aug 14 19:39:34 lasersaur systemd[1]: lasaurapp.service: Main process exited, code=exited, status=142/n/a
Aug 14 19:39:34 lasersaur systemd[1]: lasaurapp.service: Unit entered failed state.
Aug 14 19:39:34 lasersaur systemd[1]: lasaurapp.service: Failed with result 'exit-code'.
The text was updated successfully, but these errors were encountered: