Description of problem: openl2tp don't work Version-Release number of selected component (if applicable): openl2tp-1.8-6 How reproducible: always Steps to Reproduce: 1. service openl2tp start 2. to see logs: /var/log/messages: "Invalid executable path in command line, ignoring killproc" "rpcbind terminating on signal." "Unable to register UDP RPC program" Reproducible: Steps to Reproduce:
Hardware: i586 => AllSource RPM: openl2tp => openl2tp rpcbind
Keywords: (none) => TriagedAssignee: bugsquad => dlucio
How to use Mageia 3 if half provides in Commonwealth of Independent States works with VPN L2TP? It's critical bug. Now VPN L2TP works fine only in Mageia 2 with openl2tp from Mageia Russian Community repo. Users don't want to use Mageia 3, because without Internet it's a bad distro.
Priority: Normal => HighSeverity: normal => critical
It looks like the rpcbind service was not enabled/started; # systemctl start rpcbind # systemctl start openl2tp To ensure you do't run into this after next boot: # systemctl enable rpcbind If openl2tp is so important, why has no-one requested any improvements? I must say that of the linux desktop users I know, not one requires openl2tp, so this is quite a region-specific feature it seems, and I wouldn't judge any distro based on L2TP support (many distros don't even ship openl2tp).
CC: (none) => bgmilne
There is openl2tp in MRC repo always. Mandriva had openl2tp in EduMandriva repo. Rosa haves openl2tp, xl2tpd, networkmanager-l2tp (now will be networkmanager-l2tp in Rosa distro, I think). All Russian distros haves VPN L2TP. Yes, it's region-specific.
rpcbind service is enabled by default in distro. If to run first, then openl2tp service can not start (no openl2tp in processes) and creates empty /var/run/openl2tpd.pid. If to run second, then openl2tp service can not start, because there is file /var/run/openl2tpd.pid.
i will check this,
No killproc in Mageia, no absolute paths in ExecStop=, it's critical for systemd, but problems are not only with killproc. Main problem, if to fix killproc, with loading plugin /usr/lib/openl2tp/ppp_unix.so and with auto loading kernel module l2tp_ppp (it's in /etc/init.d/openl2tpd, but no in systemd module). I don't understand why service was named openl2tp instead openl2tpd. Will you rename?
Now openl2tp works in Mageia 4 RC, but no killproc in Mageia. Please write mudules for systemd right.
Blocks: (none) => 3454
Summary: openl2tp don't work => openl2tp don't work, don't start when booting
Created attachment 4997 [details] Current boot log It's current boot log. You can see openl2tpd does not start when booting usually or starts randomly (I saw success very rarely).
Created attachment 4998 [details] Boot log with "Restart=always" If to add Restart=always in /usr/lib/systemd/system/openl2tp.service, then openl2tp starts when booting realy always. You can see in log: "openl2tp.service holdoff time over, scheduling restart." and openl2tp starts not from the first time, but from the second time.
Current fix for openl2tp.service: - move ExecStop=killproc openl2tpd - add ExecStartPre=/sbin/modprobe -q l2tp_ppp - add Restart=always (?)
Source RPM: openl2tp rpcbind => openl2tpWhiteboard: (none) => NEEDHELP
Fixed in Cauldron openl2tp-1.8-8.mga5. "Restart=always" is while WONTFIX, in waiting for better solution.
Suggested advisory: ======================== Updated openl2tp package fix: - move killproc, which non exists for Mageia, and systemd can stop openl2tp service without additional command - preload kernel module l2tp_ppp with according /etc/rc.d/init.d/openl2tpd - openl2tp is realy forking type service, not simple, and after fix openl2tp works better, more success after booting system. Please test also: ps -A|grep openl2tp some times after booting system One tester tested 100% success, but I tested only 50% success after booting system. In any case it's better, then before fix. ======================== Updated packages in updates_testing: ======================== openl2tp-1.8-7.1.mga4.i586.rpm openl2tp-1.8-7.1.mga4.x86_64.rpm openl2tp-devel-1.8-7.1.mga4.i586.rpm openl2tp-devel-1.8-7.1.mga4.x86_64.rpm Source RPMs: openl2tp-1.8-7.1.mga4.src.rpm
Version: Cauldron => 4QA Contact: (none) => qa-bugsWhiteboard: NEEDHELP => (none)
Assignee: luis.daniel.lucio => qa-bugsQA Contact: qa-bugs => (none)
Tested openl2tp-1.8-9.mga5.x86_64.rpm from cauldron on my desktop PC and Virtualbox. 1. openl2tp starts successfully every time when booting mga4 on my PC. 2. openl2tp doesn't start when booting mga4 installed at Virtualbox. It seems to me, it because of rpcbind doesn't start properly while openl2tp starts. openl2tp and rpcbind starts simultaneously, but wnen booting in Virtualbox (and maybe slow PC too) rpcbind takes more time to start. For example on my PC openl2tp starts during 13ms, rpcbind starts during 5ms, on Virtualbox openl2tp starts during 198ms, rpcbind starts during 216ms. If to add into the After= rpcbind.target in openl2tp.service i.e. "After=network.target remote-fs.target nss-lookup.target rpcbind.target", then openl2tp start when booting at Virtualbox for me too.
CC: (none) => ugal12v
Yuri, thank you for test and report. Commited, waiting submit.
Assignee: qa-bugs => loginov_alex
Suggested advisory: ======================== Updated openl2tp package fix: - move killproc, which non exists for Mageia, and systemd can stop openl2tp service without additional command - preload kernel module l2tp_ppp with according /etc/rc.d/init.d/openl2tpd - openl2tp is realy forking type service, not simple, and after fix openl2tp works better, more success after booting system. - add rpcbind.target, because openl2tp must wait rpcbind service Please test also: ps -A|grep openl2tp some times after booting system I tested on Vmware Player 10 times after reboot - 100% success now for me after booting system. ======================== Updated packages in updates_testing: ======================== openl2tp-1.8-7.2.mga4.i586.rpm openl2tp-1.8-7.2.mga4.x86_64.rpm openl2tp-devel-1.8-7.2.mga4.i586.rpm openl2tp-devel-1.8-7.2.mga4.x86_64.rpm Source RPMs: openl2tp-1.8-7.2.mga4.src.rpm
Assignee: loginov_alex => qa-bugs
Testing MGA4 64-bit on real hardware. If I understand the bug correctly (not being able to see the wood for the trees), it boils down to the fact that openl2tp did not get started correctly at boot. Also, that rpcbind needs to be installed & started also. CAUTION: when I installed openl2tp from Release media, it installed OK even though rpcbind was *not* installed (I added it subsequently). Since rpcbind seems to be a dependancy of openl2tp, has this been taken care of in the update of the latter? Before update ------------- With Release rpcbind & openl2tp, booting the system started rpcbind but *not* openl2tp, which needed starting manually as described: # systemctl start openl2tp After update (openl2tp-1.8-7.2.mga4) ------------ Re-booting the system gave: $ ps ax | grep rpcbind 1838 ? Ss 0:00 /sbin/rpcbind -w $ ps ax | grep openl2tp 1894 ? S 0:00 /usr/sbin/openl2tpd which seems to resolve the essence of the bug. If this is deemed OK, please add MGA4-64-OK to the Whiteboard field.
CC: (none) => lewyssmith
Requires: rpcbind It was before updates and no changes after updates.
Re comment 16 & comment 17: Sorry Alex, you are right. My note about having to specifically add rpcbind was untrue. I removed both packages (& their libs), and re-installed just openl2tp from Core Release. It did indeed pull in: lib64tirpc1 libtirpc openl2tp rpcbind So assuming you have implicitly agreed the simple test in Comment 16, this is OK for MGA4 64-bit.
Whiteboard: (none) => MGA4-64-OK
Anyone involved able to test the fix i586 please?
Tested openl2tp-1.8-7.2.mga4.i586.rpm package on Virtualbox with Mageia-4.1-test3-i586-DVD.iso image installed. After reboot openl2tp started 100% successfully. $ ps -A |grep openl2tp 1481 ? 00:00:00 openl2tpd $ systemctl status openl2tp openl2tp.service - The open L2TP implementation Loaded: loaded (/usr/lib/systemd/system/openl2tp.service; enabled) Active: active (running) since Ð¡Ñ 2014-04-02 12:02:19 NOVT; 18min ago Process: 1473 ExecStart=/usr/sbin/openl2tpd $OPENL2TPDARGS (code=exited, status=0/SUCCESS) Process: 1470 ExecStartPre=/sbin/modprobe -q l2tp_ppp (code=exited, status=0/SUCCESS) Main PID: 1481 (openl2tpd) CGroup: /system.slice/openl2tp.service ââ1481 /usr/sbin/openl2tpd I tested 10 times after reboot and it starts OK for me.
Hi, I tested from LiveDVD4.0KDE i586 after install testing and reboot; it is okay $ systemctl status openl2tp openl2tp.service - The open L2TP implementation Loaded: loaded (/usr/lib/systemd/system/openl2tp.service; enabled) Active: active (running) since dim. 2014-04-13 16:22:00 CEST; 1min 53s ago Process: 1432 ExecStart=/usr/sbin/openl2tpd $OPENL2TPDARGS (code=exited, status=0/SUCCESS) Process: 1402 ExecStartPre=/sbin/modprobe -q l2tp_ppp (code=exited, status=0/SUCCESS) Main PID: 1440 (openl2tpd) CGroup: /system.slice/openl2tp.service ââ1440 /usr/sbin/openl2tpd Okay afer 3 reboot on virtualbox, i think it is ok for MGA4-32-OK
CC: (none) => inster.css
Whiteboard: MGA4-64-OK => MGA4-64-OK MGA4-32-OK
Thanks everybody. Validating. Advisory uploaded. Could sysadmin please push to 4 updates Thanks
Keywords: (none) => validated_updateWhiteboard: MGA4-64-OK MGA4-32-OK => advisory MGA4-64-OK MGA4-32-OKCC: (none) => sysadmin-bugs
http://advisories.mageia.org/MGAA-2014-0101.html
Status: NEW => RESOLVEDCC: (none) => mageiaResolution: (none) => FIXED