System Crash Troubleshooting

Jim Cornette fc-cornette at insight.rr.com
Tue Feb 28 12:03:01 UTC 2006


Andy Green wrote:
> Jim Cornette wrote:
> 
>>>> # cat /var/log/messages | grep syslog
>>>> Feb 26 04:02:06 msi2 syslogd 1.4.1: restart.
>>>> Feb 26 05:00:03 msi2 syslogd 1.4.1: restart.
> 
>> Isn't the file.msi a microsoft installer file? Is it possible that you
>> are getting problems in through the windows world?
> 
> That's his hostname.
> 
> Examine /etc/crontab and /var/spool/cron/* looking for something that
> was installed that runs the postgres user stuff every 5 mins.
> 
> Most often for nasty dead meat crashes I found the problem is an X
> driver.  Try the vesa driver instead for a while, if that actually works
> on your platform.
> 
> -Andy
> 

I was referring to the below excerpt. It looks like a powerbook anyway. 
file.msi should not be part of that arch anyway.

Thanks for the info,
Jim

Feb 14 17:13:02 msi2 xinetd[2346]: Starting reconfiguration
Feb 14 17:13:02 msi2 xinetd[2346]: Swapping defaults
Feb 14 17:13:02 msi2 xinetd[2346]: Reconfigured: new=0 old=0 dropped=0 
(services)
Feb 14 17:13:48 msi2 named[2012]: client 192.168.0.2#32777: update 
'inside.msi/IN' denied
Feb 14 17:13:48 msi2 dhcpd: if RWPowerBookG4.inside.msi IN A rrset 
doesn't exist add RWPowerBookG4.inside.msi 43200 IN A 192.168.0.177: 
timed out.

https://www.redhat.com/archives/fedora-list/2006-February/msg03803.html

-- 
Well fix that in the next (upgrade, update, patch release, service pack).




More information about the fedora-list mailing list