1. Intermittent - Server not found in Kerberos database

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

2. RE: Intermittent - Server not found in Kerberos database

Hate to ask, but *does* the PTR record for the server exist in DNS? Your post doesn't say, nor do you give the version of Zenoss in use. There were a fair number of bugs in earlier versions, a lot of which have been dealt with in version 6.2.x+

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

3. RE: Intermittent - Server not found in Kerberos database

I have worked through this one as well. I found the below configuration property in the guide and just upped it to 2 from the default of 1.

zWinRMKRBErrorThreshold

Having a poor network connection can cause erroneous kerberos error events to be sent which could cause confusion or false alarms. The default value is 1, which will always send an event on the first occurrence of an error. You can increase this value to send an event only when there have been x amount of occurrences of an error during collection, where x denotes the threshold number.

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

4. RE: Intermittent - Server not found in Kerberos database

I thought zWinRMKRBErrorThreshold might be involved as well. I've bumped that all the way to 10 on a few of the affected machines and haven't seen it make a difference. I tried increasing the zWinRMConnectTimeout too, but that didn't work either.

I have worked through this one as well. I found the below configuration property in the guide and just upped it to 2 from the default of 1.

zWinRMKRBErrorThreshold

Having a poor network connection can cause erroneous kerberos error events to be sent which could cause confusion or false alarms. The default value is 1, which will always send an event on the first occurrence of an error. You can increase this value to send an event only when there have been x amount of occurrences of an error during collection, where x denotes the threshold number.

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

5. RE: Intermittent - Server not found in Kerberos database

We are running the latest version of Core (6.2.1 r218) and I did update the Microsoft.Windows ZenPack to the latest (2.9.2).

I've also tried every combination of zWinRMKrb5DisableRDNS (at the /Server/Microsoft level), manually defining the zWinRMServerName (both FQDN, none, and ${here/titleOrId}), and checking/adding SPNs.

I'd expect that if something was configured incorrectly that it would either work all of the time or none of the time. I don't understand why it's sporadic. Some servers model cleanly every time. Others are very intermittent.

Hate to ask, but *does* the PTR record for the server exist in DNS? Your post doesn't say, nor do you give the version of Zenoss in use. There were a fair number of bugs in earlier versions, a lot of which have been dealt with in version 6.2.x+

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

Hate to ask, but *does* the PTR record for the server exist in DNS? Your post doesn't say, nor do you give the version of Zenoss in use. There were a fair number of bugs in earlier versions, a lot of which have been dealt with in version 6.2.x+

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

7. RE: Intermittent - Server not found in Kerberos database

Another question; do you see any messages in the Event console saying something like "Missing counters in collection for xxx"? If so, that may be why you're missing data. I've found that if Zenoss trips over a failed collection, rather than handling it and carrying on, it throws an exception and halts collection completely and silently.....for a few hours. Then it does the periodic remodel of the servers and graphing and event log collection begins again.

Are any messages like that seen? As well, has the krb5-workstation packages been installed on the host? While it shouldn't be needed for proper operation as that should be handled by the docker images.....I find that it's required for consistent operation for Windows monitoring.

One other note...restarting the Zenoss server seems to clear a lot of these. Once the server restarts, it typically models most of the servers successfully for a short time.Original Message:Sent: 11-08-2018 03:38 PMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

Hate to ask, but *does* the PTR record for the server exist in DNS? Your post doesn't say, nor do you give the version of Zenoss in use. There were a fair number of bugs in earlier versions, a lot of which have been dealt with in version 6.2.x+

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

8. RE: Intermittent - Server not found in Kerberos database

Nothing in the event console for missing counters. Typically I'll see the "server not found in Kerberos..." error along with a handful of actual events and sometimes the EventLog failed collection.

I didn't have krb5-workstation loaded. I've just added that. I'll see if it helps.It's also confusing to me that some servers never have the issue. A few of my Windows servers have perfect monitoring and never miss a model.

Another question; do you see any messages in the Event console saying something like "Missing counters in collection for xxx"? If so, that may be why you're missing data. I've found that if Zenoss trips over a failed collection, rather than handling it and carrying on, it throws an exception and halts collection completely and silently.....for a few hours. Then it does the periodic remodel of the servers and graphing and event log collection begins again.

Are any messages like that seen? As well, has the krb5-workstation packages been installed on the host? While it shouldn't be needed for proper operation as that should be handled by the docker images.....I find that it's required for consistent operation for Windows monitoring.

One other note...restarting the Zenoss server seems to clear a lot of these. Once the server restarts, it typically models most of the servers successfully for a short time.Original Message:Sent: 11-08-2018 03:38 PMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

