Topic: Action Controller: Exception Caught

Posted under General

Anthro-Lover

Member

I apologize if there is already a tag based on this. This has been confusing me for a while and I want to know if this is supposed to be some kind of bug. Every time I click favorites, I get this:

ActiveRecord::StatementInvalid in PostController#index

PGError: ERROR: canceling statement due to statement timeout
: SELECT COUNT(*) FROM posts p JOIN favorites f ON f.post_id = p.id JOIN users fu ON f.user_id = fu.id WHERE true AND p.status <> 'deleted' AND lower(fu.name) = lower('anthro-lover')
RAILS_ROOT: /home/e621/e621-production/release-2014-06-08

Application Trace | Framework Trace | Full Trace
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract_adapter.rb:227:in log' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:520:in execute'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1002:in select_raw' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:989:in select'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all_without_query_cache' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:81:in cache_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:13:in select_one' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:19:in select_value'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:920:in count_by_sql' /home/e621/e621-production/release-2014-06-08/app/models/post/count_methods.rb:19:in fast_count'
/home/e621/e621-production/release-2014-06-08/lib/cache.rb:44:in get' /home/e621/e621-production/release-2014-06-08/app/models/post/count_methods.rb:18:in fast_count'
/home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:394:in index_before_thousand' /home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:466:in index'
Request

Parameters:

{"tags"=>"fav:Anthro-Lover"}
Show session dump

Response

Headers:

{"Cache-Control"=>"no-cache",
"Set-Cookie"=>"blacklisted_tags=; path=/\nblacklist_avatars=true; path=/\nblacklist_users=false; path=/",
"Content-Type"=>""}

I'm not sure what this is supposed to mean. And I'm just wondering if I'm not the only one getting this. Can it be fixed somehow?

Updated by Genjar

Blodsho

Member

I was getting it earlier too, so it's not just you. I'm not a super programmer genius, but I'm pretty sure this part

PGError: ERROR: canceling statement due to statement timeout

means that the site's taking too long to do its thing and just gives up. There was a notice at the top of the page earlier (not sure where it went, I don't remember closing it) that said they'll be fandangling with the server's whatsit bits at 9PM PST tonight. So hopefully that will resolve it.

EDIT: Also forgot to mention, the entire site in general's been running slow for me today. It's usually not so bad until the heavy load messages start coming up, but today it's just been really sluggish.

Updated by anonymous

spight

Former Staff

As part of the pagination process, the server tries to get a count of the number of posts that match your search, but the process is... non-optimized. It's one of our primary concerns currently, along with many other query optimizations.

Sorry for the inconvenience, but thank you for reporting it.

