Bug 6886

Summary:

[TC 202] Syslog from lsb image is not configurable

Product:

[Build System, Metadata & Runtime] OE-Core

Reporter:

Costin <costin.c.constantin>

Component:

core

Assignee:

Alejandro Hernandez <alejandro.hernandez>

Status:

RESOLVED NOTABUG

QA Contact:

Severity:

normal

Priority:

Medium

CC:

alexandru.c.georgescu, georgex.l.musat, meta.mr.watcher, meta.watcher, sgw, tom.zanussi

Version:

1.7

Target Milestone:

1.8

Hardware:

E-Menlow

OS:

x86

Whiteboard:

OS type for building Yocto:

---

Type of Regression:

New (Never tested)

Verified:

Documentation change:

Don't know

Attachments:

Description	Flags
messages file retrieved from the machine	none

Description Costin 2014-10-24 13:54:56 UTC

Hello,

While performing "TC 202 - syslog configurable":

TC content:
"
1. Get a yocto image from autobuilder or local build
2. Launch image and check if syslog is started by default in background with ps command: (ps -elf|grep syslog)
3. Modify /etc/syslog-startup.conf, change the LOGFILE to /var/log/messages.test
4. Restart syslog with command "/etc/init.d/syslog restart"
5. Check if syslog is started in background with ps command
6. Check if there is file generated under /var/log/messages.test
"

Expected results:
"Syslog could be configured by user and run without problem ."

after configuring  syslog-startup.conf and restarting the daemon, the expected messages.test file is not created and more-over the /var/log/messages is still being written. Attached is a copy of it.

poky: 924da20c6f2f183fa7e930e4c3c6b14c090acbe5
meta-intel: 002bef4c2a59e95503a2bb7729e7749cd5a9f65b

For the image itself, I used: 
PREFERRED_VERSION_linux-yocto_linuxstdbase ?= "3.10%"
and the installed image reports: 
#uname -a 
Linux intel-core2-32 3.10.55-ltsi-yocto-standard ...

The built version of syslog is:
root@intel-core2-32:/var/log# syslogd -v
syslogd 1.5.0


Regards,

Costin

Comment 1 Costin 2014-10-24 13:56:31 UTC

Created attachment 2212 [details]
messages file retrieved from the machine

Comment 2 Lucian Musat 2014-10-24 14:00:40 UTC

This reproduces also on core-i7-64 core-image-lsb-sdk, same builds.

Comment 3 Alexandru Georgescu 2014-10-28 10:06:10 UTC

This was found in a core-2-32 lsb-sdk image

(In reply to comment #0)
> Hello,
> 
> While performing "TC 202 - syslog configurable":
> 
> TC content:
> "
> 1. Get a yocto image from autobuilder or local build
> 2. Launch image and check if syslog is started by default in background with
> ps command: (ps -elf|grep syslog)
> 3. Modify /etc/syslog-startup.conf, change the LOGFILE to
> /var/log/messages.test
> 4. Restart syslog with command "/etc/init.d/syslog restart"
> 5. Check if syslog is started in background with ps command
> 6. Check if there is file generated under /var/log/messages.test
> "
> 
> Expected results:
> "Syslog could be configured by user and run without problem ."
> 
> after configuring  syslog-startup.conf and restarting the daemon, the
> expected messages.test file is not created and more-over the
> /var/log/messages is still being written. Attached is a copy of it.
> 
> poky: 924da20c6f2f183fa7e930e4c3c6b14c090acbe5
> meta-intel: 002bef4c2a59e95503a2bb7729e7749cd5a9f65b
> 
> For the image itself, I used: 
> PREFERRED_VERSION_linux-yocto_linuxstdbase ?= "3.10%"
> and the installed image reports: 
> #uname -a 
> Linux intel-core2-32 3.10.55-ltsi-yocto-standard ...
> 
> The built version of syslog is:
> root@intel-core2-32:/var/log# syslogd -v
> syslogd 1.5.0
> 
> 
> Regards,
> 
> Costin

Comment 4 Alexandru Georgescu 2014-10-28 10:19:04 UTC

as a note, on sato-sdk images this issue is not present.

Comment 5 Alejandro Hernandez 2014-11-03 18:37:44 UTC

This is not a bug, it's just not being configured correctly.
LSB images do not use Busybox's Syslog, (which is the one that's configured using /etc/syslog-startup.conf), on LSB images, Syslog must be configured using /etc/syslog.conf.

Comment 6 Costin 2014-11-10 07:48:44 UTC

Hello,

Thank you for the info, I will try your recommendation 

Regards,

Costin