The Vertica Forum recently got a makeover! Let us know what you think by filling out this short, anonymous survey.

Error Management Console

Hello friends, my Vertica Management Console this showing that database is with CRITICAL status, but I'm emitrindo sql commands and is normal, you know it can be?

Comments

  • SruthiASruthiA Employee

    Could you please explain error in more detail?? if possible, could you please attach screenshot

     

     

    -Regards,

     Sruthi

  • Annex images of the console.

  • SruthiASruthiA Employee

    Could you please restart the database through management console UI and also share me with the following information

     

    1) Status of vertica agent on all nodes
    You can get this by executing below mentioned command

    /etc/init.d/vertica_agent status

    2) Plese check if vertica process is running on management console server.

    ps -ef | grep vertica

    3) Please send us agent.log from all the nodes :

    /opt/vertica/log/agent
    /opt/vertica/log/agentStdMsg.log
    /opt/vertica/log/agentTool-<username>.log

     

     

    -Regards,

     Sruthi

  • Anexx Logs

     

     

    [email protected]:~# /etc/init.d/vertica_agent status

     

    Vertica Agent: (pid 2342) is running...

    [email protected]:~#
    [email protected]:~# ps -ef | grep vertica

     

    dbadmin 2290 1 2 10:18 ? 00:02:37 /opt/vconsole/vendor/oracle/java/jre/1.7.0_51/bin/java -Dvertica.home=/opt/vertica -Dvconsole.home=/opt/vconsole -Djava.library.path=/opt/vconsole/lib -Dderby.system.home=/opt/vconsole/mcdb/derby -Xmx2048m -Xms1024m -XX:MaxPermSize=256m -jar /opt/vconsole/lib/webui.war
    dbadmin 2342 1 0 10:18 ? 00:00:00 /bin/bash /opt/vertica/agent/agent.sh /opt/vertica/config/users/dbadmin/agent.conf
    dbadmin 2354 2342 1 10:18 ? 00:01:04 /opt/vertica/oss/python/bin/python ./simply_fast.py
    dbadmin 3966 1 0 10:25 ? 00:00:00 /opt/vertica/spread/sbin/spread -c /home/dbadmin/BIHC/v_bihc_node0001_catalog/spread.conf
    dbadmin 3968 1 2 10:25 ? 00:01:48 /opt/vertica/bin/vertica -D /home/dbadmin/BIHC/v_bihc_node0001_catalog -C BIHC -n v_bihc_node0001 -h xxxxxxxx -p 5433 -P 4803 -Y ipv4
    dbadmin 3972 3968 0 10:25 ? 00:00:01 /opt/vertica/bin/vertica-udx-zygote 12 10 3968 debug-log-off /home/dbadmin/BIHC/v_bihc_node0001_catalog/UDxLogs
    root 28758 3199 0 11:55 pts/0 00:00:00 grep --color=auto vertica

  • A CRITICAL node is a node which has the final copy of some peice of information or would require that the cluster stop if it failed.

     

    Vertica uses data replication to ensure that if a fault occurs, you do not lose data. If you have 2 copies of data then you can lose 1 copy and continue operating. This is called K-Safety with k=1.

     

    A 1-node database cannot have K-Safety, since there is no where else to place your data. k=0.

     

    Therefore your node will always be critical. If something happens to that node, your database stops and you may lose your data.

     

    The K Safety and Critical concepts should be available in our documentation.

     

    - Derrick

  • I got it , okay thanks for the help!

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file

Can't find what you're looking for? Search the Vertica Documentation, Knowledge Base, or Blog for more information.