There was a notice at the top of the page earlier (not sure where it went, I don't remember closing it) that said they'll be fandangling with the server's whatsit bits at 9PM PST

Actually, this maintenance is for the underlying servers, not for the application itself.

Updated by anonymous

VaporStrike

Member

Well, I was going to make a thread about this, but I stumbled onto this and figured it'd be better to add to this (even if it is a huge necro) just to keep everything in one topic.

Recently, every now and then a search would end up on the screen described above. I figured it was just some lag, so I'd search again and it'd be fine. However, for some reason I can't search anything anymore without getting this screen, so basically I can't even use the site anymore. Does anyone have any ideas why it might be happening this much, or how to fix it?

Updated by anonymous

EDFDarkAngel1

Former Staff

VaporStrike said:
Well, I was going to make a thread about this, but I stumbled onto this and figured it'd be better to add to this (even if it is a huge necro) just to keep everything in one topic.

Recently, every now and then a search would end up on the screen described above. I figured it was just some lag, so I'd search again and it'd be fine. However, for some reason I can't search anything anymore without getting this screen, so basically I can't even use the site anymore. Does anyone have any ideas why it might be happening this much, or how to fix it?

Thank you for letting us know. I'll forward it on to see what we can do to get it fixed!

Updated by anonymous

spight

Former Staff

VaporStrike said:
Well, I was going to make a thread about this, but I stumbled onto this and figured it'd be better to add to this (even if it is a huge necro) just to keep everything in one topic.

Recently, every now and then a search would end up on the screen described above. I figured it was just some lag, so I'd search again and it'd be fine. However, for some reason I can't search anything anymore without getting this screen, so basically I can't even use the site anymore. Does anyone have any ideas why it might be happening this much, or how to fix it?

Can you give me the simplest example of tags for which you've searched that exhibit this behavior recently?

The DB -is- running a bit slow lately, but most simple queries should still return well within the 60-second limit

Updated by anonymous

Genjar

Former Staff

spight said:
Can you give me the simplest example of tags for which you've searched that exhibit this behavior recently?

Simple queries work, but more complex ones are almost guaranteed to trigger that. For instance, -solo -duo -group -tentacles -comic order:random -feral. I've been unable to work on some of my projects for a couple of months now.

And it's not just the searches. I tried looking up one active users comments (through their profile) yesterday, and got similar error several times in a row. Probably because they had 2000+ comments.

Updated by anonymous

furrypickle

Admin

spight said:
Can you give me the simplest example of tags for which you've searched that exhibit this behavior recently?

The DB -is- running a bit slow lately, but most simple queries should still return well within the 60-second limit

For a week or so now, -duo -solo -group will only work once in a blue moon. Almost every time it gives me that timeout error. To work on that tagging project, I end up having to add a tag to the search to create a smaller pile of results in order to get it to actually work. So for example male -duo -solo -group will usually work fine. I just tested it before posting this, to double-check this is still true, and it is.

But I have also gotten that timeout error page on a wide variety of things in the last week (or so) attempting: viewing someone's tag history, viewing someone's (not the same person) comment history, trying to load a wiki page, trying to search wider than just a few days in this page: https://e621.net/report/tag_updates . And trying to use the search options on this page: https://e621.net/post_tag_history/index will sometimes work (to my amazement) but usually it will fail due to timeout and give that error. And that last one is true no matter how small the tag is, so even if there were only a handful of times that tag was used in the history of the site, it still will usually give up before returning with any results. So it's not just requests that would mean a massive amount of results, it chokes on small ones too.

Most of these things will work on occasion but regularly and randomly things will just roll over and die and give that timeout error instead. So I've gotten very used to seeing that error page crop up all over the place. Which sounds horrible but I guess you grow accustomed.

It's especially bad (more likely to show the Timeout Error) during from about 6pm to about maybe 1am-ish Mountain Time Zone USA. I'm guessing the traffic load is just higher during that time and so the site has more trouble managing any request it seems to find difficult to do. Hopefully that can help give you more information to play with. If I can be anymore help, let me know.

Updated by anonymous

Genjar

Former Staff

Seems to be worse today. I've been the error even for simple searches as 'breasts -nipples'.

Updated by anonymous

EDFDarkAngel1

Former Staff

Spight found a potential cause for this and we will be investigating this daily. Please continue to update as issues occur until Spight or Tony says to stop!

Updated by anonymous

furrypickle

Admin

Got one just now while trying to load this page: https://e621.net/wiki/show?title=text

ActiveRecord::StatementInvalid in WikiController#show

PGError: ERROR: canceling statement due to statement timeout
: SELECT posts.* FROM "posts" JOIN posts_tags ON posts_tags.post_id = posts.id JOIN tags ON tags.id = posts_tags.tag_id WHERE (tags.name = 'text' AND posts.status <> 'deleted') ORDER BY posts.id DESC LIMIT 8
RAILS_ROOT: /home/e621/e621-production/release-2014-06-08

Application Trace | Framework Trace | Full Trace
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract_adapter.rb:227:in log' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:520:in execute'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1002:in select_raw' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:989:in select'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all_without_query_cache' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:81:in cache_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:665:in find_by_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:1582:in find_every'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:619:in find' /home/e621/e621-production/release-2014-06-08/app/models/post/sql_methods.rb:11:in find_by_tag_join'
/home/e621/e621-production/release-2014-06-08/app/presenters/wiki_page_presenter.rb:10:in initialize' /home/e621/e621-production/release-2014-06-08/app/controllers/wiki_controller.rb:109:in new'
/home/e621/e621-production/release-2014-06-08/app/controllers/wiki_controller.rb:109:in show' Request Parameters: {"title"=>"text"} [/section] I haven't been getting them as often, but I have also gotten out of habit of doing the things which were setting them off, so I'll have to test a bunch of things today and see if I can provoke those errors or not. In this case, refreshing the page a few minutes later loaded it fine. No idea why it freaked out the first time.

Updated by anonymous

furrypickle

Admin

Got one just now running this search: https://e621.net/post/index/8/-solo%20-duo%20-group

ActiveRecord::StatementInvalid in PostController#index

PGError: ERROR: canceling statement due to statement timeout
: SELECT COUNT(*) FROM posts p LEFT JOIN posts_tags ept0 ON p.id = ept0.post_id AND ept0.tag_id = (SELECT id FROM tags WHERE name = 'solo') LEFT JOIN posts_tags ept1 ON p.id = ept1.post_id AND ept1.tag_id = (SELECT id FROM tags WHERE name = 'duo') LEFT JOIN posts_tags ept2 ON p.id = ept2.post_id AND ept2.tag_id = (SELECT id FROM tags WHERE name = 'group') WHERE true AND p.status <> 'deleted' AND ept0.tag_id IS NULL AND ept1.tag_id IS NULL AND ept2.tag_id IS NULL
RAILS_ROOT: /home/e621/e621-production/release-2014-06-08

Application Trace | Framework Trace | Full Trace
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract_adapter.rb:227:in log' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:520:in execute'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1002:in select_raw' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:989:in select'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all_without_query_cache' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:81:in cache_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:13:in select_one' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:19:in select_value'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:920:in count_by_sql' /home/e621/e621-production/release-2014-06-08/app/models/post/count_methods.rb:19:in fast_count'
/home/e621/e621-production/release-2014-06-08/lib/cache.rb:44:in get' /home/e621/e621-production/release-2014-06-08/app/models/post/count_methods.rb:18:in fast_count'
/home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:402:in index_before_thousand' /home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:474:in index'
Request

Parameters:

{"page"=>"8",
"tags"=>"-solo -duo -group"}

It's been working delightfully well earlier today, but just gave me the error a few minutes ago. I guess technically it's not quite the same error wording as the original post. But everything else about it seems the same as previous versions of this type of error. The first couple of refreshes produced the same error, but after about three or so refereshes I got the page to load for me. So it may be going in and out of working.

Updated by anonymous

Genjar

Former Staff

No changes since my last report, I'm still getting them regularly for most searches, including that 'breasts -nipples. It definitely seems worse during peak times. And yeah, it usually starts working after a few refreshes.

Updated by anonymous

VaporStrike

Member

Been a while since I originally necro'd this, but I might as well add my everyday search results. 99% of the time, all I search is "date:yyyy-mm-dd order:score__asc". I figure both of those are probably more complex, but from looking above, it seems like the site is failing on a lot of levels, not just complex searches. Also, most days, no ammount of refreshes help, and I just have to give up until the next day.

Hope this helps, it would be nice to be able to use the site again.

Updated by anonymous

Genjar

Former Staff

Just got it while searching for 'muscles'. Complex searches fail more often, but yes, even simple ones do it occasionally.

Updated by anonymous

furrypickle

Admin

A lot of wikis are loading fine, but for some odd reason this one in particular will only give me this error right now, though I swear it loaded fine earlier. Numerous refreshes but it's being stubborn.
https://e621.net/wiki/show?title=female

ActiveRecord::StatementInvalid in WikiController#show

PGError: ERROR: canceling statement due to statement timeout
: SELECT posts.* FROM "posts" JOIN posts_tags ON posts_tags.post_id = posts.id JOIN tags ON tags.id = posts_tags.tag_id WHERE (tags.name = 'female' AND posts.status <> 'deleted') ORDER BY posts.id DESC LIMIT 8
RAILS_ROOT: /home/e621/e621-production/release-2014-06-08

Application Trace | Framework Trace | Full Trace
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract_adapter.rb:227:in log' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:520:in execute'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1002:in select_raw' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:989:in select'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all_without_query_cache' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:81:in cache_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:665:in find_by_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:1582:in find_every'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:619:in find' /home/e621/e621-production/release-2014-06-08/app/models/post/sql_methods.rb:11:in find_by_tag_join'
/home/e621/e621-production/release-2014-06-08/app/presenters/wiki_page_presenter.rb:10:in initialize' /home/e621/e621-production/release-2014-06-08/app/controllers/wiki_controller.rb:109:in new'
/home/e621/e621-production/release-2014-06-08/app/controllers/wiki_controller.rb:109:in show' Request Parameters: {"title"=>"female"} [/section]

Updated by anonymous

abadbird

Janitor

Was checking a user's comments (to see if they are still active) and got the error. My first time getting this error. I don't know how long the page was loading before I got the error as I was looking at a different tab, but the page loaded properly after ~5 seconds on my second attempt.

Of all the tag searches or links mentioned in this thread, only one failed to load, resulting in a normal, nondescript timeout (60 seconds?), which loaded after ~45 seconds on my second try. Given that, I was surprised to get the action controller error at all.

ActiveRecord::StatementInvalid in CommentController#search

PGError: ERROR: canceling statement due to statement timeout
: SELECT * FROM "comments" WHERE (user_id = 18776) ORDER BY id desc LIMIT 30 OFFSET 0

RAILS_ROOT: /home/e621/e621-production/release-2014-06-08
Application Trace | Framework Trace | Full Trace

/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract_adapter.rb:227:in log' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:520:in execute'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1002:in select_raw' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:989:in select'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all_without_query_cache' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:81:in cache_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:665:in find_by_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:1582:in find_every'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:619:in find' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:82:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:82:in paginate' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/collection.rb:99:in create'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:76:in paginate' /home/e621/e621-production/release-2014-06-08/app/controllers/comment_controller.rb:183:in search'

Request

Parameters:

{"query"=>"user:Rainbow_Dash"}

Show session dump
Response

Headers:

{"Set-Cookie"=>"blacklisted_tags=death_by_penis&strikeanywhere&mouth_nipples&id%3A217625&id%3A429175&score%3A-1000..-10&obese&male_pregnancy&hoihoi&vaginal_prolapse&anal_prolapse&prolapse&nipple_penetration&nipple_insertion&anal_fisting&hyper&cock_and_ball_torture&amputee&egg&morbidly_obese&gore&unbirthing&sounding&urethral_penetration&modeseven&urethral&cannibalism&absorption_vore&vore&decapitation&gore&vore&blood&scat&all_the_way_through&castration; path=/\nblacklist_avatars=true; path=/\nblacklist_users=false; path=/",
"Cache-Control"=>"no-cache",
"Content-Type"=>""}

Updated by anonymous

EDFDarkAngel1

Former Staff

Good morning, everyone. Hope you enjoyed your Labor Day weekend (for Americans, anyway. Is that even a holiday outside of the US?)

Anyway, talked to Tony a bit about this. Genjar's example is being worked on, requiring some practice in optimizing how the site calls for information.

The comment page and the favorites appear to be working fine. It's possible that you may have experienced that problem during peak times. We can take a stab at that later, if it seems to be happening during non-peak times.

Updated by anonymous

Xch3l

Admin

EDFDarkAngel1 said:
Good morning, everyone. Hope you enjoyed your Labor Day weekend (for Americans, anyway. Is that even a holiday outside of the US?)

In Mexico it's on May 1st c:

Anyway, talked to Tony a bit about this. Genjar's example is being worked on, requiring some practice in optimizing how the site calls for information.

The comment page and the favorites appear to be working fine. It's possible that you may have experienced that problem during peak times. We can take a stab at that later, if it seems to be happening during non-peak times.

I've experienced them (along with "Server is under heavy load") at midnight - 12:00 am where I am right now and assuming you haven't moved from Arizona, 10:00pm - and they usually last for about an hour

Updated by anonymous

TheGreatWolfgang

Privileged

At first I have no idea what is this.

But WHAT IS THIS!!?

----
ActiveRecord::RecordNotFound
in PoolController#update

C o u l d n ' t f i n d P o o l w i t h I D = 2 3 6 7 0

R A I L S _ R O O T : / h ome / e 6 2 1 / e 6 2 1 - p r o d u c t i o n /
r e l e a s e - 2 0 1 4 - 0 6 - 0 8

Application Trace | Framework Trace | Full Trace

/ o p t / r b e n v / v e r s i o n s / r e e - 1 . 8 . 7 - 2 0 1 2 . 0 2 / l i b / r u b y / g ems / 1 . 8 / g ems / a c t i v e r e c o r d - 2 . 3 . 1 8 / l i b / a c t i v e _ r e c o r d / b a s e . r b : 1 6 2 0 : i n f i n d _ o n e ' / o p t / r b e n v / v e r s i o n s / r e e - 1 . 8 . 7 - 2 0 1 2 . 0 2 / l i b / r u b y / g ems / 1 . 8 / g ems / a c t i v e r e c o r d - 2 . 3 . 1 8 / l i b / a c t i v e _ r e c o r d / b a s e . r b : 1 6 0 3 : i n f i n d _ f r om _ i d s '
/ o p t / r b e n v / v e r s i o n s / r e e - 1 . 8 . 7 - 2 0 1 2 . 0 2 / l i b / r u b y / g ems / 1 . 8 / g ems / a c t i v e r e c o r d - 2 . 3 . 1 8 / l i b / a c t i v e _ r e c o r d / b a s e . r b : 6 2 0 : i n f i n d ' / h ome / e 6 2 1 / e 6 2 1 - p r o d u c t i o n / r e l e a s e - 2 0 1 4 - 0 6 - 0 8 / a p p / c o n t r o l l e r s / p o o l _ c o n t r o l l e r . r b : 5 6 : i n u p d a t e '

Request
Parameters:

{ " i d " = > " 2 3 6 7 0 " }

Show session dump

Response
Headers:

{ " S e t - C o o k i e " = > " b l a c k l i s t e d _ t a g s = ; p a t h = / \ n b l a c k l i s t _ a v a t a r s = t r u e ; p a t h = / \ n b l a c k l i s t _ u s e r s = f a l s e ; p a t h = / " ,
" C o n t e n t - T y p e " = > " " ,
" C a c h e - C o n t r o l " = > " n o - c a c h e " }

----

I was trying to edit a pool but it redirects. help!!

Updated by anonymous

EsalRider

Member

Wolfgang415 said:
At first I have no idea what is this.

But WHAT IS THIS!!? (...)

This is a different error, it's not a timeout.
Though I have to wonder... Why's there a space after almost every character?

Also: interpreting error message: pool #23670 does not exist. What pool were you trying to edit?

Updated by anonymous

Lizardite

Privileged

There you go. Another one, for your enjoyment: https://e621.net/tag_alias

NoMethodError in Tag_alias#index

Showing app/views/tag_alias/index.html.erb where line #103 raised:

undefined method `forum_post_id' for #<TagAlias:0x3fd14e0>
Extracted source (around line #103):

100: 								<span title="<%= a.created_at.strftime("%b %d, %Y %I:%M %p") %>"><%= time_ago_in_words(a.created_at) %> ago</span>
101: 							<% end %>
102: 						</td>
103: 						<td><%= link_to("Link", :controller => "forum", :action => "show", :id => a.forum_post_id) if a.forum_post_id %></td>
104: 					</tr>
105: 				<% end %>        
106: 			</tbody>

Updated by anonymous

Merry Rose

Member

I get this almost every time I look at '-Male' and only that... If I go to any other tag in the search it works perfectly fine but when I try the '-male' it almost always gives me that error...

Updated by anonymous

TheGreatWolfgang

Privileged

EsalRider said:
This is a different error, it's not a timeout.
Though I have to wonder... Why's there a space after almost every character?

I'm using a crappy symbian phone to do my uploading and editing. When I copy & paste several paragraphs, they all stick into one. So I tried to fix it.

Also: interpreting error message: pool #23670 does not exist. What pool were you trying to edit?

I see the error, try reading the description of the pool .

i can edit it by using another page .

Updated by anonymous

EsalRider

Member

Wolfgang415 said:
I see the error, try reading the description of the pool .

i can edit it by using another page .

You're looking for this page. The link you gave me is a historical version which shows what posts were in the pool in a previous state. That's not the main page of the pool.
If you see a message like "This is a historical version of the pool as it was 16 days ago." in the description, then you're looking at a previous version. Don't try to edit it from there. It won't work.

Updated by anonymous

TheGreatWolfgang

Privileged

EsalRider said:
You're looking for this page. The link you gave me is a historical version which shows what posts were in the pool in a previous state. That's not the main page of the pool.
If you see a message like "This is a historical version of the pool as it was 16 days ago." in the description, then you're looking at a previous version. Don't try to edit it from there. It won't work.

Ok, thx.

Updated by anonymous

VaporStrike

Member

So, after figuring out the timing, e621 seems to only make this popup for me when searching "order:score_asc date:yyyy-mm-dd" between somewhere around 1 PM to somewhere around 1 AM, central time (Illinois, Iowa, Texas, etc).

Any other tags I search are fine all day, and searching those 2 in combination are fine outside of the aforementioned times.

I'm stumped.

Updated by anonymous

Xch3l

Admin

Oh, I think I know what causes these midnight errors: if I recall correctly, Aurali and Tony (two devs, one no longer active and the other still alive and doing science, respectively; for those who don't know) said that the server makes nightly cleanup of unused tags (and some other stuff) that could be overloading the server which, at those good ol' times, didn't cause any struggle but with the recent increase of the userbase (and posts, features, etc.) it could be pushing e6 to its limits...

just a thought, of course...

Updated by anonymous

VaporStrike

Member

I'm now to the point that I'm lucky if I can get on at all with any search. Is there not a single solution, even temporary?

Updated by anonymous

Genjar

Former Staff

Got this again while searching for 'width:<3200 height:<2400 absurd_res'.

ActiveRecord::StatementInvalid in PostController#index

PGError: ERROR: canceling statement due to statement timeout
: SELECT p.* FROM posts p WHERE true AND p.width < 3200 AND p.height < 2400 AND p.status <> 'deleted' AND tags_index @@ to_tsquery('danbooru', E'(''absurd_res'')') ORDER BY p.id DESC LIMIT 300 OFFSET 0
RAILS_ROOT: /home/e621/e621-production/release-2014-06-08

Application Trace | Framework Trace | Full Trace
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract_adapter.rb:227:in log' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:520:in execute'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1002:in select_raw' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:989:in select'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all_without_query_cache' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:81:in cache_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:665:in find_by_sql' /home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:384:in index_before_thousand'
/home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:377:in index_before_thousand' /home/e621/e621-production/release-2014-06-08/app/controllers/post_controller.rb:451:in index'
Request

Parameters:

{"tags"=>"width:<3200 height:<2400 absurd_res",
"page"=>"1"}
Show session dump

---


Should we even keep reporting these? I mean, the errors are pretty common and I get those for something like third of the searches.

Updated by anonymous

furrypickle

Admin

Genjar said:

Should we even keep reporting these? I mean, the errors are pretty common and I get those for something like third of the searches.

This. I get them at least half the time I try to open wiki pages. Especially wiki pages with high amount of posts attached to them. For instance last night, loading the wiki page for video_games would go in an out of being cooperative. At one point, I had to refresh it at least ten times in a row to get it to work. I wasn't counting so it could have been more. I was at it for half an hour. And I couldn't get the nintendo wiki page to ever open. But other wikis would load fine. (actually I just got the error message again just now trying to open the nintendo wiki just to double-check I'm spelling it right. It loaded correctly on the second try.) I didn't report it because I get this error about half the times I try to make a wiki page load. And this thread is over a month old with hardly any feedback, just reports. So I'm not convinced it makes any difference to go find this thread, and post the same error message that's already been posted here a dozen times, every time it happens. But if it actually accomplishes something, I'll do it. Otherwise, I'll just keep refreshing, trying again later and crossing fingers.

I also get it regularly on pages like this: https://e621.net/user?name=&level=-1&order=tagedits (only on rare occasions can I get it to work)

ActiveRecord::StatementInvalid in UserController#index

PGError: ERROR: canceling statement due to statement timeout
: SELECT * FROM "users" WHERE (name ILIKE '%%' ESCAPE E'\') ORDER BY (SELECT count(*) FROM post_tag_histories WHERE user_id = users.id) DESC LIMIT 20 OFFSET 0
RAILS_ROOT: /home/e621/e621-production/release-2014-06-08

Application Trace | Framework Trace | Full Trace
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract_adapter.rb:227:in log' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:520:in execute'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1002:in select_raw' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:989:in select'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all_without_query_cache' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:81:in cache_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:665:in find_by_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:1582:in find_every'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:619:in find' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:82:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:82:in paginate' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/collection.rb:99:in create'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:76:in paginate' /home/e621/e621-production/release-2014-06-08/app/controllers/user_controller.rb:164:in index'
Request

Parameters:

{"order"=>"tagedits",
"name"=>"",
"level"=>"-1"}

(continuing reports in next post because error messages take up a lot of text space and it's telling me it's too large to post all in one.)

Updated by anonymous

furrypickle

Admin

It has improved on some things though. Even though I just got this error on this page: https://e621.net/report/tag_updates?start_date=2014-06-10&end_date=2014-09-13&limit=29&level=

ActiveRecord::StatementInvalid in ReportController#tag_updates

PGError: ERROR: canceling statement due to statement timeout
: SELECT users.id, COUNT(*) as change_count FROM post_tag_histories JOIN users ON users.id = post_tag_histories.user_id WHERE post_tag_histories.created_at BETWEEN '2014-06-10' AND '2014-09-13' GROUP BY users.id ORDER BY change_count DESC LIMIT 29
RAILS_ROOT: /home/e621/e621-production/release-2014-06-08

Application Trace | Framework Trace | Full Trace
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract_adapter.rb:227:in log' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:520:in execute'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1002:in select_raw' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:989:in select'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all_without_query_cache' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:81:in cache_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/home/e621/e621-production/release-2014-06-08/lib/core_extensions.rb:12:in __send__' /home/e621/e621-production/release-2014-06-08/lib/core_extensions.rb:12:in select_all_sql'
/home/e621/e621-production/release-2014-06-08/lib/report.rb:92:in usage_by_user' /home/e621/e621-production/release-2014-06-08/lib/report.rb:114:in tag_updates'
/home/e621/e621-production/release-2014-06-08/app/controllers/report_controller.rb:7:in tag_updates' Request Parameters: {"level"=>"", "start_date"=>"2014-06-10", "end_date"=>"2014-09-13", "limit"=>"29"} [/section] It actually did successfully let me search when the parameters were just a few days, and then again when parameters were just one month. It choked at several months. So that's better than it used to be. It used to give this error at anything over maybe 4 days worth. I also have gotten it a lot less often on searches. For instance, at the moment I can do both {{-solo -duo -group}} and {{female male -straight sex -bisexual -intersex -gay -ambiguous_gender}} without getting this error message. But I haven't been working on those lately as often as I was, so I can't tell you if it goes in an out of working. I do know both were giving me more errors than working several weeks ago, so that's also improvement. However, this type of error has shown up more frequently: [section] Website is offline No cached version of this page is available. Error 524 Ray ID: 1696ea683d7e0d4f A timeout occurred You Browser Working Los Angeles CloudFlare Working e621.net Host Error What happened? The origin web server timed out responding to this request. What can I do? If you're a visitor of this website: Please try again in a few minutes. If you're the owner of this website: The connection to the origin web server was made, but the origin web server timed out before responding. The likely cause is an overloaded background task, database or application, stressing the resources on your web server. To resolve, please work with your hosting provider or web development team to free up resources for your database or overloaded application. Additional troubleshooting information here. [/section] So idk what that's about, but I've been seeing it more often lately. Oh and heavy-load errors, but those are at a medium-low frequency. I'll only get them a couple times a day, but not too bad. I've seen much worse.

Updated by anonymous

VaporStrike

Member

I'd just be happy if someone could confirm or deny that they're looking into it. It's gotten steadily worse over the months and it's to the point that, for me, only one-term searches work, and even then, only the first page.

Updated by anonymous

Lance Armstrong

Janitor

VaporStrike said:
I'd just be happy if someone could confirm or deny that they're looking into it. It's gotten steadily worse over the months and it's to the point that, for me, only one-term searches work, and even then, only the first page.

spight is working on it: https://e621.net/forum/show/28544?page=39

Updated by anonymous

Genjar

Former Staff

This seems to happen every time I search the comments for 'idiot'. Which is odd, since other comment searches seem to work fine.

Full error

ActiveRecord::StatementInvalid in CommentController#search

PGError: ERROR: canceling statement due to statement timeout
: SELECT * FROM "comments" WHERE (text_search_index @@ plainto_tsquery('idiot')) ORDER BY id desc LIMIT 30 OFFSET 0
RAILS_ROOT: /home/e621/e621-production/release-2014-06-08

Application Trace | Framework Trace | Full Trace
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract_adapter.rb:227:in log' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:520:in execute'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1002:in select_raw' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/postgresql_adapter.rb:989:in select'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all_without_query_cache' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:81:in cache_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/query_cache.rb:60:in select_all'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:665:in find_by_sql' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:1582:in find_every'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/activerecord-2.3.18/lib/active_record/base.rb:619:in find' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:82:in send'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:82:in paginate' /opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/collection.rb:99:in create'
/opt/rbenv/versions/ree-1.8.7-2012.02/lib/ruby/gems/1.8/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:76:in paginate' /home/e621/e621-production/release-2014-06-08/app/controllers/comment_controller.rb:223:in search'
Request

Parameters:

{"query"=>"idiot"}
Show session dump

Updated by anonymous

  • 1