Koozali.org: home of the SME Server

Cant VPN to server, where do i start trouble shooting

Offline janet

  • *****
  • 4,812
  • +0/-0
Re: Cant VPN to server, where do i start trouble shooting
« Reply #30 on: December 19, 2008, 12:05:35 AM »
ber

To set the correct default kernel (which should not unduly affect further investigation if required)

pico -w /boot/grub/grub.conf

change
default=7
to
default=1

to save, at the same time press ctrl o
to exit, at the same time press ctrl x

reboot your server and it should run the required default kernel
(ie the second kernel listed in grub.conf 0=1st 1=2nd & so on)

Beyond that, if your issues still persist, please do as chris suggests.
Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Offline ber

  • *****
  • 239
  • +0/-0
Re: Cant VPN to server, where do i start trouble shooting
« Reply #31 on: December 19, 2008, 12:15:51 AM »
 :P Mary, Hi, Im in the process of forwarding a detailed report in the bugs forum, as someone has advised the server "had" been using the latest kernel but for whatever reason is using an old one. Ill send all info and this particular thread to the developer team and see what they come up with. Pardon me for my ignorance- is the latest kernel option available on my server or does it need to be "downloaded". I may not be using the right terminology. Does the kernels Ive listed in the previous replies state that there is a latest version kerenel available on my server that I can use?
Is you latest reply/solution dealing with the issues Ive brought up?

Regards John

Offline janet

  • *****
  • 4,812
  • +0/-0
Re: Cant VPN to server, where do i start trouble shooting
« Reply #32 on: December 19, 2008, 12:26:01 AM »
ber

Back in reply #15
http://forums.contribs.org/index.php/topic,42858.msg203057.html#msg203057
you listed the contents of grub.conf, which indicated the latest kernel was listed, but the default setting was set to run a different kernel
My answer should correct that wrong setting, which may resolve your issues

You can see which kernels are actually installed with
rpm -q kernel kernel-smp

grub.conf is just a file that tells sme what to do when it starts up, and it does list all the available installed kernels to choose from.
It is normal to run the current latest kernel but some non standard situations require a different kernel to run. Try to avoid those situations as they only create problems when upgrading.
« Last Edit: December 19, 2008, 12:30:59 AM by mary »
Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Offline ber

  • *****
  • 239
  • +0/-0
Re: Cant VPN to server, where do i start trouble shooting
« Reply #33 on: December 19, 2008, 01:00:57 AM »
mary, sorry no luck heres some data from the server that may help...

