简介
本文档介绍问题并提供有关SMF系统同步失败问题的解决方案。
先决条件
要求
本文档没有任何特定的要求。
使用的组件
本文档不限于特定的软件和硬件版本。
本文档中的信息都是基于特定实验室环境中的设备编写的。本文档中使用的所有设备最初均采用原始（默认）配置。如果您的网络处于活动状态，请确保您了解所有命令的潜在影响。
背景信息
会话管理功能(SMF)无法启动服务，当发生问题时，会在通用执行环境(CEE)上发出警报。
问题
SMF-RCDN继续循环执行Ops Center System Upgrade，然后失败。
在CEE上，您会看到以下警报：
[smf-rcdn/cee-rcdn] cee# show alerts active summary | inc ops
ops-system-sync-runni 687ca7b9266c minor 09-07T17:59:36 smf-rcdn-mas ops center system upgrade for smf-rcdn is in progress
ops-latest-sync-faile 31531915bf54 major 09-07T10:52:26 smf-rcdn-mas ops center latest system sync for smf-rcdn failed
在SMF上，您会看到以下错误：
[smf-rcdn/smf-rcdn] smf#
Message from confd-api-manager at 2022-09-07 17:49:32...
Helm update is STARTING. Trigger for update is STARTUP.
[smf-rcdn/smf-rcdn] smf#
Message from confd-api-manager at 2022-09-07 17:49:51...
Helm update is ERROR. Trigger for update is STARTUP. Message is:
InterruptedException: one or multiple helm chart installations failed
javax.ws.rs.WebApplicationException: HTTP 500 Internal Server Error
at com.broadhop.confd.config.proxy.dao.HelmRepositoryDAO.sendConfiguration(HelmRepositoryDAO.java:272)
at com.broadhop.confd.config.proxy.service.ConfigurationSynchManager.run(ConfigurationSynchManager.java:233)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.InterruptedException: one or multiple helm chart installations failed
at com.broadhop.confd.config.proxy.dao.HelmRepositoryDAO.sendConfiguration(HelmRepositoryDAO.java:266)
... 8 more
分析
要对此进行故障排除，您必须从SMF运营中心Pod查看内部日志。
在此场景中，smf-rcdn没有启动smf相关pod。
cloud-user@smf-rcdn-master-1:~$ kubectl get pods -n smf-rcdn
NAME READY STATUS RESTARTS AGE
documentation-69768456cb-klq8d 1/1 Running 0 102d
ops-center-smf-rcdn-ops-center-85899d6b90-9kx6h 5/5 Running 1 40m
smart-agent-smf-rcdn-ops-center-6b9cd64f85-8f8cz 1/1 Running 0 22h
cloud-user@smf-rcdn-master-1:~$
记下运营中心Pod的名称，并为容器confd-api-bridge收集日志。
cloud-user@smf-rcdn-master-1:~$ kubectl logs ops-center-smf-rcdn-ops-center-85899d6b90-9kx6h -n smf-rcdn -c confd-api-bridge
Preparing upgrade logic for helm ...
日志内部是系统无法启动的原因。在本示例中，问题是由于sgw-service配置。配置文件没有配置接口。
WARN [2022-09-13 19:44:55,860] com.broadhop.confd.config.proxy.dao.helm.ReleaseInstallCallable: [436] Install or upgrade failure for chart: sgw-service,
release-name: smf-rcdn-sgw-service, command: [/usr/local/bin/helm, upgrade, smf-rcdn-sgw-service, /tmp/chart1014799367411807494.tgz,
--install, -f, /tmp/override1205042274924409625.yaml, -f, /tmp/values4318819924777544020.yaml, --namespace, smf-rcdn, --dry-run]
WARN [2022-09-13 19:44:55,860] com.broadhop.confd.config.proxy.dao.helm.ReleaseInstallCallable: Command result:
Release "smf-rcdn-sgw-service" does not exist. Installing it now.
Error: template: sgw-service/templates/sgw-service.yaml:14:30: executing "sgw-service/templates/sgw-service.yaml" at
<$endpoint.service.nodeCount>: nil pointer evaluating interface {}.nodeCount
INFO [2022-09-13 19:44:55,860] com.broadhop.confd.config.proxy.dao.helm.ReleaseInstallCallable: Command result:
Release "smf-rcdn-udp-proxy" does not exist. Installing it now.
NAME: smf-rcdn-udp-proxy
LAST DEPLOYED: Tue Sep 13 19:44:55 2022
NAMESPACE: smf-rcdn
STATUS: pending-install
REVISION: 1
TEST SUITE: None
HOOKS:
MANIFEST:
在SMF上，选中 show running-configuration. This 配置包含sgw-service的配置文件，但未定义必需参数。
profile smf smfprof
mode offline
locality LOC1
allowed-nssai [ slice1 ]
instances 1 fqdn xxx
instances 2 fqdn xxx
plmn-list mcc 123 mnc 456
exit
service name nsmf-pdu
type pdu-session
schema http
version 1.0.2
http-endpoint base-url http://smf-service
icmpv6-profile icmpprf1
compliance-profile June19
priority 20
access-profile idft
subscriber-policy polsub
exit
exit
profile sgw cn-sgw
exit
解决方案
解决方案是消除配置错误。
相关信息
反馈