Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: gdbs on July 09, 2007, 01:54:32 PM
-
hi,
since last upgrade of 3 servers (7.1>7.1.3) i can't connect to them using pptp!
this is the message log file part on the server:
Jul 9 13:42:18 serveureof pptpd[6277]: CTRL: Client XXX.XXX.XXX.XXX control connection started
Jul 9 13:42:19 serveureof pptpd[6277]: CTRL: Starting call (launching pppd, opening GRE)
Jul 9 13:42:19 serveureof pppd[6278]: Plugin radius.so loaded.
Jul 9 13:42:19 serveureof pppd[6278]: RADIUS plugin initialized.
Jul 9 13:42:19 serveureof pppd[6278]: pppd 2.4.4 started by root, uid 0
Jul 9 13:42:19 serveureof kernel: divert: not allocating divert_blk for non-ethernet device ppp0
Jul 9 13:42:19 serveureof pppd[6278]: Using interface ppp0
Jul 9 13:42:19 serveureof pppd[6278]: Connect: ppp0 <--> /dev/pts/0
Jul 9 13:42:29 serveureof pppd[6278]: Modem hangup
Jul 9 13:42:29 serveureof pptpd[6277]: CTRL: Reaping child PPP[6278]
Jul 9 13:42:29 serveureof pppd[6278]: Connection terminated.
Jul 9 13:42:29 serveureof kernel: divert: no divert_blk to free, ppp0 not ethernet
Jul 9 13:42:29 serveureof pppd[6278]: Exit.
Jul 9 13:42:29 serveureof pptpd[6277]: CTRL: Client XXX.XXX.XXX.XXX control connection finished
On the client (Ubuntu 7.04):
Jul 9 13:42:18 computer pppd[6180]: Plugin nm-pppd-plugin.so loaded.
Jul 9 13:42:18 computer pppd[6180]: nm-pppd-plugin: plugin initialized.
Jul 9 13:42:18 computer kernel: [ 165.428177] PPP generic driver version 2.4.2
Jul 9 13:42:18 computer pppd[6193]: pppd 2.4.4 started by root, uid 0
Jul 9 13:42:18 computer pppd[6193]: Using interface ppp0
Jul 9 13:42:18 computer pppd[6193]: Connect: ppp0 <--> /dev/pts/0
Jul 9 13:42:19 computer pppd[6193]: nm-pppd-plugin: CHAP check hook.
Jul 9 13:42:29 computer pppd[6193]: Terminating on signal 15
Jul 9 13:42:29 computer pppd[6193]: Modem hangup
Jul 9 13:42:29 computer pppd[6193]: Connection terminated.
Jul 9 13:42:29 computer pppd[6193]: Child process /usr/sbin/pptp 123.123.123.123 --nolaunchpppd (pid 6194) terminated with signal 15
Jul 9 13:42:29 computer pppd[6193]: Exit.
thx for your help.
-
Hi,
It sometimes helps to disable and enable the VPN access in servermanager.
That rewrites the config files.
Irian
-
gdbs
> since last upgrade of 3 servers (7.1>7.1.3) i can't connect to them using pptp!
Did you follow the correct upgrade process re repositories, there is a serious issue going straight from 7.1 CD to 7.1.3, see the FAQ.
You may have wrong packages installed ie kernel & mppe modules conflict.
-
Ray, I missed this and stuffed my VPN link, can you link the FAQ ?
Anyone done this and rescued the situation?
Jul 10 08:04:09 server pptpd[11465]: CTRL: Client 81.174.174.x
control connection started
Jul 10 08:04:09 server pptpd[11465]: CTRL: Starting call (launching pppd, opening GRE)
Jul 10 08:04:09 server pppd[11466]: Plugin radius.so loaded.
Jul 10 08:04:09 server pppd[11466]: RADIUS plugin initialized.
Jul 10 08:04:09 server pppd[11466]: pppd 2.4.4 started by root, uid 0
Jul 10 08:04:09 server kernel: divert: not allocating divert_blk for non-ethernet device ppp0
Jul 10 08:04:09 server pppd[11466]: Using interface ppp0
Jul 10 08:04:09 server pppd[11466]: Connect: ppp0 <--> /dev/pts/0
Jul 10 08:04:09 server pptpd[11465]: CTRL: Ignored a SET LINK INFO packet with real ACCMs!
Jul 10 08:04:09 server pppd[11466]: MPPE required, but kernel has no support.
Jul 10 08:04:09 server pppd[11466]: Connection terminated.
Jul 10 08:04:09 server pppd[11466]: Connect time 0.0 minutes.
Jul 10 08:04:09 server pppd[11466]: Sent 0 bytes, received 0 bytes.
Jul 10 08:04:09 server kernel: divert: no divert_blk to free, ppp0 not ethernet
Jul 10 08:04:09 server pppd[11466]: Exit.
Jul 10 08:04:09 server pptpd[11465]: GRE: read(fd=6,buffer=804ebe0,len=8196) from PTY failed: status = -1 error = Input/output error, usually c
aused by unexpected termination of pppd, check option syntax and pppd logs
Jul 10 08:04:09 server pptpd[11465]: CTRL: PTY read or GRE write failed (pty,gre)=(6,7)
Jul 10 08:04:09 server pptpd[11465]: CTRL: Reaping child PPP[11466]
Jul 10 08:04:09 server pptpd[11465]: CTRL: Client 81.174.174.x
control connection finished
Jul 10 08:05:01 server su(pam_unix)[11503]: session opened for user qmailr by (uid=0)
Jul 10 08:05:04 server su(pam_unix)[11503]: session closed for user qmailr
Jul 10 08:05:54 server sshd(pam_unix)[11525]: session opened for user root by root(uid=0)
-
gbentley
>...can you link the FAQ ?
Learn to look, it's pretty easy to find
http://wiki.contribs.org/Main_Page
-
Hi,
my 3 servers work fine now. Thx for your help.
On the first one, Ray was true, i've upgrade from a 7.0, not a 7.1... so some source servers wasn't enable...
On the overs, after a uname -a, i've noticed that a kernel 2.6.9-55 was in use! in fact, as i've never update from test/dev servers, and according to over forums, there was a problem on updates servers weeks ago...
so i've done a little rpm -Uvh --force on kernel 2.6.9-42.0.10 and everything work fine now!
8)
thx again... this may help some...
-
gdbs
> after a uname -a, i've noticed that a kernel 2.6.9-55 was in use!
> so i've done a little rpm -Uvh --force on kernel 2.6.9-42.0.10 and everything work fine now!
Good, I lodged a bug request asking for a readme file to be included in the iso download folder so that people will hopefully see it & be aware of the issue before it happens.
For the record, can you please quote the exact command(s) & steps you entered to fix your problem. Use your up cursor key to see the history of commands entered.
-
Sure!
I use a i686 SMP kernel (select a different link for your kernel):
rpm -Uvh --force http://mirror.contribs.org/smeserver/releases/7.1/smeupdates/i386/RPMS/kernel-smp-2.6.9-42.0.10.EL.i686.rpm
then verify your grub.conf to make sure you'll boot on the right kernel:
cat /etc/grub.conf
may start with the right kernel first:
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title SME Server (2.6.9-42.0.10.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.10.ELsmp ro root=/dev/main/root
initrd /initrd-2.6.9-42.0.10.ELsmp.img
...
...
...
if not, a signal-event post upgrade may do it right...
then do
signal-event reboot
after reboot, verify your kernel version:
uname -a
Linux serveureof 2.6.9-42.0.10.ELsmp #1 SMP Tue Feb 27 10:11:19 EST 2007 i686 i686 i386 GNU/Linux
:lol:
you have what you wanted to Ray?
-
gdbs
Thanks
-
Ray,
I learnt to look a long time ago. Indeed I spent 20 mins searching the forum on such keywords as VPN Kernel etc before posting because I coudl not find an answer.
Nowhere I can find described how to reverse my situation ???
Thanks for the reply though however its after the event so the warning youre probably referring me to that I didnt look for isnt relevent any more...
-
Ray,
I learnt to look a long time ago. Indeed I spent 20 mins searching the forum on such keywords as VPN Kernel etc before posting because I coudl not find an answer.
Nowhere I can find described how to reverse my situation ???
Thanks for the reply though however its after the event so the warning youre probably referring me to that I didnt look for isnt relevent any more...
and after a 5 minutes search:
http://wiki.contribs.org/SME_Server:Documentation:FAQ#Which_repositories_should_be_enabled
++
-
>>you need to ensure you have the latest versions of the following rpms prior to applying the rest of the updates
My point is that I am now POST installing all the updates from a 7.1 CD to 7.1.3 so I didnt see how this is relevent to my situation, hence asking for more info.
If you could explain this it might help my understaning better then RTFM.
Thank you.
-
[root@server ~]# yum update smeserver-support smeserver-yum yum yum-plugin-fastest-mirror python-sqlite
==============================================================
WARNING: Additional commands may be required after running yum
==============================================================
Loading "fastestmirror" plugin
Loading "smeserver" plugin
Setting up Update Process
Setting up repositories
smeaddons 100% |=========================| 951 B 00:00
updates 100% |=========================| 951 B 00:00
base 100% |=========================| 1.1 kB 00:00
smeos 100% |=========================| 951 B 00:00
smeupdates 100% |=========================| 951 B 00:00
Loading mirror speeds from cached hostfile
Reading repository metadata in from local files
Excluding Packages from CentOS - updates
Finished
Excluding Packages from CentOS - os
Finished
Could not find update match for python-sqlite
Could not find update match for yum
Could not find update match for smeserver-yum
Could not find update match for yum-plugin-fastest-mirror
Could not find update match for smeserver-support
No Packages marked for Update/Obsoletion
================================================================
No new rpms were installed. No additional commands are required.
================================================================
[root@server ~]#
If there is anyone who can advise on how to recover from the above situation and can offer advice I would really appreciate it. This seems to be a serious problem for those needing their VPN link.
-
Trying to answer my own question ... from what I understand I have 'mistakingly' installed some Cent OS kernels that are ahead of the modules installed that match the SME kernels.
Is it possible to edit the grub config and reference the correct SME kernel ?
I am asking becasue I have not done this before and dont want to be left in a worse state than I am now i.e. at least I currently have a bootable system to work from.
[root@server boot]# ls
config-2.6.9-42.0.10.EL initrd-2.6.9-42.0.10.EL.img System.map-2.6.9-42.0.10.EL vmlinuz-2.6.9-42.0.3.EL
config-2.6.9-42.0.3.EL initrd-2.6.9-42.0.3.EL.img System.map-2.6.9-42.0.3.EL vmlinuz-2.6.9-42.0.3.ELsmp
config-2.6.9-42.0.3.ELsmp initrd-2.6.9-42.0.3.ELsmp.img System.map-2.6.9-42.0.3.ELsmp vmlinuz-2.6.9-55.0.2.EL
config-2.6.9-55.0.2.EL initrd-2.6.9-55.0.2.EL.img System.map-2.6.9-55.0.2.EL vmlinuz-2.6.9-55.0.2.ELsmp
config-2.6.9-55.0.2.ELsmp initrd-2.6.9-55.0.2.ELsmp.img System.map-2.6.9-55.0.2.ELsmp
grub lost+found vmlinuz-2.6.9-42.0.10.EL
[root@server boot]# cat /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/main/root
# initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.9-55.0.2.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.2.EL ro root=/dev/main/root
initrd /initrd-2.6.9-55.0.2.EL.img
title CentOS (2.6.9-55.0.2.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-55.0.2.ELsmp ro root=/dev/main/root
initrd /initrd-2.6.9-55.0.2.ELsmp.img
title CentOS (2.6.9-42.0.10.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.10.EL ro root=/dev/main/root
initrd /initrd-2.6.9-42.0.10.EL.img
title SME Server (2.6.9-42.0.3.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.3.ELsmp ro root=/dev/main/root
initrd /initrd-2.6.9-42.0.3.ELsmp.img
title SME Server-up (2.6.9-42.0.3.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.3.EL ro root=/dev/main/root
initrd /initrd-2.6.9-42.0.3.EL.img
[root@server boot]#
-
ok,
do this and give us the result:
rpm -qa | grep kernel
and
uname -a
-
login as: root
root@88.104.xxx.xxx's password:
Last login: Tue Jul 10 19:35:17 2007 from xx
[root@server ~]# rpm -qa | grep kernel
kernel-smp-2.6.9-55.0.2.EL
kernel-smp-2.6.9-42.0.3.EL
kernel-2.6.9-55.0.2.EL
kernel-2.6.9-42.0.3.EL
kernel-2.6.9-42.0.10.EL
kernel-utils-2.4-13.1.99
[root@server ~]# uname -a
Linux server 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 26 14:30:58 EDT 2007 i686 i686 i386 GNU/Linux
[root@server ~]#
Jul 9 20:09:42 server kernel: Intel machine check architecture supported.
Jul 9 20:09:36 server rc.sysinit: Configuring kernel parameters: succeeded
Jul 9 20:09:42 server kernel: Intel machine check reporting enabled on CPU#0.
Jul 9 20:09:36 server date: Mon Jul 9 20:09:36 BST 2007
Jul 9 20:09:42 server kernel: CPU0: Intel P4/Xeon Extended MCE MSRs (24) available
Jul 9 20:09:36 server rc.sysinit: Setting clock (utc): Mon Jul 9 20:09:36 BST 2007 succeeded
Jul 9 20:09:43 server esmith::event[2744]: Processing event: bootstrap-console-save
Jul 9 20:09:42 server kernel: CPU0: Thermal monitoring enabled
Jul 9 20:09:36 server rc.sysinit: Loading default keymap succeeded
Jul 9 20:09:43 server esmith::event[2744]: Running event handler: /etc/e-smith/events/bootstrap-console-save/S00initialize-default-databases
Jul 9 20:09:43 server kernel: Enabling fast FPU save and restore... done.
Jul 9 20:09:36 server rc.sysinit: Setting hostname server: succeeded
Jul 9 20:09:43 server kernel: Enabling unmasked SIMD FPU exception support... done.
Jul 9 20:09:36 server fsck: /dev/main/root: clean, 168038/8683520 files, 3555094/17367040 blocks
Jul 9 20:09:43 server kernel: Checking 'hlt' instruction... OK.
Jul 9 20:09:36 server rc.sysinit: Checking root filesystem succeeded
Jul 9 20:09:43 server kernel: CPU0: Intel(R) Xeon(TM) CPU 3.00GHz stepping 03
Jul 9 20:09:36 server rc.sysinit: Remounting root filesystem in read-write mode: succeeded
Jul 9 20:09:43 server kernel: per-CPU timeslice cutoff: 5851.21 usecs.
Jul 9 20:09:43 server esmith::event[2744]: Migrating existing database yum_installed
Jul 9 20:09:36 server lvm.static: 2 logical volume(s) in volume group main now active
Jul 9 20:09:43 server kernel: task migration cache decay timeout: 5 msecs.
Jul 9 20:09:43 server esmith::event[2744]: Migrating existing database spamassassin
Jul 9 20:09:36 server rc.sysinit: Setting up Logical Volume Management: succeeded
Jul 9 20:09:43 server kernel: Booting processor 1/1 eip 3000
Jul 9 20:09:43 server esmith::event[2744]: Migrating existing database configuration
Jul 9 20:09:36 server lvm.static: 2 logical volume(s) in volume group main now active
Jul 9 20:09:43 server kernel: CPU 1 irqstacks, hard=c03f2000 soft=c03d2000
Jul 9 20:09:36 server rc.sysinit: Setting up Logical Volume Management: succeeded
Jul 9 20:09:43 server kernel: Initializing CPU#1
Jul 9 20:09:36 server fsck: /dev/md1: clean, 51/26104 files, 27105/104320 blocks
Jul 9 20:09:43 server kernel: Calibrating delay using timer specific routine.. 6000.21 BogoMIPS (lpj=3000106)
Jul 9 20:09:36 server rc.sysinit: Checking filesystems succeeded
Jul 9 20:09:43 server kernel: CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000
Jul 9 20:09:36 server rc.sysinit: Mounting local filesystems: succeeded
Jul 9 20:09:43 server kernel: CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000
Jul 9 20:09:36 server rc.sysinit: Enabling local filesystem quotas: succeeded
Jul 9 20:09:43 server kernel: monitor/mwait feature present.
Jul 9 20:09:37 server rc.sysinit: Enabling swap space: succeeded
Jul 9 20:09:43 server kernel: CPU: Trace cache: 12K uops, L1 D cache: 16K
Jul 9 20:09:38 server net.agent[2193]: remove event not handled
Jul 9 20:09:43 server kernel: CPU: L2 cache: 2048K
Jul 9 20:09:38 server init: Entering runlevel: 7
Jul 9 20:09:43 server kernel: CPU1: Initial APIC ID: 1, Physical Processor ID: 0
Jul 9 20:09:39 server microcode_ctl: Applying Intel Microcode update:
Jul 9 20:09:43 server kernel: CPU: After all inits, caps: bfebfbff 20100000 00000000 00000180
Jul 9 20:09:39 server microcode_ctl: microcode_ctl startup succeeded
Jul 9 20:09:44 server kernel: Intel machine check architecture supported.
Jul 9 20:09:39 server microcode_ctl: [60G[
Jul 9 20:09:44 server kernel: Intel machine check reporting enabled on CPU#1.
Jul 9 20:09:39 server microcode_ctl:
Jul 9 20:09:44 server kernel: CPU1: Intel P4/Xeon Extended MCE MSRs (24) available
Jul 9 20:09:39 server rc.e-smith: Starting microcode_ctl: succeeded
Jul 9 20:09:44 server kernel: CPU1: Thermal monitoring enabled
Jul 9 20:09:39 server syslog: Starting system logger:
Jul 9 20:09:44 server kernel: CPU1: Intel(R) Xeon(TM) CPU 3.00GHz stepping 03
Jul 9 20:09:44 server kernel: Total of 2 processors activated (12003.96 BogoMIPS).
Jul 9 20:09:44 server kernel: ENABLING IO-APIC IRQs
Jul 9 20:09:44 server kernel: ..TIMER: vector=0x31 pin1=2 pin2=-1
Jul 9 20:09:44 server kernel: checking TSC synchronization across 2 CPUs: passed.
Jul 9 20:09:44 server kernel: Brought up 2 CPUs
Is this a Dual 3Ghz Xeon then ? Or some Dual - Core CPU?
Is SMP = Symmetric Multi Processor - which SME Kernel would give correct support for CPU ? What is EL ???
-
login as: root
root@88.104.xxx.xxx's password:
Last login: Tue Jul 10 19:35:17 2007 from xx
[root@server ~]# rpm -qa | grep kernel
kernel-smp-2.6.9-55.0.2.EL
kernel-smp-2.6.9-42.0.3.EL
kernel-2.6.9-55.0.2.EL
kernel-2.6.9-42.0.3.EL
kernel-2.6.9-42.0.10.EL
kernel-utils-2.4-13.1.99
[root@server ~]# uname -a
Linux server 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 26 14:30:58 EDT 2007 i686 i686 i386 GNU/Linux
So you have the same probleme as my 2 servers as you use a developpement SMP kernel included in updates for a while...
Is this a Dual 3Ghz Xeon then ? Or some Dual - Core CPU?
Is SMP = Symmetric Multi Processor - which SME Kernel would give correct support for CPU ? What is EL ???
Yes Xeon dual core, yes for SMP (http://en.wikipedia.org/wiki/Symmetric_multiprocessing), you have to use i686 SMP, EL = Entreprise Linux
So, to repair your server, you only have to do what i've write before:
rpm -Uvh --force http://mirror.contribs.org/smeserver/releases/7.1/smeupdates/i386/RPMS/kernel-smp-2.6.9-42.0.10.EL.i686.rpm
then , verify your grub.conf like you've done it before, the new kernel may be il first position.
you can also remove dev kernel using for exemple:
yum remove kernel-2.6.9-55.0.2.EL
hope i've help to solve your problem too...
-
Really appreciate this, thanks for your time in replying.
I have some questions though ;
If the kernel is already on disc why the need to D/L or force install ?
And, once this is done may I leave my repo selection as it was ?
-
Will my PPTP be restored if I restore to the previous kernel as indicated in te previous post...
i.e
Code:
rpm -Uvh --force http://mirror.contribs.org/smeserver/releases/7.1/smeupdates/i386/RPMS/kernel-smp-2.6.9-42.0.10.EL.i686.rpm
then , verify your grub.conf like you've done it before, the new kernel may be il first position.
you can also remove dev kernel using for exemple:
Code:
yum remove kernel-2.6.9-55.0.2.EL
-
If the kernel is already on disc why the need to D/L or force install ?
you don't have the SMP one... that's why...
Will my PPTP be restored if I restore to the previous kernel as indicated in te previous post...
I suppose... for me it solved the problem...
If you have the same problem than us (dev kernel), you will solve it like us...
Just verify your kernel before install the good one (i586, i686, i686SMP...)
-
EDIT: Sorry... stupid double clic :lol: :lol: :lol:
-
Thanks you for your patience. This works a treat. Now am back in with my VPN connection.
-
Thanks gdbs,
My VPN is no longer broken..... VPN up and Running...!! 8)