Ruby on Rails Wednesday, April 10, 2019

Hi

You can try the following:

1. In your database.yml, increase the `pool` size. 
2. In database.yml, pass `reconnect: true`
3. Make sure `max_connections` in your Mysql server configuration is a number big enough to support the pool size you are setting.

Unni

On Thu, 11 Apr 2019 at 10:51, Loganathan Sellappa <loganathan.ms@gmail.com> wrote:
Hi Everyone, 

I'm getting the below error randomly in my Ruby On Rails application whenever the number of requests increases to the server.


Mysql2::Error::ConnectionError (Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)):

I'm not sure whether it is because of my server memory or is it something to do with mysql2 gem. Any help would be really appreciated, thanks in advance.

Ruby '2.5.0'  Rails '5.2.0  Mysql2 0.5.2  Phusion Passenger 5.3.4  Server version: Apache/2.4.6 (CentOS)  RAM SIZE: 1.5GB  MySQL Community Server (GPL): 5.6.41
Regards,
Loganathan

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/3f2416a7-1ba8-44c3-81e6-17384309af43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
Unni

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAK7OhfZd_URiSUSXyJD8H0owxRiF%2BWvhavh69-JqgkA2bY%2Bg6w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment