I found the problem now. It was actually nothing related to either
Ruby/Rails or Postgres, but to Ubuntu.
Wouldn't have thought that, but it seems there was a big bug with the
glibc library that caused the Postgres connections to crash.
postgres[8194]: segfault at 0 ip b6eb5e11 sp bfb3e41c erro
Well my setup is different, I use rails 3+, I've used pg 0.10 and now pg
0.11, posgresql 8.4, ruby 1.8.7 and the current passenger.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To view this discussion on the web visit
https://groups.
Nothing seems to help.
Turned off ssl and added it to database.yml
Stopped passenger spawning
Downgraded pg gem to 0.10.1.
Still get the random errors
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Tal
I read your post somewhere and already tried to turn ssl off. My db is
on the same server currently.
I will turned it off in Postgres explicitly and will add the yml flag to
database.yml as another try.
Jim Morris wrote in post #1018382:
> I was getting these errors too, in my case it turned ou
I was getting these errors too, in my case it turned out to be the ssl
connection to postgresql (on a local to local connection). Seems it uses ssl
by default, and there is an issue with long running ssl connections.
Simple solution for me was to turn off SSL on the connection, as it was a
loca
Exequiel wrote in post #1018312:
> Is the postgres server running on the same machine? or is a remote
> server?. It could be a timing out problem. OR, are you using a fork
> method in some place, maybe the app is missing the db connection. I
> think I had same error message some time ago and if I r
Is the postgres server running on the same machine? or is a remote
server?. It could be a timing out problem. OR, are you using a fork
method in some place, maybe the app is missing the db connection. I
think I had same error message some time ago and if I remember well I
updated the pg-ruby bindin
Exequiel wrote in post #1018244:
> Could you set your log level to debug and send us the error message
> +backtrace?. The log entries would help.
Attached one of the traces I get from exception mailer
Attachments:
http://www.ruby-forum.com/attachment/6546/stack_trace.txt
--
Posted via http://w
Could you set your log level to debug and send us the error message
+backtrace?. The log entries would help.
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubs
9 matches
Mail list logo
