Austin Ranney | 10 Jun 2009 16:01
Picon
Favicon

From: Mr.Austin Ranney.

From: Mr.Austin Ranney. 
Address: #52 Mitchley Close London N13 8HG 
Occupations: External Auditor 
  very Important.
Do accept my sincere apologies if my mail does not meet your personal
ethics although, I wish to use this medium to get in touch with you first
because it's fastest means. I am an extenal auditor of a well known Bank
here in the United Kingdom. 
  In one of our periodic auditing I discorved a dormant accounts with
holding balance of 36,759,000.00 (THIRTY SIX MILLION SEVEN HUNDRED AND
FIFTY NINE THOUSAND BRITISH POUNDS) which has not been operated for years.
From my investigations and confirmations, the owner of this account, a
foreigner by name Mr. Rafik Hariri.
  Rafik Bahaa Edine Hariri (November 1, 1944 - February 14, 2005), married
to Nazek Audi Hariri, was a Lebanese self-made millionaire and business
tycoon, and was five times Prime Minister of Lebanon (1992-1998 and
2000-2004) before his last resignation from office on October 20, 2004. The
late Rafik Hariri died on February 14, 2005 when explosives equivalent to
around 300 kg of C4 were detonated as his motorcade drove past the Saint
George Hotel In the
Lebanese capital.
  and since then nobody has done anything as egards the claiming of this
money because he has no family members who are aware of the existence of
neither the account nor the funds. I have secretly discussed this matter
with a top senior minister official of the federal ministry of finance here
and we have agreed to find a reliable foreign partner to deal with us,
although due to his possition he did not want to take active part but as
soon as you follow my instructions everything will be successfull because
we will be working hand in hand with him. 
  We thus propose to do business with you,standing in as the next of kin of
(Continue reading)

aiguisagegeneral | 12 Jun 2009 11:47
Picon

£1,000,000.00 GPB

Congratulations, click reply for the claim.
Dharmosoth Seetharam | 12 Jun 2009 11:25
Favicon

/var/log/messages doesn't have crash info when kernel gets panic/oops/crash

Hi,

I have encounter a problem called /var/log/messages does not contain any information 
on kernel crash dump.

Prior to enabling KEXEC we saw stack traces and bug info etc in /var/log/messages.
After enabling KEXEC feature those info was missed.

How can we get those missed info in /var/log/messages even when KEXEC feature is enabled.

Any help will appreciate.

Thanks and Regards
Seetharam

____________________________________________________________
Receive Notifications of Incoming Messages
Easily monitor multiple email accounts & access them with a click.
Visit http://www.inbox.com/notifier and check it out!
Neil Horman | 12 Jun 2009 22:05
Picon
Favicon

Re: /var/log/messages doesn't have crash info when kernel gets panic/oops/crash

On Fri, Jun 12, 2009 at 01:25:49AM -0800, Dharmosoth Seetharam wrote:
> Hi,
> 
> I have encounter a problem called /var/log/messages does not contain any information 
> on kernel crash dump.
> 
> Prior to enabling KEXEC we saw stack traces and bug info etc in /var/log/messages.
> After enabling KEXEC feature those info was missed.
> 
> How can we get those missed info in /var/log/messages even when KEXEC feature is enabled.
> 
> Any help will appreciate.
> 
run crash on the resultant vmcore file that kexec can produce/save and get the
dmesg log out of it.
alternatively you can use makedumpfile with the --dump-dmesg log

Neil

> 
> Thanks and Regards
> Seetharam
> 
> ____________________________________________________________
> Receive Notifications of Incoming Messages
> Easily monitor multiple email accounts & access them with a click.
> Visit http://www.inbox.com/notifier and check it out!
> 
> _______________________________________________
> kexec mailing list
(Continue reading)

Dharmosoth Seetharam | 13 Jun 2009 09:01
Favicon

Re: /var/log/messages doesn't have crash info when kernel gets panic/oops/crash


Hi Neil,

Thanks for your quick reply.

What you have suggested is nice when we got/save crash dump (i.e vmcore)
What if we failed to save/capture vmcore info or vmcore is corrupted etc. then we dont get any information
regarding the panic/crash/oops at anywhere?

Thanks and Regards

 Seetharam

> -----Original Message-----
> From: nhorman <at> redhat.com
> Sent: Fri, 12 Jun 2009 16:05:13 -0400
> To: dseetharam <at> inbox.com
> Subject: Re: /var/log/messages doesn't have crash info when kernel gets
> panic/oops/crash
> 
> On Fri, Jun 12, 2009 at 01:25:49AM -0800, Dharmosoth Seetharam wrote:
>> Hi,
>> 
>> I have encounter a problem called /var/log/messages does not contain any
>> information
>> on kernel crash dump.
>> 
>> Prior to enabling KEXEC we saw stack traces and bug info etc in
>> /var/log/messages.
>> After enabling KEXEC feature those info was missed.
(Continue reading)

Eric W. Biederman | 13 Jun 2009 09:11
Favicon

Re: /var/log/messages doesn't have crash info when kernel gets panic/oops/crash

Dharmosoth Seetharam <dseetharam <at> inbox.com> writes:

> Hi Neil,
>
> Thanks for your quick reply.
>
> What you have suggested is nice when we got/save crash dump (i.e vmcore)
> What if we failed to save/capture vmcore info or vmcore is corrupted etc. then we dont get any information
> regarding the panic/crash/oops at anywhere?

Basic questions.
1) Do you have panic on oops set?
   I think that setting more than anything else will be the
   difference in what shows up in /var/log/messages.