Hate to ask, but *does* the PTR record for the server exist in DNS? Your post doesn't say, nor do you give the version of Zenoss in use. There were a fair number of bugs in earlier versions, a lot of which have been dealt with in version 6.2.x+

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

9. RE: Intermittent - Server not found in Kerberos database

Once installed, you'll need to restart the Zenoss application for any Kerberos changes to take effect. If that doesn't help, can you post the Configuration Properties Windows section (with any IPs, hostnames and user IDs changed to similar but invalid values)?

Nothing in the event console for missing counters. Typically I'll see the "server not found in Kerberos..." error along with a handful of actual events and sometimes the EventLog failed collection.

I didn't have krb5-workstation loaded. I've just added that. I'll see if it helps.It's also confusing to me that some servers never have the issue. A few of my Windows servers have perfect monitoring and never miss a model.

Another question; do you see any messages in the Event console saying something like "Missing counters in collection for xxx"? If so, that may be why you're missing data. I've found that if Zenoss trips over a failed collection, rather than handling it and carrying on, it throws an exception and halts collection completely and silently.....for a few hours. Then it does the periodic remodel of the servers and graphing and event log collection begins again.

Are any messages like that seen? As well, has the krb5-workstation packages been installed on the host? While it shouldn't be needed for proper operation as that should be handled by the docker images.....I find that it's required for consistent operation for Windows monitoring.

One other note...restarting the Zenoss server seems to clear a lot of these. Once the server restarts, it typically models most of the servers successfully for a short time.Original Message:Sent: 11-08-2018 03:38 PMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

Hate to ask, but *does* the PTR record for the server exist in DNS? Your post doesn't say, nor do you give the version of Zenoss in use. There were a fair number of bugs in earlier versions, a lot of which have been dealt with in version 6.2.x+

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

Once installed, you'll need to restart the Zenoss application for any Kerberos changes to take effect. If that doesn't help, can you post the Configuration Properties Windows section (with any IPs, hostnames and user IDs changed to similar but invalid values)?

Nothing in the event console for missing counters. Typically I'll see the "server not found in Kerberos..." error along with a handful of actual events and sometimes the EventLog failed collection.

I didn't have krb5-workstation loaded. I've just added that. I'll see if it helps.It's also confusing to me that some servers never have the issue. A few of my Windows servers have perfect monitoring and never miss a model.

Another question; do you see any messages in the Event console saying something like "Missing counters in collection for xxx"? If so, that may be why you're missing data. I've found that if Zenoss trips over a failed collection, rather than handling it and carrying on, it throws an exception and halts collection completely and silently.....for a few hours. Then it does the periodic remodel of the servers and graphing and event log collection begins again.

Are any messages like that seen? As well, has the krb5-workstation packages been installed on the host? While it shouldn't be needed for proper operation as that should be handled by the docker images.....I find that it's required for consistent operation for Windows monitoring.

One other note...restarting the Zenoss server seems to clear a lot of these. Once the server restarts, it typically models most of the servers successfully for a short time.Original Message:Sent: 11-08-2018 03:38 PMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

Hate to ask, but *does* the PTR record for the server exist in DNS? Your post doesn't say, nor do you give the version of Zenoss in use. There were a fair number of bugs in earlier versions, a lot of which have been dealt with in version 6.2.x+

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

11. RE: Intermittent - Server not found in Kerberos database

