Unable to process GET request to elasticsearch URL 'http://localhost:9200'

Technical assistance
1

Infos:

I am trying to set up Zammad so I can test it out and see if we want to change to this ticket system.
I have hit a wall with trying to get the reporting to work. It seems to be something with elasticsearch.
I have gone over several of the forms post trying different things but so far none of it has fixed my issue.

Help would be greatly appreciated.

Expected behavior:

Reporting to work within the ticket system

Actual behavior:

sudo zammad run rake searchindex:rebuild --trace
** Invoke searchindex:rebuild (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute searchindex:rebuild
** Execute searchindex:drop
drop indexes…done
** Execute searchindex:drop_pipeline
rake aborted!
Unable to process GET request to elasticsearch URL ‘http://localhost:9200’. Elasticsearch is not reachable, probably because it’s not running or even installed.

Response:
#<UserAgent::Result:0x000055ec94a16d10 @success=false, @body=nil, @data=nil, @code=0, @content_type=nil, @error="#<Errno::ECONNREFUSED: Failed to open TCP connection to localhost:9200 (Connection refused - connect(2) for “localhost” port 9200)>">

Payload:
nil

Payload size: 0M
/opt/zammad/lib/search_index_backend.rb:37:in info' /opt/zammad/lib/tasks/search_index_es.rake:104:inblock (2 levels) in <top (required)>’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/task.rb:271:in block in execute' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/task.rb:271:ineach’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/task.rb:271:in execute' /opt/zammad/lib/tasks/search_index_es.rake:14:inblock (2 levels) in <top (required)>’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/task.rb:271:in block in execute' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/task.rb:271:ineach’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/task.rb:271:in execute' /opt/zammad/lib/tasks/search_index_es.rake:141:inblock (2 levels) in <top (required)>’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/task.rb:271:in block in execute' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/task.rb:271:ineach’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/task.rb:271:in execute' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/task.rb:213:inblock in invoke_with_call_chain’
/opt/zammad/vendor/ruby-2.4.4/lib/ruby/2.4.0/monitor.rb:214:in mon_synchronize' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/task.rb:193:ininvoke_with_call_chain’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/task.rb:182:in invoke' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/application.rb:160:ininvoke_task’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/application.rb:116:in block (2 levels) in top_level' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/application.rb:116:ineach’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/application.rb:116:in block in top_level' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/application.rb:125:inrun_with_threads’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/application.rb:110:in top_level' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/application.rb:83:inblock in run’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/application.rb:186:in standard_exception_handling' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/lib/rake/application.rb:80:inrun’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.3.1/exe/rake:27:in <top (required)>' /opt/zammad/vendor/bundle/ruby/2.4.0/bin/rake:23:inload’
/opt/zammad/vendor/bundle/ruby/2.4.0/bin/rake:23:in <top (required)>' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/lib/bundler/cli/exec.rb:74:inload’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/lib/bundler/cli/exec.rb:74:in kernel_load' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/lib/bundler/cli/exec.rb:27:inrun’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/lib/bundler/cli.rb:360:in exec' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/lib/bundler/vendor/thor/lib/thor/command.rb:27:inrun’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in invoke_command' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/lib/bundler/vendor/thor/lib/thor.rb:369:indispatch’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/lib/bundler/cli.rb:20:in dispatch' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/lib/bundler/vendor/thor/lib/thor/base.rb:444:instart’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/lib/bundler/cli.rb:10:in start' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/exe/bundle:30:inblock in <top (required)>’
/opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/lib/bundler/friendly_errors.rb:121:in with_friendly_errors' /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.2/exe/bundle:22:in<top (required)>’
/opt/zammad/bin/bundle:3:in load' /opt/zammad/bin/bundle:3:in’
Tasks: TOP => searchindex:rebuild

Steps to reproduce the behavior:

Create VM
install Ubuntu server 16.04 with ssh
Follow install instructions

sudo echo “deb https://artifacts.elastic.co/packages/5.x/apt stable main” | sudo tee -a /etc/apt/sources.list.d/elastic-5.x.list
sudo wget -qO - https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo apt-key add -
sudo apt-get update
sudo apt-get install openjdk-8-jre elasticsearch
sudo /usr/share/elasticsearch/bin/elasticsearch-plugin install ingest-attachment
sudo systemctl restart elasticsearch
sudo systemctl enable elasticsearch
sudo wget -qO- https://dl.packager.io/srv/zammad/zammad/key | sudo apt-key add -
sudo wget -O /etc/apt/sources.list.d/zammad.list https://dl.packager.io/srv/zammad/zammad/stable/installer/ubuntu/16.04.repo
sudo apt-get update
sudo apt-get install zammad
#update url for /etc/nginx/sites-enabled/zammad.conf
sudo sysctl -w vm.max_map_count=262144
sudo zammad run rails r “Setting.set(‘es_url’, ‘http://localhost:9200’)”
sudo zammad run rake searchindex:rebuild

2

I noticed you set max_map_count after you started elasticsearch, maybe elasticsearch didn’t start?
have a look at

sudo netstat -nlp|grep 9200

and

sudo journalctl -u elasticsearch

1 Like
3

Connection refused mostly will result in elasticsearch not running or a firewall being in your way.

4

Elasticsearch is Running

elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2018-10-08 08:14:12 CDT; 1s ago
Docs: http://www.elastic.co
Process: 1503 ExecStartPre=/usr/share/elasticsearch/bin/elasticsearch-systemd-pre-exec (code=exited, status=0/SUCCESS)
Main PID: 1507 (java)
Tasks: 17
Memory: 127.6M
CPU: 2.144s
CGroup: /system.slice/elasticsearch.service
└─1507 /usr/bin/java -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+AlwaysPreTouch -server -Xss1m -Djava.awt.headless=true -Dfile.e

Oct 08 08:14:12 zammadTicketSystem systemd[1]: Starting Elasticsearch…
Oct 08 08:14:12 zammadTicketSystem systemd[1]: Started Elasticsearch.

Can you tell me how to disable any firewall that Ubuntu 16.04 could be running that would be blocking localhost:9200 ?

I have already run the command

sudo ufw disable

and confirmed that it is inactive

localtech@zammadTicketSystem:~$ sudo ufw status
Status: inactive

5

Found and Fixed my Issue.

Turns out my VM while set to Dynamic RAM was not upping the available RAM for Elasticsearch to work properly.
After I changed the minimum ram to 4GB I know have the ticket system up and running with reporting working.

6

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.