Closed GoogleCodeExporter closed 9 years ago
Please verify that searchd is running. You can check by connecting to it with
MySQL:
mysql -h127.0.0.1 -P9306
If it is running, verify that MySQL is running:
mysql syslog
Original comment by mchol...@gmail.com
on 4 Oct 2012 at 8:59
Ok, So, when I ran mysql -h127.0.0.1 -P9306
I got a reply that searchd was not installed, even though all the files were
present.
So, I reinstalled sphinxsearch, tried again and recieved: Access denied.
I reran the upgrade script, retried, same Access denied.
This even happens with sudo
thanks for the help, any ideas? getting the same error on the web interface as
well.
Original comment by edb14030...@suu.edu
on 5 Oct 2012 at 9:22
I am now getting:
ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111)
Original comment by edb14030...@suu.edu
on 5 Oct 2012 at 9:31
Is searchd now running and listening on 9306? I don't understand how you could
get a reply that "searchd was not installed." What gave you that message?
Original comment by mchol...@gmail.com
on 5 Oct 2012 at 10:05
the mysql -h127.0.0.1 -P9306 gave me the searchd was not installed message.
when I #searchd --status
I get
FATAL: no readable config file (looked in /etc/shinxsearch/sphinx.conf,
./sphinx.conf).
Original comment by edb14030...@suu.edu
on 5 Oct 2012 at 10:18
I'm still very confused about the "not installed" message, but I guess it
doesn't matter. Searchd's config file is at /usr/local/etc/sphinx.conf, so it
needs to start with --config /usr/local/etc/sphinx.conf. You may choose to
simply symlink /etc/sphinxsearch/sphinx.conf.
Original comment by mchol...@gmail.com
on 6 Oct 2012 at 4:01
I now have the sphinx.conf symlinked so #searchd --status is returning:
searchd status
---------------
uptime: 993
connections: 2
maxed_out: 0
command_search: 0
command_excerpt: 0
command_update: 0
command_keywords: 0
command_persist: 0
command_status: 2
command_flushattrs: 0
agent_connect: 0
agent_retry: 0
queries: 0
dist_queries: 0
ag_distributed_local_0_query_timeouts: 0
ag_distributed_local_0_connect_timeouts: 0
ag_distributed_local_0_connect_failures: 0
ag_distributed_local_0_network_errors: 0
ag_distributed_local_0_wrong_replies: 0
ag_distributed_local_0_unexpected_closings: 0
query_wall: 0.000
query_cpu: OFF
dist_wall: 0.000
dist_local: 0.000
dist_wait: 0.000
query_reads: OFF
query_readkb: OFF
query_readtime: OFF
avg_query_wall: 0.000
avg_query_cpu: 0.000
avg_dist_wall: 0.000
avg_dist_local: 0.000
avg_dist_wait: 0.000
avg_query_reads: OFF
avg_query_readkb: OFF
avg_query_readtime: OFF
Now, when I use the mysql -h127.0.0.1 -P9306 I am still getting:
ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111)
thanks for all the help, it is appreciated.
Original comment by edb14030...@suu.edu
on 8 Oct 2012 at 10:25
Please run
netstat -anp | grep searchd
after starting searchd. Either there are two servers involved here, or it's
listening on a different port. Since you're not using the Sphinx config as
written by the install.sh script, it's hard to say for sure what weirdness
Ubuntu has put in extra, such as apparmor security settings, SELinux, etc.
Original comment by mchol...@gmail.com
on 9 Oct 2012 at 1:51
Your right, there are 2 on here. one listening @ 3307 the other 3312.
would it be easier to just reinstall from scratch? any suggestions to backup
the database before hand?
Original comment by edb14030...@suu.edu
on 9 Oct 2012 at 2:02
No need: looks like it's using an older config. Change the
sphinx/mysql_port to 3307 in the elsa_web and node config files.
On Tuesday, October 9, 2012, wrote:
Original comment by mchol...@gmail.com
on 9 Oct 2012 at 2:39
I changed the port in the etc/elsa_node.conf to 3307.
the line did not exist in the elsa_web.conf file.
still getting:
ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111)
when I run:
mysql -h127.0.0.1 -P9306
and:
No nodes available at /usr/local/elsa/web/lib/API.pm line 1995.
when I attempt to query on the web interface.
Original comment by edb14030...@suu.edu
on 9 Oct 2012 at 4:05
You need to let the web app know the new port, so you should specify a
sphinx_port of 9306 under the "nodes" config.
On Tue, Oct 9, 2012 at 11:05 AM,
<enterprise-log-search-and-archive@googlecode.com> wrote:
Original comment by mchol...@gmail.com
on 9 Oct 2012 at 11:01
Getting the same errors after adding the sphinx_port 9306 to the
elsa_nodes.conf file.
I went ahead and took a snapshot of the system and tried doing a full format /
install of ubuntu 12.04.1 and of course elsa with the quickstart install
script. The install script fails at:
gzip: /tmp/GeoIP.dat.gz: not in gzip format
C API installed already via apt-get
build_web_perl FAIL
Original comment by edb14030...@suu.edu
on 11 Oct 2012 at 3:36
Ok, got the original server / vm working by adding:
"sphinx_port": "3307" to the elsa_web.conf file under "nodes".
the 9306 didnt/doesnt work but 3307 took care of it, able to query normally.
Thanks for all the help.
Original comment by edb14030...@suu.edu
on 11 Oct 2012 at 4:54
Glad you're up and running! The port that Sphinx listens on is dictated by
/usr/local/etc/sphinx.conf, and that file is generated at install time. The
sphinx_port config setting tells the web interface how to connect to Sphinx.
Original comment by mchol...@gmail.com
on 11 Oct 2012 at 5:49
Original issue reported on code.google.com by
edb14030...@suu.edu
on 4 Oct 2012 at 6:14