jbfavre / docker-vertica Goto Github PK

# docker run -p 5433:5433 --name vertica jbfavre/vertica:latest
Starting up
Fixing filesystem permissions
Creating database
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.
Error: Not all nodes could be reached during database creation
Could not reach node 127.0.0.1
Shutting Down
Vertica: Closing active sessions
vsql: could not connect to server: Connection refused
Is the server running on host "???" and accepting
TCP/IP connections on port 5433?

jbfavre/vertica:8.1 works fine

I didn't have any problems until very recently, and now I see

docker run -p 5433:5433 -e DATABASE_PASSWORD='foo123' jbfavre/vertica:latest          

Starting up
Fixing filesystem permissions
Creating database
Database with 1 or 2 nodes cannot be k-safe and it may lose data if it crashes
Distributing changes to cluster.
	Creating database docker
	Starting bootstrap node v_docker_node0001 (127.0.0.1)
	Starting nodes: 
		v_docker_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_docker_node0001: (DOWN) 
	Node Status: v_docker_node0001: (DOWN) 
	Node Status: v_docker_node0001: (DOWN) 
	Node Status: v_docker_node0001: (DOWN) 
	Node Status: v_docker_node0001: (DOWN) 
	Node Status: v_docker_node0001: (DOWN) 
	Node Status: v_docker_node0001: (DOWN) 
	Node Status: v_docker_node0001: (DOWN) 
	Node Status: v_docker_node0001: (DOWN) 
	Node Status: v_docker_node0001: (DOWN) 
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

Docker desktop on Mac just updated itself, now that's on Version 2.3.0.5 (engine is 19.03.12). Not sure what's going on.

Steps:

1. Run docker run -p 5433:5433 -d -v ~/vertica:/home/dbadmin/docker jbfavre/vertica:9.2.0-7_ubuntu-16.04. Everything good. Stop the container. Exit
2. Run again the same command docker run -p 5433:5433 -d -v ~/vertica:/home/dbadmin/docker jbfavre/vertica:9.2.0-7_ubuntu-16.04. The container exits with error_message=Catalog parent directory already exists: . This is because the directory was already created and rerunning is trying to create the same directory again.

Full log:

Starting up
Fixing filesystem permissions
Creating database
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.
Error: The following nodes(s) could not be prepared: 
Failed to prepare a host for database participation.
See /opt/vertica/log/adminTools.log for details. Host hints follow.
127.0.0.1 directory already exists: [Details - <ATResult> status=2 host=127.0.0.1 error_type=<class 'vertica.engine.api.errors.ATDBPrepareError'> error_message=Catalog parent directory already exists: (/home/dbadmin/docker/catalog/docker)] 

I think we can do something like this to check if the database already exists

Hi, I'm running docker run -p 5433:5433 -d -v ~/vertica_data:/home/dbadmin/docker jbfavre/vertica:9.2.0-7_centos-7 but when shutting down the following lines are not executed:

https://github.com/jbfavre/docker-vertica/blob/master/docker-entrypoint.sh#L15-L19

As a consequence of this trying to start against a previously created persistent store tries to re-create the DB again and fails.

By re-ordering the commands like so it works correctly (i.e. saving the configuration prior to invoke the shutdown of Vertica):

 # Vertica should be shut down properly
 function shut_down() {
-  echo "Shutting Down"
-  vertica_proper_shutdown
   echo 'Saving configuration'
   mkdir -p ${VERTICADATA}/config
   /bin/cp /opt/vertica/config/admintools.conf ${VERTICADATA}/config/admintools.conf
+  echo "Shutting Down"
+  vertica_proper_shutdown
   echo 'Stopping loop'
   STOP_LOOP="true"
 }

Hello @jbfavre. I am not a user of your docker images, but just asking for a little help.

The problem is I can not find anywhere on the web some older vertica packages.
I currently have a setup of 8.1 verticas, and I want to upgrade it. Documentation states that all upgrades should be done incrementally, so 8.1 -> 9.0 -> 9.1 -> 9.2 -> 9.3 -> 10.0 then.
Okay, but (as you probably know) Vertica's website only provides the most recent version in their 'downloads' section.
So do you by any chance have a working link to download those 9.x versions?
I've seen somewhere in Dockerfiles you had your own apt repository for it, but that link is not working for me at this moment.

I create a database with persistent data store. It has a catalog over 1g. When I start the container, I got this error msg. Can I change somewhere to make it wait a little bit longer or this could be something else? Thanks!

Starting up
Fixing filesystem permissions
Starting Database
Info: no password specified, using none
Starting nodes:
v_docker_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_docker_node0001: (DOWN)
Node Status: v_docker_node0001: (DOWN)
Node Status: v_docker_node0001: (DOWN)
Node Status: v_docker_node0001: (INITIALIZING)
Node Status: v_docker_node0001: (DOWN)
Node Status: v_docker_node0001: (DOWN)
Node Status: v_docker_node0001: (DOWN)
Node Status: v_docker_node0001: (DOWN)
Node Status: v_docker_node0001: (DOWN)
Node Status: v_docker_node0001: (DOWN)
Database startup not yet successful --- no nodes report up.
Waiting can sometimes resolve this problem, especially on databases
with large catalogs. See Database Cluster State in Main Menu for updated
cluster state.
Database docker did not start successfully: Nodes Failed to come up

Is there a variable I can set so the db has a password?