-
Confirm that GridDB administrator password has been properly set (e.g. admin).
Please refer to http://griddb.org/griddb_nosql/manual/GridDB_QuickStartGuide.html#sec-2-2-4 .
-
Confirm the cluster/clusterName setting in gs_cluster.json.
Please refer to http://griddb.org/griddb_nosql/manual/GridDB_QuickStartGuide.html#sec-2-3-2 .
-
Confirm that the output of "$ hostname -i" is not 127.0.0.1 but your IP address.
- Otherwise, check the setting in /etc/hosts.
Please refer to http://griddb.org/griddb_nosql/manual/GridDB_QuickStartGuide.html#sec-2-3-1 .
-
After installing RPM or DEB package, if the "environment variable not set" error occurs:
- Login as "gsadm" user after setting its password. The environment variable will be automatically configured.
- If you login with the su command, add "-" or "-l" option, for example "$ su - gsadm".
Please refer to http://griddb.org/griddb_nosql/manual/GridDB_RPM_InstallGuide.html#sec-1.3 .
-
If a proxy variable (http_proxy) has been set up, it is necessary to configure the --no-proxy option.
- Specify "127.0.0.1" and the address of "$ hostname -i", for example "$ export no_proxy=127.0.0.1,10.0.2.15".
Please refer to "[Points to note when using operating commands]" in http://griddb.org/griddb_nosql/manual/GridDB_QuickStartGuide.html#sec-3 .
-
The firewall might be the cause. Open the required port number to allow connections through the firewall.
- Example for CentOS: $ firewall-cmd --zone=public --add-port=31999/udp
- Example for Ubuntu: $ ufw allow 31999/udp
Please refer to "/transaction/notificationPort" in http://griddb.org/griddb_nosql/manual/GridDB_QuickStartGuide.html#sec-5-1-2 .
-
Use Fixed list method or Provider method insted of Multicast method (default) as GridDB cluster configuration.
Please refer to http://griddb.org/griddb_nosql/manual/en/GridDB_FeaturesReference.html#42-cluster-configuration-methods .