Bug 1848 - syslogd can not startup with 1.2 M1 20111213 build
Summary: syslogd can not startup with 1.2 M1 20111213 build
Status: VERIFIED FIXED
Alias: None
Product: System Startup
Classification: Runtime
Component: system-startup (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.2 M2
Assignee: Joshua Lock - Disabled
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-12-20 01:14 UTC by Yi Zhao
Modified: 2012-01-12 23:11 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2011-12-20 01:14:10 UTC
Tree/Branch: poky/1.2_M1
Poky Commit: b806f726b1db2cb605869c1022ef727c1110255b

Image location:
http://autobuilder.pokylinux.org/nightly/20111213-4/machines/

The syslogd can not startup when system boot up. Only klogd startup.
###############
root@qemuarm:~# ps aux|grep syslogd
root       513  0.0  0.4   2128   500 pts/0    S+   09:05   0:00 grep syslogd

root@qemuarm:~# /etc/init.d/syslog stop   
Stopping syslogd/klogd: no syslogd found; none killed

root@qemuarm:~# killall klogd
root@qemuarm:~# ps aux|grep log
root       521  0.0  0.4   2128   500 pts/0    S+   09:09   0:00 grep log
root@qemuarm:~# 
root@qemuarm:~# /etc/init.d/syslog start
Starting syslogd/klogd: done

root@qemuarm:~# ps aux|grep log
root       526  0.0  0.4   2124   548 ?        Ss   09:09   0:00 /sbin/klogd -n
root       528  0.0  0.4   2128   500 pts/0    S+   09:10   0:00 grep log
###############

When I ran syslogd command in terminal, I got the error message:
##############
root@qemuarm:~# /sbin/syslogd -n -C64 -m 20
syslogd: bad line 1: 1 tokens found, 2 needed
root@qemuarm:~# 
###############

This issue doesn't happen with Yocto 1.1.
Comment 1 Saul Wold 2011-12-27 11:56:10 UTC
Seems that the busybox syslog config has changed to be more like the full version now, so the simple syslog.config is wrong now.
Comment 2 Joshua Lock - Disabled 2012-01-02 12:27:16 UTC
The issue is that busybox didn't support syslog.conf before 1.19, the syslog.conf file we ship is read by the syslog init script to set syslog parameters at start time.

Now that busybox 1.19 is trying to read the syslog.conf and expecting an rsyslog style configuration file it's seeing our options file, failing to read it and crashing.

AFAICT syslog.conf doesn't support some of the parameters we use with syslog so I'm going to propose we rename the file used by the init script to something like syslog-startup.conf.

I'll probably add some comments to the file to make it more obvious what is going on.
Comment 4 Yi Zhao 2012-01-12 23:11:01 UTC
Verified with 1.2 M2 RC1 
syslog can start up and works well.


Tree/branch: poky/1.2_M2
Commit: 0f4d99d207b224bb9ce23de00a48f795ae20b3a0