login as: root
root@192.168.0.254's password:
Last login: Fri Dec 19 12:32:53 2008 from 192.168.0.153
[root@server ~]# cat /boot/grub/menu.lst
# 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/main/root
#          initrd /initrd-version.img
#boot=/dev/hda
default=7
timeout=5
splashimage=(hd0,0)/grub/smeserver.xpm.gz
foreground 000000
background 4E95D3
hiddenmenu
title SME Server (2.6.9-78.0.8.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-78.0.8.EL ro root=/dev/main/root
        initrd /initrd-2.6.9-78.0.8.EL.img
title SME Server (2.6.9-78.0.8.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-78.0.8.ELsmp ro root=/dev/main/root
        initrd /initrd-2.6.9-78.0.8.ELsmp.img
title SME Server (2.6.9-78.0.5.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-78.0.5.ELsmp ro root=/dev/main/root noapic noacpi
        initrd /initrd-2.6.9-78.0.5.ELsmp.img
title SME Server (2.6.9-78.0.5.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-78.0.5.EL ro root=/dev/main/root noapic noacpi
        initrd /initrd-2.6.9-78.0.5.EL.img
title SME Server (2.6.9-67.0.15.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.0.15.EL ro root=/dev/main/root
        initrd /initrd-2.6.9-67.0.15.EL.img
title SME Server (2.6.9-67.0.15.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.0.15.ELsmp ro root=/dev/main/root
        initrd /initrd-2.6.9-67.0.15.ELsmp.img
title SME Server (2.6.9-67.0.7.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.0.7.EL ro root=/dev/main/root
        initrd /initrd-2.6.9-67.0.7.EL.img
title SME Server (2.6.9-67.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.ELsmp ro root=/dev/main/root
        initrd /initrd-2.6.9-67.ELsmp.img
title SME Server (2.6.9-67.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-67.EL ro root=/dev/main/root
        initrd /initrd-2.6.9-67.EL.img
[root@server ~]# rpm -q kernel kernel-smp
kernel-2.6.9-67.EL
kernel-2.6.9-67.0.7.EL
kernel-2.6.9-67.0.15.EL
kernel-2.6.9-78.0.5.EL
kernel-2.6.9-78.0.8.EL
kernel-smp-2.6.9-67.EL
kernel-smp-2.6.9-67.0.15.EL
kernel-smp-2.6.9-67.0.20.EL
kernel-smp-2.6.9-78.0.5.EL
kernel-smp-2.6.9-78.0.8.EL
[root@server ~]#

Regards John

Offline janet

  • *****
  • 4,812
  • +0/-0
Re: Cant VPN to server, where do i start trouble shooting
« Reply #34 on: December 19, 2008, 01:13:46 AM »
ber

Quote
sorry no luck....

I don't really know what that means.
Please advise what you did.

If the listing you provide is the current status of the grub.conf file, then the default is still set to 7, so of course your system will boot the "wrong" kernel

Did you run
pico -w /boot/grub/grub.conf
and make the suggested change and ensure you saved the change and then rebooted ?

Use grub.conf and not menu.lst

You do appear to have the current kernel-2.6.9-78.0.8 installed

Here's the output from my system for comparison

rpm -q kernel kernel-smp

kernel-2.6.9-67.0.1.EL
kernel-2.6.9-67.0.4.EL
kernel-2.6.9-67.0.7.EL
kernel-2.6.9-78.0.8.EL
kernel-smp-2.6.9-67.0.1.EL
kernel-smp-2.6.9-67.0.4.EL
kernel-smp-2.6.9-67.0.7.EL
kernel-smp-2.6.9-78.0.8.EL

To see the kernel that is running do
uname -r
2.6.9-78.0.8.ELsmp
Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: Cant VPN to server, where do i start trouble shooting
« Reply #35 on: December 19, 2008, 02:19:10 AM »
To set the correct default kernel (which should not unduly affect further investigation if required)

pico -w /boot/grub/grub.conf

change
default=7
to
default=1

Mary, that's not necessary. SME server should always rewrite the default to the last-booted kernel. So all that should be required is to reboot by the desired kernel at the grub splash screen.

Offline pfloor

  • *****
  • 889
  • +1/-0
Re: Cant VPN to server, where do i start trouble shooting
« Reply #36 on: December 19, 2008, 02:45:27 AM »
Mary, that's not necessary. SME server should always rewrite the default to the last-booted kernel. So all that should be required is to reboot by the desired kernel at the grub splash screen.

The OP can't select the proper kernel and shows similar symptoms of this bug http://bugs.contribs.org/show_bug.cgi?id=4802 as the proper kernel is not listed on his splash screen.

ber, please follow up in that bug as your server seems to exhibit similar issues.
In life, you must either "Push, Pull or Get out of the way!"

Offline pfloor

  • *****
  • 889
  • +1/-0
Re: Cant VPN to server, where do i start trouble shooting
« Reply #37 on: December 19, 2008, 02:58:59 AM »
:P Hi Chris, I rebooted and was not able to find the kernel option that you recommended.

I did get the following options. I didnt choose any and supposed that I need to download the latest kernel..How?\
Here is the options that I do get...

Centos (2.6.9-67.ELsmp)
Centos (2.6.9-67. EL)
SME Server (2.6.9-55.0.12 EL)
SME Server (2.6.9-55.0.12. ELsmp)
SME Server (2.6.9-55.0.2. ELsmp)
SME Server-up (2.6.9-55.0.2. EL)

Can you shed some light?...

No but you have.  Your grub.conf and your kernel list on your splash screen don't match.  Go to the bug report you opened and make sure you include this information.

I am closing this thread, please solve this in the bug tracker.
In life, you must either "Push, Pull or Get out of the way!"