Neo4j version - 3.1.1
Neo4j.rb - 8.0.13
Rails - 4.2.2
I am using these versions on local, somtimes same query is giving different results, I am noticing this issue from couple of days since I have tried to upgrade my application (Rails) but that's in seprate branch, Not sure what is going on here need help??
I am not able to find the cause of it but found some workaround and have some research, this is only happing after I upgraded rails and only on the development env. If I do eager_load = true in development as well then it is working as expected, but it has some disadvantages as well after doing code changes I have to restart the server, etc. According to me, there is some file load issue
config.eager_load = true
Related
I'm writing this after about 3 days of researches without ending in a solution that has sense.
I had several setups to host Wordpress sites, using Apache directly and using Plesk, everything hosted on AWS. Recently I setup a new Plesk installation on a m5a.xlarge instance, and things started behaving strange.
Basically the performances on this new instances, profiling the TTFB of the wp-login.php are unacceptable. We are talking about 2.0 secs in comparison of the old setup.
To make the thing short, I made tons of tests and the results are the following:
TTFB 0.3-0.4 on Apache AWS Linux 2 with Mariadb 10.2, t3.medium
TTGB 0.3-0.4 on Plesk t3.medium running Mariadb 5.5
TTGB 1.8-2.2 on Plesk m5a.xlarge running Mariabdb 10.5 (the last one).
Final test, bring up a new machine m5a.xlarge and installed another plesk, TTFB 0.2-0.5 but plesk installed Mariadb 5.5
Now first of all I did not understand why plesk intalled 5.5 twice and 10.4 on one instance. There's no choice during the installation.
I made every kind of test, I have the sensation that there's something about encoding and collations, but also running a mysql benchmark from withing WP, no differences are shown and the results are pretty much the same.
So anyone can show the light what's going one there ? Mariadb 10.5 ? Or is it possibile a faulty disk ? Ever happened ? (I also detached the disk and tried on another instance, no difference, so faulty instance is out of scope).
Thanks !
To anyone that may experience a foolish problem like mine, basically when I did the installation of the faulty server, I updated MariaDB to 10.5. The problem was there, it does not play nice with Wordpress, that's all. I found a lot of people reporting performances regression with Wordpress and even this sounds weird, that's the problem. I've rebuilt a server, kept MariaDB 5.X and everything is going smooth.
BTW Plesk support has been totally useless keeping uninstalling my plugins and telling me that the problem was in the plugins.. :/
I'm installing Jira locally with the latest version (7.13 x64 version).
When doing the custom install and trying to switch to using MySQL as the database,
I get the error:
You have specified a database that is not empty, please specify an empty database.
The database is brand new, I literally just created it and if I query it I can see it has no tables created.
I created the database (and several others) using either the standard CREATE DATABASE ... or be specifying UTF-8 as well, which is how the Atlassisn docs suggest it is done.
But, no matter what I do, the same error keeps appearing. Topics on the Atlassian site mentioning this error haven't been any help and all seem to do with version conflicts which aren't relevant here.
I have installed the Java/MySQL connector version 8.0.13. Is it something to do with that?
Thanks in advance.
It was the JDBC connector that was the problem. I downloaded and installed the latest (version 8.0.13) but it was causing the error.
Installing version 5.1.47 works just fine, even though it isn't recommended for use with MySQL 5.6, which I'm using.
But, using that connector, I have a database installed and Jira is functioning as it should.
I know is so late for answer but say answer to other searcher this question
I found this error in the logs which lead me to https://jira.atlassian.com/browse/JRASERVER-67274
Loading class com.mysql.jdbc.Driver'. This is deprecated. The new driver class is com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.
The long and short of it is you need an older mysql-connector-java-5.1.x.jar driver instead of the latest mysql-connector-java-8.0.x.jar that the documentation would lead you to install.
Reverting my driver to mysql-connector-java-5.1.49.jar fixed the issue for me.
I normally migrate databases for wordpress installs using wp_sync_db plugin. It has never failed before. Now when I'm trying to migrate from my local development server to the live site it's giving the following error.
I've tried only migrating specific fields, but it always runs into an error, just the field will be different.
I've tried to manually import the database to the live site and that is also failing with this error:
I'm not a database expert, and this is really frustrating. I have about two days of work I'm trying to migrate to the live site and can't do it with these errors.
I've been working on trying to solve this issue for a few hours, but have got no where. I've tried deleting the fields mentioned in the error, but that changes nothing. I've tried about 1000 different variations and configurations and it just keeps failing.
Please some database expert step in and save me!
I have no idea about the wp_sync_db plugin, but the phpMyAdmin error comes from having an older version of MySQL on your host which doesn't support the utf8mb4_unicode_ci collation.
You could look for the "Database system or older MySQL server to maximize output compatibility with:" dropdown on the phpMyAdmin export page, then select MYSQL40 there, but you run the risk of losing data if you have multibyte characters stored in your database.
This support page has a good summary of the situation and strongly suggests that you make your local MySQL version match as closely to your hosted version as possible, but that seems like a harsh reality in which to develop. I'm not a WordPress expert, but I believe that if you export for MYSQL40 compatibility and check the resulting imported data for any flaws you should be relatively safe.
When it comes to pushing databases,the problem starts for the amateurs.
i have my local mysql installed in windows 7,and referring to the heroku tutorial
http://devcenter.heroku.com/articles/taps they say that you can specify heroku db:push
mysql://root:mypass#localhost/mydb in the command line My question is Do i have to include
anything in my source code related with postgres? thanks in advance
When on Heroku, unless you have specified otherwise, you'll be running on Postgres. It you're using an ORM to access your database, then chances are you'll be OK.
If not, then there are literally hundreds of differences between PG SQL and MySQL SQL so something will probably need tweaking depending on how complex your queries are.
Also, depending on the platform you're using you might need to include some dependencies for Postgres such as the pg gem for Ruby.
Something worth noting is that if you're using Rails, you can just do heroku db:push and Heroku does the rest for you ;)
I'm running Ruby on Rails on a Solaris 10 server. I just reinstalled Ruby today to get things to work correctly with my MySQL system so I could add a new application I've been working on. I also updated my gems and the system. MySQL is the only thing in this system that hasn't been updated lately, that's at version 5.1.25.
When I run the Mongrel server the system will work okay for a couple loads, sometimes more. After reloading the index of one of my scaffolds a couple times, or adding a new item and loading its show page, the server reports a segmentation fault and exits. There is no debug output other than: "Segmentation Fault (core dumped)". All other output appears normal.
I've made a couple new applications on my server, and those show the same errors. Creating an application with the database disabled does not present this problem.
Any help or advice is greatly appreciated!
UPDATE: Unfortunately downgrading to MySQL 5.0.45 and reinstalling the mysql gem did not resolve the problem. If you have another suggestion, please let me know! You can see a complete list of the software installed and its versions here.
This is almost certainly a problem with the native C extensions of the mysql gem. There are a couple things I would try
Update your mysql-devel packages in your package manager and rebuild the mysql gem
Install a 5.0 version of mysql, and rebuild the mysql gem
Use the pure ruby mysql gem (http://www.tmtm.org/en/ruby/mysql/)
You might try installing the latest 5.0.x series version of MySQL, currently 5.0.83. I've never been able to get ActiveRecord to work with MySQL 5.1.x. I haven't gotten segfaults -- in my case it was different errors -- but I am using CentOS.
I think 5.0.x is the way to go.
if you check database.yml it's on the first line
MySQL. Versions 4.1 and 5.0 are recommended.
I ran into similar problems in XP with mysql 5.1
If all the other anwsers are not working, roll back to rails 2.1 that still has the mysql connector instead of the gem. I saw on some machines that the mysql gems was causing the software to crash or not work properly...