Symptoms:
After fixing the issues related to a a failed vertica upgrade, and then rerunning the upgrade, the following error is seen:
Database is running. Please stop the database via admintools and re-run install_dr.sh. [FAIL]
When attempting to launch adminTools from /opt/vertica/bin to verify if the database is running the following error is seen:
[Errno 13] Permission denied: '/opt/vertica/config/admintools.conf.lock'
Environment:
2.6 Data Repository
Cause:
The cause of the [Errno 13] Permission denied: '/opt/vertica/config/admintools.conf.lock' error when launching adminTools was that several directories changed owner and group. The directories were:
The owner and group changed to root for both /opt/vertica/config and /opt/vertica/log. For /opt/vertica/scripts, just the group changed to root
Workaround:
The owner and group for /opt/vertica/config and /opt/vertica/log should be changed to dradmin (or the equivalent user) and verticadba respectively and the group for /opt/vertica/scripts should be changed to verticadba. This can be accomplished with the following commands:
This is what it should look like after running the commands noted above and doing a directory listing:
You will now be able to successfully launch adminTools without seeing the [Errno 13] Permission denied: '/opt/vertica/config/admintools.conf.lock', confirm the database is down, and rerun your install