Please take this survey to help us learn more about how you use third party tools. Your input is greatly appreciated!


This host was down due to some maintenance activity. Now returning error to start.
Please help

[[email protected] ~]$ admintools -t restart_node -d snapdealdwh -s 10.65.XX.XXX
Info: no password specified, using none
*** Restarting nodes for database dwh ***
restart host 10.XX.XX.102 with catalog v_dwh_node0001_catalog
issuing multi-node restart
Starting nodes:
v_dwh_node0001 (10.XX.XX.XXX)
Starting Vertica on all nodes. Please wait, databases with a large catalog may take a while to initialize.
Restart Nodes result: Host: Result: status=2 host=10.XX.XX.XX error_type= error_message=local variable 'start_list' referenced before assignment

    Stack Trace from Executor follows

Traceback (most recent call last):
File "/opt/vertica/share/eggs/vertica/engine/api/", line 60, in exec_module
result = instance.execute(command)
File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/engine/api/", line 86, in execute
self._do_db_start(node, delete_corrupted_data, last_epoch, unsafe_startup, environment, result)
File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/engine/api/", line 120, in _do_db_start
command = ' '.join(start_list)
UnboundLocalError: local variable 'start_list' referenced before assignment



  • Jim_KnicelyJim_Knicely Administrator

    What version of Vertica?

  • SK21SK21

    Issue Resolved ............Directories were not having appropriate permissions so recovery process was not able to write.

  • Jim_KnicelyJim_Knicely Administrator

    :) - But what version of Vertica is this? admintools should give a better error message. I can open a Jira.

  • SK21SK21

    Hello Jim its

    But having some other problem now two nodes were having scratch recovery.......others were up(during whole db startup)
    When i pressed enter after message "return to continue" all nodes went down....Please help

        Node Status: v_sdwh_node0001: (RECOVERING) v_sdwh_node0002: (UP) v_sdwh_node0003: (UP) v_sdwh_node0004: (UP) v_sdwh_node0005: (UP) v_sdwh_node0006: (UP) v_sdwh_node0007: (UP) v_sdwh_node0008: (UP) v_sdwh_node0010: (UP) v_sdwh_node0011: (UP) v_sdwh_node0013: (UP) v_sdwh_node0014: (RECOVERING) v_sdwh_node0016: (UP) v_sdwh_node0017: (UP) v_sdwh_node0018: (UP) v_sdwh_node0019: (UP) v_sdwh_node0020: (UP) v_sdwh_node0021: (UP) v_sdwh_node0022: (UP) v_sdwh_node0023: (UP) v_sdwh_node0024: (UP)

    Nodes UP: v_sdwh_node0005, v_sdwh_node0024, v_sdwh_node0020, v_sdwh_node0011, v_sdwh_node0010, v_sdwh_node0022, v_sdwh_node0013, v_sdwh_node0003, v_sdwh_node0002, v_sdwh_node0016, v_sdwh_node0017, v_sdwh_node0007, v_sdwh_node0006, v_sdwh_node0023, v_sdwh_node0008, v_sdwh_node0021, v_sdwh_node0019, v_sdwh_node0018, v_sdwh_node0004
    Nodes DOWN: v_sdwh_node0001, v_sdwh_node0014 (may be still initializing).
    Server startup was successful on some nodes, but not complete

    Press RETURN to continue

  • SK21SK21

    There was an issue starting the database and not all nodes were started. x
    x The database will be shutdown.

  • SK21SK21

    The workaround was to do not press enter after message "Press RETURN to continue" the nodes will recover and will be up.

    Another potential jira for you @Jim_Knicely

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file

Can't find what you're looking for? Search the Vertica Documentation, Knowledge Base, or Blog for more information.