ipsec报错，有会解决的大佬吗？

李不兴

Job for ipsec.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status ipsec.service" and "journalctl -xe" for details.
谷歌了好久的资料，一直没解决，有会的大佬指点一下吗，小鸡系统ubuntu 20.04

具体报错信息如下：

root@evoxt:~# ipsec restart
Redirecting to: systemctl restart ipsec.service
Job for ipsec.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status ipsec.service" and "journalctl -xe" for details.
root@evoxt:~# systemctl status ipsec.service
● ipsec.service - Internet Key Exchange (IKE) Protocol Daemon for IPsec
     Loaded: loaded (/lib/systemd/system/ipsec.service; enabled; vendor preset: enabled)
     Active: failed (Result: core-dump) since Tue 2024-04-23 17:29:14 CEST; 5s ago
       Docs: man:ipsec(8)
             man:pluto(8)
             man:ipsec.conf(5)
    Process: 67877 ExecStartPre=/usr/local/libexec/ipsec/addconn --config /etc/ipsec.conf --checkconfig (code=exited, status=0/SUCCESS)
    Process: 67878 ExecStartPre=/usr/local/libexec/ipsec/_stackmanager start (code=exited, status=0/SUCCESS)
    Process: 68131 ExecStartPre=/usr/local/sbin/ipsec --checknss (code=exited, status=0/SUCCESS)
    Process: 68132 ExecStartPre=/usr/local/sbin/ipsec --checknflog (code=exited, status=0/SUCCESS)
    Process: 68143 ExecStart=/usr/local/libexec/ipsec/pluto --leak-detective --config /etc/ipsec.conf --nofork (code=dumped, signal=AB>
    Process: 68149 ExecStopPost=/sbin/ip xfrm policy flush (code=exited, status=0/SUCCESS)
    Process: 68150 ExecStopPost=/sbin/ip xfrm state flush (code=exited, status=0/SUCCESS)
    Process: 68151 ExecStopPost=/usr/local/sbin/ipsec --stopnflog (code=exited, status=0/SUCCESS)
   Main PID: 68143 (code=dumped, signal=ABRT)

Apr 23 17:29:14 evoxt.com systemd[1]: ipsec.service: Scheduled restart job, restart counter is at 5.
Apr 23 17:29:14 evoxt.com systemd[1]: Stopped Internet Key Exchange (IKE) Protocol Daemon for IPsec.
Apr 23 17:29:14 evoxt.com systemd[1]: ipsec.service: Start request repeated too quickly.
Apr 23 17:29:14 evoxt.com systemd[1]: ipsec.service: Failed with result 'core-dump'.
Apr 23 17:29:14 evoxt.com systemd[1]: Failed to start Internet Key Exchange (IKE) Protocol Daemon for IPsec.

还有下面的报错：

root@evoxt:~# journalctl -xe
Apr 23 17:32:19 evoxt.com rsyslogd[571]: action 'action-2-builtinmfile' (module 'builtinmfile') message lost, could not be process>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-err>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: action 'action-2-builtinmfile' (module 'builtinmfile') message lost, could not be process>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-err>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: action 'action-2-builtinmfile' (module 'builtinmfile') message lost, could not be process>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-err>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: action 'action-2-builtinmfile' (module 'builtinmfile') message lost, could not be process>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-err>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: action 'action-2-builtinmfile' (module 'builtinmfile') message lost, could not be process>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-err>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be process>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-err>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be process>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-err>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be process>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-err>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be process>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-err>
Apr 23 17:32:19 evoxt.com rsyslogd[571]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be process>

mtdickens

提示不是说了看 systemctl status ipsec.service" and "journalctl -xe"，所以看日志啊

dupit8

这个跟ipsec没啥关系，大概率你系统升级不完整，导致系统处于一个乱七八糟的状态。你这个要解决需要连进系统去调，仅仅这一点信息，除了神仙没有人能解决

李不兴

mtdickens 发表于 2024-4-23 23:07
提示不是说了看 systemctl status ipsec.service" and "journalctl -xe"，所以看日志啊

已贴上报错信息

李不兴

dupit8 发表于 2024-4-23 23:17
这个跟ipsec没啥关系，大概率你系统升级不完整，导致系统处于一个乱七八糟的状态。你这个要解决需要连进系 ...

报错信息已附上，大佬帮忙看下

mtdickens

看看这个命令能给出什么日志？journalctl -u ipsec.service

李不兴

mtdickens 发表于 2024-4-24 01:07
看看这个命令能给出什么日志？journalctl -u ipsec.service

root@evoxt:~# journalctl -u ipsec.service
-- Logs begin at Wed 2024-04-24 09:12:39 CEST, end at Wed 2024-04-24 09:13:38 CEST. --
-- No entries --