display logging

Purpose

Displays contents of the event log. This log records events throughout the Digi device’s system, such as:

Starting or resetting the Digi device
Configuring features
Critical actions performed by various interfaces and subsystems
Starting applications and other important events.

Many but not all Digi devices have the event log feature. The event log is always enabled and is not user-configurable. When the Digi device operates in an unexpected manner, you can send the log entries to Digi for analysis by Technical Support and Engineers. The event log cannot be turned off, so that Digi receives an accurate view of all aspects of the operation of the device. Command options control how much or which portion of the event log is displayed, and clear the event log.

The event log is a 64KB circular buffer that can contain a varying number of log entries. A log entry can have a maximum number of bytes per entry. Based upon the size of the entries, the number of entries kept in the log varies. When the log “overflows,” the oldest entries are overwritten with new ones, so the history is incomplete.

The event log is maintained in RAM, and there is no history across reboots of the device. Logging is always on, and there is no way for a user to enable/disable, adjust what is logged, or adjust the level of detail.

Required permissions

For Digi products with two or more users, permissions must be set to set permissions display=execute to use this command. See set permissions for details on setting user permissions for commands.

Syntax

display logging [action={clear|display}]
  [head=lines]
  [tail=lines]

display logging [options...]

Where:

options:
    [action={clear|display}]

