finit: finit errors on boot & trouble with logging
I am trying finit 3.1 and I am having two issues. Hopefully I am just doing something wrong. ๐
First, when finit starts up, the following messages appear in the log:
Jan 1 00:10:13 igep00x0 syslog.info syslogd started: BusyBox v1.19.4
Jan 1 00:10:15 igep00x0 daemon.err finit[1]: cond_set_path():Unable to read configuration generation (/var/run/finit/cond/net/lo/exist)
Jan 1 00:10:15 igep00x0 daemon.err finit[1]: cond_set_path():Unable to read configuration generation (/var/run/finit/cond/net/lo/up)
Jan 1 00:10:15 igep00x0 daemon.err finit[1]: cond_set_path():Unable to read configuration generation (/var/run/finit/cond/net/lo/running)
Jan 1 00:10:15 igep00x0 daemon.err finit[1]: cond_set_path():Unable to read configuration generation (/var/run/finit/cond/net/eth0/exist)
Jan 1 00:10:15 igep00x0 daemon.err finit[1]: cond_set_path():Unable to read configuration generation (/var/run/finit/cond/net/eth0/up)
Jan 1 00:10:15 igep00x0 daemon.err finit[1]: cond_set_path():Unable to read configuration generation (/var/run/finit/cond/net/eth0/running)
Jan 1 00:10:15 igep00x0 daemon.err finit[1]: cond_set_path():Unable to read configuration generation (/var/run/finit/cond/net/route/default)
Jan 1 00:10:16 igep00x0 daemon.err finit[1]: cond_set_path():Unable to read configuration generation (/var/run/finit/cond/net/eth0/exist)
Jan 1 00:10:16 igep00x0 daemon.err finit[1]: cond_set_path():Unable to read configuration generation (/var/run/finit/cond/net/eth0/up)
Jan 1 00:10:16 igep00x0 daemon.err finit[1]: cond_set_path():Unable to read configuration generation (/var/run/finit/cond/net/eth0/running)
Jan 1 00:10:16 igep00x0 auth.info login[412]: root login on 'ttyO2'
I realize that BusyBox is rather old, but that is what I am stuck with for this project.
The error message appears to be coming from the file reconf missing from the directory /var/run/finit/cond/ (line 75 in cond-w.c).
Next, I wanted to test out the logging features.
I tried putting the following in finit.conf:
task [2345] log:/var/log/test1 uname -a
task [2345] log uname -a
task [2345] log:/var/log/test2 <svc/sbin/syslogd> uname -a
The files appear in /var/log/ except they are empty. Also, no output from the task appear in the syslog messages.
I was expecting to see the following:
The same is true if I change task to service in the above snippet.
Could you suggest some steps to help troubleshoot these issues?
I am using the bootmisc and netlink plugins on this test setup. The hardware is an IGEP0020 board running a custom Yocto with Linux kernel 2.6.37. Thanks very much!
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 22 (22 by maintainers)
Commits related to this issue
- Workaround troglobit/finit#100 missing /var/run --> /run symlink This seems to be necessary early at boot due to troglobit/finit#100 Signed-off-by: Joachim Nilsson <troglobit@gmail.com> — committed to troglobit/tinyroot by troglobit 6 years ago
- Fix #100: Adjust path to COND_RECONF /var/run symlink may be missing On systems with the new /run hierarchy the compat symlink from /var/run may be missing, or not yet be set up by bootmisc.so. This... — committed to troglobit/finit by troglobit 6 years ago
- Follow-up #100: Remove buggy "optimization", caught by Coverity Scan We cannot allow pid_runpath() to return its 'file' argument because that may be a stack variable in a helper function. Signed-off... — committed to troglobit/finit by troglobit 6 years ago
No problem, I appreciate the time youโre spending on this already. ๐
I will probably get back to working on this next week, and hopefully I will report back here with a solution.