getting in kaui 500 error "We're sorry, but something went wrong." - in login

[zat]

hi,

we are getting in kaui "We're sorry, but something went wrong." 

the deployment is : tomcat  with jdk 7 db mysql

installed killbill 18.0.3 used kpm for installation include kaui

set all relevant info for killbill  on catalina.properties  and database.yml for kaui

# Kill Bill properties

org.killbill.dao.url=jdbc:mysql://<ip>:3306/killbill

org.killbill.dao.user=username

org.killbill.dao.password=password

ANTLR_USE_DIRECT_CLASS_LOADING=true

# Kill Bill properties

org.killbill.billing.osgi.dao.url=jdbc:mysql://<ip>:3306/killbill

org.killbill.billing.osgi.dao.user=username

org.killbill.billing.osgi.dao.password=password

# Kaui properties

#kaui.db.adapter=jdbcmysql

kaui.db.url=jdbc:mysql://<ip>:3306/kaui

kaui.db.username=user

kaui.db.password=pass

-----------------------

we see new new rows in mysql when we try to the sign up in kaui

what may be the problem

when looking in the logs (see below) nothing special beside http 500 error  (how we can have better/more logs for kaui in the authentication? )

we have also catalina.log  with INFO /DEBUG  - no error !

also curl call is not working.

what may be the problem ?

Thanks.

<ip> - - [14/Feb/2017:20:33:08 +0000] "POST /kaui/users/sign_in HTTP/1.1" 500 643

127.0.0.1 - - [14/Feb/2017:20:36:40 +0000] "GET /1.0/kb/security/subject HTTP/1.1" 200 252

127.0.0.1 - - [14/Feb/2017:20:38:03 +0000] "GET /1.0/kb/security/permissions HTTP/1.1" 200 785

127.0.0.1 - - [14/Feb/2017:20:39:35 +0000] "POST /1.0/kb/tenants HTTP/1.1" 500 327

127.0.0.1 - - [14/Feb/2017:20:41:00 +0000] "POST /1.0/kb/security/users HTTP/1.1" 201 -

127.0.0.1 - - [14/Feb/2017:20:43:43 +0000] "GET /1.0/kb/security/subject HTTP/1.1" 200 252

[stephane brossier]

Zat,

Your description is a little terse, just seeing traces with '500' will not be enough to help you. First of all:

• Which KAUI version are you using?
• How did you deploy? Are you using our docker images? If not how?
• Can you verify your Kill Bill installation is correct by running our tutorial first (to understand if issue is Kill Bill server or KAUI)

Stéphane

--
You received this message because you are subscribed to the Google Groups "Kill Bill users mailing-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to killbilling-users+unsubscribe@googlegroups.com.
To post to this group, send email to killbilling-users@googlegroups.com.
Visit this group at https://groups.google.com/group/killbilling-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/killbilling-users/d9e7b71c-52c8-4b6b-88b7-bf62dcfd3ffd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[zat]

HI,

Yes i know the info is limited that was our problem as well. since in the logs that was the only error we have found.

Btw - now the killbill and kaui system is working after we 2 hours we try to sign up with new user name (using kaui) this open "add new tenant" we created new tenant

and surprise  the kaui and kill start to work well and now we can see the 2 tenants the new one and the standard (based on tutorial ) that we have try to create in the 1st try (bob lazar) 

yet we want to get into the bottom of the issue.

1. The kaui is the latest  base on kpm install https://github.com/killbill/killbill-cloud/tree/master/kpm

2.  no Docker - ubuntu on aws and install kpm 

3. we are not using jetty we use tomcat 7 and we use https://github.com/killbill/killbill-cloud/tree/master/kpm

I think the problem was on killbill since we could not create tenant nor get the bob/lazar info also using Curl command 

1. How can we modify setting and gets more detail/debug logs for kaui  ?

2. One important input was that after we have deployed the killbill and kaui using kpm we have started the killbill using ./catalina.sh start 

than try to create new tenant (bob /lazar) using Curl but got timeout.

3. after that stop the tomcat service change the configuration to my sql DB .

4. got the error message   "We're sorry, but something went wrong." 

Thank you.

 

To unsubscribe from this group and stop receiving emails from it, send an email to killbilling-us...@googlegroups.com.
To post to this group, send email to killbill...@googlegroups.com.

