Skip to main content

Posts

Showing posts from 2019

sql server 2017 CLR

CREATE or ALTER ASSEMBLY for assembly 'Test.CLRFunctions' with the SAFE or EXTERNAL_ACCESS option failed because the 'clr strict security' option of sp_configure is set to 1. Microsoft recommends that you sign the assembly with a certificate or asymmetric key that has a corresponding login with UNSAFE ASSEMBLY permission. Alternatively, you can trust the assembly using sp_add_trusted_assembly. solution: sp_configure 'clr strict security', 0 RECONFIGURE;

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)

Vertica Request for X percent of Y CPUs rounds to zero CPUs

when trying to create a resource pool using some % of the total CPUs you may encounter this error: Vertica Request for 10% percent of 4 CPUs rounds to zero CPUs \n (6006) (SQLExecDirectW) why? since 10% of 4, rounded by vertica to 0. and you can allocate 0 CPUs to a resource pool how to fix: fix % to be at least 25% or use static allocation of CPU set to a resource pool