...
Syslog | Description | Example | |
---|---|---|---|
Mimosa client started | Thread started | ||
M My IP | IP change triggers MIMOSA disconnect-reconnect | ||
M Tx epRC Request bootstrap | |||
DNS response | |||
M Rx epRCr Bootstrap | only response parsed | ||
Mimosa connected to II | epRequestControl has been answered OK | ||
M Tx sNCf Send chan names | Important for SA380: must have external | ||
M Build Event | After 1.5 the logger only logs the fact that the message has been serialised. tick:ticktime interval, smp:number of samples in message,evt=number of events Events contain the samples. | time=2015-10-28T08:58:48.290Z,tick=1395864412451-1395864412500,smp=503,evt=50 | |
M Tx sNDE DAInt heartbeat | |||
M Tx sNDES DADataSeq | On old loggers (before 1.5) ch:channel name, n:number of samples, time, tick, ch1:channel name, off1:MIMOSA offset, id1:calculated MIMOSA ID | ch:TC 1 Sec 4 TF n:7 time:2014-04-08T00:24:13.250Z tick:64424673636 ch1:TC 1 Sec 4 TF off1:577 id1:4750341636673 | |
M Tx sNDES DAWaveform | On old loggers (before 1.5) | ch:2325A N-R n:352 time:2014-04-07T03:12:25.070Z tick:55834692254 ch1:2325A WI off1:68 id1:4750350352452 | |
M Rx HTTP 200-OK | On old loggers (before 1.5) | ||
No DNS response | h:hostname, t:timeout | h:sntp.corp.ukrail.net t:36s | |
M Tx Couldn\'t send data | send() failed | ||
M Tx Socket opening failed | invalid handle or connect() error | ||
M Tx Send failed - no conn | No bearer; Too many retries | ||
M My IP changed! | Triggers MIMOSA reconnect | ||
M Tx No bearer | No bearer; GPRS down, eth: no IP address | ||
M Rx No response from core sys | |||
M Rx HTTP error | Logger stores the failed messages in mimosa/mimlog.txt | 503-Service Unavailable | |
M Tx Fallback for | retry in given time | ||
M Tx File processing failed | |||
M Rx Error processing | epRequestControl response parsing error | ||
Mimosa disconnected from II | Probably easiest to look for this and then trying to find the root cause. | ||
Mimosa client ended |
...