Hi Frank,

I can remember this thread. :)

So normally the default issue is an invalid version of the elasticsearch 
mapper-attachment plugin. To solve this you can check the following:

what is the output of: "/usr/share/elasticsearch/bin/elasticsearch-plugin 
list"

If the plugin is incompatible, follow this steps:

1) systemctl stop elasticsearch
2) /usr/share/elasticsearch/bin/elasticsearch-plugin remove mapper-
attachments
3) /usr/share/elasticsearch/bin/elasticsearch-plugin install mapper-
attachments
4) systemctl start elasticsearch
5) zammad run rake searchindex:rebuild


As far as I can remember, this was not the solution on your side, right?

Other ideas what I have, please let me know what the output of the 
following is:

1) zammad run rails r 'p Setting.get("proxy")'

2) zammad run rails r 'p Setting.get("es_url")'


Greetings,

 -Martin

Am Dienstag, 25. Juli 2017 16:11:40 UTC+2 schrieb Frank Thommen:
>
> Hi, 
>
> I'm am totally at a loss and therefore coming back to this old and still 
> unresolved thread.  I had reported, that we cannot update the 
> elasticsearch index: 
>
> $ 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... 
> ** Execute searchindex:create 
> create indexes... 
> rake aborted! 
> Unable to process PUT at http://127.0.0.1:9200/zammad_production 
> # 
> <http://127.0.0.1:9200/zammad_production#><UserAgent::Result:0x00558195000c78 
> @success=false, @body=nil, 
> @data=nil, @code="403", @content_type=nil, @error="Client Error: 
> #<Net::HTTPForbidden 403 Forbidden readbody=true>!"> 
> /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/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:248:in 
>
> `block in execute' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:243:in 
>
> `each' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:243:in 
>
> `execute' 
> /opt/zammad/lib/tasks/search_index_es.rake:60:in `block (2 levels) in 
> <top (required)>' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:248:in 
>
> `block in execute' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:243:in 
>
> `each' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:243:in 
>
> `execute' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:187:in 
>
> `block in invoke_with_call_chain' 
> /opt/zammad/vendor/ruby-2.3.1/lib/ruby/2.3.0/monitor.rb:214:in 
> `mon_synchronize' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:180:in 
>
> `invoke_with_call_chain' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/task.rb:173:in 
>
> `invoke' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:152:in
>  
>
> `invoke_task' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:108:in
>  
>
> `block (2 levels) in top_level' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:108:in
>  
>
> `each' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:108:in
>  
>
> `block in top_level' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:117:in
>  
>
> `run_with_threads' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:102:in
>  
>
> `top_level' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:80:in
>  
>
> `block in run' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:178:in
>  
>
> `standard_exception_handling' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/lib/rake/application.rb:77:in
>  
>
> `run' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/gems/rake-11.2.2/exe/rake:27:in 
> `<top (required)>' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/bin/rake:23:in `load' 
> /opt/zammad/vendor/bundle/ruby/2.3.0/bin/rake:23:in `<main>' 
> Tasks: TOP => searchindex:rebuild 
> $ 
>
> elasticsearch otherwise works absolutely fine and I can PUT and GET 
> content via curl locally. 
>
> Martin Edenhofer suggested, that this might be a proxy issue.  However I 
> never consciously configured any proxy settings for zammad, but I had 
> proxies configured in my environment ($http_proxy, $https_proxy) when 
> installing zammad and I had to configure proxies in 
> /etc/default/elasticsearch to be able to install the 
> "mapper-attachments" elasticsearch plugin. 
>
> The Java proxy settings in /etc/default/elasticsearch have been removed 
> and elasticsearch restarted and neither the root account nor the zammad 
> account contain any reference to our proxies.  There are no files in 
> /etc and in /opt/zammad (with the exception of some files in 
> /opt/zammad/tmp/cache_file_store_production/) which contain /any/ 
> reference to our outbound proxies. 
>
> *Still*: When running `zammad run rake searchindex:rebuild` I can see in 
> wireshark that no connection to localhost is opened at all and instead I 
> can see (using `netstat`), that two connections to our outbound proxies 
> have been established.  There are no associated process IDs, though. 
>
> If anyone has an idea where these proxy settings could be hidden and how 
> I could get rid of them, or if you have further ideas on how to debug 
> this nasty problem: Please let me know. I ran out of ideas :-} 
>
>
> Cheers 
> frank 
>

-- 
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/58dcb046-9064-4315-bbe9-9ce389a8956f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to