Log Management

The base system provides an RFC 5426 compliant syslog server at 198.18.2.1:514 (UDP). Collected logs are available via the ACU6 Device Manager Get Logs feature. Any application or logging framework that can send RFC 5426 UDP syslog messages to 198.18.2.1:514 will work.

Forwarding example using BusyBox syslogd

One way to forward logs to the base system syslog server is to use busybox syslogd. syslogd is included in the default BusyBox configuration used by the system.

Configure busybox syslogd with -L to keep a local copy of the logs and -R <ip> to forward logs to a remote receiver. The actia-syslog-config-examples demo package installs a ready-to-use /etc/default/syslogd file with forwarding pre-configured.

Run make menuconfig and navigate to External options -> ACU6 OH Demo Applications and enable ACTIA syslog base system forwarding example. Exit and save the configuration.

Retrieving Logs

Collected logs, including forwarded User VM syslogs, can be retrieved via the ACU6 Device Manager portal using the Get Logs action. See the ACU6 Device Manager documentation for details.

Local Encrypted Retrieval

Base system logs can also be fetched directly from the device as an encrypted bundle over a local TCP socket at 198.18.2.1:12357. The bundle is encrypted with an Actia-held key and can only be decrypted by Actia. The base system streams the bundle followed by a 32-byte SHA-256 trailer upon connection:

<encrypted bundle> || <SHA-256(encrypted bundle), 32 bytes>

Example

The actia-encrypted-logs-demo package is a minimal client for the local retrieval path. Enable it via make menuconfig → External options → ACU6 OH Demo Applications → actia-encrypted-logs-demo.

# encrypted-logs-demo -a 198.18.2.1 -p 12357
/tmp/acu6-logs-20260508-143022.bin
SHA-256 OK (2348112 bytes)
sha256: 3f9a...e21b