• Post Reply Bookmark Topic Watch Topic
  • New Topic

Starting MySQL in RedHat  RSS feed

 
David O'Meara
Rancher
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Was going to post this in JDBC, but here is probably better.
So, how do you do it
I've read instructions and config files and run scripts and wandered directories and verified stuff and now I feel like I've done enough to come and say I'm stumped, I got nothin'.
It's just the default install of MySQL that comes with RedHat 7.1, sorry I can't report the error, but attempting to start the daemon just... stops it again.
 
Frank Carver
Sheriff
Posts: 6920
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
OK, you can't supply us with an error, but can you clarify the following for us:
1. Which version of MySQL you are using.
2. Where it is installed in your file system
3. Which ways of starting it you have already tried, and what happened in each case.

thanks.
 
Mark Fletcher
Ranch Hand
Posts: 897
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
David,
Have you tried using the commands mysqld or safe_mysqld? Could you try running those commands and sending us the output?
Cheers,
Mark
 
Tim Holloway
Saloon Keeper
Posts: 18799
74
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As root:
/sbin/service mysqld start
Assuming you've installed MySQL as an RPM. You might also want to use the control panel or /sbin/chkconfig utilities to make it come up at system boot.
 
David O'Meara
Rancher
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just a quick update - I'm currently blaming 'user error' for my problems. (aka the ID-Ten-T error) I'm guessing I bloke MySQL while trying to start it.
I removed then reinstalled it and managed to get it running, but then broke it again and now I can't get gnorpm running

Luckily this is what I designed this machine for (ie breaking and doing a complete re-install) so this might be the next step
 
Tim Holloway
Saloon Keeper
Posts: 18799
74
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
1. mount the RedHat binary CD 1
From the command line, as root:
ls /mnt/cdrom/RedHat/RPMS/gnorpm*
If you don't get a filename back, eject CD 1
/usr/bin/eject /mnt/cdrom
And mount binary CD 2
rpm -uvh --force /mnt/cdrom/RedHat/RPMS/gnorpm-0.96.11-1.i386.rpm
(use whatever name you got from "ls")
If if fails, saying gnorpm's not installed repeat:
rpm -ivh --force /mnt/cdrom/RedHat/RPMS/gnorpm-0.96.11-1.i386.rpm
You can also do some testing for broken parts via
rpm -V gnorpm
BTW, if you're not running as root, neither rpm nor gnorpm are going to work, since the rpm database is protected!
 
David O'Meara
Rancher
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks, I'll try it tonight.
Interestingly, I get the same error or gnorpm, gnorpm-auth and kpackage, but don't get that error for any other apps

I'll have a serach on the net today and try repairing gnoprm tonight.
Oh, the error is
memory alloc (1911175664 bytes) returned NULL
but I'll go do a search...
 
David O'Meara
Rancher
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just to continue the story, it appears to be a much bigger problem with the computer. It still only shows up in rpm related activities (failed to reinstall gnorpm or mysql via the command line)
It now appears that the original problems may be related to a bad power supply that resulted in a corrupted file system (methinks) and has now become quite a significant problem rather than a wierd hard-to-diagnose one.
Maybe I should fix that first.
I'm still not ruling out user error though.
 
Tim Holloway
Saloon Keeper
Posts: 18799
74
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'd test that RAM, too - did you notice how much it's attempting to get?!
Since you have serveral different programs which look to be trying the same thing with the same bad results, check the RAM, do a surface-test check on the disk, and either re-install or at least do an rpm -Va so you have a known good OS.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!