Segmentation fault for admintools

Hello Oleg,

Thanks for posting! Could you provide us with a screenshot of the exact error you're getting so we can investigate the problem?

Thanks,
Rory

Ho Oleg,

The root cause of this issue is the corruption on some python libraries at your end.
Maybe you can trace the error and pass on the trace file here.

Hope this helps.
NC

Hello Rory,

Below you can see message with error

[dbadmin@dwh-test-node1 ~]$ admintools
Segmentation fault
[dbadmin@dwh-test-node1 ~]$ which admintools
/opt/vertica/bin/admintools

Hello Navin.
How could i trace error ?

Oleg.

Hi

1) have you tried rebooting the node?
2) check out admintools-dbadmin.log to see if there are any errors.  located in dir /opt/vertica/log
3) does this happen on other nodes?
4) can you issue command line commands such as
/opt/vertica/bin/admintools -t view_cluster

Regards

Hi!

I've restarted node.
Now vertica does not start at all.

Vertica Agent: sh dead but pid file existsVertica Console: status OK
Vertica: Segmentation fault (core dumped)
status not OK

I try again but have the same error

[root@dwh-test-node1 init.d]# /opt/vertica/sbin/verticad status
Vertica: Segmentation fault (core dumped)
status not OK

In log file i have many lines like this

Dec  8 11:21:34  [7443] [SSH.checkDatabaseState] dbName=None, port=5433, nodemap={'v_dwh_prod_node0001': '10.11.6.21'}Dec  8 11:21:34  [7443] [SSH.checkDatabaseState] vsql_cmd = /opt/vertica/bin/vsql --no-vsqlrc -n -p 5433 -h '10.11.6.21'
Dec  8 11:21:34  [7443] [SSH.checkDatabaseState] vsql return code = 2
Dec  8 11:21:34  [7443] [SSH.checkDatabaseState] dbName=None, port=5433, nodemap={'v_dwh_prod_node0001': '10.11.6.21'}
Dec  8 11:21:34  [7443] [SSH.checkDatabaseState] vsql_cmd = /opt/vertica/bin/vsql --no-vsqlrc -n -p 5433 -h '10.11.6.21'
Dec  8 11:21:34  [7443] [SSH.checkDatabaseState] vsql return code = 2


Oleg.

Hi!

May be to reinstall? Because something wrong with database initialization.
Take a look on your output:

Dec  8 11:21:34  [7443] [SSH.checkDatabaseState] dbName=None

dbName = None, that is a reason for segfault.


For example how looks my log:

Dec  8 19:23:19  [2515] [SSH.checkDatabaseState] dbName=dev, port=5433, nodemap={'v_dev_node0001': '127.0.0.1'}
Dec  8 19:23:19  [2515] [SSH.checkDatabaseState] vsql_cmd = /opt/vertica/bin/vsql --no-vsqlrc -n -p 5433 -h '127.0.0.1' dev
Dec  8 19:24:24  [2515] [SSH.checkDatabaseState] vsql return code = 2
Dec  8 19:24:24  [2515] {"type":"NODEHOST", "state":"INITIALIZING", "host":"127.0.0.1", "node":"v_dev_node0001", "dbname":"dev", "msg":"", "maxSteps":"1", "currStep":"1"}
Dec  8 19:24:24  [2515] [SSH.checkForRunning] nodeStatusString:     Node Status: v_dev_node0001: (INITIALIZING)

PS
1. Can you post your arguments to vertica_install script?
2. Did you created a database from command line or via adminTools?
(posting logs are useful - its for your second question about Oracle)

Some time ago i installed vertica on host dwh-test-node1 and made vertica db dwh_prod

Befor making this post i tried add host dwh-test-node2 into cluster but have error seg fault.

May be there were some problem with db or host and i lost db configuration.

How could i check if db configuration is ok ?

Oleg.

Hi!

How could i check if db configuration is ok ?

I don't know what exactly you are looking, but if db is down so only via Vertica Editor. Unfortunately Vertica Editor is undocumented. I don't wanna explain how to use in Vertica Editor, better that employee will explain.

Hi.

I'm looking possibility to check what is wrong, why my vertica db does not start and what i should do to recover db availability.

Oleg.