If you get these errors: Unexpected error. Unable to verify database connection.  Checking the logs, we see the following: 2019-06-24 23:42:18,402 INFO scm-web-118667:com.cloudera.enterprise.JavaMelodyFacade: Entering HTTP Operation: Method:POST, Path:/clusters/2/healthStatusBar 2019-06-24 23:42:18,404 INFO scm-web-119745:com.cloudera.enterprise.JavaMelodyFacade: Entering HTTP Operation: Method:POST, Path:/clusters/2/statusContent 2019-06-24 23:42:18,412 INFO scm-web-118667:com.cloudera.enterprise.JavaMelodyFacade: Exiting HTTP Operation: Method:POST, Path:/clusters/2/healthStatusBar, Status:200 2019-06-24 23:42:18,420 INFO scm-web-119745:com.cloudera.enterprise.JavaMelodyFacade: Exiting HTTP Operation: Method:POST, […]

If you're getting the following on your patroni cluster: Jun 24 23:30:50 psql02 etcd: failed to send out heartbeat on time (exceeded the 250ms timeout for 1.229927109s) Jun 24 23:30:50 psql02 etcd: server is likely overloaded Jun 24 23:30:50 psql02 etcd: failed to send out heartbeat on time (exceeded the 250ms timeout for 1.22987947s) Jun […]

In case you receive the following: cloudera-scm-server.log:2019-06-21 01:16:57,763 ERROR CommandPusher:com.cloudera.cmf.model.DbCommand: Command 609(HiveTestDatabaseConnection) has completedFINISHED, success:false, msg:User cannot run DDL statements on the specified database. Attempt to create and drop a table failed. check the logs or test creating a temporary table: cloudera-scm-server.log:Caused by: org.postgresql.util.PSQLException: ERROR: cannot execute UPDATE in a read-only transaction cloudera-scm-server.log:Caused by: java.sql.BatchUpdateException: […]

When you get this: Cannot read XML: (41) Specification mandate value for attribute data-pjax-transient [Line: 38 | Column: 40]. ensure you're download the xml or any file from github using the clone or download a zip option, instead of Save As / Save Link As …. Thx, TK

Problems restoring a database? No worries: https://forums.mysql.com/read.php?20,675392,675404#msg-675404 Here’s the session: [root@mysql01 tmp]# ls -altri total 592120 134766607 -rw-r–r–.  1 root root 606322782 Jun  5 07:53 mysql-c01.sql.1556440201 134604506 drwxr-xr-x.  2 root root        37 Jun  5 07:54 . 201326721 dr-xr-x—. 14 root root      4096 Jun  8 13:03 .. [root@mysql01 tmp]# mysql -u […]

Another issue we can run into is the following set of messages: 2019-06-08T04:56:24.518538Z 0 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 110 (Connection timed out) at gcomm/src/pc.cpp:connect():158 2019-06-08T04:56:24.518591Z 0 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():209: Failed to open backend connection: -110 (Connection timed out) 2019-06-08T04:56:24.518764Z 0 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1458: Failed to […]

Let's setup some PostgreSQL backups.   In this post, we'll set up a pull methodology in order to get backups of our PostgreSQL Cluster .  The backups will be saved remotely so any failures in our cluster will be independent of our PostgreSQL backups. First, let's prepare the postgres account so we can login remotely without […]

So we run into a little problem getting out PostgreSQL Patroni w/ ETCD cluster going after a rather serious failure.  # sudo su – postgres $ /usr/pgsql-10/bin/postgres -D /data/patroni –config-file=/data/patroni/postgresql.conf –listen_addresses=192.168.0.118 –max_worker_processes=8 –max_locks_per_transaction=64 –wal_level=replica –track_commit_timestamp=off –max_prepared_transactions=0 –port=5432 –max_replication_slots=10 –max_connections=100 –hot_standby=on –cluster_name=postgres –wal_log_hints=on –max_wal_senders=10 -d 5 This resulted in one of the 3 messages above.  Hence […]