Logger with Rails app
pfeodrippe opened this issue · comments
I exec deis logs and it says it's not logging correctly. I was using heroku before and pushed the code to deis without any modifications. Maybe do I have to configure something to use fluentd?
Error: There are currently no log messages. Please check the following things:
1) Logger and fluentd pods are running.
2) If you just installed the logger components via the chart, please make sure you restarted the workflow pod.
3) The application is writing logs to the logger component.
You can verify that logs are appearing in the logger component by issuing the following command:
curl http://<log service ip>:80/logs/quaint-zoologer on a kubernetes host.
To get the service ip you can do the following: kubectl get svc deis-logger --namespace=deis
The chart should work out of the box with most installations of kubernetes. Few questions:
- Are you using aws? GKE?
- Did you happen to follow the instructions in the error message? Like restarting the controller pod.
- If you do
kubectl exec <flunetd pod> ls /var/log/containersdoes anything return?
- I'm using AWS
- Yes, I've restarted the controller
- It returns
deis-builder-ndcxw_deis_deis-builder-4c56fc06e227634903d28174107f5202cc1bcaa617aafd5225e64d846570533e.log
deis-builder-ndcxw_deis_deis-builder-60a7e9db575d9770c380cf0a555e2e621399f66c45302457e548b1f6a4c6e074.log
deis-controller-t90hs_deis_POD-4ff6026a8c5b9d04e706f2d815162742edae847066a4c1579a9f25c823d0b95e.log
deis-controller-t90hs_deis_deis-controller-0a71aa77cf994254f95fbce0d796ba4c6ece4e084f4a3c0c32f36ed943e3ab77.log
deis-controller-t90hs_deis_deis-controller-43a09d42ecae9f32a4e9f716396b216b29a70599fa284241afed73addb6d1f1b.log
deis-controller-t90hs_deis_deis-controller-d1e0b12289f15252b94d830be1e2904ed0380fa5c05e417922192206bebc0e5c.log
deis-database-927n2_deis_POD-a6be41bf4cd08c3fe17030182e3b0316f446618b896b472b2c4a49bcf5934d76.log
deis-database-927n2_deis_deis-database-5d648a6a9e7e7025c84e1109a47214151f9223056dedeb540e37bfde5b43b617.log
deis-logger-8ufjw_deis_POD-deeb8e3dc7966e19ae8df8dcb44b596219b399c22339023d7bb41645269f5a03.log
deis-logger-8ufjw_deis_deis-logger-0605d11b3145ce45bd05bd6128032d6ce42b8e7633d0492d72bb5bab23bd612f.log
deis-logger-fluentd-qp6oj_deis_POD-0b5746b3a48e5441c9741df4b2b4d33e96bb1ed6007d62650fd9ca19c2e7d140.log
deis-logger-fluentd-qp6oj_deis_deis-logger-fluentd-f2afd833e0592d0e02bec32d562cde59cad3ffd697746c53a35283f21286351e.log
deis-minio-hrpom_deis_POD-bc051250de4ce1096ce53fac5a2c72654327bc5744fb533856fb23207d9f7920.log
deis-minio-hrpom_deis_deis-minio-578651dd0c98d030178655db3c48277cb09c82e10368ae3ac044ce4c78f6e22c.log
deis-registry-dlzx0_deis_POD-6576f463ab2a3e18dad908602fac031cf0a3a5b4bea3c7326a7fabf382a7146c.log
deis-registry-dlzx0_deis_deis-registry-3b738a4b57ca1e6387c63e43f905f96acdd6d8173bf2514a9d100f04e1adf825.log
deis-registry-dlzx0_deis_deis-registry-a04d060f9dac691c9c1feb621fa5d4206c799a3da2670f4136ff5c141c36b53f.log
deis-registry-dlzx0_deis_deis-registry-f97637b65c74855d3e12aa224ca9305bc4a6bdba7e1eee56fa9de5a9a1ac570e.log
deis-router-n9i0j_deis_POD-7fd903e70c33a44dc276e1c6682d697d3d2fef735b0d6a0c5b152a355fb4df38.log
deis-router-n9i0j_deis_deis-router-b0c27787fa1e655c11986ca1cac93e5635f341360aec7330078939546e036f06.log
deis-workflow-manager-wg2hu_deis_POD-17a4045ba34e144d979819559b8eb31d39dcc1bcf3710d54917961f8ae0c4b0b.log
deis-workflow-manager-wg2hu_deis_deis-workflow-manager-95780efb8bc150422786b838f7b9123865e11c970d9da2307157a43225215a6e.log
fluentd-elasticsearch-ip-172-20-0-222.ec2.internal_kube-system_POD-8f68b02c3ad5710bc534978a51f94110f7faf0f2f6b4511c27fb622710ac3a55.log
fluentd-elasticsearch-ip-172-20-0-222.ec2.internal_kube-system_fluentd-elasticsearch-6d17bf130a4982177d2210fbfc9b4a3bb1b4d71d55d23f5834684ca948af5911.log
heapster-v1.0.2-1818579379-buzg6_kube-system_POD-743cee535f80685b90f4944b59ee52630cde3b9f9ea9797f6bb90181bb685821.log
heapster-v1.0.2-1818579379-buzg6_kube-system_eventer-4fdc62425b6bb10ff499556f42d9a9408be1cdc5b71bb464af81d774547d5b0c.log
heapster-v1.0.2-1818579379-buzg6_kube-system_eventer-nanny-c97500deb85a6d75377f8c0d9afbba37169b6947c3f4473a8dea4dab6e9ad70e.log
heapster-v1.0.2-1818579379-buzg6_kube-system_heapster-62c60824eeeb5b34a9f957ca0a53b73f667788608a48ee23a8557a7b15e37e37.log
heapster-v1.0.2-1818579379-buzg6_kube-system_heapster-nanny-9a35e6bc74740f4e5c4dcb4d1acef53b43afa8e22bf63110f6086f7c87c9c83d.log
hungry-question-v3-web-832p3_hungry-question_POD-3b28928990aea1207c2d8e9fbba046052d5408f2e0023b71b7efdcd4d5b9d345.log
hungry-question-v3-web-832p3_hungry-question_hungry-question-web-f8416b40d7a68f13167b344c30e2765b56f9f564f95d5162d6a15addb9d66bf1.log
kibana-logging-v1-1onb1_kube-system_POD-0e2aea1f0aab2f27c26966d9a214545296f341be61c73e3bd30e98033a125842.log
kibana-logging-v1-1onb1_kube-system_kibana-logging-2a1fd632c6dca8737f091405bac6ff06b55cf0b8b339e1103d61d40f1ca27c14.log
kibana-logging-v1-1onb1_kube-system_kibana-logging-a4a20d545e87054bd196b2734e2bba24fb3f693fe7d44a30686c06b1f232fa61.log
kibana-logging-v1-1onb1_kube-system_kibana-logging-a735580555f5ae359360ece689c45d71d6b063cf296f9d4525c732a262d86f6c.log
kube-dns-v11-9haoh_kube-system_POD-8f59cc5b657fd22ef1c3b9f55d84b91577ecfe9d625eb24a1a63849a5a3aa25c.log
kube-dns-v11-9haoh_kube-system_etcd-67cfb568f066ad08788879179d80140306063b1e4c372f720688a92cb84a6219.log
kube-dns-v11-9haoh_kube-system_healthz-99cf9e3882f6ad66ac14f23c4ceff113d96ec113327e2f17fef9a832a809f86d.log
kube-dns-v11-9haoh_kube-system_kube2sky-34cf5eeae8c5df34d7caf8ef206d6169f9abda4fd661d42f9c0cb1599381067c.log
kube-dns-v11-9haoh_kube-system_skydns-8e7ed4bc505d45027f9c979f18463d5c99ff2eb11479131024121c2a095aa053.log
kube-proxy-ip-172-20-0-222.ec2.internal_kube-system_POD-8cc6dbc079aaba7e5e1daa55e4c39275489134fb9eec407c7fbe43cd8fa1d371.log
kube-proxy-ip-172-20-0-222.ec2.internal_kube-system_kube-proxy-e62955e4d3ef1e568841bb0f719c091245b44225da4d731f1d2909fdc3160616.log
kubernetes-dashboard-v1.0.1-an2tx_kube-system_POD-a2a3d2ef8120cd2fd632c7ac4d053e39fc21416fc5760c0f26c78477f21c1222.log
kubernetes-dashboard-v1.0.1-an2tx_kube-system_kubernetes-dashboard-56aeff536dda0933ea691a91cf5a0e4955fbfb79c462296e8ac50e3908606733.log
quaint-zoologer-v3-cmd-eeh2f_quaint-zoologer_POD-bb6ee392f76ec17fc6f4badd4f2a1e63e87993843d0e2e3b69024fd7e7b94e4c.log
quaint-zoologer-v3-cmd-eeh2f_quaint-zoologer_quaint-zoologer-cmd-267e6f388e75ee21005a44d4095602245a800a80b4e7c109e4e5748b37a5754a.log
quaint-zoologer-v3-cmd-eeh2f_quaint-zoologer_quaint-zoologer-cmd-73ea61b81301a13de353ef4b8063725ebfb69eae4613fb142f7fc9de0b8ac46b.log
slugbuild-hungry-question-e1590887-f843e1e3_deis_POD-19da2fa4bfb3803ccf655108fee70f62a43c6b0a889fce61a0204251b994c44b.log
slugbuild-hungry-question-e1590887-f843e1e3_deis_deis-slugbuilder-f9cba6b883375448016b8ee0475b992cb858fa7197b57b6b30588ea70c06ec5a.log
slugbuild-quaint-zoologer-aa491142-c68f8cdb_deis_POD-89ce0c5829c42e3445c408248245403a699543e9c94a257a83dd477693a85025.log
slugbuild-quaint-zoologer-aa491142-c68f8cdb_deis_deis-slugbuilder-b30c03a90ad4bf50fbdba19fc190b00a1da92100130da822d827994c481ce16d.log
slugbuild-quaint-zoologer-affdf5e3-2e39b27d_deis_POD-36c696abd409515c804016d16385d15289c1963d49ec7f2e0f8ceada8e470144.log
slugbuild-quaint-zoologer-affdf5e3-2e39b27d_deis_deis-slugbuilder-c553d59c84cb903d504af9459c77077780875ebeb0bd2428bf2ac2103508fd0b.log
slugbuild-quaint-zoologer-affdf5e3-f680aaf9_deis_POD-5249c7dda5356552ad9264018b1c6f0584daafc597f7c90a66d37c46a2531f72.log
slugbuild-quaint-zoologer-affdf5e3-f680aaf9_deis_deis-slugbuilder-645f993cd317053ce8bd17c257894c63933241b51886c20208eca6bb66debb10.log
slugbuild-valued-babushka-7ea01c9e-1f7e97da_deis_POD-07875186964e5e4a4b5cf11a34e713631d511d7a0955097272a06a21b1d45722.log
slugbuild-valued-babushka-7ea01c9e-1f7e97da_deis_deis-slugbuilder-d8889aa98c0b007ca26a669dc41089128b9f22f3c39a873029e16f77d04ec618.log
So I am in the middle of working out a concurrency bug that may be causing issues for some people. I'll let you know when the image is up and you can try it out and see if it fixes your problem.
I'll wait, thanks =)
If you want you can clone this repo and use the make targets to build and
install a new logger onto your cluster and see if it helps
On Apr 11, 2016 5:16 PM, "Paulo Rafael Feodrippe" notifications@github.com
wrote:
I'll wait, thanks =)
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#52 (comment)
Do you mean to make kube-install ?
Yeah you'll need to use docker-build and docker-push to push to a public
registry like quay.io. and you'll need to call build-binary as well. So
something like make build-binary docker-build docker-push kube-<install | update>
On Apr 11, 2016 6:22 PM, "Paulo Rafael Feodrippe" notifications@github.com
wrote:
Do you mean to make kube-install ?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#52 (comment)
Ok, I'll try it, man =). I forgot to say that while the rails app was not working with logger, the https://github.com/deis/example-ruby-sinatra was, I don't know why
You can also edit the chart to use quay.io/deisci/logger:canary
On Apr 11, 2016 6:31 PM, "Paulo Rafael Feodrippe" notifications@github.com
wrote:
Ok, I'll try it, man =). I forgot to say that while the rails app was not
working with logger, the https://github.com/deis/example-ruby-sinatra
was, I don't know why—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#52 (comment)
Did this ever get worked out? Logger has changed quite a bit over the past few releases.
Yeah I think an update would be nice. Logger is much different now
I'm closing this since it hasn't had an update in a long time, but @pfeodrippe please re-open if there is something here we can fix.