Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: Elliott on December 29, 2006, 09:54:57 PM
-
Hi.
I am running SME 7.0 and VPN connections were working without a problem from various XP boxes. In the last few days I've installed a few extras and suddenly the VPN connections are failing.
It doesn't make sense to me mainly becasue the additions were mostly email or virus specific. For example, I added the cron.daily for sa-update to keep the spamassasin database updated. I also added the mailstats.cron to update the spamassasin filter stats. The only other thing that I see in my history that I've doen that's a system change is removed the SARG package.
The error that I get happens after the MS machine authenticates and is trying to "log in to the network". It says Error 734: The PPP link control protocol was terminated. Here's an image with more info:
(http://www.externalis.com/error.png)
The only other thing I can think of that might be pertinent is that somewhere in the process prior to me removing the SARG package, I had installed Sme7admin and between it and SARG my root and admin password seemed to get fuddled so I had to do a password reset.
Can anyone shed any light on why or how this might have effected VPN logins. Nothing on the clients or my network structure has changed so I'm certain that the problem lies within the realm of the SME box.
I really don't want to setup a new box and migrate the users and email over to it to get VPN running again if I can help it.
Thanks.
-
Bump.
Really... no ideas or suggestions? Or Perhaps the holiday ham is still settling.
-
Moving this topic to the SME Server 7.x forum, it is more appropriate there. Thanks!
-
First thing to check is the logs directory, then if you still can't find the problem then please open a bug ticket so this can be resolved as it may be a potential bug
-
Are you referring to /var/log?
I have looked at the /var/log/pptpd directory and found no useful files.
Thanks.
-
Happened here also.
-
What does the output of the following give..
uname -r
rpm -qa | grep kernel
rpm -qa | grep kmod
-
uname -r
RETURNS
2.6.9-34.0.2.EL
rpm -qa | grep kernel
RETURNS
kernel-smp-2.6.9-34.EL
kernel-smp-2.6.9-42.0.2.EL
kernel-module-ppp-1.0.2-2_2.6.9_42.0.2.EL
kernel-smp-module-ppp-1.0.2-2_2.6.9_42.0.2.EL
kernel-2.6.9-34.EL
kernel-utils-2.4-13.1.80
kernel-2.6.9-42.0.2.EL
kernel-module-appletalk-1.0-1_2.6.9_42.0.2.EL
kernel-smp-module-appletalk-1.0-1_2.6.9_42.0.2.EL
kernel-smp-module-slip-1.0-1_2.6.9_42.0.2.EL
kernel-smp-2.6.9-34.0.2.EL
kernel-2.6.9-34.0.2.EL
kernel-module-slip-1.0-1_2.6.9_42.0.2.EL
rpm -qa | grep kmod
RETURNS
nothing
-
And on that note (not related to the stoppage of VPN connections...) I thought I'd be running an SMP kernel since I'm running on a hyperthreaded Xeon.
-
uname -r
RETURNS
2.6.9-34.0.2.EL
rpm -qa | grep kernel
RETURNS
kernel-smp-2.6.9-34.EL
kernel-smp-2.6.9-42.0.2.EL
kernel-module-ppp-1.0.2-2_2.6.9_42.0.2.EL
kernel-smp-module-ppp-1.0.2-2_2.6.9_42.0.2.EL
kernel-2.6.9-34.EL
kernel-utils-2.4-13.1.80
kernel-2.6.9-42.0.2.EL
kernel-module-appletalk-1.0-1_2.6.9_42.0.2.EL
kernel-smp-module-appletalk-1.0-1_2.6.9_42.0.2.EL
kernel-smp-module-slip-1.0-1_2.6.9_42.0.2.EL
kernel-smp-2.6.9-34.0.2.EL
kernel-2.6.9-34.0.2.EL
kernel-module-slip-1.0-1_2.6.9_42.0.2.EL
From that it appears you are running the wrong kernel as you must have updated via yum and the latest you have is ...42.0.2 so you need to reboot and select the latest kernel. Watch out for the .EL and ELsmp looks like you need the .EL version
-
And on that note (not related to the stoppage of VPN connections...) I thought I'd be running an SMP kernel since I'm running on a hyperthreaded Xeon.
OK then you need to select the SMP kernel.
-
I don't see any menu when I boot. I'm assuming this is something I should already know how to do but on my other *nix machines I usually see a quick menu that comes up on boot time. In fact I seem to remember that being the case with SME.
Perhaps this changed with the move to CentOs?
-
if you reboot and you will see a white background press the up and down arrow key (maybe the "esc" key) and you should then see the list of kernels
-
Don't you need to hit "return" at boot time to get the menu of kernels - you do on my test 7.1 system that I've just tried!
Just realised - the "any" key will probably work.
-
So I finally got the menu up and rebooted and it looks like the VPN connections are being accepted again. How does using the SMP kernel or the standard one have anything to do with VPN or PPTP connections... and what would have caused my system to start booting into the standard kernel in the first place?
Thanks for the help!
-
So I finally got the menu up and rebooted and it looks like the VPN connections are being accepted again. How does using the SMP kernel or the standard one have anything to do with VPN or PPTP connections...
Thanks for the help!
Your installed kernel modules have to match your running kernel.
You were running this kernel .... 2.6.9-34.0.2.EL but have this module installed.... kernel-module-ppp-1.0.2-2_2.6.9_42.0.2.EL
2.6.9-34.0.2.EL for one,
2.6.9_42.0.2.EL for the other.
-
So from this point forward reboots *SHOULD* go to the correct kernel? Can't I somehow remove the older kernels if I'm satisfied with the stability of the current one? Also, is it necessary to have the single and multiprocessor kernels on the machine?
Thanks!
-
Edit / deleted.
-
So I finally got the menu up and rebooted and it looks like the VPN connections are being accepted again. How does using the SMP kernel or the standard one have anything to do with VPN or PPTP connections... and what would have caused my system to start booting into the standard kernel in the first place?
Thanks for the help!
It doesn't. You were using the 2.6.9-34.0.2 kernel and 2.6.9-42.0.2 modules. The module version must match the kernel or those modules won't work with that kernel.
When the kernel is updated it installs the newer kernel and leaves the old one in case the newer one won't work. It however updates the modules and erases the older ones and sometimes during the update grub does not select the correct kernel so it loads the old kernel that won't work with the newer modules.
-
I see. So should I delete old kernels manually to help prevent this or could that cause potential future problems?
-
I see. So should I delete old kernels manually to help prevent this or could that cause potential future problems?
Each new kernel is installed. Thats why you have more than one kernel version.
Kernel modules are upgrade. Thats why you only have the newest one.
What happened to you should not happen.
While your system is now working, someone else my suffer the same problem. To help avoid this, you should report this issue in the Bug Tracker.
-
I see. So should I delete old kernels manually to help prevent this or could that cause potential future problems?
Each new kernel is installed. Thats why you have more than one kernel version.
Kernel modules are upgrade. Thats why you only have the newest one.
What happened to you should not happen.
While your system is now working, someone else my suffer the same problem. To help avoid this, you should report this issue in the Bug Tracker.
This is a known issue. There are a couple of bug reports discussing the best way to handle kernel and kernel module updates.
http://bugs.contribs.org/show_bug.cgi?id=2101
http://bugs.contribs.org/show_bug.cgi?id=2199