Error Communicating With Server Greenplum
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us error communicating with server 2k15 Learn more about Stack Overflow the company Business Learn more about hiring developers or
Error Communicating With Server Facebook
posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow
Error Communicating With Server Hbo
Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Cannot Setup Instance of Greenplum Command Center Web Application
Error Communicating With Server Hbo Go
on Greenplum Open Source Database with Centos 7 Cluster up vote 0 down vote favorite I have Greenplum Open Source Database running on a 3-node Centos 7 cluster. The database is running and I am able to connect and run queries. Installation of Greenplum Command Center 2.0 works. When I try to configure an instance for the web appliance part using gpcmdr --setup I get the following error communicating with server nba 2k15 error: Creating instance schema in GPDB. Please wait ... Failed to setup Command Center instance [myCustomInstance]: Exception encountered while fetching GPDB version info Connection error for query select version();: FATAL: Ident authentication failed for user "gpmon" Here is my pg_hba.conf file for testing purposes. This still generates the above error even with the host all all ::1/128 trust # IPv6 local connections: local all gpadmin ident host all gpadmin 127.0.0.1/28 trust host all gpadmin 172.17.0.1/32 trust host all gpadmin 192.168.65.90/32 trust host all gpadmin 192.168.122.1/32 trust host all gpadmin ::1/128 trust host all gpadmin fe80::210:18ff:fe94:3768/128 trust host all gpadmin fe80::42:11ff:fea9:f1df/128 trust host all gpadmin fe80::b84c:8bff:fe4a:5ce2/128 trust host all gpadmin fe80::419:d7ff:fe90:6c48/128 trust host all gpadmin fe80::c0ff:81ff:feae:c1ec/128 trust local replication gpadmin ident host replication gpadmin samenet trust local gpperfmon gpmon md5 host all gpmon 0.0.0.0/0 md5 host all gpmon ::1/128 md5 host all all ::1/128 trust Added in host all gpmon ::1/128 md5 before last line. Restarted the database and reran gpcmdr --setup. Below are the log files gpperfmon/logs 2016-03-14 20:37:19|:-LOG: sounds like you have just upgraded your database, creating newer tables 2016-03-14 20:37:19|:-WARNING: [gpmondb.c:55] failed to execut query 'BEGIN; CREATE TABLE public.log_alert_history (LIKE gp_toolkit.__gp_log_master_ext) DISTRIBUTED BY (logtime) PARTITION BY range (logtime)(START
Read Quick Links Today's Posts View Site Leaders Who's Online Advanced Search Forum Attunity Replicate Data Warehouses Greenplum Topics Error when trying to define a new Greenplum database Results 1 to 1 of 1 Thread: Error when trying error communicating with server 2k14 to define a new Greenplum database LinkBack LinkBack URL About LinkBacks Bookmark & error communicating with server ps4 Share Digg this Thread!Add Thread to del.icio.usBookmark in TechnoratiTweet this thread Thread Tools Show Printable Version Email this Page… Search Thread Advanced error communicating with server game center Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 10-04-2012,10:43 AM #1 DrorHarari CTO Join Date Sep 2006 Posts 233 Rep Power 10 Error when trying to define a new Greenplum database Issue http://stackoverflow.com/questions/35997662/cannot-setup-instance-of-greenplum-command-center-web-application-on-greenplum-o The following error was observed when trying to define a new Greenplum database in Attunity Replicate: 120: 2012-10-04T16:25:38 [greenplum_imp.c :01672]I: Going to connect to server greenplum421 database nirs 120: 2012-10-04T16:25:38 [greenplum_imp.c :01219]E: Unexpected result was return from the gpfdist test (
Unauthorized
), HTTP status was 401. [122400] Error: Greenplum endpoint initialization error. The error was seen when clicking on the drop down menu for http://forums.attunity.com/forums/greenplum-topics/error-when-trying-define-new-greenplum-2151.html selecting the Greenplum database to use. Solution The default port number proposed for gpfdist was 8080. When clicking the drop down menu for selecting the Greenplum database, Attunity Replicate tries to connect to both Greenplum and to the gpfdist on the specified port (in this case, 8080). As it happened, on the same machine where Attunity Replicate was installed, there was also installed the Oracle Server software which starts its management console (an HTTP server) on port 8080. When Attunity Replicate tried to communicate with gpfdist on port 8080 it actually was talking with the Oracle web server which issues the error. The solution is to simply pick up a different port for gpfdist that is not in use. Share Share this post on Digg Del.icio.us Technorati Twitter By Dror Harari To Find Out more About Attunity Technology: Attunity or: Contact Us Reply With Quote « - | automated migration and conversion » Posting Permissions You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is On [VIDEO] code is On HTML code is Off Trackbacks are On Pingbacks are On Refbacks are On Forum Rules Contact Us Attunity Integration Technology Forum Archive Top All times are GMT4.3.3.1 Release Notes Greenplum Database 4.3.3 Release Notes Greenplum Database 4.3.2.1 Release Notes Greenplum Database 4.3.2 Release Notes Greenplum Database 4.3.1 http://gpdb.docs.pivotal.io/4330/install_guide/prep_os_install_gpdb.html Release Notes Greenplum Database 4.3 Release Notes Greenplum Database 4.3.x http://kb.tableau.com/articles/knowledgebase/err-large-data-odbc-oledb Resolved Issues Server Documentation Installation Guide Preface Introduction to Greenplum The Greenplum Master The Segments The Interconnect ETL Hosts for Data Loading Greenplum Performance Monitor Estimating Storage Capacity Calculating Usable Disk Capacity Calculating User Data Size Calculating Space Requirements for Metadata error communicating and Logs Configuring Your Systems and Installing Greenplum System Requirements Setting the Greenplum Recommended OS Parameters Running the Greenplum Installer Installing and Configuring Greenplum on all Hosts Installing Oracle Compatibility Functions Installing Greenplum Database Extensions Creating the Data Storage Areas Synchronizing System Clocks Enabling iptables Next Steps Validating Your Systems Validating error communicating with OS Settings Validating Hardware Performance Validating Network Performance Validating Disk I/O and Memory Bandwidth Configuring Localization Settings Initializing a Greenplum Database System Installation Management Utilities gpactivatestandby gpaddmirrors gpcheck gpcheckperf gpdeletesystem gpinitstandby gpinitsystem gppkg gpscp gpseginstall gpssh-exkeys gpssh gpstart gpstop gptransfer Greenplum Environment Variables Required Environment Variables Optional Environment Variables Administrator Guide About This Guide Greenplum Database Concepts About the Greenplum Architecture About Redundancy and Failover in Greenplum Database About Parallel Data Loading About Management and Monitoring Utilities Managing a Greenplum System Starting and Stopping Greenplum Database Accessing the Database Configuring Your Greenplum System Enabling High Availability Features Backing Up and Restoring Databases Expanding a Greenplum System Migrating Data with Gptransfer Monitoring a Greenplum System Routine System Maintenance Tasks Managing Greenplum Database Access Configuring Client Authentication Managing Roles and Privileges Using LDAP Authentication with TLS/SSL Using Kerberos Authentication Working with Databases Defining Database Objects Managing Data Loading and Unloading Data Querying Data
a large data source through an ODBC or OLE DB connection, you might experience slow performance when querying the database or creating an extract. In many cases, the Processes tab of the Windows Task Manager might indicate that the tabprotosrv.exe or vizqlserver process is using an extremely large amount of memory. The performance issue can occur while accessing data through Tableau Desktop or through tabcmd. Common errors that can occur in this scenario If an error message occurs, it typically indicates an error 0x80004005 with a memory-related error. For example, the second error could be a memory allocation or out of memory error. Occasionally, error 0x80004005 is not the primary error. In this situation, a related memory error still occurs. The errors might also reference com.tableausoftware.vizql.dll. These errors can appear in Tableau Desktop or Server log files or in alerts on the screen. Customize the driver buffer settings One possible solution to the performance errors is to configure the driver setting that specifies the number of rows at a time that the driver fetches from the database and returns to Tableau (driver buffer size). Important: Although changing the driver buffer size can resolve issues caused by too large or too frequent data fetches, the change might not resolve all performance-related issues. How you configure the driver depends on the data source. Typically this involves changing a setting that refers to the row fetch count. The following sections describe how to do this with a few different data sources. Note: Use the information in this article as a supplement to the documentation that was provided for your database software. Consult the database documentation for any recommended settings or other relevant information. Greenplum and PostgreSQL To change the driver setting for Greenplum for PostgreSQL, create a Tableau Datasource Customization (TDC) file and specify the row fetch count. A TDC file binds to a single data source, and it defines the capabilities for that data source. The TDC identifies the vendor and d