[zat]

now after the input below once agin we get 500 error

after restart the aws server . what is wrong ??

thanks.

last log after restrat

2017-02-16T12:26:02,737+0000 lvl='INFO', log='AbstractValidatingSessionManager', th='http-bio-8080-exec-3', xff='', rId='', aRId='', tRId='', Enabling session validation scheduler...

2017-02-16T12:26:02,741+0000 lvl='INFO', log='EhCacheManager', th='http-bio-8080-exec-3', xff='', rId='', aRId='', tRId='', Using existing EHCache named [shiro-activeSessionCache]

see logs replicate each time calling login in kaui:

 - - [16/Feb/2017:13:04:53 +0000] "GET /kaui/main/available_engines.json HTTP/1.1" 401 72

- - [16/Feb/2017:13:04:53 +0000] "GET /favicon.ico HTTP/1.1" 404 973

 - - [16/Feb/2017:13:05:39 +0000] "GET /kaui/home HTTP/1.1" 302 112

 - - [16/Feb/2017:13:06:21 +0000] "GET /kaui/users/sign_in HTTP/1.1" 200 3177

 - - [16/Feb/2017:13:06:21 +0000] "GET /kaui/assets/application-0bb35510d692e43940b6e790aff82d7b15d7c6c56a33c535e53dff51e06c2d86.css HTTP/1.1" 304 -

 - - [16/Feb/2017:13:06:21 +0000] "GET /kaui/assets/application-d7733d4437fedda4cc40e198b6a1db99f5e88c83c0b0ee7d09a5fd0f5f9f0c34.js HTTP/1.1" 304 -

 - - [16/Feb/2017:13:06:21 +0000] "GET /kaui/assets/kaui/logo-17118d22c6045d1d57be70a8a0b45fa94ecc355c5ce007af5a07cac407f94448.png HTTP/1.1" 304 -

 - - [16/Feb/2017:13:06:21 +0000] "GET /kaui/main/available_engines.json HTTP/1.1" 401 72

 - - [16/Feb/2017:13:06:27 +0000] "POST /kaui/users/sign_in HTTP/1.1" 500 643

[zat]

retry login in kaui get error and show the following logs:

2017-02-16T15:18:20,268+0000 lvl='INFO', log='LoggingFilter', th='http-bio-8080-exec-183', xff='', rId='ad3996da-4d9c-4367-8f66-ba43da6cb6de', aRId='', tRId='', 18 * Server in-bound request

18 > GET http://127.0.0.1:8080/1.0/kb/security/permissions

18 > accept: application/json

18 > user-agent: killbill/1.3.0; jruby 1.7.24 (1.9.3p551) 2016-01-20 bd68d85 on OpenJDK 64-Bit Server VM 1.8.0_121-8u121-b13-0ubuntu1.16.04.2-b13 +jit [linux-amd64]

18 > authorization: Basic YWRtaW46cGFzc3dvcmQ=

18 > host: 127.0.0.1:8080

18 > 

2017-02-16T15:18:20,269+0000 lvl='INFO', log='LoggingFilter', th='http-bio-8080-exec-183', xff='', rId='ad3996da-4d9c-4367-8f66-ba43da6cb6de', aRId='', tRId='', 18 * Server out-bound response

18 < 200

18 < Content-Type: application/json

18 < 

[thorst...@gmail.com]

Hi Guys I had exactly the same Problem:
Fresh and clean install of latest killbill version 18 on AWS Ubuntu 16.04. I set up everything as mention in killbil documentation. even with mysql db and correct configuration.
Every time a restarted the process via ./bin/startup.sh i had to wait at least 2 hours until i could login in KAUI. If i tried to early I got the error "Sorry but something went wrong". So I had a look at catalina.out and found an interesting WARNING:
"System property java.security.egd has not been set, this may cause some requests to hang because of a lack of entropy. You should probably set it to 'file:/dev/./urandom'"
So I found an interesting post here:
http://ruleoftech.com/2016/avoiding-jvm-delays-caused-by-random-number-generation
they mention that you can test if you current security setting leads to a problem by trying command:
head -n 1 /dev/random
if this is slow you will get delay problems.
I Solved it via adjustments of the java.security file with setting parameter:
securerandom.source=file:/dev/./urandom
I Hope this will help someone else since it took me days to find a solution for this behavior. Maybe killbill-team might even put it to the FAQ or Troubleshooting section

[Pierre-Alexandre Meyer]

Hi Thorsten,

Thank you for updating the group.

Make sure also to have enough entropy generated by the system, this is covered in our post deployment checklist here:

  http://docs.killbill.io/latest/userguide_deployment.html#_pre_and_post_deployment_checklist

I've also created https://github.com/killbill/killbill-admin-ui-standalone/issues/16 for tracking the issue on the Kaui side.

--
You received this message because you are subscribed to the Google Groups "Kill Bill users mailing-list" group.

To unsubscribe from this group and stop receiving emails from it, send an email to killbilling-users+unsubscribe@googlegroups.com.
To post to this group, send email to killbilling-users@googlegroups.com.

Visit this group at https://groups.google.com/group/killbilling-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/killbilling-users/75ae20ea-ff02-49f6-b0aa-d688fc24b154%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Pierre

[Dhruvin Patel]

I tried the same but error is still shown : "

We're sorry, but something went wrong.

You can see the error below:

[cedric...@gmail.com]

You need to show us what you have in your killbill log. I suspect killbill or KAUI is not able to connect to the database

You need  

[Dhruvin Patel]

Logs:

20-Jul-2020 10:54:36.848 SEVERE [catalina-exec-3] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [default] in context with path [] threw exception [org.skife.jdbi.v2.exceptions.UnableToObtainConnectionException: java.sql.SQLTimeoutException: Timeout after 10001ms of waiting for a connection.] with root cause

java.sql.SQLTimeoutException: Timeout after 10001ms of waiting for a connection.

at com.zaxxer.hikari.pool.BaseHikariPool.getConnection(BaseHikariPool.java:233)

at com.zaxxer.hikari.pool.BaseHikariPool.getConnection(BaseHikariPool.java:183)

at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:93)

at net.sf.log4jdbc.sql.jdbcapi.DataSourceSpy.getConnection(DataSourceSpy.java:147)

at org.skife.jdbi.v2.DataSourceConnectionFactory.openConnection(DataSourceConnectionFactory.java:36)

at org.skife.jdbi.v2.DBI$4.execute(DBI.java:226)

at org.skife.jdbi.v2.DBI$4.execute(DBI.java:223)

at org.killbill.commons.profiling.Profiling.executeWithProfiling(Profiling.java:33)

at org.skife.jdbi.v2.DBI.open(DBI.java:223)

at org.skife.jdbi.v2.DBI.open(DBI.java:215)

at org.skife.jdbi.v2.sqlobject.OnDemandHandleDing.getHandle(OnDemandHandleDing.java:38)

at org.skife.jdbi.v2.sqlobject.OnDemandHandleDing.retain(OnDemandHandleDing.java:46)

at org.skife.jdbi.v2.sqlobject.SqlObject.invoke(SqlObject.java:179)

at org.skife.jdbi.v2.sqlobject.SqlObject$1.intercept(SqlObject.java:76)

at org.skife.jdbi.v2.sqlobject.CloseInternalDoNotUseThisClass$$EnhancerByCGLIB$$b5ba1c96.create(<generated>)

at org.killbill.billing.util.security.shiro.dao.JDBCSessionDao.doCreate(JDBCSessionDao.java:76)

at org.apache.shiro.session.mgt.eis.AbstractSessionDAO.create(AbstractSessionDAO.java:116)

at org.apache.shiro.session.mgt.eis.CachingSessionDAO.create(CachingSessionDAO.java:184)

at org.apache.shiro.session.mgt.DefaultSessionManager.create(DefaultSessionManager.java:177)

at org.apache.shiro.session.mgt.DefaultSessionManager.doCreateSession(DefaultSessionManager.java:158)

at org.apache.shiro.session.mgt.AbstractValidatingSessionManager.createSession(AbstractValidatingSessionManager.java:136)

at org.killbill.billing.server.security.KillBillWebSessionManager.start(KillBillWebSessionManager.java:39)

at org.apache.shiro.mgt.SessionsSecurityManager.start(SessionsSecurityManager.java:152)

at org.apache.shiro.subject.support.DelegatingSubject.getSession(DelegatingSubject.java:336)

