How to add the syslog in /var/log

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to add the syslog in /var/log

3,608 Views
Chethan
Contributor III

Hi,

I am using LS1046ardb board for one of project. In that I am using yocto root file system but in that /var/log/message it has only some log data but I want all kernel logs and other logs,

Please help me out off this problem.

and my /var/log/message output

root@DevelLinux:/var/log# cat messages
Oct 6 16:30:26 DevelLinux syslog.info syslogd started: BusyBox v1.31.0
Oct 6 16:30:26 DevelLinux user.err ecryptfsd: main: Current kernel does not have support for /dev/ecryptfs; please use 2.6.26 or newer
Oct 6 16:30:27 DevelLinux daemon.info avahi-daemon[4020]: Found user 'avahi' (UID 998) and group 'avahi' (GID 998).
Oct 6 16:30:27 DevelLinux daemon.info avahi-daemon[4020]: Successfully dropped root privileges.
Oct 6 16:30:27 DevelLinux daemon.info avahi-daemon[4020]: avahi-daemon 0.7 starting up.
Oct 6 16:30:27 DevelLinux daemon.info avahi-daemon[4020]: Successfully called chroot().
Oct 6 16:30:27 DevelLinux daemon.info avahi-daemon[4020]: Successfully dropped remaining capabilities.
Oct 6 16:30:27 DevelLinux daemon.info avahi-daemon[4020]: No service file found in /etc/avahi/services.
Oct 6 16:30:27 DevelLinux daemon.info avahi-daemon[4020]: Network interface enumeration completed.
Oct 6 16:30:27 DevelLinux daemon.info avahi-daemon[4020]: Server startup complete. Host name is DevelLinux.local. Local service cookie is 468629823.
Oct 6 16:30:27 DevelLinux daemon.notice rpc.statd[4021]: Version 2.3.4 starting
Oct 6 16:30:27 DevelLinux daemon.warn rpc.statd[4021]: Flags: No-Daemon TI-RPC
Oct 6 16:30:27 DevelLinux daemon.warn rpc.statd[4021]: Running as root. chown /var/lib/nfs/statd to choose different user
Oct 6 16:30:36 DevelLinux authpriv.notice login[3996]: ROOT LOGIN on '/dev/ttyS0' "

Thanks & Regards,

Chethan GR.

Labels (1)
0 Kudos
Reply
8 Replies

3,587 Views
yipingwang
NXP TechSupport
NXP TechSupport

Which Yocto SDK release do you use?

I downloaded NXP Yocto 3.1 release from https://source.codeaurora.org/external/qoriq/qoriq-components/yocto-sdk/tree/readme?h=dunfell, built images for LS1046ARDB.

On the target board, I checked /var/log/messages, it contains Kernel logs as the following.

Aug 3 13:06:17 ls1046ardb syslogd[1169]: syslogd v2.1.1: restart.
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd082]
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] Linux version 5.4.3+g134788b16485 (oe-user@oe-host) (gcc vers
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] Machine model: LS1046A RDB Board
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] efi: Getting EFI parameters from FDT:
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] efi: UEFI not found.
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] OF: reserved mem: initialized node qman-fqd, compatible id fs
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] OF: reserved mem: initialized node qman-pfdr, compatible id f
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] OF: reserved mem: initialized node bman-fbpr, compatible id f
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] cma: Reserved 320 MiB at 0x00000000e7c00000
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] NUMA: No NUMA configuration found
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] NUMA: Faking a node at [mem 0x0000000080000000-0x0000000bff7f
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] NUMA: NODE_DATA [mem 0xbfa804800-0xbfa805fff]
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] Zone ranges:
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] DMA32 [mem 0x0000000080000000-0x00000000ffffffff]
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] Normal [mem 0x0000000100000000-0x0000000bff7fffff]
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] Movable zone start for each node
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] Early memory node ranges
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] node 0: [mem 0x0000000080000000-0x00000000fbdfffff]
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] node 0: [mem 0x0000000880000000-0x0000000bfbffffff]
Aug 3 13:06:17 ls1046ardb kernel: [ 0.000000] node 0: [mem 0x0000000bff000000-0x0000000bff7fffff]

 

On the target board, please check /etc/syslog.conf whether it contains the following configuration.

*.=info;*.=notice;*.=warn;\
auth,authpriv.none;\
cron,daemon.none;\
mail,news.none -/var/log/messages

0 Kudos
Reply

3,581 Views
Chethan
Contributor III

Hi,

My Yocto version and details is 

/conf/distro$ cat poky.conf
DISTRO = "poky"
DISTRO_NAME = "Poky (Yocto Project Reference Distro)"
DISTRO_VERSION = "3.0.4"
DISTRO_CODENAME = "zeus"
SDK_VENDOR = "-pokysdk"

But after changing the above steppes in /etc/syslog.conf still its same only

Thanks & Regards,

Chethan GR. 

0 Kudos
Reply

3,575 Views
yipingwang
NXP TechSupport
NXP TechSupport

Would you please download NXP Yocto 3.0 release(zeus) from https://source.codeaurora.org/external/qoriq/qoriq-components/yocto-sdk/tree/readme?h=zeus

I checked the rootfs filesystem built from this release, file /var/log/messages contains Linux Kernel information.

0 Kudos
Reply

3,572 Views
Chethan
Contributor III

Hi,

How I can build yocto roof file system from flex-build using that link?

Thanks & Regards,

Chethan GR.

0 Kudos
Reply

3,566 Views
yipingwang
NXP TechSupport
NXP TechSupport

I checked LSDK 20.12 pre-built image lsdk2012_yocto_tiny_LS_arm64.itb.

