I'm a little surprised that we don't see any indices created for your logging project yet. But the last two lines in your ES logs indicate that some of your operations logs were written and should be available to query.
If you can't see the .operations.* index in your list of Kibana indices, make sure the user you are using to connect to Kibana is an OpenShift cluster-admin. You can also adjust the time range of your Kibana matches in the upper right hand corner of Kibana. It defaults to the last 15 minutes. On Mon, Feb 8, 2016 at 2:32 PM, Bob Kozdemba <[email protected]> wrote: > On Mon, Feb 8, 2016 at 9:13 AM, Eric Wolinetz <[email protected]> wrote: > >> On Sat, Feb 6, 2016 at 2:49 PM, Bob Kozdemba <[email protected]> wrote: >> >>> On Sat, Feb 6, 2016 at 10:32 AM, Akram Ben Aissi < >>> [email protected]> wrote: >>> >>>> Hi guys, >>>> >>>> I am running a containarized install of OpenShift, and after the >>>> successful installation of the log centralization with EFK using docs, I >>>> can get any log search results from Kibana: Every result is empty. >>>> >>> >>> I'm having a similar problem with an rpm-based install. The kibana web >>> page reports "no results found :)". I have the es, fluentd and kibana pods >>> running. Aside from initial log entries, all 3 logs don't report any >>> activity as projects and apps are created. Any trouble shooting hints would >>> be great. >>> >> >> What initial log entries are you referring to; could you paste them here? >> Do you see any *.log.pos files created at /var/log/ ? >> >> Are you using the OPS cluster deployment? If so, which Kibana and ES are >> you looking at? >> > > Hi Eric: > I posted the logs at: http://pastebin.test.redhat.com/347076 and > http://pastebin.test.redhat.com/347077 > > # oc get pods > NAME READY STATUS RESTARTS AGE > logging-es-4bxv8k6k-1-cd1d1 1/1 Running 1 1d > logging-fluentd-1-cv2qf 1/1 Running 1 1d > logging-kibana-1-fcm8a 2/2 Running 2 2d > # > > Thanks, > Koz > > >> >>> Koz >>> >>> >>>> I guess that logging may rely on nodes journalctl output, which is not >>>> populated apparently in case of container install. >>>> >>>> Do you have any tips to make it work: a different configuration for the >>>> logging template? or a way to redirect the openshift container journalctl >>>> to the node journalctl? >>>> >>>> Greetings >>>> Akram >>>> >>>> >>>> _______________________________________________ >>>> dev mailing list >>>> [email protected] >>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Bob Kozdemba >>> Domain Architect >>> Openshift/Atomic Enterprise Platform >>> 512-944-8092 >>> >>> _______________________________________________ >>> dev mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>> >>> >> > > > -- > Bob Kozdemba > Domain Architect > Openshift/Atomic Enterprise Platform > 512-944-8092 >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
