Header Shadow Image


Archive for the 'NIX Posts' Category

cloudera-scm-agent: SSLError: sslv3 alert bad certificate

Getting this? [06/Jul/2019 19:49:28 +0000] 2245 MainThread agent        ERROR    Heartbeating to cm-r01nn01.mws.mds.xyz:7182 failed. Traceback (most recent call last):   File "/opt/cloudera/cm-agent/lib/python2.7/site-packages/cmf/agent.py", line 1387, in _send_heartbeat     self.cfg.max_cert_depth)   File "/opt/cloudera/cm-agent/lib/python2.7/site-packages/cmf/https.py", line 139, in __init__     self.conn.connect()   File "/opt/cloudera/cm-agent/lib/python2.7/site-packages/M2Crypto/httpslib.py", line 69, in connect     sock.connect((self.host, self.port))   File […]

ERROR    Heartbeating to failed.

Getting this error when connecting cloudera-scm-agents to the server? [06/Jul/2019 16:16:55 +0000] 23442 MainThread agent        ERROR    Heartbeating to srv-c01.mws.mds.xyz:17182 failed. Traceback (most recent call last):   File "/opt/cloudera/cm-agent/lib/python2.7/site-packages/cmf/agent.py", line 1387, in _send_heartbeat     self.cfg.max_cert_depth)   File "/opt/cloudera/cm-agent/lib/python2.7/site-packages/cmf/https.py", line 139, in __init__     self.conn.connect()   File "/opt/cloudera/cm-agent/lib/python2.7/site-packages/M2Crypto/httpslib.py", line 69, in […]

Setting tune.ssl.default-dh-param to 1024 by default, if your workload permits it you should set it to at least 2048. Please set a value >= 1024 to make this warning disappear.

Getting this? haproxy-systemd-wrapper[17526]: [WARNING] 186/151058 (17527) : Setting tune.ssl.default-dh-param to 1024 by default, if your workload permits it you should set it to at least 2048. Please set a value >= 1024 to make this warning disappear. add this to your haproxy config: global         log             […]

Unexpected error. Unable to verify database connection. / Cannot find CDH’\”s bigtop-detect-javahome.

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, […]

ERROR: cannot execute CREATE TABLE in a read-only transaction

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 […]

User cannot run DDL statements on the specified database. Attempt to create and drop a table failed.

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: […]

Cannot read XML: (41) Specification mandate value for attribute data-pjax-transient [Line: 38 | Column: 40].

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

[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

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] […]

PostgreSQL Pull Backup

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 […]

PANIC:  replication checkpoint has wrong magic 0 instead of 307747550

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 […]


     
  Copyright © 2003 - 2013 Tom Kacperski (microdevsys.com). All rights reserved.

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 Unported License