[ale] server question

Chris Fowler ChrisF at computone.com
Wed Jun 13 13:31:53 EDT 2001 




1. Buy a bigger drive. 
2. Install it as a secondary
3. Boot off Tom's Root/Boot CD
4. Partition and format drive
5. Move /usr and /var to that drive
6. Edit /etc/fstab
7. Reboot



-----Original Message-----
From: Leonard Thornton [mailto:Leonard at Intelis-inc.net]
To: ale at ale.org
Sent: Wednesday, June 13, 2001 1:54 PM
To: morrigu_irm at springmail.com
Cc: ale at ale.org
Subject: Re: Re: [ale] server question



At 12:58 PM 6/13/2001 -0400, you wrote:
>Hi Leonard! *wave*


*Wave* (and I am using ALL of the fingers on my hand, not just one <grin>)


>I guess you haven't killed anyone at ATT yet? Did anyone ever come out to 
>repair your lines? The guy who installed ours said that the ATT repair 
>dept. was understaffed with clueless boneheads.


No fatalities yet, but I have a lot of VPs jumping through hoops.  First 
they claimed that the 3Com Sharkfin modems had a firmware bug and they were 
downloading a fix. *Strike One*.  Then they replaced the lines to my house 
from the street. *Strike Two*.  Then they replaced the modem with a 
Motorola. *Strike Three*.


Then, low and behold, on Monday afternoon, the Technical Supervisor for my 
area tells me that they just found out in the last two hours that there are 
1500-1600 other people in my area having the exact same problem as me.  My 
immediate question was:  "so if I had not gone to the Regional VP and 
screamed, no one would have done anything about all of these trouble 
reports?"  Go figure....


Still no complete resolution ... They claim they are attempting to isolate 
the problem in their network, but no joy yet.  Film at 11....



>Free disk space? none. It looks like mysql may be what's eating it up, 
>but, like I said, I could be wrong.
>
>Ummm...this was rather stupid of me, but I don't recall what the kernal 
>panic message was...I'll see if Bob remembers. As I recall, though, it 
>didn't offer a whole lot in the way of information. However, I remember we 
>checked syslog, and it offered no clues, other than the system ran out of 
>real memory (not virtual memory).
>
>The only message that has been consistent is "Can't find a free page". 
>Sound familiar to anyone? What I'm finding really weird is the periods 
>between downtimes decreasing exponentially. When I get to work, I'll try 
>logging on to that piece of crap, and see if I can find anything helpful.


If you have no free disk space I can understand why you would be getting 
panics and why those panics are getting closer together.  Cleanup all the 
trash,  buy a bigger trash can, or whatever else you have to do to increase 
your available disk space for mysql and the system.


>Thanks!
>
>-Indira
>
>-Sage
>
>
>On Wed, 13 Jun 2001 12:49:04 -0400 Leonard Thornton 
><Leonard at Intelis-inc.net> wrote:
>
>The first thing I would check is the free disk space.
>
>Secondly, what are your panic messages telling you?  What about
>syslog?  Enquiring minds want to know....
>
>At 11:34 AM 6/13/2001 -0400, you wrote:
> >Heyla, all!
> >
> >We have a server doing a really odd thing. Since November, the time this
> >stupid thing stays up without a reboot is decreasing exponentially. It
> >started off having to reboot every four months, and uptime without a
> >reboot is now about every 6 hours. Last week, we finally had to set a
> >crontab entry to automatically reboot the stupid thing every 24 hours,
> >then every 12, then every 8, and now, every four. (I got a bit ill having
> >to run downtown 4 days in a row) I predict the damn thing won't live
> >through the weekend.
> >
> >It seems to have an awful lot of mysql processes running when it's up. The
> >mysql version is 3.21.33b. Here lately, we've also been getting kernal
> >panic messages. The kernal version is 2.0.36. (Am I spelling kernal
> >right?) Yes, I know it's as old as hell, should have been upgraded, yadda,
> >yadda, yadda. That would be the client's call, and their option was just
> >to replace the whole box, but they can't seem to locate the people who did
> >the old machine, and we're kind of running out of time.
> >
> >Question is; has anyone come across a problem like this, and was there a
> >solution? It looks like it may be possible that the mysql processes aren't
> >getting killed after users log out, but I may be wrong.
> >
> >Any suggestions would be appreciated.
> >
> >-Sage
> >
> >--
> >To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message
> >body.
>
>The difficult while you wait.....the impossible overnight.
>
>Leonard Thornton
>Intelis, Inc.
>5960 Crooked Creek Rd
>Suite 30
>Norcross, GA  30092
>
>Office: 770.825.0032
>Fax:            770.825.0028
>Cellular:       404.583.5402
>Pager:          888.785.9188
>Email:          Leonard at Intelis-Inc.net
>
>--
>To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message 
>body.


The difficult while you wait.....the impossible overnight.


Leonard Thornton
Intelis, Inc.
5960 Crooked Creek Rd
Suite 30
Norcross, GA  30092


Office: 770.825.0032
Fax:            770.825.0028
Cellular:       404.583.5402
Pager:          888.785.9188
Email:          Leonard at Intelis-Inc.net


--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.

More information about the Ale mailing list