Strange indeed.
Tried remotely, no go. I removed the server from the rack, only to find
that there was only one kernel listed in the grub menu. I tried to edit
it pointing it to the new kernel to no avail. It says file not found
and I had to revert back to the old kernel. Where is the QMT grub
getting it's config from? /boot/grub/grub.conf simply can't be.
At this point I am not going to waste my time with it. I am curious
why, but don't have time to deal with it and I'm migrating from this
server to another anyways. The primary has updated correctly and is
current on all fronts including Spamdyke.
I will likely set up this server as a back up or retire it as I have
enough hardware (primary and backup) up and running with my new config
to suit my current needs.
Thanks for all you help.
CJ
Maxwell Smart wrote:
> Clean install on formatted drive. Only QMT ISO installed.
>
> It's headless so without removing it from the rack, not easily.
>
> I just changed the default to 1 and then 2, no change.
>
> I'll either pull it out of the rack or try to reinstall grub remotely.
>
> Eric Shubert wrote:
>
>> Very strange. Perhaps there's something else going on with that hard
>> drive that we're not seeing. Any other partitions on it? Was there
>> ever any other boot loader on it?
>>
>> Are/can you seeing the grub boot menu when it boots? What does it list?
>>
>> I might try reinstalling grub in the mbr, but only after I thought
>> there was some reason it might fix something. This definitely sounds
>> like a grub misconfiguration issue. (duh)
>>
>> Maxwell Smart wrote:
>>
>>> The /boot/grub/grub.conf file reads the same. The other 2 are both
>>> symlinks as expected.
>>>
>>> It has been rebooted and is still loading the old kernel. I also
>>> removed the lines in the grub.conf file referring to the -92 kernel and
>>> it still boots to the -92 kernel.
>>> [r...@mail ~]# rpm -qa kernel
>>> kernel-2.6.18-128.1.10.el5
>>> kernel-2.6.18-92.1.13.el5
>>> kernel-2.6.18-128.2.1.el5
>>> kernel-2.6.18-128.4.1.el5
>>> kernel-2.6.18-92.1.22.el5
>>>
>>>
>>> Eric Shubert wrote:
>>>
>>>> Maxwell Smart wrote:
>>>>
>>>>> Eric,
>>>>>
>>>>> Everything worked as expected.
>>>>>
>>>> Glad to hear it.
>>>>
>>>>
>>>>> However, I have a second mail server that I just updated and wanted
>>>>> to install all of the latest updates. It required I update the
>>>>> kernel. I updated the kernel, but it still boots to the previous
>>>>> kernel. How do I change the default kernel that it boots to?
>>>>> This will allow me to update the simscan and install the Spamdyke
>>>>> making both of my servers identical.
>>>>>
>>>>> I know it's late, but theses look all the same to me. How do I know
>>>>> which one is default=0? Default=0 is the first one listed correct?
>>>>>
>>>> Correct. Grub is consistently "relative to zero".
>>>>
>>>>
>>>>> uname -a output
>>>>>
>>>>> Linux mail.area510.net 2.6.18-92.1.13.el5 #1 SMP Wed Sep 24 19:33:52
>>>>> EDT 2008 i686 athlon i386 GNU/Linux
>>>>>
>>>>> grub.conf
>>>>>
>>>>> #boot=/dev/hda
>>>>>
>>>>> default=0
>>>>> timeout=5
>>>>> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
>>>>> hiddenmenu
>>>>> title CentOS (2.6.18-128.4.1.el5)
>>>>> root (hd0,0)
>>>>> kernel /boot/vmlinuz-2.6.18-128.4.1.el5 ro root=LABEL=/
>>>>> initrd /boot/initrd-2.6.18-128.4.1.el5.img
>>>>> title CentOS (2.6.18-128.2.1.el5)
>>>>> root (hd0,0)
>>>>> kernel /boot/vmlinuz-2.6.18-128.2.1.el5 ro root=LABEL=/
>>>>> initrd /boot/initrd-2.6.18-128.2.1.el5.img
>>>>> title CentOS (2.6.18-128.1.10.el5)
>>>>> root (hd0,0)
>>>>> kernel /boot/vmlinuz-2.6.18-128.1.10.el5 ro root=LABEL=/
>>>>> initrd /boot/initrd-2.6.18-128.1.10.el5.img
>>>>> title CentOS (2.6.18-92.1.22.el5)
>>>>> root (hd0,0)
>>>>> kernel /boot/vmlinuz-2.6.18-92.1.22.el5 ro root=LABEL=/
>>>>> initrd /boot/initrd-2.6.18-92.1.22.el5.img
>>>>> title Sonia (2.6.18-92.1.13.el5)
>>>>> root (hd0,0)
>>>>> kernel /boot/vmlinuz-2.6.18-92.1.13.el5 ro root=LABEL=/
>>>>> initrd /boot/initrd-2.6.18-92.1.13.el5.img
>>>>>
>>>> That looks correct to me. If your system has been rebooted and it's
>>>> still rebooting to 2.6.18-92.1.13 (the oldest kernel in the list btw),
>>>> then grub isn't using this grub.conf file. My guess would be that one
>>>> of your symlinks is a normal file instead of a symlink, which is
>>>> preventing grub from seeing this file.
>>>>
>>>> A normal CentOS5 configuration will have:
>>>> [r...@doris ~]# ls -l /etc/grub.conf
>>>> lrwxrwxrwx 1 root root 22 May 30 2008 /etc/grub.conf ->
>>>> ../boot/grub/grub.conf
>>>> [r...@doris ~]# ls -l /boot/grub/menu.lst
>>>> lrwxrwxrwx 1 root root 11 May 30 2008 /boot/grub/menu.lst ->
>>>> ./grub.conf
>>>> [r...@doris ~]# ls -l /boot/grub/grub.conf
>>>> -rw------- 1 root root 1138 Aug 3 15:48 /boot/grub/grub.conf
>>>>
>>>> The /boot/grub/grub.conf file is the real file. If one of the other 2
>>>> is a file instead of a symlink pointing to the real file, there is
>>>> your problem. Be careful when you fix it that you don't lose the
>>>> updated configuration.
>>>>
>>>>
>>>>> Eric Shubert wrote:
>>>>>
>>>>>> Maxwell Smart wrote:
>>>>>>
>>>>>>> Perfect.
>>>>>>>
>>>>>>> If I use the qmailtoaster-plus to install Spamdyke, do the default
>>>>>>> config settings work for starters?
>>>>>>>
>>>>>> Yes. (that's why they're the default)
>>>>>>
>>>>>>
>>>>>>> Is is easy to undo if it doesn't work correctly?
>>>>>>>
>>>>>> Yes. Instructions are on the wiki page for spamdyke. You should read
>>>>>> that page regardless.
>>>>>>
>>>>>>
>>>>>>> I am using QMT ISO 5.3 with all the current updates and no real
>>>>>>> config changes. It works just fine right out of the box for my
>>>>>>> needs.
>>>>>>>
>>>>>> So will spamdyke.
>>>>>>
>>>>>> There is one setting in /etc/spamdyke/spamdyke.conf
>>>>>> (reject-ip-in-cc-rdns) that I would uncomment if you're in the US
>>>>>> and don't get international email. That will reject emails with a
>>>>>> country code in the reverse DNS entry for the sending server. This
>>>>>> setting is commented out by default as a courtesy to our foreign and
>>>>>> international users.
>>>>>>
>>>>>>
>>>>>>> CJ
>>>>>>>
>>>>>>>
>>> ---------------------------------------------------------------------------------
>>>
>>> Qmailtoaster is sponsored by Vickers Consulting Group
>>> (www.vickersconsulting.com)
>>> Vickers Consulting Group offers Qmailtoaster support and
>>> installations.
>>> If you need professional help with your setup, contact them today!
>>> ---------------------------------------------------------------------------------
>>>
>>> Please visit qmailtoaster.com for the latest news, updates, and
>>> packages.
>>> To unsubscribe, e-mail:
>>> qmailtoaster-list-unsubscr...@qmailtoaster.com
>>> For additional commands, e-mail:
>>> qmailtoaster-list-h...@qmailtoaster.com
>>>
>>>
>>>
>>>
>>
>
> ---------------------------------------------------------------------------------
> Qmailtoaster is sponsored by Vickers Consulting Group
> (www.vickersconsulting.com)
> Vickers Consulting Group offers Qmailtoaster support and installations.
> If you need professional help with your setup, contact them today!
> ---------------------------------------------------------------------------------
> Please visit qmailtoaster.com for the latest news, updates, and packages.
>
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>
>
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
