Good morning, good afternoon and good evening. My name is Dustin. I am a Subject Matter Expert
in the systems management space. Today I will be going over log reading in OpenManage Enterprise.
I have already enabled debug logging, and now it's time to export those logs and analyze them.
So first let's talk about the issue that we'll be analyzing. I have an email set up here,
I'm trying to go to gmail.com and i'm trying to go with this username. We'll put a password in
and we're using port 25, and honestly i don't expect this to work because google doesn't allow
this setup, but let's see what it looks like when we have the login going. So what I'm going to do
to make sure that we see that process is I'm going to try to run a report and email it. It doesn't
really matter which one. Okay, so now that's done I will go to 'Monitor', 'Audit Logs' and I will
export my console logs. This will get all the logs bundled into one zip that you can extract and see.
So from here we can already see there's an error trying to email the report but let's go see
exactly what's going on. Right, so within the console logs you'll first have to extract them,
and then you'll have a folder like this and then from here you have a lot of other folders. The
main two that we almost always are looking in are the application log and the task execution log,
so since we just did the issue we can just grab the latest because that's where our logs
are going to be. I personally prefer Notepad++ however you can use any log reader and notepad
that you'd like. Notepad++ just makes it easier for me. So first off we look in here and we see
we have a lot of information, especially with the debug enabled. So I like to do a control
f for whatever it is that I am i'm looking for, in this case we are doing, what, SMTP?
We're trying to discover, trying to troubleshoot around that right? So I'm going to find all in all
open documents which just has my application and task execution service log and then I see all this
right from here. I like to just try to find the very first time it has maybe an error or a warning
so I can try to find where it's all starting. So here's a warning, so let's start there.
So just to see how this is set up, first we have the state of the log, in that case it's a
warn info debug error those are all the options, then we have the time and date that the log was
created, then we have the process so this is the process you want to follow. If you see here we
have a different process. That means that this log right here most likely has nothing to do
with this log right here. They're not the same thread if you will. And then we have
the information about what is going on so from here it's saying it's trying to resolve
the FQDN for smtp.gmail.com. So if we start going through this process we can start seeing that
all right we want to turn that into an IP address, this is what we got back for the IP address,
let's try to create a route for that IP address. We can kind of keep going down the stream of info
to see what's going on and usually you're going to get to your error eventually.
In this case here's our error and it's basically saying it couldn't connect to the host
smtp.gmail.com this IP address on port 25
connection refused. So what this tells me is that google.com, Gmail, is refusing this connection.
We already know why it's refusing it because we know how gmail works, and we're using the wrong
port and and who knows what else, right? But we do know that it's being refused by the end point,
and that's kind of where we would stop in here because if it's being refused then we're done. But
the whole idea is how to read these logs and this is really just how you read them. You're going to
look through for your warns and your errors. Your debug will give you extended info, then you go
through and try to figure out why the failure is happening in the first place. So that's it. I hope
you enjoyed my video on log reading and OpenManage Enterprise. Thank you and have a wonderful day.