Options to display the full event log (action=display):

    [timeformat={auto|datetime|raw|uptime}

Options to display a portion of the event log:

    [head=lines]
    [tail=lines]

Options

action={clear|display}

Perform an action on the event log.

clear

Clears the event log.

display

Displays the full event log

The default is display.

timeformat={auto|datetime|raw|uptime}

The format for displaying time in event log messages.

auto

Automatically select the time format (default).

datetime

Display time in a date/time format of YYYY-MM-DD hh:mm:. For example

2008-08-23 09:26:51

raw

Display time as a raw value: show the time as an integer number of seconds.

uptime

Display time in an uptime format: +N days hh:mm:ss. For example:

+2 days 13:06:32

head=lines

Displays the first lines of the event log, that is, the oldest lines. The lines value must be 1 or more.

tail=lines

Displays the last lines of the event log; that is, the most recent lines. The lines value must be 1 or more.

The lines value can be followed by a + character to request that the last lines event log entries be displayed, after which the command waits for and display new event log messages as they are added to the log, in other words, continue tailing the log. Enter Ctrl+C to end the command.

For example, appending a + to the tail option value displays the last 10 lines of the log, after which the Digi device continues waiting for and displaying, new log entries as they arrive.

#> display logging tail=10+
>>> Tailing the event log (Ctrl-C to cancel)...
2011-10-24 18:19:40 mobile     Mobile CID changed to 14349 from 14343.  MCC: 310 MNC: 410
2011-10-24 18:19:42 mobile     RSSI: -102 dBm
2011-10-24 18:19:46 mobile     RSSI: -98 dBm
2011-10-24 18:20:04 mobile     RSSI: -94 dBm
2011-10-24 18:20:25 mobile     RSSI: -83 dBm
2011-10-24 18:20:28 mobile     RSSI: -98 dBm
2011-10-24 18:20:31 mobile     Mobile CID changed to 14343 from 14349.  MCC: 310 MNC: 410
2011-10-24 18:20:31 mobile     RSSI: -84 dBm
2011-10-24 18:20:57 mobile     Mobile CID changed to 14349 from 14343.  MCC: 310 MNC: 410
2011-10-24 18:20:57 mobile     RSSI: -99 dBm
>>> Tail canceled.
2011-10-24 18:21:15            [End of Event Log at +3 days 02:27:07]

Entering CTRL+C to cancel the continuous tail. The last two lines are output. This is similar to ending a ping.

Examples

Display the event log

#> display logging

2011-10-04 18:06:41 boot       Unit started.
2011-10-04 18:06:41 time       RTC initialized: Tue Oct  4 18:06:41 2011.
2011-10-04 18:06:41 time       Applying system time adjustment threshold of 60 seconds.
2011-10-04 18:06:41 time       Lost time source recovery is enabled.
2011-10-04 18:06:41 system     Product: ConnectPort X4 (ID 0x0085).
2011-10-04 18:06:41 system     Firmware Version: 2.14.1 (Version Skipjack 07/14/
2011 02:43:01 CDT).
2011-10-04 18:06:41 system     Boot Version: 1.1.3 (release_82001975_C).
2011-10-04 18:06:41 system     Post Version: 1.1.3 (release_82001753_D).
2011-10-04 18:06:41 system     Product VPD Version: release_82002010_B.
2011-10-04 18:06:41 system     Hardware Strapping: 0x0044.
2011-10-04 18:06:41 failover   Failover feature is started.
2011-10-04 18:06:41 failover   Failover state is OFF, fallback is ON.
2011-10-04 18:06:41 dnsproxy   DNS Proxy start-up succeeded.
2011-10-04 18:06:41 failover   Link testing for "eth0" is ON.
2011-10-04 18:06:41 system     Network Port Scan Cloak feature is enabled.
2011-10-04 18:06:41 dcloud     Device ID: 00000000-00000000-00409DFF-FF492A01
2011-10-04 18:06:41 dcloud     Vendor ID: 0xFE000000
2011-10-04 18:06:41 dcloud     Device Type: ConnectPort X4
2011-10-04 18:06:42 time       Jump to new baseline at uptime 1 (src 5, rank 50,
delta 1317751601).
2011-10-04 18:06:42 mesh       Radio version: HW 0x1a41 FW 0x3128
2011-10-04 18:06:47 failover   Interface "eth0" status is now 4 (down).
2011-10-04 18:06:47 failover   Interface "eth0" status is now 2 (up).
2011-10-04 18:06:49 dcloud     Starting device-initiated connection.
2011-10-04 18:06:49 dcloud     Finding Service, URL=en://login.etherios.com
2011-10-04 18:06:49 dcloud     Trying TCP.
2011-10-04 18:06:49 dcloud     Connected at socket level: Local=10.8.16.111:4813
3 Remote=50.56.41.153:3197.
2011-10-04 18:06:49 dcloud     Keep-alive parameters are: RX=60 TX=60 wait=3.
2011-10-04 18:06:49 dcloud     Connected Using TCP.
2011-10-05 15:50:46 dcloud     Error 116 on TCP socket read.
2011-10-05 15:50:46 dcloud     Disconnected from server.
2011-10-05 15:50:46 dcloud     Device-initiated connection failed, return=-6
2011-10-05 15:50:46 dcloud     Connection Error: Connection to Server Closed.
2011-10-05 15:50:46 dcloud     Will reconnect to server in 10 seconds.
2011-10-05 15:50:56 dcloud     Starting device-initiated connection.
2011-10-05 15:50:56 dcloud     Finding Service, URL=en://login.etherios.com
2011-10-05 15:50:56 dcloud     Trying TCP.
2011-10-05 15:51:05 dcloud     Connected at socket level: Local=10.8.16.111:3809
3 Remote=50.56.41.153:3197.
2011-10-05 15:51:05 dcloud     Keep-alive parameters are: RX=60 TX=60 wait=3.
2011-10-05 15:52:48 dcloud     Connected Using TCP.
2011-10-21 15:17:42 time       Jump to new baseline at uptime 1458721 (src 5, rank 50, 
delta -60).
2011-10-21 23:11:32            [End of Event Log at +17 days 05:05:51]

Display the last ten lines from the event log

#> display logging tail=10

1970-01-01 00:00:08 dhcpserver No scopes/interfaces started successfully.
1970-01-01 00:00:08 dhcpserver Stopping DHCP Server.
1970-01-01 00:00:08 dhcpserver DHCP Server stopped.
1970-01-01 00:00:10 mobile     Module reset (type 25: Sierra Wireless MC87X5).
1970-01-01 00:00:10 mesh       Radio version: HW 0x1941 FW 0x2141
1970-01-01 00:00:24 mobile     Radio temperature: 33 (C)
1970-01-01 00:00:24 mobile     Mobile LAC changed to 0 from -1.  Country: 0, Network:
1970-01-01 00:00:24 mobile     Mobile CID changed to 0 from -1.  Country: 0, Network:
1970-01-01 00:00:24 mobile     SIM Status changed to SIM removed (2) from SIM OK (0)
1970-01-01 00:01:02 mobile     RSSI: -110 dBm
1970-01-02 06:44:14            [End of Event Log]

Clear the event log

#> display logging action=clear