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.
Related
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
So I am trying to use my xampp server and for the life of me can't understand why my ProFTPD will not turn on. It only became cause for concern when I saw the word "bogon" in the application log. Can anyone translate to me what the application log means and maybe how I go about troubleshooting the problem ?
Stopping all servers...
Stopping Apache Web Server...
/Applications/XAMPP/xamppfiles/apache2/scripts/ctl.sh : httpd stopped
Stopping MySQL Database...
/Applications/XAMPP/xamppfiles/mysql/scripts/ctl.sh : mysql stopped
Starting ProFTPD...
Exit code: 8
Stdout:
Checking syntax of configuration file
proftpd config test fails, aborting
Stderr:
bogon proftpd[3948]: warning: unable to determine IP address of 'bogon'
bogon proftpd[3948]: error: no valid servers configured
bogon proftpd[3948]: Fatal: error processing configuration file '/Applications/XAMPP/xamppfiles/etc/proftpd.conf'
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 use the Zend libray, especially Loader class. But I take the following exception:
Uncaught exception 'Zend_Http_Client_Adapter_Exception' with message 'Unable to Connect to ssl://www.googleapis.com:443. Error #0:
I should say that when I run my code local, I don't face any problem, but the exception show when I try to run my file in server. The server I use has ssl security. Is there any possibility to there is any conflict with it?
This error may be caused by SSL level error like untrusted/expired SSL certificate which can be caused by wrong local system date.
If you on Ubuntu try add in your php.ini
openssl.capath=/etc/ssl/certs
For more info read this issue
On starting jboss I am getting the following error :
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
State: NOTYETINSTALLED
Depends On Me:
jboss.ejb:service=EJBTimerService,persistencePolicy=database
jboss:service=KeyGeneratorFactory,type=HiLo
jboss.mq:service=StateManager
jboss.mq:service=PersistenceManager
And for all database connections in the servlet I get the following exception :
org.postgresql.util.PSQLException: FATAL: password a
uthentication failed for user "poll"
It was working fine and all of a sudden I started getting these errors. My password is correct. I even tried changing the password and then tried again it showed the same exception. What is happening here?
The DefaultDS data source is what the name suggests; the default datasource. It ships with JBoss and is configured to use the Hypersonic (ie in-memory) database. JBoss uses the DefaultDS datasource to read/write internal queues, timed events, etc
Check the file ../conf/standardjbosscmp-jdbc.xml to see what you've got configured for the DefaultDS datasource. It sounds like you've edited that file unintentionally. Unless you need to persist internal queues etc across boots, just leave it as shipped using Hypersonic.
See the JBoss doc for more.