OpenWrt/LEDE Project

  • Status Unconfirmed
  • Percent Complete
  • Task Type Bug Report
  • Category Packages
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version openwrt-19.07
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Dan Berger - 01.12.2020

FS#3485 - logd: log starts up before networking, causing remote logging to miss boot messages

# grep PRETTY_NAME /etc/os-release
PRETTY_NAME=”OpenWrt 19.07.4”

rc.d contains:

K10ddns → ../init.d/ddns
K99socat → ../init.d/socat
S00sysfixtime → ../init.d/sysfixtime
S00urngd → ../init.d/urngd
S01haveged → ../init.d/haveged
S10boot → ../init.d/boot
S10system → ../init.d/system
S11sysctl → ../init.d/sysctl
S12log → ../init.d/log
S12rpcd → ../init.d/rpcd
S19dnsmasq → ../init.d/dnsmasq
S19dropbear → ../init.d/dropbear
S19firewall → ../init.d/firewall
S20network → ../init.d/network

note log is S12, network is S20

there’s a comment at the top of the log rc script which suggests this is the wrong order:

# cat /etc/init.d/log
#!/bin/sh /etc/rc.common
# Copyright (C) 2013

# start after and stop before networking

note: “start after ... networking”

Dan Berger commented on 02.12.2020 07:50

making log start after network improves the situation, but boot messages are still missing from both the remote syslog server and the local log file.

this was observed in lede 17, and closed without resolution:

Dan Berger commented on 04.12.2020 17:27


Available keyboard shortcuts


Task Details

Task Editing