Recently we did upgrade from GPDB 4.3 to GPDB 6.x, now I'm testing the new version , I got the error below when I'm reading from external table, I'm stuck and I can't find out a solution:
ERROR: connection with gpfdist failed for "gpfdist://XXX.XXX.XXX.XXX:8090//REFILL/.gz", effective url: "http://XXX.XXX.XXX.XXX:8090//REFILL/.gz": error code = 4 (Interrupted system call); (seg0 slice1 xxx.xx.xx.x:6000 pid=752074)
SQL state: 08006
It seems with the new upgrade the following settings might have changed.
GPFdist path.
Check the port on which gpfdist is running.
It seems you have not specified file name correctly. You just specified .gz
Related
here is error info:
2022-12-31 15:13:57.433 ( 0.010s) [main thread ] loguru.cpp:770 INFO| Logging to 'application.log', mode: 'a', verbosity: 9 2022-12-31 15:13:57.446 ( 0.023s) [main thread ] otl_header.h:389 ERR| open connection : [Driver={MySQL ODBC 8.0 ANSI Driver};Server=xxx.xxx.xxx.xxx;Port=3306;Database=dbname;User=xx;Password=xxxx;Option=3;] 失败, error message: [unixODBC][MySQL][ODBC 8.0(w) Driver]Invalid connection parameters 状态码(code): HY000 执行语句(SQL):
Application runs on Centos 7.3. I have installed unixODBC, mysql-connector-odbc (8.0.31)
At the very begining, error message shows that: Can't find ODBC driver(IM002). I tried to create /etc/odbc.ini and edit it, and error message shows: Invalid connection parameters(HY000).Connect string references to connectionstrings.com
I'm wondering if odbc connection exist security problem, and on some cases it is necessary to disable odbc. Because on an other Windows platform, error message also shows that can't find Driver, even thought DSN was configured.
I cannot figure out the problem that ANSI Driver references to 'libmyodbc8a.so', but applcation seems to try to connect with 'libmyodbc8w.so' according to error message.
Did anyone have met these issues, please give me some advises, thanks a lot.
I am getting an error as follow:
File operation error: eacces. Target: /opt/ejabberd-16.03/lib/xmerl-1.3.7/ebin. Function: list_dir. Process: application_controller.
On AWS server but it is working locally.Further it was working in the past but now its not working..
It means ejabberd does not have access to the target repository. You have an installation issue. Fix your Linux directory access rights.
I've been using my SQL database initialization script for a while, but it seems that recently the database crashes in the middle of the execution and I don't know why, but here's some details:
I am running OrientDB on Ubuntu 14 Trusty x64 (via Vagrant)
It always seems to crash while the script attempts to create a UNIQUE_HASH_INDEX, but doesn't always crash at the same UNIQUE_HASH_INDEX instruction
The script creates a lot of vertices and edges, but for example, it will crash here (see line with UNIQUE_HASH_INDEX):
CREATE CLASS Channel EXTENDS V;
CREATE PROPERTY Channel.version LONG;
CREATE PROPERTY Channel.channelId STRING;
CREATE INDEX Channel.uq_channelId ON Channel(channelId) UNIQUE_HASH_INDEX;
The database crashes entirely with the following error:
Creating index... Error:
com.orientechnologies.orient.core.exception.OStorageException: Error
on executing command: sql.create INDEX Channel.uq_channelId ON
Channel(channelId) UNIQUE_HASH_INDEX
Error: java.io.EOFException
Looking at the log files, the only hint I get are the last two lines:
2016-01-14 17:17:05:437 INFO Received signal: SIGTERM [OSignalHandler]
2016-01-14 17:17:05:454 INFO Received signal: SIGTERM [OSignalHandler]
How can I resolve this issue, or at least get better hints as to what is making the database crash?
I also test with OrientDB 2.1.6, as I was running the older version initially. Same problem.
Sorry, false alarm -- this is a Vagrant issue, not an OrientDB issue. Running the exact same script on a 32bit instance instead of 64bit solved my problem, and installing the same script on a real 64bit server also works.
I have installed Gnumeric in CentOS 6.5, then use ssconvert command to convert .xls/.xlsx file to CSV, but I still get the following error:
$ ssconvert
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you
have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Not
running within active session)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you
have stale NFS locks due to a system crash. See
http://projects.gnome.org/gconf/ for information. (Details - 1: Not
running within active session)
** (ssconvert:5725): WARNING **: Configured default font 'Sans 10.000000' not available, trying fallback...
** (ssconvert:5725): WARNING **: Fallback font 'Sans 10.000000' not available, trying 'fixed'...
** (ssconvert:5725): WARNING **: Even 'fixed 10' failed ?? We're going to exit now,there is something wrong with your font
configuration
Can you help me?
As this is an old question, the answer is in case someone will get the same error (like me today on CentOS 6.8), you missed to install the Sans font:
yum install gnu-free-sans-fonts
For docker alpine images this might help:
RUN apk add --update \
msttcorefonts-installer fontconfig \
ttf-opensans
I was following the processes in this very helpful post:
How do I run a Play Framework 2.0 application as a Windows service?
when I ran into trouble in Step 9. When I execute runConsole.bat, the service cycles between the running and restarting states. The full log is here:
wrapper.log
but what jumps out at me in the log are the following:
INFO|7268/0|play.core.server.NettyServer|13-12-28 13:07:28|Oops, cannot start the server.
INFO|7268/0|play.core.server.NettyServer|13-12-28 13:07:28|Configuration error: Configuration error[Cannot connect to database [default]]
...
INFO|7268/0|play.core.server.NettyServer|13-12-28 13:07:28|Caused by: org.h2.jdbc.JdbcSQLException: Database may be already in use: "Locked by another process". Possible solutions: close all other connection(s); use the server mode [90020-168]
...
INFO|wrapper|play.core.server.NettyServer|13-12-28 13:07:28|restart process due to default exit code rule
INFO|wrapper|play.core.server.NettyServer|13-12-28 13:07:28|restart internal RUNNING
INFO|wrapper|play.core.server.NettyServer|13-12-28 13:07:28|stopping process with pid/timeout 7268 45000
INFO|wrapper|play.core.server.NettyServer|13-12-28 13:07:30|process exit code: -1
...
INFO|7812/1|play.core.server.NettyServer|13-12-28 13:07:45|[error] c.j.b.h.AbstractConnectionHook - Failed to obtain initial connection Sleeping for 0ms and trying again. Attempts left: 0. Exception: null
INFO|7812/1|play.core.server.NettyServer|13-12-28 13:07:45|Oops, cannot start the server.
INFO|7812/1|play.core.server.NettyServer|13-12-28 13:07:45|Configuration error: Configuration error[Cannot connect to database [default]]
repeats several times...
Half way through writing this post, I realized that before step 9., you should terminate the start.bat script which you start up in step 6. When I did this, runConsole.bat would execute normally without all the errors I list above.