File /var/log/messages contains Kernel information as the following.

Aug 3 15:09:20 TinyLinux syslog.info syslogd started: BusyBox v1.31.0
Aug 3 15:09:20 TinyLinux user.notice kernel: klogd started: BusyBox v1.31.0 (2020-09-17 08:00:32 UTC)
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd0
Aug 3 15:09:20 TinyLinux user.notice kernel: [ 0.000000] Linux version 5.4.47 (jenkins@saturn) (gcc version
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] Machine model: LS1046A RDB Board
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] efi: Getting EFI parameters from FDT:
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] efi: UEFI not found.
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] OF: reserved mem: initialized node qman-fqd, compati
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] OF: reserved mem: initialized node qman-pfdr, compat
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] OF: reserved mem: initialized node bman-fbpr, compat
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] cma: Reserved 320 MiB at 0x00000000e7c00000
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] NUMA: No NUMA configuration found
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] NUMA: Faking a node at [mem 0x0000000080000000-0x000
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] NUMA: NODE_DATA [mem 0xbfa803800-0xbfa804fff]
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] Zone ranges:
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] DMA32 [mem 0x0000000080000000-0x00000000fffffff
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] Normal [mem 0x0000000100000000-0x0000000bff7ffff
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] Movable zone start for each node
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] Early memory node ranges
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] node 0: [mem 0x0000000080000000-0x00000000fbdfff
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] node 0: [mem 0x0000000880000000-0x0000000bfbffff
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] node 0: [mem 0x0000000bff000000-0x0000000bff7fff
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000
Aug 3 15:09:20 TinyLinux user.debug kernel: [ 0.000000] On node 0 totalpages: 4163072
Aug 3 15:09:20 TinyLinux user.debug kernel: [ 0.000000] DMA32 zone: 8192 pages used for memmap
Aug 3 15:09:20 TinyLinux user.debug kernel: [ 0.000000] DMA32 zone: 0 pages reserved
Aug 3 15:09:20 TinyLinux user.debug kernel: [ 0.000000] DMA32 zone: 507392 pages, LIFO batch:63
Aug 3 15:09:20 TinyLinux user.debug kernel: [ 0.000000] Normal zone: 57120 pages used for memmap
Aug 3 15:09:20 TinyLinux user.debug kernel: [ 0.000000] Normal zone: 3655680 pages, LIFO batch:63
Aug 3 15:09:20 TinyLinux user.info kernel: [ 0.000000] psci: probing for conduit method from DT.

 

0 Kudos
Reply

3,564 Views
Chethan
Contributor III

Hi,

yes but I am using devel Not tiny so that.

Thanks & Regards,

Chethan GR

0 Kudos
Reply

3,554 Views
yipingwang
NXP TechSupport
NXP TechSupport

I verified clean built rootfs_lsdk2012_yocto_devel_arm64.tgz provided by Linux SDK testing team.

/var/log/messages contains Kernel information as the following. So this problem should be caused by your modification, please check your new added packages.

Aug 3 18:22:49 DevelLinux syslog.info syslogd started: BusyBox v1.31.0
Aug 3 18:22:49 DevelLinux user.notice kernel: klogd started: BusyBox v1.31.0 (2020-09-17 08:00:32 UTC)
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd
Aug 3 18:22:49 DevelLinux user.notice kernel: [ 0.000000] Linux version 5.4.47 (jenkins@saturn) (gcc versio
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] Machine model: LS1046A RDB Board
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] efi: Getting EFI parameters from FDT:
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] efi: UEFI not found.
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] OF: reserved mem: initialized node qman-fqd, compat
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] OF: reserved mem: initialized node qman-pfdr, compa
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] OF: reserved mem: initialized node bman-fbpr, compa
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] cma: Reserved 320 MiB at 0x00000000e7c00000
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] NUMA: No NUMA configuration found
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] NUMA: Faking a node at [mem 0x0000000080000000-0x00
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] NUMA: NODE_DATA [mem 0xbfa803800-0xbfa804fff]
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] Zone ranges:
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] DMA32 [mem 0x0000000080000000-0x00000000ffffff
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] Normal [mem 0x0000000100000000-0x0000000bff7fff
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] Movable zone start for each node
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] Early memory node ranges
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] node 0: [mem 0x0000000080000000-0x00000000fbdff
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] node 0: [mem 0x0000000880000000-0x0000000bfbfff
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] node 0: [mem 0x0000000bff000000-0x0000000bff7ff
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x0000
Aug 3 18:22:49 DevelLinux user.debug kernel: [ 0.000000] On node 0 totalpages: 4163072
Aug 3 18:22:49 DevelLinux user.debug kernel: [ 0.000000] DMA32 zone: 8192 pages used for memmap
Aug 3 18:22:49 DevelLinux user.debug kernel: [ 0.000000] DMA32 zone: 0 pages reserved
Aug 3 18:22:49 DevelLinux user.debug kernel: [ 0.000000] DMA32 zone: 507392 pages, LIFO batch:63
Aug 3 18:22:49 DevelLinux user.debug kernel: [ 0.000000] Normal zone: 57120 pages used for memmap
Aug 3 18:22:49 DevelLinux user.debug kernel: [ 0.000000] Normal zone: 3655680 pages, LIFO batch:63
Aug 3 18:22:49 DevelLinux user.info kernel: [ 0.000000] psci: probing for conduit method from DT.

0 Kudos
Reply

3,569 Views
yipingwang
NXP TechSupport
NXP TechSupport

You could build rootfs filesystem in the above Yocto environment as the following.

No need flex-build.

$: source ./setup-env -m ls1046ardb
$: bitbake fsl-image-networking

 

0 Kudos
Reply