Try undefining zWinRMKrb5DisableRDNS, zWinRMServerName (which I think is what's causing the issue; that should be defined with a string at the server level, not a variable at the container level), zWinTrustedKDC, and zWinTrustedRealm. Restart Zenoss within Control Centre, then give it an hour and see how it behaves?

If you want leave the variables set as they are, though, try undefining only zWinRMServerName at the /Server/Microsoft level, then going to one of the servers causing grief and setting that variable with the server's fully-qualified domain name in the Configuration properties of that server, and see what happens after an hour or so?

Once installed, you'll need to restart the Zenoss application for any Kerberos changes to take effect. If that doesn't help, can you post the Configuration Properties Windows section (with any IPs, hostnames and user IDs changed to similar but invalid values)?

Nothing in the event console for missing counters. Typically I'll see the "server not found in Kerberos..." error along with a handful of actual events and sometimes the EventLog failed collection.

I didn't have krb5-workstation loaded. I've just added that. I'll see if it helps.It's also confusing to me that some servers never have the issue. A few of my Windows servers have perfect monitoring and never miss a model.

Another question; do you see any messages in the Event console saying something like "Missing counters in collection for xxx"? If so, that may be why you're missing data. I've found that if Zenoss trips over a failed collection, rather than handling it and carrying on, it throws an exception and halts collection completely and silently.....for a few hours. Then it does the periodic remodel of the servers and graphing and event log collection begins again.

Are any messages like that seen? As well, has the krb5-workstation packages been installed on the host? While it shouldn't be needed for proper operation as that should be handled by the docker images.....I find that it's required for consistent operation for Windows monitoring.

One other note...restarting the Zenoss server seems to clear a lot of these. Once the server restarts, it typically models most of the servers successfully for a short time.Original Message:Sent: 11-08-2018 03:38 PMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

Hate to ask, but *does* the PTR record for the server exist in DNS? Your post doesn't say, nor do you give the version of Zenoss in use. There were a fair number of bugs in earlier versions, a lot of which have been dealt with in version 6.2.x+

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

Try undefining zWinRMKrb5DisableRDNS, zWinRMServerName (which I think is what's causing the issue; that should be defined with a string at the server level, not a variable at the container level), zWinTrustedKDC, and zWinTrustedRealm. Restart Zenoss within Control Centre, then give it an hour and see how it behaves?

If you want leave the variables set as they are, though, try undefining only zWinRMServerName at the /Server/Microsoft level, then going to one of the servers causing grief and setting that variable with the server's fully-qualified domain name in the Configuration properties of that server, and see what happens after an hour or so?

Once installed, you'll need to restart the Zenoss application for any Kerberos changes to take effect. If that doesn't help, can you post the Configuration Properties Windows section (with any IPs, hostnames and user IDs changed to similar but invalid values)?

Nothing in the event console for missing counters. Typically I'll see the "server not found in Kerberos..." error along with a handful of actual events and sometimes the EventLog failed collection.

I didn't have krb5-workstation loaded. I've just added that. I'll see if it helps.It's also confusing to me that some servers never have the issue. A few of my Windows servers have perfect monitoring and never miss a model.

Another question; do you see any messages in the Event console saying something like "Missing counters in collection for xxx"? If so, that may be why you're missing data. I've found that if Zenoss trips over a failed collection, rather than handling it and carrying on, it throws an exception and halts collection completely and silently.....for a few hours. Then it does the periodic remodel of the servers and graphing and event log collection begins again.

Are any messages like that seen? As well, has the krb5-workstation packages been installed on the host? While it shouldn't be needed for proper operation as that should be handled by the docker images.....I find that it's required for consistent operation for Windows monitoring.

One other note...restarting the Zenoss server seems to clear a lot of these. Once the server restarts, it typically models most of the servers successfully for a short time.Original Message:Sent: 11-08-2018 03:38 PMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

Hate to ask, but *does* the PTR record for the server exist in DNS? Your post doesn't say, nor do you give the version of Zenoss in use. There were a fair number of bugs in earlier versions, a lot of which have been dealt with in version 6.2.x+

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

13. RE: Intermittent - Server not found in Kerberos database

I'm sure you've checked already, but are there duplicate IP entries for any of the servers in DNS, either in the forward *or* the reverse lookup zones for the domain? I *have* seen this error before when there were duplicate hostnames for a specific IP address....where in AD DNS scavenging is off, and stale records get left behind when new ones are created. Even when in the forward zone. Not generally a problem for server records, but sometimes...

I did notice that on most of them when I blanked the zWinTrustedKDC and zWinTrustedRealm values, and immediately ran a model, it would go through...but within 30 minutes or so, the error returned.

Any other ideas?

Very confusing as to why some Win servers on the same network would model without issue nearly 100% of the time with the same config settings.Original Message:Sent: 11-14-2018 12:26 PMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

Try undefining zWinRMKrb5DisableRDNS, zWinRMServerName (which I think is what's causing the issue; that should be defined with a string at the server level, not a variable at the container level), zWinTrustedKDC, and zWinTrustedRealm. Restart Zenoss within Control Centre, then give it an hour and see how it behaves?

If you want leave the variables set as they are, though, try undefining only zWinRMServerName at the /Server/Microsoft level, then going to one of the servers causing grief and setting that variable with the server's fully-qualified domain name in the Configuration properties of that server, and see what happens after an hour or so?

Once installed, you'll need to restart the Zenoss application for any Kerberos changes to take effect. If that doesn't help, can you post the Configuration Properties Windows section (with any IPs, hostnames and user IDs changed to similar but invalid values)?

Nothing in the event console for missing counters. Typically I'll see the "server not found in Kerberos..." error along with a handful of actual events and sometimes the EventLog failed collection.

I didn't have krb5-workstation loaded. I've just added that. I'll see if it helps.It's also confusing to me that some servers never have the issue. A few of my Windows servers have perfect monitoring and never miss a model.

Another question; do you see any messages in the Event console saying something like "Missing counters in collection for xxx"? If so, that may be why you're missing data. I've found that if Zenoss trips over a failed collection, rather than handling it and carrying on, it throws an exception and halts collection completely and silently.....for a few hours. Then it does the periodic remodel of the servers and graphing and event log collection begins again.

Are any messages like that seen? As well, has the krb5-workstation packages been installed on the host? While it shouldn't be needed for proper operation as that should be handled by the docker images.....I find that it's required for consistent operation for Windows monitoring.

One other note...restarting the Zenoss server seems to clear a lot of these. Once the server restarts, it typically models most of the servers successfully for a short time.Original Message:Sent: 11-08-2018 03:38 PMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

Hate to ask, but *does* the PTR record for the server exist in DNS? Your post doesn't say, nor do you give the version of Zenoss in use. There were a fair number of bugs in earlier versions, a lot of which have been dealt with in version 6.2.x+

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

14. RE: Intermittent - Server not found in Kerberos database

We do have some servers with IPv6 and IPv4 addresses listed. But that's true for some of the servers that are working as well. One of the servers that will consistently not model only has a single IP listed in forward and reverse zones.

Could it be a resource issue? I've noticed that some services will report an 'answering' status after the Zenoss server has been online for 7 or so days. When I restart the host, it seems like all modeling goes through without issue for a bit.

It's looking more an more like we're going to just stick with the old working 3.2 Zenoss install we have.

I'm sure you've checked already, but are there duplicate IP entries for any of the servers in DNS, either in the forward *or* the reverse lookup zones for the domain? I *have* seen this error before when there were duplicate hostnames for a specific IP address....where in AD DNS scavenging is off, and stale records get left behind when new ones are created. Even when in the forward zone. Not generally a problem for server records, but sometimes...

I did notice that on most of them when I blanked the zWinTrustedKDC and zWinTrustedRealm values, and immediately ran a model, it would go through...but within 30 minutes or so, the error returned.

Any other ideas?

Very confusing as to why some Win servers on the same network would model without issue nearly 100% of the time with the same config settings.Original Message:Sent: 11-14-2018 12:26 PMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

Try undefining zWinRMKrb5DisableRDNS, zWinRMServerName (which I think is what's causing the issue; that should be defined with a string at the server level, not a variable at the container level), zWinTrustedKDC, and zWinTrustedRealm. Restart Zenoss within Control Centre, then give it an hour and see how it behaves?

If you want leave the variables set as they are, though, try undefining only zWinRMServerName at the /Server/Microsoft level, then going to one of the servers causing grief and setting that variable with the server's fully-qualified domain name in the Configuration properties of that server, and see what happens after an hour or so?

Once installed, you'll need to restart the Zenoss application for any Kerberos changes to take effect. If that doesn't help, can you post the Configuration Properties Windows section (with any IPs, hostnames and user IDs changed to similar but invalid values)?

Nothing in the event console for missing counters. Typically I'll see the "server not found in Kerberos..." error along with a handful of actual events and sometimes the EventLog failed collection.

I didn't have krb5-workstation loaded. I've just added that. I'll see if it helps.It's also confusing to me that some servers never have the issue. A few of my Windows servers have perfect monitoring and never miss a model.

Another question; do you see any messages in the Event console saying something like "Missing counters in collection for xxx"? If so, that may be why you're missing data. I've found that if Zenoss trips over a failed collection, rather than handling it and carrying on, it throws an exception and halts collection completely and silently.....for a few hours. Then it does the periodic remodel of the servers and graphing and event log collection begins again.

Are any messages like that seen? As well, has the krb5-workstation packages been installed on the host? While it shouldn't be needed for proper operation as that should be handled by the docker images.....I find that it's required for consistent operation for Windows monitoring.

One other note...restarting the Zenoss server seems to clear a lot of these. Once the server restarts, it typically models most of the servers successfully for a short time.Original Message:Sent: 11-08-2018 03:38 PMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

Hate to ask, but *does* the PTR record for the server exist in DNS? Your post doesn't say, nor do you give the version of Zenoss in use. There were a fair number of bugs in earlier versions, a lot of which have been dealt with in version 6.2.x+

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.

15. RE: Intermittent - Server not found in Kerberos database

I was thinking more multiple IPv4 addresses, rather than both v4 and v6, but that doesn't seem to be the case. Hmm....this is a good one. How does your WinRM configuration look? Are you applying it via Group Policy and if so, have you restricted the IP range that can communicate with the Windows servers and if so, can you try unrestricting the range? Use the * wildcard to allow all, just as a test?

We do have some servers with IPv6 and IPv4 addresses listed. But that's true for some of the servers that are working as well. One of the servers that will consistently not model only has a single IP listed in forward and reverse zones.

Could it be a resource issue? I've noticed that some services will report an 'answering' status after the Zenoss server has been online for 7 or so days. When I restart the host, it seems like all modeling goes through without issue for a bit.

It's looking more an more like we're going to just stick with the old working 3.2 Zenoss install we have.Original Message:Sent: 11-19-2018 09:15 AMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

I'm sure you've checked already, but are there duplicate IP entries for any of the servers in DNS, either in the forward *or* the reverse lookup zones for the domain? I *have* seen this error before when there were duplicate hostnames for a specific IP address....where in AD DNS scavenging is off, and stale records get left behind when new ones are created. Even when in the forward zone. Not generally a problem for server records, but sometimes...

I did notice that on most of them when I blanked the zWinTrustedKDC and zWinTrustedRealm values, and immediately ran a model, it would go through...but within 30 minutes or so, the error returned.

Any other ideas?

Very confusing as to why some Win servers on the same network would model without issue nearly 100% of the time with the same config settings.Original Message:Sent: 11-14-2018 12:26 PMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

Try undefining zWinRMKrb5DisableRDNS, zWinRMServerName (which I think is what's causing the issue; that should be defined with a string at the server level, not a variable at the container level), zWinTrustedKDC, and zWinTrustedRealm. Restart Zenoss within Control Centre, then give it an hour and see how it behaves?

If you want leave the variables set as they are, though, try undefining only zWinRMServerName at the /Server/Microsoft level, then going to one of the servers causing grief and setting that variable with the server's fully-qualified domain name in the Configuration properties of that server, and see what happens after an hour or so?

Once installed, you'll need to restart the Zenoss application for any Kerberos changes to take effect. If that doesn't help, can you post the Configuration Properties Windows section (with any IPs, hostnames and user IDs changed to similar but invalid values)?

Nothing in the event console for missing counters. Typically I'll see the "server not found in Kerberos..." error along with a handful of actual events and sometimes the EventLog failed collection.

I didn't have krb5-workstation loaded. I've just added that. I'll see if it helps.It's also confusing to me that some servers never have the issue. A few of my Windows servers have perfect monitoring and never miss a model.

Another question; do you see any messages in the Event console saying something like "Missing counters in collection for xxx"? If so, that may be why you're missing data. I've found that if Zenoss trips over a failed collection, rather than handling it and carrying on, it throws an exception and halts collection completely and silently.....for a few hours. Then it does the periodic remodel of the servers and graphing and event log collection begins again.

Are any messages like that seen? As well, has the krb5-workstation packages been installed on the host? While it shouldn't be needed for proper operation as that should be handled by the docker images.....I find that it's required for consistent operation for Windows monitoring.

One other note...restarting the Zenoss server seems to clear a lot of these. Once the server restarts, it typically models most of the servers successfully for a short time.Original Message:Sent: 11-08-2018 03:38 PMFrom: Jason OlsonSubject: Intermittent - Server not found in Kerberos database

Hate to ask, but *does* the PTR record for the server exist in DNS? Your post doesn't say, nor do you give the version of Zenoss in use. There were a fair number of bugs in earlier versions, a lot of which have been dealt with in version 6.2.x+

Server not found in Kerberos database: Attempted to get ticket for HTTP@SERVERNAME. Ensure reverse DNS is correct.

We're monitoring 17 Windows Servers right now and seeing this error intermittently. I've stepped through all of the troubleshooting docs and posts I could find, but nothing seems to work. That same server will show that error, but periodically through the day info and events will come up. So I know it's working, it's just not consistent. At any give time I'll see the same error on 3-4 servers, but the others are all reporting fine.

Also seeing random occurences of Windows Event Log collection failing. That also is working, because we see events for the server, but a lot of this error as well.

WindowsEventLog: failed collection SERVERNAME

We are running the latest version of Zenoss Core on a dedicated machine that meets the hardware reqs.Any ideas on what we can do to troubleshoot? If it was consistently not working, I'd imagine the config wasn't sound...but the fact that everything works (some of the time) seems to indicate some other type of issue.