Failed to load file, but oper-status is up

521

Views

Helpful

Replies

One of my service-packages got a broken xml template.

If I start NSO with "--with-package-reload" the service package with the broken xml template loads into NSO and NSO shows "oper-status up" for this package.

But if I run "package reload" via NCS_CLI again, then the service-package changes to "oper-status file-load-error" with error message "Unknown namespace" in xml file.

Why NSO doesn't recognize the broken XML template at start of NSO directly?

Does exist a solution to catch the broken XML file at beginning?

NSO version: 5.2.3

Java: 1.8.0_242

Python: 3.6.8

Thanks.

0 Replies 0

Learn, share, save

Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.

New here? Get started with these tips. How to use Community New member guide

Polls

AI-powered tools for network troubleshooting are likely to be part of everyone’s workflow sooner or later. What is the single biggest challenge or concern you see with adopting these tools in your organization?

Security, compliance, or privacy concerns
AI decisions being a “black box”
Organizational resistance to change
Skills or knowledge gaps among staff
Data quality and completeness issues
Lack of trust in AI recommendations
Fear of automation causing outages or misconfigurations
Other