xl2tpd.service start issue

本帖最後由 251523294 於 2015-11-3 17:00 編輯
  1. systemctl enable xl2tpd
複製代碼
No result:
  1. systemctl start xl2tpd
複製代碼
result:
  1. A message:Job for xl2tpd.service failed. See 'systemctl status xl2tpd.service' and 'journalctl -xn' for details.
複製代碼
that run
  1. systemctl status xl2tpd.service
複製代碼
  1. xl2tpd.service - Level 2 Tunnel Protocol Daemon (L2TP)
  2.    Loaded: loaded (/usr/lib/systemd/system/xl2tpd.service; enabled)
  3.    Active: [color=Red]failed[/color] (Result: start-limit) since Tue 2015-11-03 08:22:26 UTC; 24min                                               ago
  4.   Process: 3333 ExecStartPre=/sbin/modprobe -q l2tp_ppp[color=Red] (code=exited, status=1/F                                              AILURE)
  5. [/color]
  6. Nov 03 08:22:26 hostname systemd[1]: xl2tpd.service: control process exite...=1
  7. Nov 03 08:22:26 hostname systemd[1]: [color=Red]Failed to start Level 2 Tunnel Protoc...).[/color]
  8. Nov 03 08:22:26 hostname systemd[1]: Unit xl2tpd.service entered failed state.
  9. Nov 03 08:22:26 hostname systemd[1]: xl2tpd.service holdoff time over, sch...t.
  10. Nov 03 08:22:26 hostname systemd[1]: Stopping Level 2 Tunnel Protocol Daem.....
  11. Nov 03 08:22:26 hostname systemd[1]: Starting Level 2 Tunnel Protocol Daem.....
  12. Nov 03 08:22:26 hostname systemd[1]: xl2tpd.service start request repeated...t.
  13. Nov 03 08:22:26 hostname systemd[1]: [color=Red]Failed to start Level 2 Tunnel Protoc...).[/color]
  14. Nov 03 08:22:26 hostname systemd[1]: Unit xl2tpd.service entered failed state.
  15. Hint: Some lines were ellipsized, use -l to show in full.
複製代碼
that run:
  1. journalctl –xn
複製代碼
result:
  1. -- Logs begin at Tue 2015-11-03 08:10:10 UTC, end at Tue 2015-11-03 08:47:23 UTC. --
  2. Nov 03 08:46:02 hostname systemd[1]: Starting Session 4 of user root.
  3. -- Subject: Unit session-4.scope has begun with start-up
  4. -- Defined-By: systemd
  5. -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  6. --
  7. -- Unit session-4.scope has begun starting up.
  8. Nov 03 08:46:02 hostname systemd-logind[2521]: New session 4 of user root.
  9. -- Subject: A new session 4 has been created for user root
  10. -- Defined-By: systemd
  11. -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  12. -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
  13. --
  14. -- A new session with the ID 4 has been created for the user root.
  15. --
  16. -- The leading process of the session is 3577.
  17. Nov 03 08:46:02 hostname systemd[1]: Started Session 4 of user root.
  18. -- Subject: Unit session-4.scope has finished start-up
  19. -- Defined-By: systemd
  20. -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  21. --
  22. -- Unit session-4.scope has finished starting up.
  23. --
  24. -- The start-up result is done.
  25. Nov 03 08:46:02 hostname sshd[3577]: pam_unix(sshd:session): session opened for user root by (uid=0)
  26. Nov 03 08:47:21 hostname sshd[3602]: Invalid user openbravo from ip
  27. Nov 03 08:47:21 hostname sshd[3602]: input_userauth_request: invalid user openbravo [preauth]
  28. Nov 03 08:47:21 hostname sshd[3602]: pam_unix(sshd:auth): check pass; user unknown
  29. Nov 03 08:47:21 hostname sshd[3602]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=
  30. Nov 03 08:47:23 hostname sshd[3602]: Failed password for invalid user openbravo from ip port 47369 ssh2
  31. Nov 03 08:47:23 hostname sshd[3602]: Connection closed by ip [preauth]
  32. lines 1-31/31 (END)
複製代碼

can you type
/sbin/modprobe -q l2tp_ppp
as root and see any error message (or dmesg)

TOP

can you type
/sbin/modprobe -q l2tp_ppp
as root and see any error message (or dmesg)
chancho 發表於 2015-11-4 07:34



     no result after run
  1. [root@localhost ~]# /sbin/modprobe -q l2tp_ppp
複製代碼

TOP

can you type
/sbin/modprobe -q l2tp_ppp
as root and see any error message (or dmesg)
chancho 發表於 2015-11-4 07:34



    Fixed


kernel Problem

TOP

good news, i was going to say may be sshd config problem.

TOP