Kill Bill Docker Analytic Plugin Not Working

[Jm Tiong]

Hi!

I configure my kill bill docker image as followed

```
docker run -tid \
--name killbilltest \
-p 5555:8080 \
--link mysql:mysql \
-v $HOME/projects/killbill_docker_compose/killbill/stripe.yml:/etc/killbill/stripe.yml \
-e KILLBILL_PLUGIN_STRIPE=1 \
-e KILLBILL_PLUGIN_ANALYTICS=1 \
-e KILLBILL_CONFIG_DAO_URL=jdbc:mysql://mysql:3306/killbill \
-e KILLBILL_CONFIG_DAO_USER=root \
-e KILLBILL_CONFIG_DAO_PASSWORD=password \
killbill/killbill:0.18.21
```

After the server has started, I tried visiting `http://localhost:5555/1.0/kb/nodesInfo` but it told me that analytics-plugin's state is STOPPED.

Trying out the healthcheck endpoint `http://localhost:5555/plugins/killbill-analytics/healthcheck`, it returns 404 to me.

May I know how do I install this plugin properly?

[Pierre-Alexandre Meyer]

Hello,

Kill Bill 0.18 is not supported on this mailing-list anymore, could you try our latest version 0.20?

See http://docs.killbill.io/0.20/getting_started.html.

Best regards,

--
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-us...@googlegroups.com.
To post to this group, send email to killbill...@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/11919eb1-a44c-422e-a4fb-e6b46d177966%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Pierre

[Jm Tiong]

Hi Pierre!

Thanks for replying, I have tried out the getting started guide and if I followed the steps entirely, it is working properly.

However, when I wanted to include the plugins and using my own custom mysql db, the Kill Bill Api could not be started.

This is my docker compose file

version: '3.2'

services:

killbill:

image: killbill/killbill:0.20.5

ports:

- "5555:8080"

- "5554:8000"

- "12345:12345"

environment:

- KILLBILL_DAO_URL=jdbc:mysql://mysql:3306/killbill

- KILLBILL_DAO_USER=root

- KILLBILL_DAO_PASSWORD=killbill

- KILLBILL_PLUGIN_STRIPE=1

- KILLBILL_PLUGIN_ANALYTICS=1

network_mode: "bridge"

external_links:

- custom_mysql:mysql

And when the killbill container is started, it hang at this line

task path: /var/lib/tomcat/.ansible/roles/killbill-cloud/ansible/roles/tomcat/tasks/restart.yml:20
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["/usr/share/tomcat/bin/catalina.sh", "stop", "30", "-force"], "delta": "0:00:00.410085", "end": "2019-02-13 03:09:12.905859", "msg": "non-zero return code", "rc": 1, "start": "2019-02-13 03:09:12.495774", "stderr": "", "stderr_lines": [], "stdout": "$CATALINA_PID was set but the specified file does not exist. Is Tomcat running? Stop aborted.", "stdout_lines": ["$CATALINA_PID was set but the specified file does not exist. Is Tomcat running? Stop aborted."]}
...ignoring
2019-02-13T03:09:12.990468600Z 
TASK [clean up Tomcat deployment files] ****************************************
task path: /var/lib/tomcat/.ansible/roles/killbill-cloud/ansible/roles/tomcat/tasks/restart.yml:31
ok: [localhost] => (item=webapps/ROOT) => {"changed": false, "item": "webapps/ROOT", "path": "/var/lib/tomcat/webapps/ROOT", "state": "absent"}
changed: [localhost] => (item=work/) => {"changed": true, "item": "work/", "path": "/var/lib/tomcat/work/", "state": "absent"}
2019-02-13T03:09:13.956849600Z 
TASK [start Tomcat] ************************************************************
task path: /var/lib/tomcat/.ansible/roles/killbill-cloud/ansible/roles/tomcat/tasks/restart.yml:43
changed: [localhost] => {"changed": true, "cmd": ["nohup", "/usr/share/tomcat/bin/catalina.sh", "start"], "delta": "0:00:00.414818", "end": "2019-02-13 03:09:14.656756", "rc": 0, "start": "2019-02-13 03:09:14.241938", "stderr": "", "stderr_lines": [], "stdout": "Tomcat started.", "stdout_lines": ["Tomcat started."]}
2019-02-13T03:09:14.758568100Z 
TASK [run Tomcat] **************************************************************
task path: /var/lib/tomcat/.ansible/roles/killbill-cloud/ansible/roles/tomcat/tasks/restart.yml:54
skipping: [localhost] => {"changed": false, "skip_reason": "Conditional result was False"}
META: ran handlers
META: ran handlers
2019-02-13T03:09:14.819640300Z 
PLAY RECAP *********************************************************************
localhost                  : ok=5    changed=3    unreachable=0    failed=0   
2019-02-13T03:09:14.823469500Z 

What have I done wrongly? 

[Jm Tiong]

Hi Pierre!

I finally managed to get it running, apparently 2GB of memory is not sufficient and I have to increase to 3GB. With that, Kill Bill is running, however, the plugins are not working.

When I go to `http://localhost:5555/1.0/kb/nodesInfo`, I couldn't make up the information from there but searching key terms like analytic and stripe

bundleSymbolicName	"org.kill-bill.billing.plugin.java.analytics-plugin"
pluginKey	null
pluginName	"org.kill-bill.billing.plugin.java.analytics-plugin"
version	null
state	"STOPPED"
isSelectedForStart	true
services	[]

bundleSymbolicName	"org.kill-bill.billing.killbill-platform-osgi-bundles-jruby-1"
pluginKey	"STRIPE"
pluginName	"killbill-stripe"
version	"4.1.1"
state	"RUNNING"
isSelectedForStart	true

Going to this link `http://localhost:5555/plugins/killbill-analytics/healthcheck` and `http://localhost:5555/plugins/killbill-stripe` returns a 404.

On Tuesday, February 12, 2019 at 6:14:53 PM UTC+8, Pierre-Alexandre Meyer wrote:

[Pierre-Alexandre Meyer]

Hi Jm,

I don't think we have enough information to understand what is not working. I would suggest taking a look at the Kill Bill logs (try `docker logs') during the startup sequence, this would probably show the issue.

Hope that helps,

To view this discussion on the web visit https://groups.google.com/d/msgid/killbilling-users/5080222e-a048-4dcd-9977-05ef7f5c03e5%40googlegroups.com.

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

--

Pierre