Zum Hauptinhalt gehen

Cassandra NoHostAvailableException

Kommentare

15 Kommentare

  • Permanently deleted user

    Hi Dileep, This issue has been reported as bug CORE-1031. One question, are you running Essentials in a load-balanced scenario? Or is it a single server?

    Also, do you know how often it happens? (approximately)

    0
  • Permanently deleted user

    Hi Alejandro,

    This is currently running on a single server. We are planning to deploy on a load-balanced environment but aren't there yet.

    This error usually occurs once a day.

    Thanks,

    Dileep

    0
  • Permanently deleted user

    Thanks Dileep, I've added all the information to the bug ticket. 

    -Alejandro

    0
  • Permanently deleted user

    We received this error for the first time today. 

    Single server configuration.  GE version 4.3.1 on Server 2008 R2

     

    Here's an entry from the application log:

    System.AggregateException: One or more errors occurred. ---> Cassandra.NoHostAvailableException: None of the hosts tried for query are available (tried: 10.68.170.21)

     

       at Cassandra.ControlConnection.Connect(Boolean firstTime)

     

       at Cassandra.ControlConnection.Init()

     

       at Cassandra.Cluster.Init()

     

       at Cassandra.Cluster.Connect(String keyspace)

     

       at Geocortex.Platform.Security.Support.Storage.Cassandra.CassandraService.<Connect>d__8.MoveNext()

     

       --- End of inner exception stack trace ---

     

       at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)

     

       at Geocortex.Essentials.PostInstall.DialogBasedTaskWaiter.WaitForResult(Task task, TimeSpan timeout, CancellationToken cancellationToken, Object source)

     

       at Geocortex.Platform.Security.Support.TaskWaiter.WaitForResult[TResult](Task`1 task, TimeSpan timeout, CancellationToken cancellationToken, Object source)

     

       at Geocortex.Platform.Security.Support.Storage.Cassandra.CassandraService.get_Session()

     

       at Geocortex.Platform.Security.Support.Storage.Cassandra.CassandraService.ExecuteAsync(String cql, Object[] args)

     

       at Geocortex.Platform.Security.Support.Storage.Cassandra.GraphIterator.SelectFirst(IGraphInspector inspector)

     

       at Geocortex.Platform.Security.Integration.Contexts.SecurityContext.Fetch(IBag source)

     

       at Geocortex.Platform.Security.Support.Collections.StorageBasedBag.GetEnumerator()

     

       at Geocortex.Platform.Security.Support.Collections.BagBase.Import(IBag bag)

     

       at Geocortex.Essentials.PostInstall.SecurityUtility.LoadDetails()

     

       at Geocortex.Essentials.PostInstall.EssentialsPostInstall.StartupAsync(InitWindow window)

     

    ---> (Inner Exception #0) Cassandra.NoHostAvailableException: None of the hosts tried for query are available (tried: 10.68.170.21)

     

       at Cassandra.ControlConnection.Connect(Boolean firstTime)

     

       at Cassandra.ControlConnection.Init()

     

       at Cassandra.Cluster.Init()

     

       at Cassandra.Cluster.Connect(String keyspace)

     

       at Geocortex.Platform.Security.Support.Storage.Cassandra.CassandraService.<Connect>d__8.MoveNext()<---
    0
  • Permanently deleted user

    Same error situation here, we are running GE 4.3.1 on a Windows Server 2012 R2 Standard (Single server configuration).

    0
  • Permanently deleted user

    Have you got any update on  this issue? We have a similar issue after upgrading from essentials 4.2.1 to 4.3.1 and have only happned once. We're on Windows server 2008 R2 and have a load balancer in front of the essentials servers (netscaler) but only used as a fail over switch.

    0
  • Permanently deleted user

    Noel - We heard from Latitude that this issue has been fixed in version 4.4. We upgraded our development server today and will see how it goes.

    0
  • Permanently deleted user

    I would be interested in knowing if this fixes your problem.  I have been having the same problem.

    Aron

    0
  • Permanently deleted user

    Got the same issue here.

    The project installed Geocortex site (had licensed file) in server A but plant to migrate from 3.15 to 4.3. In some reason, we installed Gecortex 4.3.1 in other server B with trial license for the testing in 11/9/2015.  

    The new Geocortex 4.3.1 in server B was running fine last week. Somehow, 22/9/2015 it threw the exception:

    Error while handling security action: Cassandra.NoHostAvailableException: None of the hosts tried for query are available (tried: 10.175.103.153)

    I am not able to login Essential Manger, or launch the Post Install application.

    Any issues may cause this? Will the same issue happen when we upgarde Geocortex 3.1.5 to 4.3.1 ?

     

     

    0
  • Ryan Cooney

    Yes this was fixed in 4.4.

    --Ryan

    0
  • Permanently deleted user

    We experienced this issue this morning.  I looked in the 4.4 release notes but there was no mention of CORE-1031.  Can Latitude confirm this is fixed in Essentials 4.4?

    0
  • Jenni Hoang
    We experienced the same issue today.  Would you please confirm CORE-1031 is fixed in v4.4?
    0
  • Permanently deleted user
    I am running 4.4 and GVH 2.5.2. I got this error twice so far, once in Dec 2015 and another one in Jan 2016. Latitude tech support reviewed my setup and log etc in Dec, but did not find anything on my end. So I do not think this bug is fixed in 4.4.
    0
  • Eric Kriener
    this has been happening to me for the last few months (using 4.4) and now happened today....using 4.5...

     

    how to troubleshoot?
    0
  • Permanently deleted user
    Latitude Tech support helped me with this. According to them, there are several different variation of this issue. In my case they had to make changes to my config files. They needed to get some sort of key to include in the configs that are different from machine to machine, so my fix won't work on yours. So I think the best bet is to contact the tech support. In my case it took couple of months to troubleshoot this issue. Hopefully yours will be resolved quickly as they got more experience with this now.
    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.