Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to hit the endpoints after bringing up the local kruize demo application #69

Open
suryaachandra opened this issue Feb 28, 2024 · 2 comments

Comments

@suryaachandra
Copy link

suryaachandra commented Feb 28, 2024

Hi @chandrams , @bharathappali ,

Need help in setting this demo application

I have setup this demo application in my locally and seems the application came up but when I try to hit the endpoints in the logs I get page cannot be displayed .

image

one change I have done is changed the MIN_MEM from 16384 to 7128

I am attaching the logs below,

autotune-f44b6c8d4-65rlc 1/2 CrashLoopBackOff 2 (16s ago) 2m45s

Log.txt

when i checked the logs i am getting this error in the log

`
--/ __ / / / / _ | / _ / /// / / / /
-/ // / // / __ |/ , / ,< / // /
--
// |//|//||//
2024-02-29 07:24:45,445 WARN [io.agr.pool] (agroal-11) Datasource '': The connection attempt failed.
2024-02-29 07:24:45,446 WARN [org.hib.eng.jdb.env.int.JdbcEnvironmentInitiator] (main) HHH000342: Could not obtain connection to query metadata: org.postgresql.util.PSQLException: The connection attempt failed.
at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:315)
at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:51)
at org.postgresql.jdbc.PgConnection.(PgConnection.java:223)
at org.postgresql.Driver.makeConnection(Driver.java:465)
at org.postgresql.Driver.connect(Driver.java:264)
at io.agroal.pool.ConnectionFactory.createConnection(ConnectionFactory.java:204)
at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:490)
at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:472)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at io.agroal.pool.util.PriorityScheduledExecutor.beforeExecute(PriorityScheduledExecutor.java:68)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.net.SocketTimeoutException: Connect timed out
at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:546)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:597)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:633)
at org.postgresql.core.PGStream.createSocket(PGStream.java:231)
at org.postgresql.core.PGStream.(PGStream.java:95)
at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:98)
at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:213)
... 12 more

2024-02-29 07:24:55,621 WARN [io.agr.pool] (agroal-11) Datasource '': The connection attempt failed.
2024-02-29 07:24:55,622 WARN [org.hib.eng.jdb.spi.SqlExceptionHelper] (main) SQL Error: 0, SQLState: 08001
2024-02-29 07:24:55,623 ERROR [org.hib.eng.jdb.spi.SqlExceptionHelper] (main) The connection attempt failed.
2024-02-29 07:24:55,635 ERROR [io.qua.run.Application] (main) Failed to start application (with profile prod): java.net.SocketTimeoutException: Connect timed out
at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:546)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:597)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:633)
at org.postgresql.core.PGStream.createSocket(PGStream.java:231)
at org.postgresql.core.PGStream.(PGStream.java:95)
at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:98)
at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:213)
at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:51)
at org.postgresql.jdbc.PgConnection.(PgConnection.java:223)
at org.postgresql.Driver.makeConnection(Driver.java:465)
at org.postgresql.Driver.connect(Driver.java:264)
at io.agroal.pool.ConnectionFactory.createConnection(ConnectionFactory.java:204)
at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:490)
at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:472)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at io.agroal.pool.util.PriorityScheduledExecutor.beforeExecute(PriorityScheduledExecutor.java:68)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)

`
Kindly help on this issue

@bharathappali
Copy link
Member

@suryaachandra Thanks for trying out Kruize.

To help you out and better understand the issue I need some details which are mentioned below:

  • I'm expecting you were running Kruize on minikube setup on a windows machine, Is my assumption correct?
  • Can you please share us the output of kubectl -n monitoring describe pod <autotune pod name>
  • Can I please know which demo you are trying? is it remote monitoring or local monitoring?
    (currently only remote monitoring demo works as we are working on developing the local monitoring use case)

@suryaachandra
Copy link
Author

suryaachandra commented Feb 29, 2024

Hi @bharathappali ,

Thank you so much for your quick response

Please find my responses below,

  1. I'm expecting you were running Kruize on minikube setup on a windows machine, Is my assumption correct?
    Yes running on my windows machine

  2. Can you please share us the output of kubectl -n monitoring describe pod
    Log:
    Log2.txt

  3. Can I please know which demo you are trying? is it remote monitoring or local monitoring?
    **Steps followed for running the demo

  1. downloaded the minikube
  2. cloned the repo https://github.com/kruize/kruize-demos to local
  3. ran the ./autotune_minikube_demo_setup.sh
    Attaching the output log
    Log3.txt
    But after the container came up unable to access the endpoints to view the results
  1. (currently only remote monitoring demo works as we are working on developing the local monitoring use case)
    I was normally executing the above command could you please let me know how to execute remote monitoring demo .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants