Open bnaecker opened 2 years ago
I also hit this when testing recovery images. We should just ship an empty file in the images.
In the recovery image, this was being caused by a missing file in the image. On a standard helios system, the system-log:default
service always touches /var/adm/messages
.
The recovery image is fixed and I just confirmed that the file is present and full of boot log information.
I don't know what was causing the original reported issue on a standard helios system.
I am pretty sure that what bnaecker hit there was https://www.illumos.org/issues/15071 If we're shipping rsyslog with helios, we should adjust the standard syslog manifest as has been done in OmniOS to work around this.
I've seen in several circumstances that the log file
/var/adm/messages
does not exist on a Helios system by default. Looking at the SMF services, this seems to correlate withsvc:/system/system-log:default
being the enabled logging SMF service. I've generally been able to "solve" this by swapping that out for thesvc:/system/system-log:rsyslog
service. At that point,/var/adm/messages
appears, and I see log messages as I'd expect.I don't have an example system where this is currently the case. However, if I undo the "fix", and re-enable
system-log:default
, I no longer see messages in/var/adm/messages
. I'm either unaware of where those messages are directed if thedefault
flavor is enabled, or there may be an issue with the logging configuration being correctly used to emit such messages.Here is
/etc/syslog.conf
onsock.eng.oxide.computer
, where I've just done the service-swap song and dance: