Hello,

since the last Update to 7.2.0.346 we get on an unfrequently base the following error Messages for random servers:

02 Apr 2019 01:48:11
Computer: [NOTESSRV01]
Monitor: [Ping NOTESSRV01]
Description: NOTESSRV01 does not respond to ping requests within 300 ms. The hostname NOTESSRV01 could not be resolved to IPv4. Winsock Err = 11001, WSA Err = 0 The specified host is unknown. The host name NOTESSRV01 could not be resolved to IPv6. Winsock Err = 11001, WSA Err = 0 The specified host is unknown. Err=0x00002AF9 (11001), CurrUser=administrator, Imp={none}]
Only entered error state (suppresses warnings for 0m 38s before entering error state)
Sent from PA Server Monitor to MONITOR04

The servers are definitfely reachable from any host in the network. We checked on the PA Monitor server during the error time if we can ping the announced server. All were reachable by Hostname.

Regards Cedric

asked 02 Apr, 08:36

RotzlerIT's gravatar image

RotzlerIT
11
accept rate: 0%


Hi RotzlerIT,

I recommend setting this value in the registry:

HKEY_LOCAL_MACHINEsoftwareWow6432NodePowerAdminServerMonitor

Ping_DoDiagnosticPing = 1

With this set, any time a host fails ping.exe (same one you and I run) will get run to also try to ping the host and it's output will be logged. That will either refute or corroborate what the Ping Monitor is reporting. So far we're seeing the Ping Monitor is correct and detecting some DNS hiccups.

If you see this again please zip up and send the log files so we can review them. To send the files open the Console and go to Settings -> System Settings and click on the FTP logs to Support.

Thanks
Quinn

Please make sure to mark your questions accepted when you have your answer by clicking the gray check mark to the left of the answer.

link

answered 02 Apr, 13:57

Quinn's gravatar image

Quinn ♦♦
14.0k3925
accept rate: 37%

edited 02 Apr, 13:58

Hello Quinn,

i changed the registry entry on the 2nd of April. I also restarted the Server. We received then again a monitoring message on 7th April. Also some more this week and tonight we got also more monitoring messages. I just send the log files via the FTP Button in System Settings. I put this Thread ID in the URL 3188 as request ID.

It started around 1:25 am. Its at line 15835

04-11-2019, 01:25:10.160, TID:03936, PID:01624

Regards Cedric

link

answered 11 Apr, 04:19

RotzlerIT's gravatar image

RotzlerIT
11
accept rate: 0%

edited 11 Apr, 04:31

Hi RotzlerIT,

It looks like this was indeed DNS related.

After you enabled the Ping_DoDiagnosticPing registry value the service would run Window's ping.exe and capture it's output when the Ping Monitor went into error and couldn't get a response. When the Ping Monitor went into alert at 1:25 am the service ran the ping.exe and this is what was returned:

04-11-2019, 01:25:13.207, TID:00304, PID:01624, [TID:03936] Output from ["C:Windowssystem32ping.exe" -n 3 -4 notessrv04]: Ping request could not find host "notessrv04". Check the name and try again.

(The text above was translated from the actual log file language of German to English.)

Between 1:25 and 1:40 am this happened for many different servers (you can search the log for "C:Windowssystem32ping.exe")

Thanks
Quinn

Please make sure to mark your questions accepted when you have your answer by clicking the gray check mark to the left of the answer.

link

answered 11 Apr, 10:10

Quinn's gravatar image

Quinn ♦♦
14.0k3925
accept rate: 37%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×1
×1
×1

Asked: 02 Apr, 08:36

Seen: 36 times

Last updated: 11 Apr, 10:10

Related questions