no system logger running

[sascha_silbe]

On an XO-1 running  dx3g091 on an SD card, there's no /var/log/messages and ps shows that no system logger is running.

This makes it impossible to diagnose some bugs occurring in the field (like issues with 3G modems).

[sascha_silbe]

I forgot to mention that even chkconfig --list didn't show any trace of a logger either and searching PATH for *log* doesn't yield anything, so we seem to be missing a system logger package. I'm puzzled how that can happen; are we explicitly removing it during build or did the build fail without aborting completely?

[m_anish]

These are the packages being removed while making the build. Does this info help?

at,
dos2unix,
dump,
finger,
ftp,
khmeros-base-fonts,
krb5-workstation,
mailx,
mlocate,
nafees-web-naskh-fonts,
nss_ldap,
quota,
pam_ccreds,
pam_passwdqc,
pam_smb,
readahead,
rdist,
rmt,
rsh,
talk,
tcp_wrappers,
tree,
smartmontools,
sos,
stunnel,
symlinks,
xfsprogs,
yp-tools,
ypbind,
ds-backup-client,

[sascha_silbe]

Figured this out with Anish on IRC. We replaced ds-backup-client by sugar-client (starting with dx3g053). ds-backup-client depended on cronie, which in turn pulled in rsyslog. Apparently no other package depends on either of those, so they got dropped by yum.

As sugar-client needs cron, too, it should depend on it. Additionally we'll add rsyslog explicitly, as it's an important system package regardless of whether sugar-client / cron needs it or not.

[alsroot]

Replying to sascha_silbe:

As sugar-client needs cron, too, it should depend on it. Additionally we'll add rsyslog explicitly, as it's an important system package regardless of whether sugar-client / cron needs it or not.

sugar-client itself doesn't require cron (it handles all background operation on its own from DBus service). But dextrose doesn't use this functionality and call sugar-client directly from cron. So, cron dependency needs to be added on dextrose level, not on sugar-client.