LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 11-15-2005, 03:17 AM   #16
cs-cam
Senior Member
 
Registered: May 2004
Location: Australia
Distribution: Gentoo
Posts: 3,544
Blog Entries: 4

Rep: Reputation: 56
Re: Re: My son is innocent!


Quote:
Originally posted by dhave
You could wait until an upgrade of the kid is available. I did this, and the current version of my son (he's at v. 17.4 now) is no longer goofing things up on my computer. In fact, he helps fix it. When my kid was at v. 2.x and even v. 3.x, however, I had a lot of problems of the type you describe.

I should warn you, however, that there are other bugs that have been introduced with the more recent versions. Still, I'm generally happy with this app.
Dork
 
Old 11-15-2005, 07:41 AM   #17
Seiken
Member
 
Registered: Sep 2004
Location: Canada
Distribution: Slackware 14
Posts: 248

Original Poster
Rep: Reputation: 30
#last says it's rebooting every morning at 04:40 every day for the past 8 days.

I figured if it's happening at the exact same time every day, maybe it IS a cron job. Well I noticed that whenever I ran slocate it said the database hasn't been updated in 8 days (!) So I ran the "slocate" script in /etc/cron.daily, which runs updatedb. I did this a few times. Each time, it would either reboot or lock up. I tried running updatedb myself instead of using the script in cron.daily and it still rebooted or froze. I guess we found the culprit.

Is there a way to get updatedb working again, or am I going to have to disable that cron job? If the latter, how do I disable it?

Thanks for all the help!
 
Old 11-15-2005, 11:35 AM   #18
Thanotos
Member
 
Registered: Oct 2005
Location: Nanaimo, BC. ~CANADA~
Posts: 70

Rep: Reputation: 15
is this a new computer?

Other than being a hardware issue it could also be a heating issue.
Your motherboard may have a default reboot for excessive heat.

You can check that in your BIOS.

Just another thought is all. Best of luck to you.
 
Old 11-15-2005, 11:40 AM   #19
Dankles
Member
 
Registered: May 2004
Location: /dev/null
Distribution: Slackware
Posts: 245

Rep: Reputation: 31
I know this problem.
Try swapping out the PSU (power supply)
 
Old 11-15-2005, 02:07 PM   #20
Seiken
Member
 
Registered: Sep 2004
Location: Canada
Distribution: Slackware 14
Posts: 248

Original Poster
Rep: Reputation: 30
It's a brand new PSU.

To the last 2 replies... are you saying that even though it happens at the exact same time every morning, and it appears to be the updatedb command causing the reboot, that you still believe it to be a hardware issue?
 
Old 11-15-2005, 02:21 PM   #21
yuchai
Member
 
Registered: Jan 2005
Location: New York, NY
Distribution: Slackware 13.0
Posts: 56

Rep: Reputation: 15
Given that it seems to be an updatedb issue. I would think it's 1 of 2 things:

1. There are corruptions in the filesystems that updatedb is performing on.
2. It's a harddrive issue so when certain spots of the harddrive (bad sectors?) are accessed the system becomes unstable.

Not a linux expert so can't comment further. Good luck.
 
Old 11-15-2005, 02:21 PM   #22
Ilgar
Member
 
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware 14.1, Slackware64 14.1
Posts: 917

Rep: Reputation: 87
Doesn't Slackware by default run updatedb at 4:30 am everyday? It does so on mine.
 
Old 11-15-2005, 02:24 PM   #23
Ilgar
Member
 
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware 14.1, Slackware64 14.1
Posts: 917

Rep: Reputation: 87
Quote:
Originally posted by yuchai
Given that it seems to be an updatedb issue. I would think it's 1 of 2 things:

1. There are corruptions in the filesystems that updatedb is performing on.
2. It's a harddrive issue so when certain spots of the harddrive (bad sectors?) are accessed the system becomes unstable.

Not a linux expert so can't comment further. Good luck.
We've posted at the same time -- yes I'd come to the same conclusion. Why not run a disk check or updatedb manually? In etiher case all corners of the hdd will be accessed and we'll see if there's a hardware problem.
 
Old 11-15-2005, 02:31 PM   #24
Seiken
Member
 
Registered: Sep 2004
Location: Canada
Distribution: Slackware 14
Posts: 248

Original Poster
Rep: Reputation: 30
If I run updatedb manually, it reboots (or sometimes just freezes.)
 
Old 11-15-2005, 03:15 PM   #25
dracolich
Senior Member
 
Registered: Jul 2005
Distribution: Slackware
Posts: 1,173

Rep: Reputation: 47
Quote:
I'm confused by the comment about me trying to keep it running all day... isn't keeping it running all day a good thing? It runs servers... :\
I just wanted to be sure I understood the situation correctly. My idea is that throughout the day the hardware inside the box build up a great amount of heat., and heat has a dramatic effect on overall system performance. If you have a small box or the inside of the box loaded with disk drives and cables and high performance cards then it's going to create a LOT of heat. After a while this can cause performance loss and even system "hiccups". That's why I asked about current ventilation and cooling.
 
Old 11-15-2005, 06:51 PM   #26
Shade
Senior Member
 
Registered: Mar 2003
Location: Burke, VA
Distribution: RHEL, Slackware, Ubuntu, Fedora
Posts: 1,418
Blog Entries: 1

Rep: Reputation: 46
Updatedb (the slocate script in /etc/cron.daily) runs at 4:40AM every day by default. You've found the problem.

Running updatedb or slocate -u uses lots of resources. It's very IO intensive on the hard drive and also uses lots of CPU cycles.

The fact that the machine reboots or freezes every time this command means that the machine will probably reboot or freeze under any other similar command that puts a good amount of stress on the system. A great stress test for this sort of thing is recompiling the kernel.

First things to check: make sure the CPU fan isn't blocked by a misplaced cable or large amounts of dust accumulation.
Also check the BIOS to see if you can get CPU / Motherboard temperature readings.

Try switching out the power supply, if you have another available. When you get large current draws from high system loads, the power may fluctuate from the PS which may in turn reboot the machine.

It seems to me that either heat on the CPU or a bad power supply are at fault here.

-- Shade
 
Old 11-16-2005, 05:31 AM   #27
freakyg
Member
 
Registered: Apr 2005
Distribution: LFS 5.0 and 6.1
Posts: 705

Rep: Reputation: 30
Re: My son is innocent!

Quote:
Originally posted by Seiken
See, I work nights so his mother gets up with him in the morning... but when she gets up, she's been falling asleep on the couch! So he gets to run around and do whatever he wants until she or I get up.
First of all, A 2 year old should NEVER EVER be left to run around and do whatever they want!!!!!!!!!!!!!!!!!
One of these days you or your wife will wake up and find your 2 year old has wandered outside and got hit by a car!!!!!! NEVER leave a two year old alone and unwatched!!!
 
Old 11-16-2005, 06:01 AM   #28
Seiken
Member
 
Registered: Sep 2004
Location: Canada
Distribution: Slackware 14
Posts: 248

Original Poster
Rep: Reputation: 30
Thanks Dr. Phil, but I was quite aware of that already. I see you've never made mistakes before, and therefore don't understand. That aside, he's not capable of undoing all of the locks to get outside. And even if he was capable of that, he still can't undo the deadbolt for the outside door, which requires a key.

Anyway, this is hardly relevent to LinuxQuestions.org. If you'd like to talk to me about parenting, you can email me at josh.darrell@gmail.com.
 
Old 11-16-2005, 06:56 AM   #29
piete
Member
 
Registered: Apr 2005
Location: Havant, Hampshire, UK
Distribution: Slamd64, Slackware, PS2Linux
Posts: 465

Rep: Reputation: 44
Could it be possible that we're overengineering the problem here?

Have you tried reinstalling the updatedb package and checking your filesystem? It might be a corrupt binary for whatever reason ... thinking about it, you might want to consider a reinstall of glibc, too, just in case that bit got corrupted somewhere along the line.

I'm sort of clutching at straws here, but reinstallation is cheaper than buying new hardware to replace possibibly faulty hardware. Like yuchai and Ilgar I highly recommend doing a manual disk check. Do you have a custom kernel? Perhaps there's some kernel level problem with disk access. I would rule out software problems before I started chasing hardware gremlins, personally.

- Piete "I've still got more opinions!" Sartain.
 
Old 11-16-2005, 10:07 AM   #30
Seiken
Member
 
Registered: Sep 2004
Location: Canada
Distribution: Slackware 14
Posts: 248

Original Poster
Rep: Reputation: 30
I would love to do a manual disk check, but I don't know how.

I am using the default 2.4.x kernel that comes with slack 10.2, so no custom kernel here.

As for reinstalling the updatedb package, which package would that be? I don't see an updatedb package in /var/log/packages.

Btw to everyone, I did chmod -x slocate in /etc/cron.daily, so as to prevent updatedb from running at 4:40am, and the PC was okay when I got up this morning. It did not freeze/reset.

Thank you for the suggestions piete. Now if I could just figure out how to do them
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Son and I are now Slackers - wife next? mikieboy LinuxQuestions.org Member Success Stories 3 11-16-2005 06:05 PM
fork and multiple son processes biiiep Programming 4 05-11-2005 11:00 AM
User beware VL bans innocent people galen VectorLinux 1 03-07-2004 12:15 PM
How to tell if your son is a hacker - Complete Bull$hit!!! 2kool General 22 05-06-2002 04:45 AM
answer waiting for son barbanero Programming 0 01-29-2002 04:59 PM


All times are GMT -5. The time now is 02:42 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration