greyoxide
Getting memory errors when I try to interact with ActiveRecord models
Just tested this by standing up a Linode server and deploying my app to it. No changes have been made to the app. Everything works great on the linode server, there's no memory allocation errors. Based on the portion of the picture I can see, this seems like an infrustructure issue with Railway.
18 replies
Talk to an Engineer form busted
Im using 15 in dev, and I'm using this gem: https://github.com/ged/ruby-pg
19 replies
Getting memory errors when I try to interact with ActiveRecord models
ok after a little digging in the logs I discovered the following error:
2023-12-27 03:15:08.891 UTC [100] FATAL: no PostgreSQL user name specified in startup packet
2023-12-27 03:15:08.934 UTC [101] FATAL: no PostgreSQL user name specified in startup packet
I have this in my config/database.yml
production:
adapter: postgresql
encoding: unicode
pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
database: <%= ENV['PGDATABASE'] %>
username: <%= ENV['PGUSER'] %>
password: <%= ENV['PGPASSWORD'] %>
host: <%= ENV['PGHOST'] %>
port: <%= ENV['PGPORT'] %>
irb(main):001> ENV['PGUSER']
=> "postgres"
at this point Im not sure what to do. I feel like I have all of the credentials set correctly. Also, Im not sure why attempting to run railway run rails db:create would return an error message about memory and the railway logs would have an entirely different error message about a username not being supplied.18 replies
Getting memory errors when I try to interact with ActiveRecord models
when I try to run railway run rails db:migrate I get an error which looks a little different
ruby(27769,0x1d995dec0) malloc: error for object 0x52: pointer being freed was not allocated
ruby(27769,0x1d995dec0) malloc: set a breakpoint in malloc_error_break to debug
18 replies
