Issues after upgrading to 5.8.0

elasticsearch

#1

After restarting pulse following upgrade to 5.8.0 all is looking normal in server.log until the following entry
2018-11-26 10:54:18.4097 Error Elastic "Template pulse-server update to Elastic Search failed: Unsuccessful low level call on PUT: /_template/pulse-server

Thereafter the following lines are repeated 1000s of times in the log

# Audit trail of this API call:
 - [1] AllNodesDead: Took: 00:00:00
 - [2] Resurrection: Node: http://localhost:9200/ Took: 00:00:00
 - [3] PingFailure: Node: http://localhost:9200/ Exception: PipelineException Took: 00:00:02.0041203
# OriginalException: Elasticsearch.Net.ElasticsearchClientException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> Elasticsearch.Net.PipelineException: Failed to ping the specified node. ---> Elasticsearch.Net.PipelineException: An error occurred trying to read the response from the specified node.
   at Elasticsearch.Net.RequestPipeline.Ping(Node node)
   --- End of inner exception stack trace ---
   at Elasticsearch.Net.RequestPipeline.Ping(Node node)
   at Elasticsearch.Net.Transport`1.Ping(IRequestPipeline pipeline, Node node)
   at Elasticsearch.Net.Transport`1.Request[TReturn](HttpMethod method, String path, PostData`1 data, IRequestParameters requestParameters)
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
# Audit exception in step 3 PingFailure:
Elasticsearch.Net.PipelineException: An error occurred trying to read the response from the specified node.
   at Elasticsearch.Net.RequestPipeline.Ping(Node node)
# Request:
<Request stream not captured or already read to completion by serializer. Set DisableDirectStreaming() on ConnectionSettings to force it to be set on the response.>
# Response:
<Response stream not captured or already read to completion by serializer. Set DisableDirectStreaming() on ConnectionSettings to force it to be set on the response.>
"

Other than elasticsearch / kibana everythign in Pulse seems to be working fine, although it did take the application server an unusually long time to be available after the upgrade (around 10 minutes).


#2

Hi, I’ve also noted on my local laptop version of Pulse that the logging of Canvas pages has stopped working. Has anyone else seen this?


#3

hi @lbrown

Is the logger set in the Canvas Admin settings?

Regards,

Erik


#4

Hi @cw-ch,

The errors that you are looking at, are elastic errors. Elastic is telling you that your nodes could be dead, Could you check that the Cluster(s) and Index(es) of your elastic installation is(are all) green?

The time of start up is more likely on account of a couple of indexes that we added in the in the history tables. Can you please send me the logs to my email?

Regards,

Erik


#5

Hi @lbrown,

It is working on my laptop with Pulse v5.8.0 and Canvas v3.1.0.

If you upgrading Canvas on your latptop, during the upgrade Canvas removes all admin settings for the samples application. If you were testing with the samples application, you will have to reenter your settings in the admin section:

Cheers,

Vincent


#6

Hi @ecarmona
I will send the logs in email.


#7

Hi @ecarmona @Vincent, thanks for the reply, I managed to fix it, originally before upgrade my URL was the name of my laptop (http://luke_cubewise:8099/) which has now stopped working, but changing it to http://localhost:8099/ seems to have made it work again.