cancel
Showing results for 
Search instead for 
Did you mean: 

dmesg output not correct

mrmo07
Regular Advisor

dmesg output not correct

Hi expert !

 

below is the dmesg output from app server.  but currently syslog not showing such error !!!

 

root@dcpapp01 [/]# dmesg

Sep 18 09:51
...
ntext - possible stack overflow.

Pid 28325 was killed due to failure in writing the signal context - possible stack overflow.

Pid 28356 was killed due to failure in writing the signal context - possible stack overflow.

Pid 28350 was killed due to failure in writing the signal context - possible stack overflow.

Pid 28353 was killed due to failure in writing the signal context - possible stack overflow.

Pid 28360 was killed due to failure in writing the signal context - possible stack overflow.

Pid 28363 was killed due to failure in writing the signal context - possible stack overflow.

Pid 28369 was killed due to failure in writing the signal context - possible stack overflow.

Pid 28430 was killed due to failure in writing the signal context - possible stack overflow.

Pid 28365 was killed due to failure in writing the signal context - possible stack overflow.

Pid 28428 was killed due to failure in writing the signal context - possible stack overflow.

Pid 28313 was killed due to failure in writing the signal context - possible stack overflow.

Pid 28438 was killed due to failure in writing the signal context - possible stack overflow.

Pid 28440 was killed due to failure in writing the signal

 

Regards,

Morshed.

1 REPLY
Dennis Handly
Acclaimed Contributor

Re: dmesg output not correct

If you don't run "dmesg -" in a cron job, then the errors may be old, since none of them are timestamped.