OpenHarmony开发者论坛

标题: OpenHarmony 5.0 Beta1编译时出现了多个服务不在启动命令白名单中的警告,dayu200烧录出现开机反复重启现象 [打印本页]

作者: 芝士玛塔塔    时间: 2024-8-10 07:01
标题: OpenHarmony 5.0 Beta1编译时出现了多个服务不在启动命令白名单中的警告,dayu200烧录出现开机反复重启现象
[md]### 【问题描述】

1. 介绍问题现象和发生的背景

   编译OpenHarmony 5.0 Beta1时在NO-Config-Cmds-In-Init 规则检查中出现了多个服务不在启动命令白名单中的警告,在NO-User-Group\_In-Init 规则检查中出现了用户组配置不一致的错误警告,程序烧录后设备无法正常启动,反复重启(无法确定与警告为因果关系,但是大概率是这个原因)
2. 相关的代码(请勿使用截图)

   Do NO-Config-Cmds-In-Init rule checking now:
   [WARNING]: resource_schedule_executor is not in start cmd list. path:/system/etc/init/resource_schedule_executor.cfg
   [WARNING]: bootanimation is not in start cmd list. path:/system/etc/init/foundation.cfg
   [WARNING]: teecd is not in start cmd list. path:/system/etc/init/teecd.cfg
   [WARNING]: faultloggerd is not in start cmd list. path:/system/etc/init/faultloggerd.cfg
   [WARNING]: audio_server is not in start cmd list. path:/system/etc/init/audio_server.cfg
   [WARNING]: write_updater is not in start cmd list. path:/system/etc/init/updater_normal.cfg
   [WARNING]: cupsd is not in start cmd list. path:/system/etc/init/cups_service.cfg
   [WARNING]: key_enable is not in start cmd list. path:/system/etc/init/key_enable.cfg
   [WARNING]: hiprofiler_daemon_sa is not in start cmd list. path:/system/etc/init/hiprofilerd.cfg
   [WARNING]: intell_voice_service is not in start cmd list. path:/system/etc/init/intell_voice_service.cfg
   [WARNING]: cadaemon is not in start cmd list. path:/system/etc/init/cadaemon.cfg
   [NOT ALLOWED]: device_usage_stats_service 'secon' is empty
   [WARNING]: 'audio_server' cannot be started in conditional mode
   [WARNING]: 'cupsd' cannot be started in conditional mode
   [WARNING]: 'key_enable' cannot be started in conditional mode
   [WARNING]: 'hiprofiler_daemon_sa' cannot be started in conditional mode
   [WARNING]: 'tlogcat' cannot be started in conditional mode
   Please refer to: https://gitee.com/openharmony/de ... s-In-Init/README.md
   Do NO-Config-SystemParameter-In-INIT rule checking now:
   Do NO-User-Group_In-Init rule checking now:
   [NOT ALLOWED]: quickfix has different passwd and group values
   Please refer to: https://gitee.com/openharmony/de ... p_In-Init/README.md
   Do NO-Plug-In_Module-Init rule checking now:
   Please modify according to README.md
   [OHOS INFO] rk3568 build success
   [OHOS INFO] Cost Time:  4:59:36
   =====build  successful=====

   其中启动动画等不在白名单的 `start-cmd-list中就很奇怪。`
3. 运行结果、错误截图
   Docker编译结果:

   ![8622123e6bfa1e6d557753bd4f7de4b.png](https://forums-obs.openharmony.c ... a4dqolgolh7blgl.png "8622123e6bfa1e6d557753bd4f7de4b.png")

   IDE编译结果:

   ![aec8f6699b7e1f1de3482a36433a53d.png](https://forums-obs.openharmony.c ... w54zmwd7wdw6ejc.png "aec8f6699b7e1f1de3482a36433a53d.png")

   两次编译结果相同,排除编译工具问题。

   其中值得注意的是,IDE中对5.0beta1版本源码无法识别OpenHarmony依赖环境,4.x版本均为正常。

   ![image.png](https://forums-obs.openharmony.c ... 3mj55lgq070z3zi.png "image.png")

   想质询一下大家,在编译5.0版本时是否有遇到相应情况,是否有相应对策和解决方法。因为有同事正常在此环境下编译成功,所有感觉手动添加启动命令在白名单中声明的解决方法应该不太正确。

### 【运行环境】

硬件:dayu200
ROM版本:
DevEvoStudio版本:4.0
SDK版本:
[/md]
作者: 芝士玛塔塔    时间: 2024-8-12 15:53
dayu200烧录出现开机反复重启现象问题解决,原因并非警告问题导致,拉取代码建议拉取“从版本发布Tag节点获取源码。可获取与版本发布时完全一致的源码。”而非“从版本分支获取源码。可获取该版本分支的最新源码,包括版本发布后在该分支的合入。”。最新版源码合并的分支中有可能存在与设备适配问题,导致设备无法正常启动,并且并无任何报错提示,所以变数较大。建议下载初始版本源码,稳定性较高。




欢迎光临 OpenHarmony开发者论坛 (https://forums.openharmony.cn/) Powered by Discuz! X3.5