122 Star 0 Fork 6

src-openEuler / dnssec-trigger

 / 详情

【23.09 round1】【arm/x86】dnssec-triggerd服务启动失败

已验收
缺陷
创建于  
2023-08-28 14:32

【环境信息】
软件信息:
1) OS版本及分支:openEuler 23.09
2) 内核信息:6.4.0-1.0.2.6.oe2309.aarch64
【操作步骤】
dnf install -y dnssec-trigger
systemctl start dnssec-triggerd
【预期结果】
命令执行成功
【实际结果】
命令执行失败
【附件】
输入图片说明

评论 (3)

ssttkx 创建了缺陷

Hi ssttkx, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Application, and any of the maintainers: @朱春意 , @Alex_Chao , @small_leek , @jimmy_hero , @caodongxia

openeuler-ci-bot 添加了
 
sig/Application
标签
ssttkx 负责人设置为caodongxia
ssttkx 计划截止日期设置为2023-08-29
ssttkx 计划开始日期设置为2023-08-28
ssttkx 计划截止日期2023-08-29 修改为2023-08-31
ssttkx 优先级设置为主要
ssttkx 里程碑设置为openEuler-23.09-round-1

journalctl -xe 可查看到错误如下:

ug 28 15:16:19 openEuler unbound-checkconf[3497]: unbound-checkconf: no errors in /etc/unbound/unbound.conf
Aug 28 15:16:22 openEuler systemd[1]: unbound.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStartPre= process belonging to unit unbound.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Aug 28 15:16:22 openEuler systemd[1]: unbound.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit unbound.service has entered the 'failed' state with result 'exit-code'.
Aug 28 15:16:22 openEuler systemd[1]: Failed to start Unbound recursive Domain Name Server.
░░ Subject: A start job for unit unbound.service has failed
░░ Defined-By: systemd

根据错误日志及issue #I6ILZ8:[23.03RC1][arm/x86]unbound.service服务启动失败 可知是unbound服务启动失败,导致dnssec-triggerd服务失败,unbound会调用unbound-anchor命令,该命令会读取/etc/resolv.conf文件,若是该文件为空则会使用默认的dns服务器,若是配置文件中指定了dns服务器,则会使用该服务器,在测试环境中,注释掉resolv.conf原先默认的服务器,采用自身的dns服务器,即可unbound服务启动成功

注释掉resolv.conf原先默认的服务器,后重新启动dnssec-triggerd服务成功,截图如下:
输入图片说明

dnssec-triggerd服务中错误日志信息根因是:报错网络无法连接。服务启动会访问http,但是访问的http地址是随机生成的,这些随机生成的地址就存在无法访问的假地址。
#I6685P:【22.03 LTS SP1 RC3】【arm/x86 】dnssec-triggerd.service服务启动之后,日志中有打印error信息 一致

综上,建议非问题关闭 @ssttkx

已确认,修改文件后后启动
输入图片说明

ssttkx 任务状态待办的 修改为已验收

登录 后才可以发表评论

状态
负责人
项目
里程碑
Pull Requests
关联的 Pull Requests 被合并后可能会关闭此 issue
分支
开始日期   -   截止日期
-
置顶选项
优先级
预计工期 (小时)
参与者(3)
5329419 openeuler ci bot 1632792936
1
https://gitee.com/src-openeuler/dnssec-trigger.git
git@gitee.com:src-openeuler/dnssec-trigger.git
src-openeuler
dnssec-trigger
dnssec-trigger

搜索帮助