Topic: Cant VPN to server, where do i start trouble shooting

[ber]

stefano,

I dont have an answer for your question- I installed SME about a year ago downloaded from SME site, then have done upgrades as advised.
I dont know why I kernel is old as you have mentioned.

heres the output:

[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

[Stefano]

hi

change the bold line

#          initrd /initrd-version.img
#boot=/dev/hda
default=7
timeout=5
splashimage=(hd0,0)/grub/smeserver.xpm.gz

to

default=1

and reboot.. ti should work..

anyway, please open a bug because this kind of problem should not appen..
ciao
Stefano

[ber]

stefano, I'm very new to Linux and am still learning command lines, can you advise how to change the data you've mentioned from the command lines...regards John

[Stefano]

Hi John

login to SME, on console or via putty

let's move to the target dir

Code: [Select]

cd /boot/grub

do a copy of the file before editing

Code: [Select]

cp menu.lst menu.bak

edit file

Code: [Select]

pico menu.lst

change the line as suggested, then close with Ctrl-X and Y (read the messages on the screen.. you could have them in different language from english according to your locale

then reboot your server..

if everything works fine, remove the back file with

Code: [Select]

rm /boot/grub/menu.bak

HTH
ciao
Stefano

[pfloor]

hi

why are you booting SME with an old kernel?

check if you have 2.6.9-78.0.8 entry in grub with

Code: [Select]

cat /boot/grub/menu.lst

Ciao
Stefano

I don't think the OP did that on purpose.  There have been a couple bug reports about the wrong kernel being (automatically) selected, kernels not installing properly and even kernels missing from the boot selection menu after upgrading to 7.4.  The cause/solution is yet to be found, see:

http://bugs.contribs.org/show_bug.cgi?id=4802
http://bugs.contribs.org/show_bug.cgi?id=4815

[Stefano]

I don't think the OP did that on purpose. 

You are right, my question could be misunderstood.. I apologize

Ciao
Stefano

[CharlieBrady]

[root@server ~]# uname -a
Linux server 2.6.9-67.ELsmp #1 SMP Fri Nov 16 12:48:03 EST 2007 i686 i686 i386 GNU/Linux
[root@server ~]#

That is the cause of your problem. You are running a very old kernel, but you do not have the VPN kernel modules installed which correspond to that version of the kernel. You need to boot the 2.6.9_78.0.8.EL version of the kernel.

[ber]

Hi all i get a general gist of what the recommendation is- "Ive got a old kernel"
How do i fix this problem-upgrading the kernel?
Will it cause other issues?
I host five domains/emails and its running sweet...just don't want to jeopardize the server due to the fact that its hosting websites for my clients.

[ber]

Hi Charlie, can you advise how I can boot my SME server to the latest kernel?

[chris burnat]

From the FAQ: "Restart your server and at the beginning of the boot-up use the arrow keys to select the kernel you would like to boot into."  You should see the 2.6.9_78.0.8.EL version of the kernel in the list, select it.  After selecting the desired kernel, press ENTER, the server will boot with selected kernel.  This operation can be reversed, you can reselect your old kernel later on if you wish.

[ber]

Chris, thanks for your help, will keep everyone posted on the progress.,...Regards John

[ber]

  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 osome light on how I can upgrade my kernel to resolve the VPN issue...Regards John
.

[janet]

ber

how I can upgrade my kernel to resolve the VPN issue

Check the server manager software updates panel and see that only the standard repositories are enabled as per FAQ
http://wiki.contribs.org/SME_Server:Documentation:FAQ#Which_repositories_should_be_enabled

Then login to sme Linux command prompt and do
yum clean all
yum update
signal-event post-upgrade
signal-event reboot

Report back your success or failure

[ber]

Hi Mary, updated my software settings as recommended and ran the commands as well. Rebooted.
No improvement on my VPN issue.
I'm still running on the my old kernel version if that was before.
Hmmm...any further suggestions?

[chris burnat]

Ber,  there are now many operations having been performed on your server without tracking the results properly, and as a result a state of confusion prevails.  For example, you have just updated your server, it would be useful having a look at the log files to ascertain whether a kernel update has taken place.  It does not end here, your reply in comment #15 suggests that at some stage, you had 2.6.9-78.0.8 present in some form - why this kernel is not showing in the boot option is a matter which should be investigated.

You problem may be the result of a shortcoming with SME software, or a succession of errors on your part, or a combination of both... .  The best course of action would have been, and still is, to report this issue in the Bugtracker, as previously suggested.   Whilst the Butracker is not a support forum, you may benefit from the detailed investigative work that will take place once you have lodged a formal report, and above all, the root cause of the problem will be identified and corrected which will benefit all if indeed we have a bug. 

So please fill a report at Bugzilla, provide a detailed summary of your issue and above all do not make any further changes to your server until such time as one of the Dev have a good look at this issue.