Skip to main content

VNETPERF error - Unable to connect to host

when running Vertica vnetperf utility you may face these errors below
although you have no FW between servers
and the communication is OK and no network errors are observed
Vertica DB is up and running on these Vertica hosts as well

[Connector Thread 172.16.8.11 ] Couldn't connect to 172.16.8.11 (family 2, attempt 0): Connection refused; errno=111 (Connection refused)

[Connector Thread 172.16.8.10 ] Couldn't connect to 172.16.8.10 (family 2, attempt 0): Connection refused; errno=111 (Connection refused)

[Connector Thread 172.16.8.12 ] Couldn't connect to 172.16.8.12 (family 2, attempt 0): Connection refused; errno=111 (Connection refused)

[Connector Thread 172.16.8.11 ] Could not find anything to connect to for 172.16.8.11; errno=111 (Connection refused)

[Connector Thread 172.16.8.10 ] Could not find anything to connect to for 172.16.8.10; errno=111 (Connection refused)

[Connector Thread 172.16.8.12 ] Could not find anything to connect to for 172.16.8.12; errno=111 (Connection refused)

Unable to connect to host 172.16.8.10:14159
Unable to connect to host 172.16.8.11:14159
Unable to connect to host 172.16.8.12:14159

why?

this is only because of a little thing -
/tmp file system should be executable on all nodes!!

login as root to all vertica nodes
type this command:
 sudo mount -o remount,exec /tmp

or remove this "noexec" flag from /etc/fstab in /tmp line and remount /tmp

after that run vnetperf again from dbadmin user

[dbadmin@vertica-N1 tmp]$ vnetperf

The maximum recommended rtt latency is 2 milliseconds. The ideal rtt latency is 200 microseconds or less. It is recommended that clock skew be kept to under 1 second.
test              | date                    | node             | index | rtt latency (us)  | clock skew (us)
-------------------------------------------------------------------------------------------------------------------------
latency           | 2018-03-06_10:17:39,795 | 172.16.8.10       | 0     | 374               | -948042
latency           | 2018-03-06_10:17:39,795 | 172.16.8.108      | 1     | 610               | -1996626
latency           | 2018-03-06_10:17:39,795 | 172.16.8.11       | 2     | 407               | -1198531
latency           | 2018-03-06_10:17:39,795 | 172.16.8.12       | 3     | 521               | -1220711
latency           | 2018-03-06_10:17:39,795 | 172.16.8.8        | 4     | 48                | 5
latency           | 2018-03-06_10:17:39,795 | 172.16.8.9        | 5     | 545               | -968135

Comments

Post a Comment

Popular posts from this blog

ORA-27104: system-defined limits for shared memory was misconfigured

I faced this error while trying to restore & recover of a PDB (pluggable database) part of the log file and the solution is described here below: log: initialization parameters used for automatic instance: db_name=CDB db_unique_name=gbux_pitr_PDB1_CDB compatible=12.1.0.2.0 db_block_size=8192 db_files=200 diagnostic_dest=/oracle/app/oracle _system_trig_enabled=FALSE sga_target=1888M processes=200 db_create_file_dest=/oracle/auxilary log_archive_dest_1='location=/oracle/auxilary' enable_pluggable_database=true _clone_one_pdb_recovery=true #No auxiliary parameter file used starting up automatic instance CDB RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of recover command at 07/31/2016 16:22:20 RMAN-04014: startup failed: ORA-27104: system-defined limits for shared...
6 comments
Read more

ora-65035 while create pluggable database from another one

or : ORA-21000: error number argument to raise_application_error of -65035 is out of range Cause: this error caused because of an unrecoverable transaction in the source DB. Solution: 1. either stop and start your pluggable source DB 2. identify the open transaction and kill it if you can. use this query to do so: select * from v$transaction t,v$session  s where t.ses_addr = s.saddr;
Post a Comment
Read more

KUP-04074: no write access to directory when trying to query EXTERNAL table

Hi All, You may think that in order to query external table you should have only read permission on the Directory Object which sounds very reasonable.... but in some external table the definition include this part of code: ACCESS PARAMETERS         ( records delimited by newline           LOGFILE   "EXTERNAL_FILES" : 'faults.txt'       FIELDS TERMINATED BY ';'             missing FIELD values are null this definition force a write permission on the directory object.  else you will run into this error: ORA-29913: error in executing ODCIEXTTABLEOPEN callout ORA-29400: data cartridge error KUP-04074: no write access to directory object EXTERNAL_FILES 29913. 00000 -  "error in executing %s callout" *Cause:    The execution of the specified callout caused an error. *Acti...
Post a Comment
Read more