VCN3000 Database Connection Error

Hi, dear!

This topic describes how to deal with the problem that VCN3000 database connection error.

Description

The Database in the VCN 3000 is a service that can be considered as a built-in database also can be named as embedded service. Although it is an embedded service, the function is still separate which means different from the other function/feature such as Real-Time Surveillance, Recording, Device Management, Media Stream Forwarding, etc. The reason is the Database using SQL programming language and the other function is using a different language. Means that, when the server boot up, it may or may not start the database service even other function is starting.

Possible Root Cause

• Current interruption (Power off due to no current)
  

• Man-made (Physically / manual boot up the server)
  

• The Power Adapter having problem
  

• The version is too old (If it is business environment, not suggested to simply upgrade, only suggested to upgrade when the same issue reoccur. If further no such issue reoccur, that means is not the version problem)
  

Solution

1. Open putty and key in your OMU IP address.

   

2. Log in as admin user (First Level user)
   

   Note: For your case, I used the account below
   

   User: root
   

   Password: Change_Me
   

3. Run the following command to switch to root user.
   

   su – root
   

4. Check the database process.
   

   su - postgres -c "/home/postgres/bin/pg_ctl status -D /DB_DATA/data/"
   

   Note :
   

   For your issue, normally it will in abnormal status, that's why you will get the error prompt out message.
   

   If it is normal, it will show as the photo below. ThePID: may be different

   
   

   Once you get the result as photo above but still can’t log in OMU portal and IVS Client, go tostep 7. If you can log in, problem solved.
   

   If it is abnormal, it will show something like “server is not running” and you will not see the directory as shown in the second row of the photo above. Go to next step
   

   

5. Boot the database service.
   

   /home/ivstool/bin/service.sh restart pgdb
   

6. Check whether the database process is started(same as step 4)
   

   su - postgres -c "/home/postgres/bin/pg_ctl status -D /DB_DATA/data/"
   

   Note:
   

   If it is in normal status, try to log in the OMU and IVS Client again.If you can log in, problem solved.
   

   If it is still in abnormal status, go to next step
   

7. Check the space usage
   

   df –h
   

   Make sure the space usage of each directory(excluding “/Snapshot” directory)does not exceed the limit (80%). Refer the circled information in the photo below.

   
   

   Note :
   

   If the space usage does not exceed the limit, kindly ask for assist or support from engineer.
   

   If the space usage exceeded the limit, go to next step
   

8. Delete unnecessary file
   

9. rm /xx/xx/xx/xx(path to go the certain file)
   

   Example : rm /dev/sdosa10/RecordIndexFile
   

   Note: Determine unnecessary file properly by yourself to avoid deleted wrong file
   

10. Reboot the server by using the command and log in to the OMU portal and IVS Client again. If you can log in, problem solved.
    

    reboot
    

    Note: Please Do Not manually power off
    

Suggestion

1. Observe for few weeks first to see whether the same issue will occur or not
   

2. If issues reoccur, kindly follow the provided solution in "Steps to Solve" and feedback the VCN's current version.
   

Thanks for reading!