Spread error; can not determine which DBs are running; attempting to continue

Document ID : KB000032480
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue:

When starting the vertica database we see:

Spread error; can not determine which DBs are running; attempting to continue.  

Then we see the following error:

Spread does not seem to be running on <ip address>. The database will not be started on this host

 

Environment:

2.4.x and up

 

Resolution:

1. Run the following command to get the spread daemon status:

# /etc/init.d/spreadd status

- This will likely give a [ Failure ] status

 

2. Run the following command to stop the spread daemon:

# /etc/init.d/spreadd stop

 

3. Again, run the following command to get the spread daemon status:

# /etc/init.d/spreadd status

 

4. This is the output you will see:

spread is stopped

 

If you are having trouble starting spread, check

/opt/vertica/config/vspread.conf

and spread logs in /tmp/spread_* and /var/log/spreadd.log

 

5. Run the following command to start the spread daemon:

# /etc/init.d/spreadd start

 

This is the output you will see:

Starting spread daemon: spread (pid  19035) is running...

                                                           [  OK  ]

 

After doing this spread should now be running.  To verify you can run the following command:

ps -ef | grep spread

 

You should see the process running on the system:

 

dradmin   8921     1  0 Nov28 ?        01:20:28 /opt/vertica/spread/sbin/spread -c /catalog/drdata/v_drdata_node0001_catalog/spread.conf

 

root     32503 20837  0 13:31 pts/0    00:00:00 grep spread

 

From here you should now be able to successfully start the vertica database through the adminTools GUI