Has anyone used the iBatis to MyBatis conversion tool like in https://code.google.com/p/mybatis/wiki/DocUpgrade3? Did you need to make a setting change for the tool to work?
I've tried 2-3 versions of this tool, but I keep getting this error:
[xslt] Loading stylesheet C:\<some-path>\migrate.xslt
[xslt] : Error! Connection timed out: connect
[xslt] : Error! com.sun.org.apache.xml.internal.utils.WrappedRuntimeExcepti
on: Connection timed out: connect
[xslt] Failed to process null
BUILD FAILED
C:\<some-path>\build.xml:2
4: javax.xml.transform.TransformerException: javax.xml.transform.TransformerExce
ption: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Connection
timed out: connect
Also, the way I tried to run it is as follows:
In a command prompt, I changed to the directory where the zip file was extracted. Then I put in one of the SQL map files into the Source folder. Then I went back to the command prompt, and ran the command "ant". I tried this command with 2-3 options too, but none of them worked. All of them gave the same error. It seems like some kind of a proxy setting kind of issue, from what I've found so far. But I don't exactly know what the error is and what the solution is, beyond this. Any idea how to resolve this?
I found a solution to this:
At first, I tried to run the Ant task by setting this property via the command prompt:
set ANT_OPTS="-Dhttp.proxyHost=proxy -Dhttp.proxyPort=8080"
And then ran in the same session: ant
But this continued to give me the same error.
So, I took out the <!DOCTYPE..> line from the source file, and then did the above steps. It worked like magic!
Related
When i try to restore my postgress db , it failed with exit code 1. What is the reason. I created the backup using postgress 11 and restoring it to postgress 12.
Appreciate your help.
Sounds like you are using PgAdmin4. You should upgrade it to the latest version (4.30) where they fixed the bug that caused it to hide the real error messages from you. Then you can try again and show us the real errors.
Better yet, use command line tools to do it in the first place.
I you don't want to try again, you can instead look in the database servers log file to find the error messages.
I am trying to create a new Strapi app on Ubuntu 16.4 using MongoDB. After stepping through the tutorial, here: https://strapi.io/documentation/3.0.0-beta.x/guides/databases.html#mongodb-installation, I get the following error: Connection test failed: spawn npm; ENOENT
The error seems obvious, but I'm having issues getting to the cause of it. I've installed latest version of MongoDB and have ensured it is running using service mongod status. I can also connect directly using nc, like below.
$ nc -zvv localhost 27017
Connection to localhost 27017 port [tcp/*] succeeded!
Here is an image of the terminal output:
Any help troubleshooting this would be appreciated! Does Strapi perhaps log setup errors somewhere, or is there a way to get verbose logging? Is it possible the connection error would be logged by MongoDB somewhere?
I was able to find the answer. The problem was with using npx instead of Yarn. Strapi documentation states that either should work, however, it is clear from my experience that there is a bug when using npx.
I switched to Yarn and the process proceeded as expected without error. Steps were otherwise exactly the same.
Update: There is also a typo in Strapi documentation for yarn. They include the word "new" before the project name, which will create a project called new and ignore the project name.
Strapi docs (incorrect):
yarn create strapi-app new my-project
Correct usage, based on my experience:
yarn create strapi-app my-project
The ENOENT error is "an abbreviation of Error NO ENTry (or Error NO ENTity), and can actually be used for more than files/directories."
Why does ENOENT mean "No such file or directory"?
Everything I've read on this points toward issues with environment variables and the process.env.PATH.
"NOTE: This error is almost always caused because the command does not exist, because the working directory does not exist, or from a windows-only bug."
How do I debug "Error: spawn ENOENT" on node.js?
If you take the function that Jiaji Zhou provides in the link above and paste it into the top of your config/functions/bootstrap.js file (above module.exports), it might give you a better idea of where the error is occurring, specifically it should tell you the command it ran. Then run the command > which nameOfCommand to see what file path it returns.
"miss-installed programs are the most common cause for a not found command. Refer to each command documentation if needed and install it." - laconbass (from the same link, below Jiaji Zhou's answer)
This is how I interpret all of the above and form a solution. Put that function in bootstrap.js, then take the command returned from the function and run > which nameOfCommand. Then in bootstrap.js (you can comment out the function), put console.log(process.env.PATH) which will return a string of all the directories your current environment is checking for executables. If the path returned from your which command isn't in your process.env.PATH, you can move the command into a path, or try re-installing.
After running CCleaner and trying to debug a fix an Oauth password encryption type error, I have this error:
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
Communications link failure
and all the local databases seemed to have disappeared
I tried to create a new database with MYSQL command line. After entering my password, there was a error and the window closed.
I have tried many solutions to debug the errors e.g. setting
compile('org.hibernate:hibernate-core')
compile('org.hibernate:hibernate-entitymanager')
to resolve an EntityFactory error which lead to this error I think.
I also tried killing the process on port 3306. But I couldn't think of any other options. Any suggestions for next steps would be...?
Apparently mysql service stopped working at some point without me realizing. The solution was going to Start -> type 'service.msc' -> run mysql80 (stands for mysql version 8.0 I think).
I have an embedded database where I start an OServer and trying to connect to it from the console. I've been doing this successfully for many months and upgrading the database as new versions come out. Now, with 2.2.13, the embedded operations seem to work but I can't connect to the server with the 2.2.13 console.sh. I get the message:
Error: com.orientechnologies.orient.core.exception.OStorageException: Cannot create a connection to remote server address(es): [127.0.0.1:2424]
DB name="master"
The java code running the embedded database gets the following exception:
$ANSI{green {db=db}} Error executing request
com.orientechnologies.orient.core.exception.ODatabaseException: Error on plugin lookup: the server did not start correctly
DB name="db"
at com.orientechnologies.orient.server.OServer.getPlugin(OServer.java:850)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.openDatabase(ONetworkProtocolBinary.java:857)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.handshakeRequest(ONetworkProtocolBinary.java:229)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.execute(ONetworkProtocolBinary.java:194)
at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:77)
Seems to be looking for the 'cluster' plugin.
Any idea why this doesn't work anymore? It did work in 2.2.12.
Thanks
Curtis
Seems I had automatic backup turned on but the config file was missing. So, the server looked like it started up but actually didn't.
I created the config file and set enabled to false. Still didn't start up because it sees the false and stops the configuration and throws an exception because the 'delay' parameter isn't set.
I think orientdb should start up without backups enabled if the config file is missing or the enabled parameter is set to false.
At least the console is working now.
I am trying to install the Sphinx Search Server. I followed the steps given here http://itsonrail.wordpress.com/2010/05/23/installing-sphinx-on%C2%A0windows/
I added C:\Sphinx\bin to environment path and Sphinx Search is listed in the Services panel. When I try to start it, this error occurs:
Windows could not start SphinxSearch service on local computer
Error: 1067 The process terminated unexpectedly.
Please help me solving this problem. Thanks in advance.
I trid this http://sphinxsearch.com/forum/view.html?id=2684 but it didn't help.
I had the same error in my Windows 7 x64. The step below helped to solve my problem:
Create folders data and log in C:\Sphinx.
Then try to start sphinx with cmd:
C:\sphinx\bin>searchd
I have faced the same problem and eventually moved the sphnix.conf to C:\Sphinx\bin\sphnix.conf from root and the services starts. Please try this. (Please make sure there are data\, log\ directories in the root with write permission)
It is looking like your configuration is not setup properly. Have you tried to run search daemon from sphinx directory path via command prompt?
C:\sphinx\bin> searchd
C:\sphinx\bin>indexer --rotate –all
Also please ensure the log via search.log or windows event log.
If it is not running after this than try to reinstall it again
I hope it will work for you
Error 1067 doesn't say much about the problem, except that the process terminated unexpectedly. Try looking some more informations in searchd.log.
I've got same error code when I tried to update Sphinx with newer version.
In the log file, I've found
FATAL: no valid indexes to serve
My problem was that I tried running new version of Sphinx using index files created with an older version. It was solved by deleting all old index files and creating new indexes.
==>> close your cmd window and restart the sphinxsearch service...
I got this error suddenly, when Shpinx was working fine yesterday. Turns out the query log file was hitting 4Gb in size. I deleted it, and service started with no problems.
Make sure all the folders defined in the conf file actually exist. I was missing the LOG folder and that's why I was getting the error. Once I added the folder, the problem was solved.