On 2016-09-19 09:50:19 +0200, Abou Al Montacir wrote: > On Thu, 2016-09-15 at 11:30 +0200, Vincent Lefevre wrote: > > Then I think that you should give strace information + system logs. > Thanks Vincent for the only valuable answer I've got on this. > > I tried that but unfortunately could not reproduce it again due to probably my > recent upgrade. I'll keep trying until I get it.
Note that since system logs don't always give enough information and for problems that are not easily reproducible, you can't get strace information, I suggest to install the atop package, which monitors system resources and process activity. So, when a crash occurs, in addition to system logs, you can see what atop has recorded (for instance, in the past I could see that some freeze or crash was due to that some process was taking more than the amount of RAM, thanks to atop information). The atop package from unstable unfortunately triggers some trap divide errors, with the consequence that nothing is recorded for some days (the daemon seems to be restarted everyday). This is apprently fixed in experimental, but this new version yields a timeout at shutdown with systemd (90 seconds by default). -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
