To be honest, I’ve been struggling with this and want you to tell the solution that worked for me. I’ve searched the around the internet and tried so many `solutions`. Until I discovered an article from Ami Mahloof which helped me on my way.
I got 502’s, 404 errors and blank Kibana pages with a large amount of Nginx and Kibana configurations. All Elasticsearch and Stackoverflow help pages didn’t work for me and questions remained unanswered. I’ve noticed a lot of users seem to struggle with this, so I want to tell you the configuration that worked for me.
I…
Another day, another task. Last year I’ve created a Elasticsearch cluster, but it was sitting around without any data because other projects had higher priority. But last week I finally had the opportunity to use the cluster. After some research I decided to use the Searchkick library for Ruby on Rails. This post will describe how I used Searchkick and Sidekiq to import all our data into Elasticsearch. By the way, Searchkick and Sidekiq are awesome!
In my case we needed to store the data of three Rails models in Elasticsearch; Users, Projects and Assets. Combined these models account for…
Our MongoDB cluster with one replica set connects to Haproxy. We’re using a simple health check to identify the master and let our applications connect to it. When restarting the proxy, or bringing down a Mongo instance it will cause a strange error. It tried to connect some hostname to an IP address. But it fails. Mongo’s own replication has started to interfere with the health check in Haproxy. When this happened, our Rails apps using MongoId started displaying empty results with no related errors.
Our health check, checks port 27020 for the master. We added a…
When upgrading our Rails app to 5.1 we received the following error when trying to access some pages:
TypeError: can’t quote Hash
ruby-2.4.1/gems/activerecord-5.1/lib/active_record/connection_adapters/abstract/quoting.rb:196:in `_quote'Together with Sidney (sidofc) we decided to dive into the issue.
Identifying the issue
When looking at the stack trace, it is clear the problem starts in a Rails association. After tweaking the association and trying to replicate it in a new Rails app we kept getting the same error.
Before we wanted to submit a issue to the Rails repository we decided to to take a look at our database columns. …
