[ 
https://issues.apache.org/jira/browse/CASSANDRA-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joshua McKenzie resolved CASSANDRA-14814.
-----------------------------------------
    Resolution: Invalid

[~Hacky44]: As indicated on the other ticket, you'll get faster, higher quality 
responses by reaching out on #cassandra on freenode or hitting up the user 
mailing lists.

Closing as invalid.

> Can anyone give me some pointers where to look, or start to look for where 
> this issue is coming from?   On startup I get this in the logs and my service 
> goes into a failed state. Active(exited)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14814
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14814
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: Ravi Gangwar
>            Priority: Major
>             Fix For: 2.2.x
>
>
> Hi,
> Can anyone give me some pointers where to look, or start to look for where 
> this issue is coming from?
> On startup I get this in the logs and my service goes into a failed state. 
> Active(exited)
> ERROR [main] 2018-08-28 16:25:01,443 CassandraDaemon.java:655 - Exception 
> encountered during startup
> java.lang.IllegalStateException: Failed to bind port 9042 on 192.168.118.237.
>       at org.apache.cassandra.transport.Server.run(Server.java:187) 
> ~[apache-cassandra-2.2.11.jar:2.2.11]
>       at org.apache.cassandra.transport.Server.start(Server.java:120) 
> ~[apache-cassandra-2.2.11.jar:2.2.11]
>       at 
> org.apache.cassandra.service.CassandraDaemon.start(CassandraDaemon.java:446) 
> [apache-cassandra-2.2.11.jar:2.2.11]
>       at 
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:548)
>  [apache-cassandra-2.2.11.jar:2.2.11]
>       at 
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:642) 
> [apache-cassandra-2.2.11.jar:2.2.11]
> WARN  [main] 2018-08-28 16:24:57,894 CLibrary.java:159 - Unable to lock JVM 
> memory (ENOMEM). This can result in part of the JVM being swapped out, 
> especially with mmapped I/O enabled. Increase RLIMIT_MEMLOCK or run Cassandra 
> as root.
> WARN  [main] 2018-08-28 16:24:57,894 StartupChecks.java:118 - jemalloc shared 
> library could not be preloaded to speed up memory allocations
> WARN  [main] 2018-08-28 16:24:57,895 StartupChecks.java:150 - JMX is not 
> enabled to receive remote connections. Please see cassandra-env.sh for more 
> info.
> WARN  [SharedPool-Worker-6] 2018-08-28 16:28:21,624 SliceQueryFilter.java:307 
> - Read 643 live and 1286 tombstone cells in system.schema_columns for key: 
> hdb (see tombstone_warn_threshold). 2147483647 columns were requested, 
> slices=[-]
> WARN  [SharedPool-Worker-4] 2018-08-28 16:29:22,318 SliceQueryFilter.java:307 
> - Read 643 live and 1286 tombstone cells in system.schema_columns for key: 
> hdb (see tombstone_warn_threshold). 2147483647 columns were requested, 
> slices=[-]
> WARN  [main] 2018-08-28 16:55:09,948 StartupChecks.java:118 - jemalloc shared 
> library could not be preloaded to speed up memory allocations
> WARN  [main] 2018-08-28 16:55:09,948 StartupChecks.java:150 - JMX is not 
> enabled to receive remote connections. Please see cassandra-env.sh for more 
> info.
>  
> Regards,
> Ravi



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to