Database connection failure

I have a fresh installation of upsource. But there is a few issues with that. The most important one - I guess - is that after a few minutes, we get a "Database connection Failure"

Log files includes this:

2018-04-02 11:24:25,857] [Upsource Error] [2018-04-02 11:24:25,856]   WARN - oxy.jetty.WebSocketProxySocket - CLIENT 3  onWebSocketError on client  
[2018-04-02 11:24:25,857] [Upsource Error] java.net.ConnectException: Connection refused
[2018-04-02 11:24:25,857] [Upsource Error]      at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[2018-04-02 11:24:25,857] [Upsource Error]      at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[2018-04-02 11:24:25,857] [Upsource Error]      at org.eclipse.jetty.io.SelectorManager.finishConnect(SelectorManager.java:355)
[2018-04-02 11:24:25,857] [Upsource Error]      at org.eclipse.jetty.io.ManagedSelector.processConnect(ManagedSelector.java:352)
[2018-04-02 11:24:25,857] [Upsource Error]      at org.eclipse.jetty.io.ManagedSelector.access$900(ManagedSelector.java:56)
[2018-04-02 11:24:25,857] [Upsource Error]      at org.eclipse.jetty.io.ManagedSelector$SelectorProducer.processSelected(ManagedSelector.java:289)
[2018-04-02 11:24:25,858] [Upsource Error]      at org.eclipse.jetty.io.ManagedSelector$SelectorProducer.produce(ManagedSelector.java:181)
[2018-04-02 11:24:25,858] [Upsource Error]      at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:249)
[2018-04-02 11:24:25,858] [Upsource Error]      at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
[2018-04-02 11:24:25,858] [Upsource Error]      at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.execute(ExecuteProduceConsume.java:100)
[2018-04-02 11:24:25,858] [Upsource Error]      at org.eclipse.jetty.io.ManagedSelector.run(ManagedSelector.java:147)
[2018-04-02 11:24:25,858] [Upsource Error]      at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
[2018-04-02 11:24:25,858] [Upsource Error]      at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
[2018-04-02 11:24:25,858] [Upsource Error]      at java.lang.Thread.run(Thread.java:748)

 

 

Cannot find out what is the root cause of it.

4 comments

I'm not 100% sure it's the same database related issue but I'm experiencing disconnects with a fresh install of Upsource and am getting the error below:

 

[Upsource Error] [2019-03-01 16:49:17,586] WARN - oxy.jetty.WebSocketProxySocket - CLIENT 2 onWebSocketError on client
[Upsource Error] java.net.ConnectException: Connection refused
[Upsource Error] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:1.8.0_191]
[Upsource Error] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) ~[?:1.8.0_191]
[Upsource Error] at org.eclipse.jetty.io.SelectorManager.finishConnect(SelectorManager.java:355) ~[jetty-io-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.io.ManagedSelector.processConnect(ManagedSelector.java:352) [jetty-io-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.io.ManagedSelector.access$900(ManagedSelector.java:56) [jetty-io-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.io.ManagedSelector$SelectorProducer.processSelected(ManagedSelector.java:289) [jetty-io-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.io.ManagedSelector$SelectorProducer.produce(ManagedSelector.java:181) [jetty-io-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:249) [jetty-util-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148) [jetty-util-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.execute(ExecuteProduceConsume.java:100) [jetty-util-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.io.ManagedSelector.run(ManagedSelector.java:147) [jetty-io-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671) [jetty-util-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589) [jetty-util-9.3.24.v20180605.jar:9.3.24.v20180605]
[Upsource Error] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_191]
0

i did a fresh install some one month back and i can see the error log at upsource home directory/log/cassandra/
if the upsource web application UI throws an error like """Database connection failure""" 
then grep the error log and you should be able to see something like 
Caused by: org.apache.cassandra.io.compress.CorruptBlockException: (/srv/upsource-2018.2.1141/data/cassandra/data/projects/largecontent-d116e430443311e994fbcb05bfbe8967/mc-1800-big-Data.db): corruption detected, chunk at 27594928 of length 64972.

am further looking into that error

0

Any ideas.  Just had this happen to me as well

0

Just a note to the developers. I was looking though the log files and cassandra-stderr contains the following

[2019-05-15 08:54:23,751] [Apache Cassandra Error] 2019-05-15T08:54:23,740 [[APP-WRAPPER] Proxy 1] WARN o.a.cassandra.service.StartupChecks - The JVM is not configured to stop on OutOfMemoryError which can cause data corruption. Use one of the following JVM options to configure the behavior on OutOfMemoryError: -XX:+ExitOnOutOfMemoryError, -XX:+CrashOnOutOfMemoryError, or -XX:OnOutOfMemoryError="<cmd args>;<cmd args>"

 

I guess this could cause the behavior observed by the reporters.

0

Please sign in to leave a comment.