[INSTRM-497] Bot reported a false alarm "no data" Created: 26/Sep/18 Updated: 26/Sep/18 Resolved: 26/Sep/18 |
|
| Status: | Won't Fix |
| Project: | Instrument control development |
| Component/s: | ics_sps_engineering_JabberBot |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Normal |
| Reporter: | fmadec | Assignee: | arnaud.lefur |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | SM1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
This night (around 23:30 french time) bot sent an alarm "no data" while there was no problem, at least a all command was sending up to date data. It was not possible to acknoledge this alarm, I had to reboot the bot to stop the alarm...
|
| Comments |
| Comment by arnaud.lefur [ 26/Sep/18 ] |
|
I don't think it's a fake alarm. I would guess that one of the keywords that we are checking for the alarms has generated a nan value. Basically, I'm checking the last value, so the sql request must return something because the table exist. But since i'm dropping the nan, it's possible to end up with ValueError('no data') been raised. Anyhow, I've tagged a new version which raise exceptions with a message a bit more specific.
|
| Comment by arnaud.lefur [ 26/Sep/18 ] |
|
it was a nan indeed ! 2018-09-25 21:23:55.662Z cmds 20 CommandLink.py:121 > 1 463929 d text="ionpump sending b'\x02\x818320\x038B'" 2018-09-25 21:23:56.708Z cmds 20 CommandLink.py:121 > 1 463929 w text="failed to create connect or send to ion pump: timed out" 2018-09-25 21:23:57.030Z cmds 20 CommandLink.py:121 > 1 463929 i ionPump1=1,7000,7.5e-05,43, nan |