The Vertica Forum recently got a makeover! Let us know what you think by filling out this short, anonymous survey.
Spread Dead but pid File Exists
If spread ends abnormally, the pid and lock file are left behind. Why would spread end abnormally? An example of output from the upgrade_vertica script when attempting to add nodes. The script fails with the following messages. Updating spread configuration... Verifying spread is running on old cluster Signaling spread to reload configuration Verifying new spread configuration on the existing cluster Error while verifying spread on all hosts (0) Nodes with errors: ['220.127.116.11', '18.104.22.168', '22.214.171.124', '126.96.36.199'] Installation completed with warnings. Installation completed with errors. Installation failed. Entry in adminTools-root.log Mar 26 04:18:36 [email protected]: ['1', ['spread dead but pid file exists', "Try using 'spreadd stop' to clear state"]] Mar 26 04:18:36 Error code 1 ['spread dead but pid file exists', "Try using 'spreadd stop' to clear state"]