The Vertica Forum recently got a makeover! Let us know what you think by filling out this short, anonymous survey.
Please take this survey to help us learn more about how you use third party tools. Your input is greatly appreciated!
new setup.. after restart issues
I setup vertica in a single redhat 6.0 linux, also i installed vertica management console, for one vertica was running w/o problems but i restart the server and i got some issues, error: cant get up my database this is the error when i tried to bring it up verica Spread does not seem to be running on 10.181.109.15. The database will not be started on this host.. and when i try to create a new bd i got this log 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 1951, in createDB result, info = self.__exec.createDB(DBName, nodesInDB, DBpassword=DBpassword, licenseFile=DBinclude.CONFIG_SHARE_DIR + "/license.key") File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/engine/adminExec.py", line 3358, in createDB portNo=port, DBpassword=DBpassword, licenseFile=licenseFile, logger=logger, whichNodesRunSpread=restrictSpread) File "/opt/vertica/oss/python/lib/python2.7/site-packages/vertica/network/SSH.py", line 1533, in createDBMultiNodes code = checkForRunning(dbName, [nodes[initiatorOffset]], askForContinue=interactive, KSafety=k, procCheck=process_checker, spreadHosts=whichNodesRunSpread, logger=logger, requires_all_up=True) IndexError: list index out of range any good fella that can help me a little??
0
Comments
Can you check if spread is running on this server?
$ /etc/init.d/spreadd status
If spread is down, please start spread as:
$ /etc/init.d/spreadd start
Once spread is runnig, try bringing DB up.
Thanks,
Pravesh
Please retstart the spread to clead PID file.
$ /etc/init.d/spreadd restart
After restarting, check the spread status again:
$ /etc/init.d/spreadd status
Once spread is UP and runnig, try starting your DB.
Thanks.