| View previous topic :: View next topic |
| Author |
Message |
ranran
Tux's lil' helper
Joined: 11 Jul 2018
Posts: 75
|
 Posted: Sun Oct 14, 2018 6:23 pm Post subject: startup script log is not saved in syslog ? |
 |
|
Hello,
On boot there is important log
(see https://pasteboard.co/HIfkzuA.png )
But I can't find it in /var/log/messages (or similar).
Is there a way to make it saved there too ?
Thank you,
ranran |
|
| Back to top |
|
 |
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sun Oct 14, 2018 11:00 pm Post subject: |
|
|
/var/log/rc.log is what you want if /etc/rc.conf allows it: | /etc/rc.conf wrote: | # rc_logger launches a logging daemon to log the entire rc process to
# /var/log/rc.log
# NOTE: Linux systems require the devfs service to be started before
# logging can take place and as such cannot log the sysinit runlevel.
#rc_logger="NO"
# Through rc_log_path you can specify a custom log file.
# The default value is: /var/log/rc.log
#rc_log_path="/var/log/rc.log"
# If you want verbose output for OpenRC, set this to yes. If you want
# verbose output for service foo only, set it to yes in /etc/conf.d/foo.
#rc_verbose=no
# By default we filter the environment for our running scripts. To allow other
# variables through, add them here. Use a * to allow all variables through.
#rc_env_allow="VAR1 VAR2" |
_________________
Defund the FCC. |
|
| Back to top |
|
|
Goverp
Veteran
Joined: 07 Mar 2007
Posts: 1996
|
| Posted: Mon Oct 15, 2018 7:50 am Post subject: |
|
|
If you're talking about the hardware error on one CPU, that's before openrc starts, so it won't appear in rc.log. It should show in dmesg; if not, you need to do things in your kernel configuration concerning "Early printk" (I think it's under kernel hacking). If your are using syslog-ng there was a problem with early messages not being logged but that's fixed in recent releases unless you've tinkered with its default configuration, or you've got a very small buffer configured.
All that said, I suspect that sort of hardware error is bad news, and I doubt more logging will help.
<edit> I think you should run memtest - that looks like a memory error.
_________________
Greybeard |
|
| Back to top |
|
|
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Mon Oct 15, 2018 8:46 am Post subject: |
|
|
mce are log in /dev/mcelog
you need proper support in kernel to have the dev entry, and could use app-admin/mcelog to handle it. |
|
| Back to top |
|
|
ranran
Tux's lil' helper
Joined: 11 Jul 2018
Posts: 75
|
| Posted: Mon Oct 15, 2018 11:28 am Post subject: |
|
|
| Thanks very much for all comments! |
|
| Back to top |
|
|
Goverp
Veteran
Joined: 07 Mar 2007
Posts: 1996
|
| Posted: Tue Oct 16, 2018 8:40 am Post subject: |
|
|
I'm not sure if AMD cpus currently support mcelog. My Phenom-based desktop doesn't.
<edit>IIUC MCE's are now written to syslog, providing you have the right bits configured in the kernel; the mcelog device support appears to be deprecated.</edit>
_________________
Greybeard |
|
| Back to top |
|
|
|
Installing Gentoo
