Skip to main content

Posts

Showing posts from March, 2019

docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.

Hi, when trying to install Graphite component using docker I faced this error: docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?. I was bit struggling to understand what does it mean, apparently it's not a permission issue or any kind of other OS issues  it's just because I've reinstalled  docker on unclean old installation of it the solution here is so simple: restart docker service and re-run the component installation  [root@VerticaNode01 ~]# service docker stop Redirecting to /bin/systemctl stop docker.service You have new mail in /var/spool/mail/root [root@VerticaNode01 ~]# service docker start Redirecting to /bin/systemctl start docker.service [root@VerticaNode01 ~]# [root@VerticaNode01 ~]# [root@VerticaNode01 ~]# docker run -d --name graphite --restart=always -p 80:80 -p 2003-2004:2003-2004 -p 2023-2024:2023-2024 -p 8125:8125/udp -p 8126:8126 graphiteapp/graphite-st

vertica 4803 error: no such file or directory

Hi All, Sometimes, especially working on virtual environments, file system can become "read only" to protect from corruptions and other failures if Vertica nodes data/catalog file systems become read only, you probably face this error after trying to restart the cluster and even the spread The solution for was to fix "read only" issues (even with just restarting the VM for most of the cases)  then start Vertica with the latest good epoch this error: vertica 4803 error: no such file or directory will appear in the spread log (dbLog)