2) Have you tried a dry run and confirmed you can get a crash dump?
3) Are you using kvm

Eric

> Thanks and Regards
>
>  Seetharam
>
>
>> -----Original Message-----
>> From: nhorman <at> redhat.com
>> Sent: Fri, 12 Jun 2009 16:05:13 -0400
>> To: dseetharam <at> inbox.com
>> Subject: Re: /var/log/messages doesn't have crash info when kernel gets
>> panic/oops/crash
(Continue reading)

Dharmosoth Seetharam | 13 Jun 2009 12:22
Favicon

Re: /var/log/messages doesn't have crash info when kernel gets panic/oops/crash


> -----Original Message-----
> From: ebiederm <at> xmission.com
> Sent: Sat, 13 Jun 2009 00:11:25 -0700
> To: dseetharam <at> inbox.com
> Subject: Re: /var/log/messages doesn't have crash info when kernel gets
> panic/oops/crash
> 
> Dharmosoth Seetharam <dseetharam <at> inbox.com> writes:
> 
>> Hi Neil,
>> 
>> Thanks for your quick reply.
>> 
>> What you have suggested is nice when we got/save crash dump (i.e vmcore)
>> What if we failed to save/capture vmcore info or vmcore is corrupted
>> etc. then we dont get any information
>> regarding the panic/crash/oops at anywhere?
> 
Hi Eric,

> Basic questions.
> 1) Do you have panic on oops set?
>    I think that setting more than anything else will be the
>    difference in what shows up in /var/log/messages.

Yes, in my case panic_on_oops was set with 1

> 2) Have you tried a dry run and confirmed you can get a crash dump?

(Continue reading)

Eric W. Biederman | 13 Jun 2009 14:51
Favicon

Re: /var/log/messages doesn't have crash info when kernel gets panic/oops/crash

Dharmosoth Seetharam <dseetharam@...> writes:

>> -----Original Message-----
>> From: ebiederm@...
>> Sent: Sat, 13 Jun 2009 00:11:25 -0700
>> To: dseetharam@...
>> Subject: Re: /var/log/messages doesn't have crash info when kernel gets
>> panic/oops/crash
>> 
>> Dharmosoth Seetharam <dseetharam@...> writes:
>> 
>>> Hi Neil,
>>> 
>>> Thanks for your quick reply.
>>> 
>>> What you have suggested is nice when we got/save crash dump (i.e vmcore)
>>> What if we failed to save/capture vmcore info or vmcore is corrupted
>>> etc. then we dont get any information
>>> regarding the panic/crash/oops at anywhere?
>> 
> Hi Eric,
>
>> Basic questions.
>> 1) Do you have panic on oops set?
>>    I think that setting more than anything else will be the
>>    difference in what shows up in /var/log/messages.
>
> Yes, in my case panic_on_oops was set with 1

That is the reason thing don't show up in /var/log/messages
(Continue reading)

Dharmosoth Seetharam | 13 Jun 2009 15:24
Favicon

Re: /var/log/messages doesn't have crash info when kernel gets panic/oops/crash


> -----Original Message-----
> From: ebiederm@...
> Sent: Sat, 13 Jun 2009 05:51:25 -0700
> To: dseetharam@...
> Subject: Re: /var/log/messages doesn't have crash info when kernel gets
> panic/oops/crash
> 
> Dharmosoth Seetharam <dseetharam@...> writes:
> 
>>> -----Original Message-----
>>> From: ebiederm@...
>>> Sent: Sat, 13 Jun 2009 00:11:25 -0700
>>> To: dseetharam@...
>>> Subject: Re: /var/log/messages doesn't have crash info when kernel gets
>>> panic/oops/crash
>>> 
>>> Dharmosoth Seetharam <dseetharam@...> writes:
>>> 
>>>> Hi Neil,
>>>> 
>>>> Thanks for your quick reply.
>>>> 
>>>> What you have suggested is nice when we got/save crash dump (i.e
>>>> vmcore)
>>>> What if we failed to save/capture vmcore info or vmcore is corrupted
>>>> etc. then we dont get any information
>>>> regarding the panic/crash/oops at anywhere?
>>> 
>> Hi Eric,
(Continue reading)

Eric W. Biederman | 13 Jun 2009 16:08
Favicon

Re: /var/log/messages doesn't have crash info when kernel gets panic/oops/crash

Dharmosoth Seetharam <dseetharam@...> writes:

>>>> Basic questions.
>>>> 1) Do you have panic on oops set?
>>>>    I think that setting more than anything else will be the
>>>>    difference in what shows up in /var/log/messages.
>>> 
>>> Yes, in my case panic_on_oops was set with 1
>> 
>> That is the reason thing don't show up in /var/log/messages
>> because you panic before syslog has a chance to write the messages.
>
> Thanks.
> So, if panic_on_oops set with 0(default), we will get all the 
> needed info like stack traces, bug info etc. in /var/log/messages then reboots.
>
> Or do we need to apply any specific patches to get info in /var/log/messages?
>
>> 
>>>> 2) Have you tried a dry run and confirmed you can get a crash dump?
>>> 
>>> No, I haven't tried this.
>> 
>> It sounds like you have not been getting the coredumps when problems
>> happen.  Running a simple test run to  Alt-sysrq-c to confirm
>> that things are basically setup ok is a good idea.
>> 
> Sorry, I misunderstood your question.
> I have gave dry run and confirmed that the dumps are getting saved in particular dir and able to analyze.
>
(Continue reading)


Gmane