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...
Related
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.
Basically I want to know where I can find a distribution of XAMPP that uses good ol' MySQL instead of MariaDB. I have a Drupal site that runs fine on MySQL 5.5.16, but when I run it on MySQL 10.1.0-MariaDB (which was what the newer XAMPP I downloaded came with), I can't clear the caches without it corrupting the database. I know MariaDB is supposedly the same as MySQL, but this error is happening with one and not the other, and nothing else is different. Where can I get that distribution?
I am presuming you are using Windows.
According to WikiPedia, MySQL 5.5.16 came installed with XAMPP 1.7.7 and the last version of XAMPP to come with MySQL (5.6.26) was XAMPP 5.6.12. (Source)
You can find all the older versions of XAMPP on Sourceforge.
I have a task to create a box with some configuration(Apache, php etc) and with MariaDb 10.0. But in this site https://puphpet.com/ we have only MySQL and searching I have found this: https://mariadb.com/kb/en/puppet-and-mariadb/, but there are nothing about MariaDb 10.0. Any advices ???
Most of the MariaDB puppet modules seem to be out of date for installing version 10 and later, so your best bet is to roll up your sleeves and do it yourself.
Basically you'll need to configure a yumrepo for MariaDB. A list of repos can be found at http://yum.mariadb.org/.
Then install the package with the version you want.
Hope this helps you get started!
What is the best version of MySQL to use with Rails 3 as of today (28/4/11)?
At the moment I got Mysql 5.5.11 community server and I have had lots of problems with it. I want to install an older version of MySQL. Which one would you recommend?
Thanks in advance.
PS: The issues were with the mysql2 gem.
I would say 5.1 only because of problems I had trying to compile the driver with MySQL 5.5 on mac (which is of course a show stopper).
And I had no issues at all with MySQL 5.1.
Even with the very public outage it recently suffered, we would recommend Amazon's RDS service. We find it has been very reliable and easy to administer.
Our RDS instance is currently running MySQL version 5.1.45.
On occasion, my local Rails app loses its connection to MySQL. I get some error that the connection failed, but if I just refresh the page, it works fine. This has never happpened in my STAGE or PROD environments (I deploy to Ubuntu), so it has not been that big a deal.
Does this happen to anybody else? Is there something I can do to fix it? Is it MySQL or Ruby?
Look like the best solution to this is to install the platform specific mysql driver. sudo gem install mysql
I remember having this problem a while back (before i upgraded to Leopard?). They're tricky to diagnose, but have a look at logfiles, and try setting "wait_timeout" longer (you shouldn't have to mess with "max_connections". See:
http://www.mysqlperformanceblog.com/2008/08/23/how-to-track-down-the-source-of-aborted_connects/
http://dev.mysql.com/doc/refman/5.0/en/communication-errors.html
http://www.softwareprojects.com/resources/programming/t-how-to-fix-mysql-database-myisam-innodb-1634.html
I think i followed Dan Benjamin's MySql install blog to not have problems:
http://hivelogic.com/articles/installing-mysql-on-mac-os-x/