am running CentOs with whm/cpanel and am whenever i reboot my server all sites that required mysql show erros ( can't connect ) it resolves by manually in the web host manager restarting mysql.
I already tried
chkconfig mysql on
then rebooted and the error persists,
I'm having troubles starting up MySQL. When I run..
# service mysqld start
I get..
Starting MySQL................................... [FAILED]
So I ran..
# ps aux | grep mysql
And did kill -9 for the running processes. When I try to run..
# service mysqld stop
I get the error..
MySQL PID file could not be found! [FAILED]
So I don't really know what to do. Does anyone have any advice about how I could resolve this issue?
I have problem getting my mysql server to start. Below is my my.cnf and mysql.log. I wonder if anyone can see what might the problem be.
P4 3Ghz w/ 1GB memory
Centos 4
my.cnf
[mysqld]
innodb_data_file_path=ibdata1:10M:autoextend
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
[mysql.server]
user=mysql
basedir=/var/lib
[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
[root@s198 etc]# tail -20 /var/log/mysqld.log
070418 12:16:42 InnoDB: Starting shutdown...
070418 12:16:43 InnoDB: Shutdown completed
070418 12:16:43 /usr/libexec/mysqld: Shutdown Complete
070418 12:16:43 mysqld ended
070418 12:16:58 mysqld started
070418 12:16:58 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start allocating memory from the OS.
InnoDB: You may get better performance if you configure a bigger
InnoDB: value in the MySQL my.cnf file for
InnoDB: innodb_additional_mem_pool_size.
070418 12:16:59 InnoDB: Started
/usr/libexec/mysqld: ready for connections
[root@s198 etc]#
Sudden on my server is started getting this error relating sql
Lost connection to MySQL server during query
When i do service mysql start i get the error
/etc/init.d/mysql start
Starting MySQL................................... [FAILED]
I'm having a bit of trouble here with MySQL, I don't know what to do. Centos 4.3, Mysql 4.1
Data is stored in /var/lib/mysql/
I'm looking to move that information to a second hard drive soon, and did a quick test of just copying it to another place on my existing drive. It won't start.
Quote:
[root@localhost ~]# service mysqld start
Timeout error occurred trying to start MySQL Daemon.
Starting MySQL: [FAILED]
Error logs
Code:
071106 12:14:33 mysqld started
071106 12:14:33 [Warning] Can't create test file /var/lib/mysqltf/localhost.lower-test
/usr/libexec/mysqld: Can't change dir to '/var/lib/mysqltf/' (Errcode: 13)
071106 12:14:33 [ERROR] Aborting
071106 12:14:33 [Note] /usr/libexec/mysqld: Shutdown complete
071106 12:14:33 mysqld ended
071106 12:17:00 mysqld started
071106 12:17:00 [Warning] Can't create test file /var/lib/mysqltf/localhost.lower-test
/usr/libexec/mysqld: Can't change dir to '/var/lib/mysqltf/' (Errcode: 13)
071106 12:17:00 [ERROR] Aborting
071106 12:17:00 [Note] /usr/libexec/mysqld: Shutdown complete
071106 12:17:00 mysqld ended
I have tried even chmod 777ing the msyqltf folder (my copy) to no avail.
my.cnf
Code:
[mysqld]
datadir=/var/lib/mysqltf/
socket=/var/lib/mysqltf/mysql.sock
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
[mysql.server]
user=mysql
basedir=/var/lib
[mysqld_safe]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
I've tried moving it to different locations. I even tried moving the original folder and renaming it, and still get this problem.
What could I fix by trying to start mysql server, recieve following errors:
plesk interface:
Code:
Failed to restart the "mysql" service.
Cannot start/stop/restart service: Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service mysql restart
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the stop(8) and then start(8) utilities,
e.g. stop mysql ; start mysql. The restart(8) utility is also available.
start: Job failed to start
from the console:
Code:
sudo service mysql start
start: Job failed to start
Code:
mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
output of plesk_11.5.30_reset_instance_data.log:
[Code] ...
see this screen shot:[url]
I used WHM to mount a spare partition and when the machine next rebooted, it give this error, nothing has been put on the disk as of yet.
Has anyone here been successful in doing a usb boot of windows xp & win2k3 server?
View 3 Replies View RelatedI've supposedly set APF firewall to start at boot time, by doing something like:
chkconfig --levels 2345 apf on
However i have my reservations to weather it is actually starting, its set to block port 80, after boot if i try and access it, the connection will get refused straight away, however if i go and manually start APF then try and access again, it will take a while, like its ignoring the connection attempt (which is good).
How could I check if APF is actually running?
How We can set a shoutcast servers to starts automatically on boot/restart/etc?
View 14 Replies View RelatedI have a problem on my dedicated server, the boot is at 99% but i am not sure
how to fix this problem.
The server runs centos 4.5 final.
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 228G 17G 199G 8% /
/dev/sda1 31M 29M 492K 99% /boot
I'm trying to put together a new 1U rackmount server that I'm intending to colocate (my first server of my own). Here are the details:
11-152-087 CHASSIS SUPERMICRO|CSE-512L-260B R
13-182-120 SERVER_MB SUPERMICRO|MBD-PDSML-LN2+
22-144-417 HD 250G|WD 7K 8M SATA2 WD2500JS
19-115-029 CPU INTEL|C2D E6750 2.66G 65N 4M R
20-134-337 MEM 1Gx2|KST KVR667D2E5K2/2G R
The stock CPU fan is obviously too big to sit in a 1U rackmount chassis, but I've got the top off and was just trying to boot up with the OEM fan to make certain everything worked (forgot to order a low-profile fan and heatsink--they're on the way).
Well, I put everything together, and it won't boot. Upon power up, there is nothing sent to the VGA port, and after a second or two, there is a hi-low alarm sound that does not stop that seems to imply the system is overheating (the MB and chassis manuals don't mention this alarm anywhere, but the read "temperature" light on the front is red). The CPU fan runs as well as the case fan, and even if I hold a huge high-velocity home fan over it, it still won't send any signal to the VGA monitor or POST.
I've checked that the power connections are good, the fans are seated properly, the memory contact is good, etc., and all I get is this hi-low chime every time I try to boot up. I think it's either a bad MB or CPU, since I can't imagine that the CPU is overheating with the heat sink and CPU fan.
Perhaps I've screwed something up, but the next issue I have is trying to figure out what could be causing the problem so I know what to return or replace. Is it the CPU? MB? RAM? Power unit? How can I test any of these without buying another set and possibly frying those?
I figured maybe some of you might have some ideas. I've built several computers over the years, but this one has me completely stymied.
This is probably the wrong location for this thread but I am unsure which section it is best located at.
I have 2 hard drives - 1 has XP pro installed (master drive) on it and the other is blank and set to slave. On the blank one i intedn to install Red Hat linux.
How is the best way to create a dual boot with these machines if each hard drive has one O/S dedicated to it.
I'm not sure exactly how to phrase the question. But, I'm researching how to PXE boot a server without having a DHCP/PXE server in each vlan.
Scenario: Datacenter with dozens of servers. 1 VLAN per server. Cisco switches and routers. Each server has a serial console available for remote management (OS and BIOS are configured for serial console). If an admin wants to re-install OS, they should be able to reboot the server and tell the BIOS to initiate a PXE boot request. A central install server is available to provide the DHCP and PXE boot images.
Has anyone tried this? I have been reading about the 'ip helper-address' for Cisco to relay DHCP requests. Interested in hearing about real-world setups. Or is there a better way to accomplish remote OS installs?
We cannot figure out why our dedicated server will not boot to the correct kernel. I've removed all other options from grub.conf but it's still booting to the default CentOS setup.
grub.conf:
Code:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,0)
# kernel /boot/vmlinuz-version ro root=/dev/mapper/ddf1_4c53492020202020808627c300000000378494a900000a28p1
# initrd /boot/initrd-version.img
#boot=/dev/mapper/ddf1_4c53492020202020808627c300000000378494a900000a28
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-028stab062.3)
root (hd0,0)
kernel /boot/vmlinux-2.6.18-028stab062.3 ro root=LABEL=/
initrd /boot/initrd-2.6.18-028stab062.3.img
Code:
uname -r
2.6.18-128.el5
I've got Centos 4 and I'm wondering what's the best way to cleanup my /boot partition?
Tried to do a yum update tonight and it included kernel, amongst other updates that belonged there so it stopped. I've googled around for commands to run and whatnot, but no go... or I just can't find it... if I had to clean it up I have an idea already about what to do, but I want to ask for advice first to see if there's an easier way.
so, how do people here clean up that partition?
I have a NAS to mount but it disappears on every (re)boot. How do I automatically mount it on boot?
View 4 Replies View Relatedon a RHE 3 system I installed a new Kernel. I did update lilo.conf and grub.conf but they are still booting an old kernel: 2.4.21-27.ELsmp. Please have a look at my files below and if you have any idea why please let me know.
lilo.conf:
prompt
timeout=50
default=2.4.21-53.ELsmp
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear
image=/boot/vmlinuz-2.4.21-53.ELsmp
label=2.4.21-53.ELsmp
initrd=/boot/initrd-2.4.21-53.ELsmp.img
read-only
append="root=/dev/hda3"
image=/boot/vmlinuz-2.4.21-47.ELsmp
label=2.4.21-47.ELsmp
initrd=/boot/initrd-2.4.21-47.ELsmp.img
read-only
append="root=/dev/hda3"
image=/boot/vmlinuz-2.4.21-47.EL
label=2.4.21-47.EL
initrd=/boot/initrd-2.4.21-47.EL.img
read-only
append="root=/dev/hda3"
image=/boot/vmlinuz-2.4.21-27.ELsmp
label=linux
initrd=/boot/initrd-2.4.21-27.ELsmp.img
read-only
append="root=/dev/hda3"
image=/boot/vmlinuz-2.4.21-27.EL
label=linux-up
initrd=/boot/initrd-2.4.21-27.EL.img
read-only
append="root=/dev/hda3"
grub.conf:
Code:
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Enterprise Linux ES (2.4.21-53.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-53.ELsmp ro root=/dev/hda3
initrd /initrd-2.4.21-53.ELsmp.img
title Red Hat Enterprise Linux ES (2.4.21-47.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-47.ELsmp ro root=/dev/hda3
initrd /initrd-2.4.21-47.ELsmp.img
title Red Hat Enterprise Linux ES (2.4.21-47.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-47.EL ro root=/dev/hda3
initrd /initrd-2.4.21-47.EL.img
title Red Hat Enterprise Linux ES (2.4.21-27.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-27.ELsmp ro root=LABEL=/
initrd /initrd-2.4.21-27.ELsmp.img
title Red Hat Enterprise Linux ES-up (2.4.21-27.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-27.EL ro root=LABEL=/
initrd /initrd-2.4.21-27.EL.img
Just asking, where should I usually install my boot loader:
/dev/sda - master boot record (MBR)
-- or --
/dev/sda1 - first sector of boot partition
My partition for /sda1/ is /boot 100MB
I have an old server with only IDE and SCSI connectors on the mobo.
However, I have only SATA drives and no IDE available. I consider to buy an entry level PCI SATA adapter card. What do you think ? Can I install and boot Linux directly from it?
There is no raid involved.
I have insalled windows in hda and linux on hdb, but after I installed grub loader it is coming to grub prompt as this:
grub>
someone suggested to do the follwing comand
root (hd0,0)
kernel /boot/vmlinux....
boot
I am not sure about this this line:
root (hd0,0)
What exactly trying to do?
Right after booting from HP-UX PA-RISC, Tomcat refuses connections.
Trouble Description:
No startup error messages are logged and processes are up and running.
Checking /etc/rc.log:
----------------------------
Starting Tomcat server
Output from "/sbin/rc3.d/S998Tomcat start":
----------------------------
Using CATALINA_BASE: /opt/mediation/Tomcat5.5
Using CATALINA_HOME: /opt/mediation/Tomcat5.5
Using CATALINA_TMPDIR: /opt/mediation/Tomcat5.5/temp
Using JRE_HOME: /opt/mediation/java/jre15_15002
/opt/mediation/Tomcat5.5/bin/catalina.sh[233]: touch: not found.
----------------------------
If Tomcat is manually stopped and restarted, it accepts connections.
I have set up Windows Small Business Server 2003 and was testing it over the past week. Everything has been going well and yesterday it requested to install an update (not to sure what it was now) and soon after the update was installed a restart was required.
After the server shutdown and tried to restart the system will not restart.
The machine powers up and then I am faced with a blank black screen (no load bar nothing). The monitor led light flashes from green to orange then to a static green light after the Dell splash screen.
I can load up into safe mode although I do not know how to work out what is wrong. I am guessing the update has caused the issue, possibly a boot sector needs repairing. There are no new additions to control panel -> install/remove programs which i believe is where all updates can be uninstalled from.
I backed a system up with rsync, and just used rsync to copy it into a new machine... I just backed up / to my home directory on another machine, and then 'extracted' it to / on the new machine.
But now everything (and I mean everything) is owned by "matt", my user on the intermediate machine. I rebooted the system to get it to boot the new stuff without realizing this, and now it's not booting... Since /etc/passwd, /bin/bash, etc. aren't owned by root.
Any tips on where to go from here? As I said, it's a brand-new machine (VM, actually: even better!), so re-imaging is a solution, but I'd still have to copy the data back over. Reinstalling is a pain, though, so if there's a simple fix, I'd prefer that. I've got pygrub installed as a boot manager for the VM, but I can't for the life of me figure out how to get into single-user mode. (Nor am I sure that a "cd /; chown -R root" will have the desired effect?)
After installing Kernels seems /boot is boing to be full soon. Which files can be safely deleted ? Mean lets say to keep the latest Kernel and previous version:
root@[/boot]# ls -la
total 70317
drwxr-xr-x 4 root root 3072 Dec 4 11:28 ./
drwxr-xr-x 22 root root 4096 Sep 29 10:41 ../
-rwxr--r-- 1 root root 6144 Nov 9 2006 aquota.user*
-rw-r--r-- 1 root root 48736 Sep 28 2005 config-2.4.21-37.EL
-rw-r--r-- 1 root root 48851 Sep 28 2005 config-2.4.21-37.ELsmp
-rw-r--r-- 1 root root 48951 Oct 19 2006 config-2.4.21-47.0.1.EL
-rw-r--r-- 1 root root 49066 Oct 19 2006 config-2.4.21-47.0.1.ELsmp
-rw-r--r-- 1 root root 49066 Aug 1 2006 config-2.4.21-47.ELsmp
-rw-r--r-- 1 root root 48951 Jun 11 18:29 config-2.4.21-50.EL
-rw-r--r-- 1 root root 49066 Jun 11 18:21 config-2.4.21-50.ELsmp
-rw-r--r-- 1 root root 48951 Aug 16 17:11 config-2.4.21-51.EL
-rw-r--r-- 1 root root 49066 Aug 16 17:03 config-2.4.21-51.ELsmp
-rw-r--r-- 1 root root 48951 Sep 27 18:38 config-2.4.21-52.EL
-rw-r--r-- 1 root root 49066 Sep 27 18:30 config-2.4.21-52.ELsmp
-rw-r--r-- 1 root root 48951 Dec 3 13:51 config-2.4.21-53.EL
-rw-r--r-- 1 root root 49066 Dec 3 13:42 config-2.4.21-53.ELsmp
drwxr-xr-x 2 root root 1024 Dec 4 11:28 grub/
-rw-r--r-- 1 root root 276201 May 5 2006 initrd-2.4.21-37.EL.img
-rw-r--r-- 1 root root 283119 May 5 2006 initrd-2.4.21-37.ELsmp.img
-rw-r--r-- 1 root root 282640 Apr 10 2007 initrd-2.4.21-47.0.1.EL.img
-rw-r--r-- 1 root root 289544 Oct 21 2006 initrd-2.4.21-47.0.1.ELsmp.img
-rw-r--r-- 1 root root 289539 Sep 23 2006 initrd-2.4.21-47.ELsmp.img
-rw-r--r-- 1 root root 282779 Jun 26 22:04 initrd-2.4.21-50.EL.img
-rw-r--r-- 1 root root 289656 Jun 26 22:03 initrd-2.4.21-50.ELsmp.img
-rw-r--r-- 1 root root 282783 Aug 21 05:32 initrd-2.4.21-51.EL.img
-rw-r--r-- 1 root root 289652 Aug 21 05:32 initrd-2.4.21-51.ELsmp.img
-rw-r--r-- 1 root root 282781 Sep 28 08:22 initrd-2.4.21-52.EL.img
-rw-r--r-- 1 root root 289649 Sep 28 08:23 initrd-2.4.21-52.ELsmp.img
-rw-r--r-- 1 root root 282778 Dec 4 11:27 initrd-2.4.21-53.EL.img
-rw-r--r-- 1 root root 289653 Dec 4 11:28 initrd-2.4.21-53.ELsmp.img
-rw-r--r-- 1 root root 547 May 5 2006 kernel.h
drwx------ 2 root root 12288 May 5 2006 lost+found/
-rw-r--r-- 1 root root 10213 Jan 4 2005 message
-rw-r--r-- 1 root root 10213 Jan 4 2005 message.ja
-rwxr--r-- 1 root root 32 Nov 9 2006 quota.user*
lrwxrwxrwx 1 root root 26 Sep 29 09:37 System.map -> System.map-2.4.21-52.ELsmp
-rw-r--r-- 1 root root 578588 Sep 28 2005 System.map-2.4.21-37.EL
-rw-r--r-- 1 root root 606073 Sep 28 2005 System.map-2.4.21-37.ELsmp
-rw-r--r-- 1 root root 580154 Oct 19 2006 System.map-2.4.21-47.0.1.EL
-rw-r--r-- 1 root root 607622 Oct 19 2006 System.map-2.4.21-47.0.1.ELsmp
-rw-r--r-- 1 root root 607622 Aug 1 2006 System.map-2.4.21-47.ELsmp
-rw-r--r-- 1 root root 580321 Jun 11 18:29 System.map-2.4.21-50.EL
-rw-r--r-- 1 root root 607789 Jun 11 18:21 System.map-2.4.21-50.ELsmp
-rw-r--r-- 1 root root 580321 Aug 16 17:11 System.map-2.4.21-51.EL
-rw-r--r-- 1 root root 607789 Aug 16 17:03 System.map-2.4.21-51.ELsmp
-rw-r--r-- 1 root root 580321 Sep 27 18:38 System.map-2.4.21-52.EL
-rw-r--r-- 1 root root 607789 Sep 27 18:30 System.map-2.4.21-52.ELsmp
-rw-r--r-- 1 root root 580321 Dec 3 13:51 System.map-2.4.21-53.EL
-rw-r--r-- 1 root root 607789 Dec 3 13:42 System.map-2.4.21-53.ELsmp
-rwxr-xr-x 1 root root 2908624 Sep 28 2005 vmlinux-2.4.21-37.EL*
-rwxr-xr-x 1 root root 3543696 Sep 28 2005 vmlinux-2.4.21-37.ELsmp*
-rwxr-xr-x 1 root root 2912724 Oct 19 2006 vmlinux-2.4.21-47.0.1.EL*
-rwxr-xr-x 1 root root 3551892 Oct 19 2006 vmlinux-2.4.21-47.0.1.ELsmp*
-rwxr-xr-x 1 root root 3551888 Aug 1 2006 vmlinux-2.4.21-47.ELsmp*
-rwxr-xr-x 1 root root 2912720 Jun 11 18:29 vmlinux-2.4.21-50.EL*
-rwxr-xr-x 1 root root 3551888 Jun 11 18:21 vmlinux-2.4.21-50.ELsmp*
-rwxr-xr-x 1 root root 2912720 Aug 16 17:11 vmlinux-2.4.21-51.EL*
-rwxr-xr-x 1 root root 3551888 Aug 16 17:03 vmlinux-2.4.21-51.ELsmp*
-rwxr-xr-x 1 root root 2912720 Sep 27 18:38 vmlinux-2.4.21-52.EL*
-rwxr-xr-x 1 root root 3551888 Sep 27 18:30 vmlinux-2.4.21-52.ELsmp*
-rwxr-xr-x 1 root root 2912720 Dec 3 13:51 vmlinux-2.4.21-53.EL*
-rwxr-xr-x 1 root root 3551888 Dec 3 13:42 vmlinux-2.4.21-53.ELsmp*
-rw-r--r-- 1 root root 1252609 Sep 28 2005 vmlinuz-2.4.21-37.EL
-rw-r--r-- 1 root root 1363969 Sep 28 2005 vmlinuz-2.4.21-37.ELsmp
-rw-r--r-- 1 root root 1260075 Oct 19 2006 vmlinuz-2.4.21-47.0.1.EL
-rw-r--r-- 1 root root 1368141 Oct 19 2006 vmlinuz-2.4.21-47.0.1.ELsmp
-rw-r--r-- 1 root root 1367751 Aug 1 2006 vmlinuz-2.4.21-47.ELsmp
-rw-r--r-- 1 root root 1260875 Jun 11 18:29 vmlinuz-2.4.21-50.EL
-rw-r--r-- 1 root root 1370368 Jun 11 18:21 vmlinuz-2.4.21-50.ELsmp
-rw-r--r-- 1 root root 1260877 Aug 16 17:11 vmlinuz-2.4.21-51.EL
-rw-r--r-- 1 root root 1370369 Aug 16 17:03 vmlinuz-2.4.21-51.ELsmp
-rw-r--r-- 1 root root 1260879 Sep 27 18:38 vmlinuz-2.4.21-52.EL
-rw-r--r-- 1 root root 1370369 Sep 27 18:30 vmlinuz-2.4.21-52.ELsmp
-rw-r--r-- 1 root root 1260893 Dec 3 13:51 vmlinuz-2.4.21-53.EL
-rw-r--r-- 1 root root 1370450 Dec 3 13:42 vmlinuz-2.4.21-53.ELsmp
root@[/boot]#
This is the /etc/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda2
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title CentOS (2.4.21-53.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-53.ELsmp ro root=LABEL=/
initrd /initrd-2.4.21-53.ELsmp.img
title CentOS (2.4.21-53.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-53.EL ro root=LABEL=/
initrd /initrd-2.4.21-53.EL.img
title CentOS (2.4.21-52.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-52.ELsmp ro root=LABEL=/
initrd /initrd-2.4.21-52.ELsmp.img
title CentOS (2.4.21-52.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-52.EL ro root=LABEL=/
initrd /initrd-2.4.21-52.EL.img
title CentOS (2.4.21-51.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-51.ELsmp ro root=LABEL=/
initrd /initrd-2.4.21-51.ELsmp.img
title CentOS (2.4.21-51.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-51.EL ro root=LABEL=/
initrd /initrd-2.4.21-51.EL.img
title CentOS (2.4.21-50.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-50.EL ro root=LABEL=/
initrd /initrd-2.4.21-50.EL.img
title CentOS (2.4.21-50.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-50.ELsmp ro root=LABEL=/
initrd /initrd-2.4.21-50.ELsmp.img
title CentOS (2.4.21-47.0.1.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-47.0.1.EL ro root=LABEL=/
initrd /initrd-2.4.21-47.0.1.EL.img
title CentOS (2.4.21-47.0.1.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-47.0.1.ELsmp ro root=LABEL=/
initrd /initrd-2.4.21-47.0.1.ELsmp.img
title CentOS (2.4.21-47.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-47.ELsmp ro root=LABEL=/
initrd /initrd-2.4.21-47.ELsmp.img
title CentOS-3 (2.4.21-37.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-37.ELsmp ro root=LABEL=/
initrd /initrd-2.4.21-37.ELsmp.img
title CentOS-3-up (2.4.21-37.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-37.EL ro root=LABEL=/
initrd /initrd-2.4.21-37.EL.img
Could someone please help me with:
1.) the command line to hard power off a VM that has frozen up
2.) the command line to boot a VM linking to its config file
I have a problem about my server, after it is unsuspended, it is not actually working anymore.
I got kvm access, when i try to choose harddisk for boot option it says INIT: No inittab file found
and asks for runlevel : I tried 1,2,6 but none of them are working.
I am choosing the rescue mode than it is asking me for rescued login which i don`t know
I've exausted my self attempting to load on a boot image to the management blade for a project that i'm doing with a few friends.
I just bought this Foundary *off ebay of course* and who ever had it last removed the image! I mean I cant even get into the primary or secondary. I tried booting from tftp, but everytime that happens, the switch just restarts and then doesnt boot up again. This is what i'm getting.
Code:
BOOT INFO: RESET ANY
master arbitrate : become primary arbitrator.
BOOT INFO: Become active CPU module
M2 BI Boot Code Version 06.05.00
Enter 'b' to go to boot monitor ...
BOOT INFO: load from primary copy
BOOT ERR: bad code image header
BOOT INFO: load from secondary copy
BOOT ERR: bad code image header
BOOT INFO: try to boot from bootp server
bootp timed out, bootp-tftp process aborted!
BOOT ERR: bootp failed
I currently have the B2R07601b.BIN image, just I dont know how to load the file onto the blade via tftp or any other method.
I've software RAID installed with one SATA and one ATA/IDE drive. It is a combined controller so I had to add noprobe=/dev/hdc to the kernel boot line. Now the disks are named /dev/sda and /dev/sdb. There are four partitions, /dev/sda1 and /dev/sdb1 are the /dev/md0 root partition and then /dev/sda2 and /dev/sdb2 are the swap partition.
First when I removed one drive I just came to the grub command line..
Then I tried to do this in grub to make both drives bootable:
grub>device (hd0) /dev/sda
grub>root (hd0,0)
grub>setup (hd0)
grub>device (hd1) /dev/sdb
grub>root (hd1,0)
grub>setup (hd1)
grub>quit
Now it looks like normal when I get to grub apart from that the background of the boot screen is black instead of blue and then the computer just restarts when it is supposed to start/boot the system.