# KONG cassandra error

**URL:** <https://discuss.konghq.com/t/kong-cassandra-error/2778>\
**Category:** General\
**Created:** [February 8, 2019, 7:09am UTC](https://discuss.konghq.com/t/kong-cassandra-error/2778 "2019-02-08T07:09:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Niranjan\_Kolly](https://avatars.discourse-cdn.com/v4/letter/n/5f8ce5/32.png) [@Niranjan\_Kolly](https://discuss.konghq.com/u/Niranjan_Kolly)\
**Post date:** [February 8, 2019, 7:09am UTC](https://discuss.konghq.com/t/kong-cassandra-error/2778/1 "2019-02-08T07:09:11Z")

</div>

We running kong EE(0.34-1) on kubernetes . We are frequently getting following error when we start kong and even during kong migration.

nginx: [error] init\_by\_lua error: /usr/local/share/lua/5.1/kong/init.lua:305: could not load routes: [nil] could not execute page query: no host details for 10.244.3.110 stack traceback:  
[C]: in function ‘assert’  
/usr/local/share/lua/5.1/kong/init.lua:305: in function ‘init’  
init\_by\_lua:3: in main chunk

After 2 to 3 restarts kong will comes to RUNNING mode.

---

<div class="post-metadata">

**Author:** ![kikito](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/kikito/32/15_2.png) [@kikito](https://discuss.konghq.com/u/kikito)\
**Post date:** [February 8, 2019, 6:46pm UTC](https://discuss.konghq.com/t/kong-cassandra-error/2778/2 "2019-02-08T18:46:14Z")

</div>

Hi, this forum is primarily for Kong Community Edition queries. You will get a more accurate answer (with an SLA) if you contact your sales / customer success representative directly.

I am aware of Cassandra sometimes returning the `no host details` error that you are experiencing in the past. Supposedly that problem was fixed with [lua-cassandra 1.3.2](https://github.com/thibaultcha/lua-cassandra/blob/master/CHANGELOG.md#132), which is the version shipped with Kong EE 0.34.

Please contact your sales / customer success representative about this. More information about your current config - especially DNS and Kubernetes settings might help.
