OES 2023 NCS service fails to start after update

Hi,

just update NCS node via zypper and after restart ncs service fail to start, this is log:

OES-REST: <load_domainutil_nlvm_funcs:20> Successfully loaded libnlvm.so
oes-rest[4530]: OES-REST: <Init:14> ADUtil queue has been initialized
oes-rest[4530]: OES-REST: <Init:13> File-Folders Properties and Operations has been initialised
oes-rest[4530]: OES-REST: <load_nlvm_funcs:216> Successfully loaded libnlvm.so
oes-rest[4530]: OES-REST: <load_ncssdk_funcs:242> Successfully loaded libncssdk.so
oes-rest[4530]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_FilterChange function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_FilterChange
oes-rest[4530]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_ClusterJoin function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_ClusterJoin
oes-rest[4530]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_ClusterLeave function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_ClusterLeave
oes-rest[4530]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_ClusterDown function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_ClusterDown
oes-rest[4530]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_IsNW6orHigher function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_IsNW6orHigher
oes-rest[4530]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_Is6Pack function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_Is6Pack
oes-rest[4530]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_Revision function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_Revision
oes-rest[4530]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_MyNodeIPAddress function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_MyNodeIPAddress
oes-rest[4530]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_UpdateResource function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_UpdateResource
OES-REST: <Init:35> NLVM Mutex initialized

Anyone else seen this?

Thanks

Parents
  • 0

    Updates:

    1. Remove bad ncs node from the cluster and clean up the cluster (/opt/novell/ncs/bin/ncs-configd.py -init)

    2. Install new OES 2023 server with ncs pattern (with different name and IP)

    3. Full update OES 2023 - Linux host 5.14.21-150400.24.100-default #1 SMP PREEMPT_DYNAMIC Mon Dec 4 19:12:13 UTC 2023 (3f5cd84) x86_64 x86_64 x86_64 GNU/Linux

    4. add existing shared disk to the new server

    5. add node via yast2 to existing nsc cluster and restart the server

    6. get some errors on the startup:

    2024-03-06T22:05:12.939484+02:00 host oes-rest[3480]: OES-REST: <load_domainutil_nlvm_funcs:20> Successfully loaded libnlvm.so
    2024-03-06T22:05:12.939643+02:00 host oes-rest[3480]: OES-REST: <Init:14> ADUtil queue has been initialized
    2024-03-06T22:05:12.993675+02:00 host oes-rest[3480]: OES-REST: <Init:13> File-Folders Properties and Operations has been initialised
    2024-03-06T22:05:13.141573+02:00 host oes-rest[3480]: OES-REST: <load_nlvm_funcs:216> Successfully loaded libnlvm.so
    2024-03-06T22:05:13.142050+02:00 host oes-rest[3480]: OES-REST: <load_ncssdk_funcs:242> Successfully loaded libncssdk.so
    2024-03-06T22:05:13.142134+02:00 host oes-rest[3480]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_FilterChange function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_FilterChange
    2024-03-06T22:05:13.142197+02:00 host oes-rest[3480]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_ClusterJoin function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_ClusterJoin
    2024-03-06T22:05:13.142249+02:00 host oes-rest[3480]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_ClusterLeave function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_ClusterLeave
    2024-03-06T22:05:13.142307+02:00 host oes-rest[3480]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_ClusterDown function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_ClusterDown
    2024-03-06T22:05:13.142361+02:00 host oes-rest[3480]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_IsNW6orHigher function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_IsNW6orHigher
    2024-03-06T22:05:13.142416+02:00 host oes-rest[3480]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_Is6Pack function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_Is6Pack
    2024-03-06T22:05:13.142468+02:00 host oes-rest[3480]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_Revision function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_Revision
    2024-03-06T22:05:13.142522+02:00 host oes-rest[3480]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_MyNodeIPAddress functionfrom libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_MyNodeIPAddress
    2024-03-06T22:05:13.142582+02:00 host oes-rest[3480]: OES-REST: <load_ncssdk_funcs:248> Failed to load NCS_UpdateResource function from libncssdk.so library due to error: /usr/lib64/libncssdk.so: undefined symbol: NCS_UpdateResource
    2024-03-06T22:05:13.142644+02:00 host oes-rest[3480]: OES-REST: <Init:35> NLVM Mutex initialized
    2024-03-06T22:05:13.423456+02:00 host bash[3480]: #033[32m[Nest] 3480 - #033[39m03/06/2024, 10:05:13 PM #033[32m LOG#033[39m #033[38;5;3m[NestFactory] #033[39m#033[32mStarting Nest application...#033[39m

  • Verified Answer

    +1 in reply to 

    It was firewall :( 

    firewalld service blocked my new ncs node from to join to the cluster ...

    still have same errors on the startup, but i guess its the cosmetic problem.

  • 0 in reply to 

    This has been the worst update in years. I really wonder what testing was even done. When it works it works great. When it goes wrong it goes really wrong. I still have a couple that went really wrong. I refuse to pay support to resolve at this point. Tired of the hassles to open cases for bugs. 

Reply
  • 0 in reply to 

    This has been the worst update in years. I really wonder what testing was even done. When it works it works great. When it goes wrong it goes really wrong. I still have a couple that went really wrong. I refuse to pay support to resolve at this point. Tired of the hassles to open cases for bugs. 

Children
No Data