Hello Martin, there is no firewall installed on the system, but I think you are right, that it is an elastic search issue. in my /etc/elasticsearch/ elasticsearch.yml there a not entries, everything is marked as comment. Is there anything to do?
# ======================== Elasticsearch Configuration ========================= # # NOTE: Elasticsearch comes with reasonable defaults for most settings. # Before you set out to tweak and tune the configuration, make sure you # understand what are you trying to accomplish and the consequences. # # The primary way of configuring a node is via this file. This template lists # the most important settings you may want to configure for a production cluster. # # Please consult the documentation for further information on configuration options: # https://www.elastic.co/guide/en/elasticsearch/reference/index.html # # ---------------------------------- Cluster ----------------------------------- # # Use a descriptive name for your cluster: # #cluster.name: my-application # # ------------------------------------ Node ------------------------------------ # # Use a descriptive name for the node: # #node.name: node-1 # # Add custom attributes to the node: # #node.attr.rack: r1 # # ----------------------------------- Paths ------------------------------------ # # Path to directory where to store the data (separate multiple locations by comma): # #path.data: /path/to/data # # Path to log files: # #path.logs: /path/to/logs # # ----------------------------------- Memory ----------------------------------- # # Lock the memory on startup: # #bootstrap.memory_lock: true # # Make sure that the heap size is set to about half the memory available # on the system and that the owner of the process is allowed to use this # limit. # # Elasticsearch performs poorly when the system is swapping the memory. # # ---------------------------------- Network ----------------------------------- # # Set the bind address to a specific IP (IPv4 or IPv6): # #network.host: 127.0.0.1 # # Set a custom port for HTTP: # #http.port: 9200 # # For more information, consult the network module documentation. # # --------------------------------- Discovery ---------------------------------- # # Pass an initial list of hosts to perform discovery when new node is started: # The default list of hosts is ["127.0.0.1", "[::1]"] # #discovery.zen.ping.unicast.hosts: ["host1", "host2"] # # Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1): # #discovery.zen.minimum_master_nodes: 3 # # For more information, consult the zen discovery module documentation. # # ---------------------------------- Gateway ----------------------------------- # # Block initial recovery after a full cluster restart until N nodes are started: # # #gateway.recover_after_nodes: 3 # # For more information, consult the gateway module documentation. # # ---------------------------------- Various ----------------------------------- # # Require explicit names when deleting indices: # #action.destructive_requires_name: true Am Montag, 20. November 2017 11:54:13 UTC+1 schrieb Martin Edenhofer: > > For me it seems to be a firewall or elasticsearch issue (not Zammad > Realated). > > Am Samstag, 18. November 2017 15:18:22 UTC+1 schrieb Gunnar Maronde: >> >> Correction, there is a listener on port 9200, but elrond.elmenhorst. is >> not the correct FQDN, there ist a de missing: >> >> gm@elrond:~$ netstat -a | grep LISTEN >> tcp 0 0 *:ssh *:* LISTEN >> tcp 0 0 localhost:3000 *:* LISTEN >> tcp 0 0 localhost:postgresql *:* LISTEN >> tcp 0 0 localhost:smtp *:* LISTEN >> tcp 0 0 localhost:6042 *:* LISTEN >> tcp 0 0 *:44327 *:* LISTEN >> tcp 0 0 *:sunrpc *:* LISTEN >> tcp 0 0 *:http *:* LISTEN >> tcp6 0 0 elrond.elmenhorst.:9300 [::]:* LISTEN >> tcp6 0 0 [::]:ssh [::]:* LISTEN >> tcp6 0 0 localhost:postgresql [::]:* LISTEN >> tcp6 0 0 localhost:smtp [::]:* LISTEN >> tcp6 0 0 [::]:44943 [::]:* LISTEN >> tcp6 0 0 [::]:sunrpc [::]:* LISTEN >> tcp6 0 0 elrond.elmenhorst.:9200 [::]:* LISTEN >> tcp6 0 0 [::]:http [::]:* LISTEN >> >> >> Am Samstag, 18. November 2017 03:40:49 UTC+1 schrieb neoremi: >>> >>> OK. >>> What is output of # curl http://localhost:9200 ? >>> What java version do you have? >>> Do you see a listener on port 9200? >>> >>> On Friday, November 17, 2017 at 3:10:58 PM UTC-5, Gunnar Maronde wrote: >>>> >>>> hello neoremi, >>>> as you told me, I created a test ticket and there are already several >>>> more tickets. elasticsearch service is running: >>>> >>>> gm@elrond:~$ ps aux | grep elasticsearch >>>> elastic+ 1944 0.1 56.7 4611936 2302580 ? Ssl 09:45 0:42 >>>> /usr/bin/java -Xms2g -Xmx2g -XX:+UseConcMarkSweepGC >>>> -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly >>>> -XX:+AlwaysPreTouch -server -Xss1m -Djava.awt.headless=true >>>> -Dfile.encoding=UTF-8 -Djna.nosys=true >>>> -Djdk.io.permissionsUseCanonicalPath=true -Dio.netty.noUnsafe=true >>>> -Dio.netty.noKeySetOptimization=true >>>> -Dio.netty.recycler.maxCapacityPerThread=0 >>>> -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true >>>> -Dlog4j.skipJansi=true -XX:+HeapDumpOnOutOfMemoryError >>>> -Des.path.home=/usr/share/elasticsearch -cp /usr/share/elasticsearch/lib/* >>>> org.elasticsearch.bootstrap.Elasticsearch -p >>>> /var/run/elasticsearch/elasticsearch.pid --quiet >>>> -Edefault.path.logs=/var/log/elasticsearch >>>> -Edefault.path.data=/var/lib/elasticsearch >>>> -Edefault.path.conf=/etc/elasticsearch >>>> >>>> >>>> Am Freitag, 17. November 2017 20:09:04 UTC+1 schrieb neoremi: >>>>> >>>>> Did you create a test ticket? >>>>> >>>>> Is your elasticsearch service is running? >>>>> >>>>> On Friday, November 17, 2017 at 12:11:57 PM UTC-5, Gunnar Maronde >>>>> wrote: >>>>>> >>>>>> Thes result remains the same. the output of "sudo >>>>>> zammad run rake searchindex:rebuild" is >>>>>> >>>>>> drop indexes... >>>>>> create indexes... >>>>>> rake aborted! >>>>>> Unable to process PUT at http://localhost:9200/zammad_production >>>>>> #<UserAgent::Result:0x0055bee02949c0 @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)>"> >>>>>> /opt/zammad/lib/search_index_backend.rb:62:in `index' >>>>>> /opt/zammad/lib/tasks/search_index_es.rake:19:in `block (2 levels) in >>>>>> <top (required)>' >>>>>> /opt/zammad/lib/tasks/search_index_es.rake:60:in `block (2 levels) in >>>>>> <top (required)>' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.1.0/exe/rake:27:in >>>>>> `<top (required)>' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:74:in >>>>>> >>>>>> `load' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:74:in >>>>>> >>>>>> `kernel_load' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:27:in >>>>>> >>>>>> `run' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:360:in >>>>>> >>>>>> `exec' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in >>>>>> >>>>>> `run' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in >>>>>> >>>>>> `invoke_command' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor.rb:369:in >>>>>> >>>>>> `dispatch' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:20:in >>>>>> >>>>>> `dispatch' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/base.rb:444:in >>>>>> >>>>>> `start' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:10:in >>>>>> >>>>>> `start' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/exe/bundle:35:in >>>>>> >>>>>> `block in <top (required)>' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/friendly_errors.rb:121:in >>>>>> >>>>>> `with_friendly_errors' >>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/exe/bundle:27:in >>>>>> >>>>>> `<top (required)>' >>>>>> /opt/zammad/bin/bundle:3:in `load' >>>>>> /opt/zammad/bin/bundle:3:in `<main>' >>>>>> Tasks: TOP => searchindex:rebuild >>>>>> (See full trace by running task with --trace) >>>>>> >>>>>> >>>>>> Am Freitag, 17. November 2017 15:32:06 UTC+1 schrieb neoremi: >>>>>>> >>>>>>> Create a test ticket and do this: >>>>>>> >>>>>>> # zammad run rails r "Setting.set('es_url', >>>>>>> 'http://localhost:9200')" >>>>>>> # zammad run rails r "Setting.set('es_index', 'zammad')" >>>>>>> # zammad run rake searchindex:rebuild >>>>>>> >>>>>>> On Friday, November 17, 2017 at 3:54:51 AM UTC-5, Gunnar Maronde >>>>>>> wrote: >>>>>>>> >>>>>>>> You are right, there was an error. The output is >>>>>>>> >>>>>>>> drop indexes... >>>>>>>> create indexes... >>>>>>>> rake aborted! >>>>>>>> Unable to process PUT at >>>>>>>> http://localhost:9200/elrond_zammad_production >>>>>>>> #<UserAgent::Result:0x0055e68bb071e8 @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)>"> >>>>>>>> /opt/zammad/lib/search_index_backend.rb:62:in `index' >>>>>>>> /opt/zammad/lib/tasks/search_index_es.rake:19:in `block (2 levels) >>>>>>>> in <top (required)>' >>>>>>>> /opt/zammad/lib/tasks/search_index_es.rake:60:in `block (2 levels) >>>>>>>> in <top (required)>' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/rake-12.1.0/exe/rake:27:in >>>>>>>> `<top (required)>' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:74:in >>>>>>>> >>>>>>>> `load' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:74:in >>>>>>>> >>>>>>>> `kernel_load' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli/exec.rb:27:in >>>>>>>> >>>>>>>> `run' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:360:in >>>>>>>> >>>>>>>> `exec' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/command.rb:27:in >>>>>>>> >>>>>>>> `run' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in >>>>>>>> >>>>>>>> `invoke_command' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor.rb:369:in >>>>>>>> >>>>>>>> `dispatch' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:20:in >>>>>>>> >>>>>>>> `dispatch' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/vendor/thor/lib/thor/base.rb:444:in >>>>>>>> >>>>>>>> `start' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/cli.rb:10:in >>>>>>>> >>>>>>>> `start' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/exe/bundle:35:in >>>>>>>> >>>>>>>> `block in <top (required)>' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/lib/bundler/friendly_errors.rb:121:in >>>>>>>> >>>>>>>> `with_friendly_errors' >>>>>>>> /opt/zammad/vendor/bundle/ruby/2.4.0/gems/bundler-1.15.1/exe/bundle:27:in >>>>>>>> >>>>>>>> `<top (required)>' >>>>>>>> /opt/zammad/bin/bundle:3:in `load' >>>>>>>> /opt/zammad/bin/bundle:3:in `<main>' >>>>>>>> Tasks: TOP => searchindex:rebuild >>>>>>>> (See full trace by running task with --trace) >>>>>>>> >>>>>>>> >>>>>>>> Am Freitag, 17. November 2017 09:50:31 UTC+1 schrieb Martin >>>>>>>> Edenhofer: >>>>>>>>> >>>>>>>>> It seems hat the index is not existing in elastichsearch. >>>>>>>>> >>>>>>>>> What was the output of: >>>>>>>>> >>>>>>>>> zammad run rake searchindex:rebuild >>>>>>>>> >>>>>>>>> -Martin >>>>>>>>> >>>>>>>>> Am Freitag, 17. November 2017 09:46:06 UTC+1 schrieb Gunnar >>>>>>>>> Maronde: >>>>>>>>>> >>>>>>>>>> Thanks, I habe done it but now I get the follwing error message >>>>>>>>>> when starting the reporting: >>>>>>>>>> >>>>>>>>>> {"error":"Unable to process POST at >>>>>>>>>> http://localhost:9200/elrond_zammad_production/Ticket/_search\n#\u003cUserAgent::Result:0x007fbd9c2e4328 >>>>>>>>>> >>>>>>>>>> @success=false, @body=nil, @data=nil, @code=\"404\", >>>>>>>>>> @content_type=nil, >>>>>>>>>> @error=\"No such file >>>>>>>>>> http://localhost:9200/elrond_zammad_production/Ticket/_search, >>>>>>>>>> 404!\"\u003e"} >>>>>>>>>> >>>>>>>>>> Am Freitag, 17. November 2017 09:24:17 UTC+1 schrieb Martin >>>>>>>>>> Edenhofer: >>>>>>>>>>> >>>>>>>>>>> https://docs.zammad.org/en/latest/install-elasticsearch.html >>>>>>>>>>> >>>>>>>>>>> Enjoy, >>>>>>>>>>> >>>>>>>>>>> -Martin >>>>>>>>>>> >>>>>>>>>>> Am Freitag, 17. November 2017 09:22:52 UTC+1 schrieb Gunnar >>>>>>>>>>> Maronde: >>>>>>>>>>>> >>>>>>>>>>>> I just updated my zammad installation from Version 1.5 to 2.1 >>>>>>>>>>>> via "apt-get install zammad". By doing that, elasticsearch was >>>>>>>>>>>> also >>>>>>>>>>>> installed, which I did not use before. When I try to open the >>>>>>>>>>>> Reporting in >>>>>>>>>>>> the Web GUI, I get the message >>>>>>>>>>>> Elasticsearch need to be configured! (see attached screenshot) >>>>>>>>>>>> >>>>>>>>>>>> What has to be done for the Configuration? I am running a >>>>>>>>>>>> Debian 8.9 jessie installation. >>>>>>>>>>>> >>>>>>>>>>> -- Open Source as Download https://zammad.org || Easy to use as SaaS https://zammad.com --- You received this message because you are subscribed to the Google Groups "zammad-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to zammad-users+unsubscr...@googlegroups.com. To post to this group, send email to zammad-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/zammad-users/4ac1c6b3-ecda-41b7-ab0d-c0587e929784%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
