Getting error while reviving the vertica db in EON mode

Raghavendra

Hello Team,

I'm getting below error while reviving the vertica db which is created in the EON mode. Error seems to be that there is already an entry of the node001 exists somewhere in the configuration files. Please check the below error and let me know if you need any other details.

2025-09-16 13:04:50.357 admintools/21725:0x7fb644d05740 [DBReviveHelper.runLoadRemoteCatalogModule] Load Remote Catalog succeeded on all hosts

2025-09-16 13:04:50.357 admintools/21725:0x7fb644d05740 [adminExec.dbRevive] EVENT: type=Status job None {"type":"REVIVE", "state":"VALIDATING", "dbname":"testdb", "msg":"Updating Node configuration.", "maxSteps":"7", "currStep":"5"}

2025-09-16 13:04:50.357 admintools/21725:0x7fb644d05740 [adminExec.do_create_node] creating node w/ ['v_testdb_node0001', '172.130.XXX.XX', '/vertica/catalog', '/vertica/datadir']

2025-09-16 13:04:50.359 admintools/21725:0x7fb644d05740 [Configurator.init] MAX_ARG_STRLEN is set to: 131072

2025-09-16 13:04:50.359 admintools/21725:0x7fb644d05740 [adminExec.do_create_node] node v_testdb_node0001 already defined as ['v_testdb_node0001', '172.130.XXX.XX', '/vertica/catalog', '/vertica/catalog']

2025-09-16 13:04:50.361 admintools/21725:0x7fb644d05740 [adminExec.dbRevive] Traceback (most recent call last):

File "/opt/vertica/oss/python3/lib/python3.13/site-packages/vertica/engine/adminExec.py", line 2217, in dbRevive

helper.saveNodeDict(adminExec=self)

~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^

File "/opt/vertica/oss/python3/lib/python3.13/site-packages/vertica/engine/db_revive.py", line 628, in saveNodeDict

raise ATError("Can't create node {}, see {} for details.".format(node.name, DBinclude.adminToolLog))

vertica.engine.api.errors.ATError: Can't create node v_testdb_node0001, see /opt/vertica/log/adminTools.log for details.