Skip to main content

No Option Error - Can't do ANYTHING with admintools - Please Help (No Option Error)

  • May 16, 2015
  • 4 replies
  • 24 views
dcruise23

I tried to change the IP addresses on each node in the cluster and after trying to create a new database - my whole vertica instance has gone bad. I literally cannot perform any task using AdminTools or command line.

 

After click ANY option in admin tools i get the following error:

 

adminTools Last Chance Error Handler running...

raised error: <class 'ConfigParser.NoOptionError'>

error message: no option ;v_atest_node0001' in section: 'Nodes'

trace file: /opt/vertica/log/adminTools-dbadmin.errors

REPORT THIS INFORMATION TO TECHNICAL SUPPORT
AND INCLUDE CONTENTS OF THE TRACE FILE IN YOUR REPORT

 

 

Trace File Contents:

handler invoked: 2015-05-16 15:18:17
raised error: <class 'ConfigParser.NoOptionError'>
Traceback (most recent call last):
File "/opt/vertica/bin/admintools", line 391, in <module>
ac.runApp()
File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/ui/adminCtrl.py", line 3374, in runApp
self.__ui.runFromNavigation("main")
File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/ui/uiMgr.py", line 165, in a_wrapper_accepting_args
fn(self, *args, **kwargs)
File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/ui/uiMgr.py", line 450, in runFromNavigation
self.__navigator.navigate(uimanager=self, startingPoint=runFrom)
File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/ui/Navigator.py", line 315, in navigate
((self.__menus[ nextMenu ][ self.NAV_MACTIONS ])[ offset ])()
File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/ui/adminCtrl.py", line 232, in restartDBFromEpoch
dbDict = self.__exec.getDBInfo()
File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/engine/adminExec.py", line 1709, in getDBInfo
config_info = c.getconfig(db)
File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/config/Configurator.py", line 283, in getconfig
props[option +"_new"].append( self.getsiteconfig( n ))
File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/config/Configurator.py", line 353, in getsiteconfig
p = self.configdict.get("Nodes",nodename).split(',')
File "/opt/vertica/oss/python/lib/python2.7/ConfigParser.py", line 566, in get
raise NoOptionError(option, section)
NoOptionError: No option 'v_atest_node0001' in section: 'Nodes'

 

 

I cannot run a vbr.py backup (did previously but cant now) or anything related to vertica. Unfortunately it seems on the python side and the v_atest_node0001 is the database i tried to create but didnt create successfully.

 

Any ideas?


Thank you - much appreciated

 

 

    4 replies

    SruthiA
    Forum|alt.badge.img+1
    • SruthiA
    • Participating Frequently
    • May 17, 2015

    Hi,

     

    Seems like your admintools.conf file may be missing some things. Please share the content of /opt/vertica/config/admintools.conf and also the number of nodes in your cluster. 

    cat /opt/vertica/config/admintools.conf

     

     

    -Regards,

     Sruthi

    Dhruva
    • Dhruva
    • New Participant
    • October 15, 2015

    Hi Sruthi,

     

     

    I have the same issue, while trying to create a database, My cluster size is 3 nodes and

     

     

    [Configuration]

    last_port = 5433

    tmp_dir = /tmp

    default_base = /home/dbadmin

    format = 3

    install_opts = --hosts 'node1,node2,node3' --rpm '/tmp/vertica-7.1.2-0.x86_64.RHEL5.rpm' -u dbadmin

    spreadlog = False

    controlsubnet = default

    controlmode = broadcast

     

    [Cluster]

    hosts = 172.31.15.64,172.31.15.65,172.31.15.66

     

    [Nodes]

    node0001 = 172.31.15.64,/home/dbadmin,/home/dbadmin

    node0002 = 172.31.15.65,/home/dbadmin,/home/dbadmin

    node0003 = 172.31.15.66,/home/dbadmin,/home/dbadmin

     

    [Database:test]

    restartpolicy = ksafe

    port = 5433

    path = /home/dbadmin/test/v_test_node0001_catalog

    nodes = v_test_node0001,v_test_node0002,v_test_node0003

     

    dcruise23
    • dcruise23
    • Author
    • New Participant
    • October 15, 2015

    Hi Dhruva,

     

    Make sure that your node names are set appropriately. You named your nodes 'node000x' but then referenced to them as 'v_test_node000x'. See the edit below where you can reference to your correct node names. Let me know if this helped!

     

    Yours:

     

    [Nodes]

    node0001 = 172.31.15.64,/home/dbadmin,/home/dbadmin

    node0002 = 172.31.15.65,/home/dbadmin,/home/dbadmin

    node0003 = 172.31.15.66,/home/dbadmin,/home/dbadmin

     

    [Database:test]

    restartpolicy = ksafe

    port = 5433

    path = /home/dbadmin/test/v_test_node0001_catalog

    nodes = v_test_node0001,v_test_node0002,v_test_node0003

     

     

    Edit:

     

     

    [Nodes]

    node0001 = 172.31.15.64,/home/dbadmin,/home/dbadmin

    node0002 = 172.31.15.65,/home/dbadmin,/home/dbadmin

    node0003 = 172.31.15.66,/home/dbadmin,/home/dbadmin

     

    [Database:test]

    restartpolicy = ksafe

    port = 5433

    path = /home/dbadmin/test/v_test_node0001_catalog

    nodes = node0001, node0002, node0003

    claudiuo
    • claudiuo
    • New Participant
    • April 6, 2016

    I am having the same problem: after creating the database adminTools errors exactly the same as for the OP and the conf file shows different node names in the Database section:

     

    [Nodes]
    node0001 = <ip1>,/home/mydba,/home/mydba
    node0002 = <ip2>,/home/mydba,/home/mydba
    node0003 = <ip3>,/home/mydba,/home/mydba

     

    [Database:cea]
    restartpolicy = ksafe
    port = 5433
    path = /home/mydba/cea
    nodes = v_cea_node0001,v_cea_node0002,v_cea_node0003

     

    What I wanted to mention though is that I didn't change the admintools.conf file manually, this is what I got after creating the database using the adminTools. I will try to modify the conf file manually but just wanted to say that this is something happening without manual changes so there must be some other cause somewhere.

    Still scrolling?
    Ask a question
    Terms & ConditionsAccessibility statement