search

mooreniemi / Transbucket_Rails

:hospital: → :camera: → :thumbsup:
http://www.transbucket.com
10 stars 4 forks source link

Search indexing failing after Heroku's DB maintenance #58

Closed mooreniemi closed 7 years ago

mooreniemi commented 7 years ago 
You've just indexed some data via Flying Sphinx (perhaps manually, perhaps via cron), and it seems that something's not quite right. Here's the output from indexer, in case that's helpful:

Sphinx 2.1.4-id64-release (rel21-r4421)
Copyright (c) 2001-2013, Andrew Aksyonoff
Copyright (c) 2008-2013, Sphinx Technologies Inc (http://sphinxsearch.com)

using config file '/mnt/local/flying-sphinx/c284f853730870f67/sphinx.conf'...
indexing index 'pin_core'...
ERROR: index 'pin_core': sql_connect: could not connect to server: Connection timed out
    Is the server running on host "ec2-107-20-206-36.compute-1.amazonaws.com" (107.20.206.36) and accepting
    TCP/IP connections on port 5432?
 (DSN=pgsql://xmcaolaatfmehn:***@ec2-107-20-206-36.compute-1.amazonaws.com:5432/daoutu3m0rt9m9).
total 0 docs, 0 bytes
total 127.350 sec, 0 bytes/sec, 0.00 docs/sec
skipping non-plain index 'pin'...
total 0 reads, 0.000 sec, 0.0 kb/call avg, 0.0 msec/call avg
total 0 writes, 0.000 sec, 0.0 kb/call avg, 0.0 msec/call avg
If you're a bit stuck with what's causing this, feel free to reply to this email - which will log a ticket at support.flying-sphinx.com.
corajr commented 7 years ago

Re-ran heroku run bundle exec flying-sphinx configure and then manually indexed with heroku run bundle exec flying-sphinx index; this seemed to work okay. Will close tomorrow once I'm sure the indexing cron job runs smoothly.

corajr commented 7 years ago

Fine now AFAICT.