4 ms·
Yup - saw that as well....bit of a jump in traffic overwhelmed the server momentarily. Apologies.
by EzGraphs 15y ago
Yup - saw that as well....bit of a jump in traffic overwhelmed the server momentarily. Apologies.
- patrickaljord 15y ago> ActiveRecord::StatementInvalid at /home SQLite3::BusyException: database is locked: select * from plans where published='T' order by created_at limit 6 file: statement.rb location: step line: 108 You shouldn't be using SQLite for a prod site, it doesn't handle concurrency well, if at all. Edit: it also seems like you're using WEBrick as web server, again this is not meant for prod. There's plenty of literature on how to serve rails apps in prod. Look it up. http://i.imgur.com/cVzAC.png http://i.imgur.com/cVzAC.png
- waffle_ss 15y agoDon't forget that that stack trace shouldn't be visible! In production you should show a standard 500 error w/o the stack trace. Now people can see your codez. Is the server running in development mode or something?
- EzGraphs 15y agoHad our admins make a number of adjustments to the site - these issues have been resolved and the site is responding much better now.