Part Number: EVMK2H
Tool/software: Linux
I am running Processor SDK 3.02.00.05 on several EVMK2H boards with the pre-built kernel and user-space images from the installation kit. On all of these boards, the syslog facility does not start correctly. During Linux boot, the following messages are seen on the serial console:
[ 5.632875] systemd[1]: System time before build time, advancing clock.
[ 5.690054] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
[ 5.718433] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
[ 5.729272] systemd[1]: systemd 229 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
[ 5.748235] systemd[1]: Detected architecture arm.
Welcome to Arago 2016.10!
[ 5.777451] systemd[1]: Set hostname to <k2hk-evm>.
[ 5.914145] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
[ 5.946962] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
[ 5.973486] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
[ 6.046693] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
[ 6.114093] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
[ 6.123479] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
[ 6.133051] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
[ 6.192453] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
[ 6.285763] systemd[1]: [/lib/systemd/system/syslog-ng.service:6] Executable path is not absolute, ignoring: @SBINDIR@/syslog-ng -F -p @LOCALSTATEDIR@/run/syslogd.pid
[ 6.300713] systemd[1]: [/lib/systemd/system/syslog-ng.service:7] Executable path is not absolute, ignoring: @BASEBINDIR@/kill -HUP $MAINPID
[ 6.313593] systemd[1]: syslog-ng.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
[ 6.410777] systemd[1]: syslog-ng.service: Cannot add dependency job, ignoring: Unit syslog-ng.service is not loaded properly: Invalid argument.
[ 6.433003] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ 6.466471] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Started Dispatch Password Requests to Console Directory Watch.
[ 6.495740] systemd[1]: Reached target Remote File Systems.
[ OK ] Reached target Remote File Systems.
[ 6.525902] systemd[1]: Listening on Network Service Netlink Socket.
[ OK ] Listening on Network Service Netlink Socket.
[ 6.558181] systemd[1]: Created slice User and Session Slice.
[ OK ] Created slice User and Session Slice.
[ 6.585837] systemd[1]: Listening on udev Control Socket.
[ OK ] Listening on udev Control Socket.
[ 6.615845] systemd[1]: Listening on Journal Socket.
[ OK ] Listening on Journal Socket.
[ 6.635741] systemd[1]: Reached target Swap.
[ OK ] Reached target Swap.
[ 6.655774] systemd[1]: Listening on udev Kernel Socket.
[ OK ] Listening on udev Kernel Socket.
[ 6.685720] systemd[1]: syslog.socket: Socket service syslog-ng.service not loaded, refusing.
[ 6.694293] systemd[1]: Failed to listen on Syslog Socket.
[FAILED] Failed to listen on Syslog Socket.
See 'systemctl status syslog.socket' for details.
[ 6.735854] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
Running that "systemctl status syslog.socket" command after logging in:
��● syslog.socket - Syslog Socket
Loaded: loaded (/lib/systemd/system/syslog.socket; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd.special(7)
www.freedesktop.org/.../syslog
Listen: /run/systemd/journal/syslog (Datagram)
What needs to be changed to get a working syslog?
Thanks
Steve Williams
