Vertica 9.1 - seems I can't create a database on SuSE ..
Hi All -
I actually seem to need help here ..
Creating a database on my laptop on openSuSE 42.3.
Before you come with the ubiquitous question about logs - the catalogue and data directories were not even created, so no luck there.
Posting commands and output of install_vertica
and then, below , as dbadmin, admintools
with the --skip-fs-checks
switch, as my laptop has no ext4 file system.
Searched the forum, Stackoverflow, and the web for answers, to no avail.
Any ideas?
See details below, for starters ...
Marco the currently not-so-sane ....
Installed it like so - after dealing with a few FAIL messages, except the one on cpu scaling:
linux-7zn4:/tmp # /opt/vertica/sbin/install_vertica --hosts 127.0.0.1 -Y --failure-threshold NONE
Got this output:
Vertica Analytic Database 9.1.0-0 Installation Tool
Validating options...
Mapping hostnames in --hosts (-s) to addresses...
Starting installation tasks.
Getting system information for cluster (this may take a while)...
Default shell on nodes: 127.0.0.1 /bin/bash
Validating software versions (rpm or deb)...
Beginning new cluster creation...
successfully backed up admintools.conf on 127.0.0.1
Creating or validating DB Admin user/group...
Password for new dbadmin user (empty = disabled) Successful on hosts (1): 127.0.0.1 Provided DB Admin account details: user = dbadmin, group = verticadba, home = /home/dbadmin Creating group... Group already exists Validating group... Okay Creating user... Adding user, Setting credentials Validating user... Okay
Validating node and cluster prerequisites...
Prerequisites not fully met during local (OS) configuration for verify-127.0.0.1.xml: HINT (S0305): https://my.vertica.com/docs/9.1.x/HTML/index.htm#cshid=S0305 TZ is unset for dbadmin. Consider updating .profile or .bashrc HINT (S0045): https://my.vertica.com/docs/9.1.x/HTML/index.htm#cshid=S0045 Could not find the following tools normally provided by the sysstat package: mpstat, iostat WARN (S0160): https://my.vertica.com/docs/9.1.x/HTML/index.htm#cshid=S0160 These disks do not have 'ext3' or 'ext4' filesystems: '/dev/sda4' = 'xfs' WARN (N0010): https://my.vertica.com/docs/9.1.x/HTML/index.htm#cshid=N0010 Linux iptables (firewall) has some non-trivial rules in tables: filter WARN (N0011): https://my.vertica.com/docs/9.1.x/HTML/index.htm#cshid=N0011 SuSEfirewall2 appears to be enabled. WARN (S0112): https://my.vertica.com/docs/9.1.x/HTML/index.htm#cshid=S0112 vm.swappiness is higher than recommended: your 60 > 1 FAIL (S0140): https://my.vertica.com/docs/9.1.x/HTML/index.htm#cshid=S0140 CPUs have invalid cpufreq scaling policies: cpu0, cpu1, cpu2, cpu3, cpu4, cpu5, cpu6, cpu7 System prerequisites passed. Threshold = NONE
Establishing DB Admin SSH connectivity...
Installing/Repairing SSH keys for dbadmin
Setting up each node and modifying cluster...
Creating Vertica Data Directory... Updating agent... Creating node node0001 definition for host 127.0.0.1 ... Done
Sending new cluster configuration to all nodes...
Starting agent...
Completing installation...
Running upgrade logic No spread upgrade required: /opt/vertica/config/vspread.conf not found on any node Installation complete. Please evaluate your hardware using Vertica's validation tools: https://my.vertica.com/docs/9.1.x/HTML/index.htm#cshid=VALSCRIPT To create a database: 1. Logout and login as dbadmin. (see note below) 2. Run /opt/vertica/bin/adminTools as dbadmin 3. Select Create Database from the Configuration Menu Note: Installation may have made configuration changes to dbadmin that do not take effect until the next session (logout and login). To add or remove hosts, select Cluster Management from the Advanced Menu.
Then, su - dbadmin
, followed by the admintools command to create the database. Answering 'yes' twice to the question if I wanted to wait (on a create-new-database, single node, on my laptop, using 127.0.0.1 as the nost....)
dbadmin@linux-7zn4:~> /opt/vertica/bin/admintools -t create_db -s localhost --skip-fs-checks -d sbx Info: no password specified, using none Database with 1 or 2 nodes cannot be k-safe and it may lose data if it crashes Distributing changes to cluster. Creating database sbx Starting bootstrap node v_sbx_node0001 (127.0.0.1) Starting nodes: v_sbx_node0001 (127.0.0.1) Starting Vertica on all nodes. Please wait, databases with a large catalog may take a while to initialize. Node Status: v_sbx_node0001: (DOWN) Node Status: v_sbx_node0001: (DOWN) Node Status: v_sbx_node0001: (DOWN) Node Status: v_sbx_node0001: (DOWN) Node Status: v_sbx_node0001: (DOWN) [. . .] Node Status: v_sbx_node0001: (DOWN) Node Status: v_sbx_node0001: (DOWN) Node Status: v_sbx_node0001: (DOWN) Node Status: v_sbx_node0001: (DOWN) Node Status: v_sbx_node0001: (DOWN) It is suggested that you continue waiting. Do you want to continue waiting? (yes/no) [yes] no ERROR: Database did not start cleanly on initiator node! Stopping all nodes Could not connect to database (EOF received)vsql: could not connect to server: Connection refused Is the server running on host "127.0.0.1" and accepting TCP/IP connections on port 5433? Error: Database did not start cleanly on initiator node! Stopping all nodes
Comments
One idea that comes to mind, reading it again:
I had never noticed any references to establishing dbadmin SSH connectivity during the run of install_vertica before.
Is that new in 9.1?
And could it interfere with using 127.0.0.1 as the host IP address?
I can't possibly use a DNS issued IP address for the database, as my laptop connects to the Net all over the place ...?
marco
SSH connectivity is important and has always been, albeit less so for single-node databases.
I would guess your issue is that localhost is actually mapped to something like 127.0.1.1 in your /etc/hosts. If you fix is to 127.0.0.1 things will work.
Hi Ben -
Thanks for reaching out -
I'm afraid not ....
I had tried with both localhost and 127.0.0.1 as the --hosts parameter, to no avail ..
Cheers -
Marco
Don't hit enter on the failed creation, go to another window - the directories should still be there.
Pull and post the last couple entries of CATALOGPATH/startup.log
I would confirm that ifconfig reports an adapter that claims to be 127.0.0.1
Thanks for the tip on not exiting the failed creation, Ben.
startup.log looks inconspicuous:
but vertica.log looks bad:
So I'm running into a segmentation violation ....!
Don't really know where to look now, but I'll try ...
Marco
Hi all, I am having the same issue but in my case after upgrading from 9.0 to 9.1. In may case I am running Vertica on SLES12SP2. I cannot start any nodes nor start any previously existing databases nor creating a new database.
Vertica.log shows the same PANIC error:
018-05-16 16:49:51.484 Main:7fae6a33bb80 [Main] Handling signal: 11
2018-05-16 16:49:51.700 Main:7fae6a33bb80 [Main] Received fatal signal SIGSEGV.
2018-05-16 16:49:51.700 Main:7fae6a33bb80 [Main] Info: si_code: 128, si_pid: 0, si_uid: 0, si_addr: (nil)
Could this be an issue with Vertica 9.1 on SUSE?
Thanks!!
Hugo