Does the Pi keep in ongoing log in case of a crash?

TPR

If I get a hard crash on the Pi is there anywhere I can look that keeps some sort of log to tell me what happened?

And I'm not talking about the runcommand.log, I mean like if I'm in an emulator core and something hard crashes to where I have to reboot the hardware, is there anywhere I can look to see what the problem might have been to cause it?

retropieuser555

@TPR for cores, you can set the logging information within RetroArch itself so it always saves the logs up to the point of a crash. That wouldn't help for non retroarch cores though, but different programs have their own logging functions usually for debugging

BuZz

@TPR If an emulator locks up but the system is still accessible over SSH you could check the output from dmesg. If the system is frozen completely the only way might be to have some serial logging which would require some efforts. Also if you're having crashes make sure you have any over clocking disabled etc.

TPR

@BuZz said in Does the Pi keep in ongoing log in case of a crash?:

@TPR If an emulator locks up but the system is still accessible over SSH you could check the output from dmesg. If the system is frozen completely the only way might be to have some serial logging which would require some efforts. Also if you're having crashes make sure you have any over clocking disabled etc.

Thank you! I think this is exactly what I was looking for! Gonna give this a try next time it happens as the system is still "alive" so I should be able to use SSH to get into it.

TPR

@retropieuser555 said in Does the Pi keep in ongoing log in case of a crash?:

@TPR for cores, you can set the logging information within RetroArch itself so it always saves the logs up to the point of a crash. That wouldn't help for non retroarch cores though, but different programs have their own logging functions usually for debugging

Oh this is good to know! How do I set that log and where do I find it?

TPR

@retropieuser555 said in Does the Pi keep in ongoing log in case of a crash?:

@TPR for cores, you can set the logging information within RetroArch itself so it always saves the logs up to the point of a crash. That wouldn't help for non retroarch cores though, but different programs have their own logging functions usually for debugging

So I went into Main Menu > Settings > Logging and turned everything "on" to do verbose logging to file, but even after doing "Override Core Settings" when I re-load a game, all those logging settings have been re-set to off again. My emulator core config file in /opt/retropie/configs/all/retroarch/config/ has the proper permissions as other RA core settings are being saved but I can't get the system to save my logging settings for each time I load a game.

Any ideas?

retropieuser555

@TPR said in Does the Pi keep in ongoing log in case of a crash?:

@retropieuser555 said in Does the Pi keep in ongoing log in case of a crash?:

@TPR for cores, you can set the logging information within RetroArch itself so it always saves the logs up to the point of a crash. That wouldn't help for non retroarch cores though, but different programs have their own logging functions usually for debugging

So I went into Main Menu > Settings > Logging and turned everything "on" to do verbose logging to file, but even after doing "Override Core Settings" when I re-load a game, all those logging settings have been re-set to off again. My emulator core config file in /opt/retropie/configs/all/retroarch/config/ has the proper permissions as other RA core settings are being saved but I can't get the system to save my logging settings for each time I load a game.

Any ideas?

Save settings on exit is probably set to off?

TPR

@retropieuser555 said in Does the Pi keep in ongoing log in case of a crash?:

@TPR said in Does the Pi keep in ongoing log in case of a crash?:

@retropieuser555 said in Does the Pi keep in ongoing log in case of a crash?:

@TPR for cores, you can set the logging information within RetroArch itself so it always saves the logs up to the point of a crash. That wouldn't help for non retroarch cores though, but different programs have their own logging functions usually for debugging

So I went into Main Menu > Settings > Logging and turned everything "on" to do verbose logging to file, but even after doing "Override Core Settings" when I re-load a game, all those logging settings have been re-set to off again. My emulator core config file in /opt/retropie/configs/all/retroarch/config/ has the proper permissions as other RA core settings are being saved but I can't get the system to save my logging settings for each time I load a game.

Any ideas?

Save settings on exit is probably set to off?

Set to "on" and I still can't get the verbose logging to stick to "on" when exiting a game.

TPR

@retropieuser555 Still trying to figure this one out. Any help on how I can get verbose logging in retroarch to stay on when I load a game?

TPR

@TPR said in Does the Pi keep in ongoing log in case of a crash?:

@retropieuser555 Still trying to figure this one out. Any help on how I can get verbose logging in retroarch to stay on when I load a game?

Just in case anyone ever needed the answer to this, I added the following to my retroarch.cfg file in my /config/gc folder and this worked:

log_verbosity = "true"
log_to_file = "true"
log_to_file_timestamp = "true"

Note this was the only fix that I found that would force logging verbosity stay on for me.