Troubleshoot common issues

Available in VPC

In using Cloud DB for MongoDB, you may encounter the following problems. View the causes and solutions of problems and take proper action:

MongoDB Server connection error

• Error occurs when connecting to MongoDB Server
• It connects directly to the instance of DB, but not to the DB connection string (Timeout occurs).
• It cannot access directly to the OS.

Cause

• You need to create an application server that will communicate with MongoDB Server.
• When accessing via Public domain, you need to edit hosts file.
• Cloud DB for MongoDB does not provide OS access permission.

Solution

Check application server
MongoDB Server created from Cloud DB for MongoDB is currently only accessible within NAVER Cloud Platform, so the applications server must also be created inside NAVER Cloud Platform. For the overall flow of server creation, check scenario and see Start guide by environment for each platform:

• Overall usage scenario
• Getting started with Cloud DB for MongoDB

Edit hosts file

• When accessing via Public domain, you need to edit hosts file of PC you are using.

Execute Failover

I am trying to perform Failover to reproduce Failover situation caused by Primary Server failure to check any effects on applications prior to opening the service.

Cause

-

Solution

You can reproduce Failover situation caused by Primary MongoDB Server failure to check any effects on applications prior to opening the service. For more information on how to use, see Primary DB Failover. The server access may not be available for a certain period during Failover process.

Notifications on exceeding MongoDB Server threshold

Unable to receive an event notification on exceeding MongoDB Server threshold.

Cause

Cloud DB for MongoDB provides monitoring service and event collection service for the performance and operating system of the server. You can directly set thresholds by integrating with Cloud Insight. If there's an error between Cloud Insight integration and custom config value, notification may not be sent normally.

Solution

By default, Cloud DB for MongoDB provides monitoring service and event collection service for the performance and operating system of the server. In addition, you can directly set thresholds and notifications via email or SMS for occurring events by integrating with Cloud Insight. For more information on usage methods, see Monitoring and Event.

Cannot change Config

Unable to change Config as change Config is disabled.

Cause

"Change Config Server" feature is to adjust the number of Config Server that is included when configuring with Sharded Cluster. If you are using Replica Set, there is no Config Server, so this feature does not apply.

Solution

It is the specification that you cannot change Config, so no action is required.

Set access from specific IP

Cannot find out how to set access from specific IP.

Cause

Cloud DB for MongoDB does not provide IP access control for each User.

Solution

It is recommended that you restrict access with ACG settings.