-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
armbianmonitor -u
: rationalize paste server retrying, use ANSI dmesg
#6836
armbianmonitor -u
: rationalize paste server retrying, use ANSI dmesg
#6836
Conversation
…se statement - `b` and `B` were never parsed - an `*` case is added to handle invalid options
- use PIPESTATUS to check all steps for failure - avoid blaming paste server if data collection failed
Looping through paste servers doesn't seem to work. At least it doesn't catch the current error to try the next server. |
Could you share logs? (eg from Here I've a machine with a network misconfiguration, and that loops over both servers (and both fail "correctly") so wondering what could it be. |
"Unfortunately" TheLinuxBug fixed the error (disk ran out of space) before thinking about grabbing such logs and now cannot test anymore. Apologize |
Hmm, in this case the bug is probably on the server side -- it should reply with a 500-level HTTP code, which would cause curl to "correctly" fail and the script to try the next server. |
Hmm, the server seems to at least try to spit out 500 error when this problem occurs: https://github.com/rpardini/ansi-hastebin/blob/fefe5edda54f5cafc113554a3a28d93cb5a9b013/lib/document_handler.js#L161-L162 Seems that |
armbianmonitor
-u
: rationalize paste server retrying, use ANSI dmesgb
andB
were never parsed*
case is added to handle invalid options-u
: rationalize paste server retrying, use ANSI dmesg