Skip to main content
Topics#Network

#Network3 discussing

Ask a question...
Pragadheeshwari Badmaprakash (Consultant at Slalom) asked in #Salesforce Developer
Oct 14, 9:25 PM
Has anyone experienced similar Salesforce UI freezing issues, even when users aren’t actively handling chats?

Hi everyone, has anyone experienced Salesforce UI freezing or significant latency in Chrome or Edge?

We’re investigating a recurring issue where Salesforce becomes unresponsive for 10–20+ seconds. It happens during active chat sessions, particularly during peak traffic, but we’ve also observed similar behavior when users aren’t actively handling chats.

Has anyone encountered similar issues, and were you able to identify the root cause or find a resolution? Any insights into browser performance, memory usage, network conditions, or known Salesforce issues would be greatly appreciated.

Thanks in advance! 

 

#Salesforce Developer  #Messaging Session  #Service Cloud  #Salesforce  #TrailblazerCommunity  #Chrome Browser  #Network

4 answers
Write an answer...
0/9000
Tableau Community Forums Member (Inactive) (Member of the Tableau Community Forums at Salesforce)
Feb 21, 2019, 11:10 AM
Tableau Server Initialization Error due to ElasticServer Error

Hello All,

I'm trying to install Tableau Server 2019.1 on RHEL Server 7.4 , and after following every instruction on :

Deploy - Tableau

I keep getting an error on server initialization step. The error starts when I run the command which is the first step in initializing the server:

tsm initialize --request-timeout 1800

  Tableau Server Initialization Error due to ElasticServer Error

The initialization always fails at finalizing topology. On searching the error logs mentioned, in tabadmincontroller, I found the error is thrown at callback:

com.tableausoftware.tabadmin.webapp.asyncjobs.InitializeServerJob

where several services are restarted. The error is generated when starting the service elasticserver with the following exception:

The following services on node node1 are in failed states, look into their corresponding logs for more details: elasticserver_0=ENABLE_FAILED

 

I examined the ElasticServer logs too and the issue seems to be this:

 

com.tableausoftware.elasticserver.ElasticServerApp - Executing searchguard command:[/var/opt/tableau/tableau_server/data/tabsvc/elasticserver/0/run-sgadmin.sh]

 

main : INFO  com.tableausoftware.elasticserver.ElasticServerApp - search guard command output: Search Guard Admin v6

WARNING: Seems you want connect to the Elasticsearch HTTP port.

         sgadmin connects on the transport port which is normally 9300.

Will connect to localhost:8185

ERR: Seems there is no Elasticsearch running on localhost:8185 - Will exit

 

I'm not sure if this is a result of a simpler mistake, or a fault in the configuration of the Elastic Server Service. I have attached log files of both Tabadmincontroller and ElasticServer.

I got a similar result in Ubuntu 16.04.

 

Any help is much appreciated.

DanKarl

tabadmincontroller_node1-0.log.rtf
16 answers
Write an answer...
0/9000