at org.apache.shiro.subject.support.DelegatingSubject.getSession(DelegatingSubject.java:312)

at org.killbill.billing.util.glue.KillBillSubjectDAO.saveToSession(KillBillSubjectDAO.java:38)

at org.apache.shiro.mgt.DefaultSubjectDAO.save(DefaultSubjectDAO.java:147)

at org.apache.shiro.mgt.DefaultSecurityManager.save(DefaultSecurityManager.java:383)

at org.apache.shiro.mgt.DefaultSecurityManager.createSubject(DefaultSecurityManager.java:350)

at org.apache.shiro.mgt.DefaultSecurityManager.createSubject(DefaultSecurityManager.java:183)

at org.apache.shiro.mgt.DefaultSecurityManager.login(DefaultSecurityManager.java:283)

at org.apache.shiro.subject.support.DelegatingSubject.login(DelegatingSubject.java:256)

at org.apache.shiro.web.filter.authc.AuthenticatingFilter.executeLogin(AuthenticatingFilter.java:53)

at org.apache.shiro.web.filter.authc.BasicHttpAuthenticationFilter.onAccessDenied(BasicHttpAuthenticationFilter.java:227)

at org.apache.shiro.web.filter.AccessControlFilter.onAccessDenied(AccessControlFilter.java:133)

at org.apache.shiro.web.filter.AccessControlFilter.onPreHandle(AccessControlFilter.java:162)

at org.apache.shiro.web.filter.PathMatchingFilter.isFilterChainContinued(PathMatchingFilter.java:203)

at org.apache.shiro.web.filter.PathMatchingFilter.preHandle(PathMatchingFilter.java:178)

at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:131)

at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)

at org.apache.shiro.guice.web.SimpleFilterChain.doFilter(SimpleFilterChain.java:41)

at org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:449)

at org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:365)

at org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)

at org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)

at org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:383)

at org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:362)

at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:125)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)

at com.codahale.metrics.servlet.AbstractInstrumentedFilter.doFilter(AbstractInstrumentedFilter.java:111)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)

at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:543)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)

at org.apache.catalina.valves.rewrite.RewriteValve.invoke(RewriteValve.java:305)

at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690)

at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:747)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)

at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:615)

at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)

at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:818)

at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1626)

at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

at java.lang.Thread.run(Thread.java:748)

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:53:39 +0530] "GET /index.html" 304 - 256 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:53:39 +0530] "GET /css/bootstrap.min.css" 304 - 23 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:53:39 +0530] "GET /css/killbill-bootstrap.css" 304 - 17 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:53:39 +0530] "GET /images/KillBillLogo400x400.png" 304 - 27 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:53:41 +0530] "GET /api.html" 304 - 5 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:53:41 +0530] "GET /css/swagger-ui.css" 304 - 7 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:53:41 +0530] "GET /css/killbill-swagger.css" 304 - 9 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:53:41 +0530] "GET /lib/swagger-ui-bundle.js" 304 - 29 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:53:41 +0530] "GET /lib/swagger-ui-standalone-preset.js" 304 - 33 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:53:41 +0530] "GET /images/killbill_logo.png" 304 - 7 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:53:43 +0530] "GET /swagger.json" 200 266110 2022 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:53:59 +0530] "GET /kaui" 302 - 0 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:54:00 +0530] "GET /kaui/" 302 117 1757 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:54:08 +0530] "GET /kaui/users/sign_in" 200 4202 7717 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:54:09 +0530] "GET /kaui/main/available_engines.json" 401 61 76 -

127.0.0.1 - - [20/Jul/2020:10:54:36 +0530] "GET /1.0/kb/security/permissions" 500 10553 10181 -

0:0:0:0:0:0:0:1 - - [20/Jul/2020:10:54:36 +0530] "POST /kaui/users/sign_in" 500 643 10453 -

Please look over this...

[cedric...@gmail.com]

This means connection cannot be established form kill bill to mysql database. ensure that mysql is running and is listening to connections by trying the following command: mysql -h your_ip -u your_user -p

you should run this command from the computer killbill is running on. 

Are killbill and mysql both running on the same computer ?

On Tuesday, February 14, 2017 at 10:58:57 PM UTC+2, Joal wrote: