/
SA380 series Syslogs

SA380 series Syslogs

Nov 12, 2014

Introduction

SA380 series loggers write a journal about the most important internal activities like startup, shutdown, communication.

The syslog is the first place to look during debugging and investigation.

Where to find the Syslog

SA380

GUI

Go to Menu. View Data. Select the appropriate date. Select the dateLog.txt file.

Syslog will show up as text file:

Web interface

 

You have to have network access to the logger to do this. It can be achieved by connecting directly with an Ethernet cable, or connecting remotely through a network.

You need to have the IP address of the logger!

 

Enter the logger's IP address into your web browser:

You will be prompted to enter username/password:

You will be able to browse the data stored on the logger as a folder:

Navigate to the syslog file:

The folder belonging an actual date can have multiple digital log files and a syslog file. Select the dateLog.txt syslog file:

 

SA380TX

GUI

Similarly to SA380: Go to Menu. Go to Digital instead of Real-time system log! Press Show. Select system log and press Show.

Syslog has to show up:

Web interface

For the SA380TX logger you have to enter the IP address and have to specify the port as well:

You will be prompted for username/password. This and navigating to the actual syslog is the same as on the SA380.

Notice that each syslog lines are broken into two lines on the screen to be able to view most of the parameters.

SA380TX-L

dPanel

This assumes you have connection to the SA380TX-L logger either connected with a USB cable or you have network access to the logger through GPRS alternatively there can be Ethernet card installed.

First you have to select the right type of connection:

For USB cable connection, select USB:

 dPanel have to pick up the logger connected to the computer. Press Connect.

The connected logger will enumerate the information on the Real-time tab:

To get to the syslog, select Historic:

Select Syslog on the sub-tab:

 Normally it shows the last syslog entries retrieved from the logger. First time around it will be empty.

To simply retrieve the latest syslog, press Refresh data:

Web interface

SA380TX-L loggers with new version of firmware (version number?) have web-based configuration tool. The presence of the web tool can be checked with dPanel:

 On the real-time tab we get a valid WWW version, which indicates the web-tool is installed on the logger.

Enter the logger's IP address into your browser:

The web configuration tool needs javascript enabled in your browser.

Successful connection will show the loading screen first:

Once loaded it shows the current configuration of the logger:

Navigate to the syslog: Select Historic tab. 

Historic data normally shows the syslog by default. If not, select Syslog sub-tab:

WebCFG retrieves the latest syslog entries:

 

How to read the Syslog

Basics

Syslog

Description

Example

Syslog

Description

Example

System startup                  

First message after the logger boots.

System startup 1.5T444 29Oct14 serno=65532

System shutdown                 

Usually the last message in the syslog before the logger powers down or restart.

no parameters

Daily status                    

Available disk space on each disks.

Slave unit statuses.

GPRS and dialup status.

Daily status dsk1:374M dsk2:Miss dsk3:Miss Master:Y Slaves:NNNNNNN RasDial:Disconnected RasServe:Enabled

Disk failed or not present      

Internal or External disk. Internal disk is critical.

SA380 needs external disk when used as juridical logger.

 

Remote access heartbeat received

Remote client connected to the logger and retrieved site name and firmware version.

no parameters

Enabling RAS server             

Disabling RAS server            

Can be seen time-by-time in SA380 loggers to

make sure the RAS server is not hung up in call.

no parameters

The SA380TX-L logger has a few more messages worth including here.

Syslog

Description

Example

Syslog

Description

Example

Database started

Part of the normal startup. Version indicates data structure changes.

Database started Database File Manager version 0.2

Slave configured

Slave processor got configuration. Optional parameters show available digital and analogue channels.

Slave configured AnaMask=0x0003, DigMask=0x0000000F

Slave has started logging

Started the slave processor logging cycle. It is not logging during configuration phase.

no parameters

Errors

Syslog

Description

Example

Syslog

Description

Example

Thread stopped                  

Software failure or possible overload. (1)

thread=DiskLogger,state=8

Thread safety system restart    

Software failure or possible overload. (2)

no parameters

Unexpected disk removal         

Error: only for Internal

 

Battery level low at startup    

Flat battery; battery is not charging. Let the logger charge the battery for a few hours.

If the error still shows, send the logger back to MPEC for battery replacement.

2.9V

Event receiver overflow         

System is overloaded. (3)

 

Could not delete folder         

Happens during old file deletion. Usually indicates file system error.

Logger restart may fix it, if it happens because of clashing file access.

\usbdisk\www\days\20140817

Could not create file           

Important for SA380: must have external disk installed.

 

Modem command failed            

Serial port error; modem error. It is not an error during modem baud-rate detection!

Try to restart communication on the logger.

missing echo

M Tx File processing failed     

Slow comms (file has been removed since), file system error.

Logger had no connection to the server long enough to fill the message queue in the meantime.

Check in the syslog if the GPRS communication was lost for a long time.

Could not build:type:EBE tick:395137049463 seqno:0 count:1 file:\usbdisk\www\Days\20120910\ebierr\2012-09-10_MMM TX_0_0.txt

In case of system overload errors (1) (2) (3), it is a good idea to double-check the data collection settings. It is possible that the logger is collecting way too much data.

Acquire-on-change thresholds are the usual suspects. You may want to set the threshold higher.

GSM Modem

SA380TX

Syslog

Description

Example

Syslog

Description

Example

Modem power off                 

 

 

Modem power on                  

 

 

Modem command                   

AT commands

 

Modem command failed            

check "Modem command" to find what triggered the error

 

GSM signal strength at turn on  

 

 

Disconnecting RASdial           

Ending GPRS connection

 

RASdial disconnected            

Important for SA380: must have external

 

Creating RASdial entry          

Have to add a number to Windows phone book to be able to call it with RasDial

 

SIM registered to               

Tells the network

 

Could not reg. with GSM network 

International Mobile Subscriber Identity; International Mobile Station Equipment Identity

 

GSM IMSI/IMEI                   

International Mobile Subscriber Identity; International Mobile Station Equipment Identity

 

Dialling RASdial entry          

RasDial call; opening PPP connection; shows user,pass

 

RASdial connected               

RasDial succeded

 

RASdial error                   

err=Remote Access Error Code

err=691

New RASserve timeout            

RAS server started; timeout restarted

 

DCD inactive (call cleared down)

Modem data carrier line is down (connection lost)

 

Disabling RAS server            

RAS server stop

 

DCD active (call connected)     

TX2: Dialup has been called

 

RING received                   

Dialup during GPRS session

 

GPRS started                    

GPRS thread start

 

GPRS ended                      

GPRS thread end

 

Modem fallback wait             

Modem didn't manage to register to network, falling back for 1 hour

 

SA380TX-L

Syslog

Description

Example

Syslog

Description

Example

Network registration failed

 

 

Network operator

 

 

AT command

 

 

AT command failed

 

 

Modem OFF

 

 

Modem ON

 

 

Signal strength

 

 

PPP Connect

shows user, pass

 

PPP Connected

shows ip, gateway, dns servers

 

PPP Disconnect

 

 

PPP Disconnected

 

 

Modem error

baud rate not detected

 

Modem fallback for

 

 

Modem restart

Restart comms

 

MIMOSA push

SA380TX

Syslog

Description

Example

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