tbreeden Absent Member.
Absent Member.
4513 views

Server Agent Yellow Diamond Status

Just updated both ZCM servers, apparently successfully, from 10.3.1 to 10.3.2 and one of the servers shows a "yellow diamond" next it its Agent Status, and the message:

"The agent service is running, but the request failed for one or more known addresses."

The zcc.log file contains these entries:

24 Jan 2011 16:35:56 DeviceHealthDescri..189 :Running AJAX ping for url:
http://xxxxxx.xxxx.xxxxxx.xxx:7628/RURunning
24 Jan 2011 16:35:56 DeviceHealthDescrip..93 :Unable to ping dns xxxxxx.xxxx.xxxxxx.xxx on port 7628,
message: Connection refused.
24 Jan 2011 16:35:56 DeviceHealthDescri..189 :Running AJAX ping for url:
http://555.555.555.555:7628/RURunning
24 Jan 2011 16:35:56 DeviceHealthDescri..118 :Ping of 555.555.555.555 was successful.

machine with dns name "xxxxxx.xxxx.xxxxxx.xxx" does in fact have a static ip address of
"555.555.555.555"

In fact, if i enter "http://xxxxxx.xxxx.xxxxxx.xxx:7628/RURunning" into the web browser I get a response
"Yes I am running".

This server is SLES 10.3 while the other one is SLES 11.1

Otherwise things seem to be working ok, but I may have a long (15 min) login problem for 10.3.1 ZCM clients.

Thanks,

Tom
Labels (2)
0 Likes
10 Replies
shaunpond Absent Member.
Absent Member.

Re: Server Agent Yellow Diamond Status

Tbreeden,

nslookup only shows one address for that DNS name?

--

Shaun Pond


0 Likes
tbreeden Absent Member.
Absent Member.

Re: Server Agent Yellow Diamond Status

spond;2068107 wrote:

nslookup only shows one address for that DNS name?
Shaun Pond


Yes, shows only one address for it. I can't imagine where another is coming from.

I do notice now that I've installed a couple of workstation clients to 10.3.2, that they will show yellow as well if they have two connections going, eg, both wired and wireless adapters (and both do show up in ZCC). That makes sense.

Tom
0 Likes
shaunpond Absent Member.
Absent Member.

Re: Server Agent Yellow Diamond Status

Tbreeden,

does this fail consistently?

--

Shaun Pond


0 Likes
tbreeden Absent Member.
Absent Member.

Re: Server Agent Yellow Diamond Status

spond;2069596 wrote:
Tbreeden,

does this fail consistently?

Shaun Pond


Yes, every time ZCC opens that server I get the same thing, and zcc.log

contains the "Connection Refused" message for the DNS name, but no error via the ipaddress, eg

28 Jan 2011 08:59:29 DeviceHealthDescri..189 :Running AJAX ping for url: http://prvmac.stud.alaska.edu:7628/RURunning
28 Jan 2011 08:59:29 DeviceHealthDescrip..93 :Unable to ping dns prvmac.stud.alaska.edu on port 7628, message: Connection refused
28 Jan 2011 08:59:29 DeviceHealthDescri..189 :Running AJAX ping for url: http://222.254.108.238:7628/RURunning
28 Jan 2011 08:59:29 DeviceHealthDescri..118 :Ping of 222.254.108.238 was successful.
28 Jan 2011 08:59:33 DeviceDetailsGener..811 :Sending AJAX request to '222.254.108.238' (prvmac.stud.alaska.edu)
28 Jan 2011 08:59:33 DeviceHealthDescri..189 :Running AJAX ping for url: http://prvmac.stud.alaska.edu:7628/RURunning
28 Jan 2011 08:59:33 DeviceHealthDescrip..93 :Unable to ping dns prvmac.stud.alaska.edu on port 7628, message: Connection refused
28 Jan 2011 08:59:33 DeviceHealthDescri..189 :Running AJAX ping for url: http://222.254.108.238:7628/RURunning
28 Jan 2011 08:59:33 DeviceHealthDescri..118 :Ping of 222.254.108.238 was successful.

And every time if I immediately type "http://prvmac.stud.alaska.edu:7628/RURunning" into Firefox, it get the message
"ZENworks Agent is Running" back.

Seems not to be a big problem, but confusing.

Thanks,

Tom
0 Likes
shaunpond Absent Member.
Absent Member.

Re: Server Agent Yellow Diamond Status

Tbreeden,

> 28 Jan 2011 08:59:29 DeviceHealthDescrip..93 :Unable to ping dns
> prvmac.stud.alaska.edu on port 7628, message: Connection refused
>

I would get a packet trace of that happening...

--

Shaun Pond


0 Likes
ryamry Absent Member.
Absent Member.

Re: Server Agent Yellow Diamond Status

Hi Guys-
I just updated a SLES11 server from 10.3.1. to 10.3.2 and I had the exact same thing going on. nslookup resolved fine both ways. I found there were two lines in /etc/hosts that would resolve to the hostname. The first was for 127.0.0.2 and the other was the actual server IP addy. If I pinged the hostname from the servers cli it resolved to the 127.0.0.2 addy. I commented out the 127.0.0.2 entry and restarted the server (maybe not necessary but its off hours). After that it came up green light on the agent status and the msgs in zcc.log show everything is fine as well.

-Rob
0 Likes
shaunpond Absent Member.
Absent Member.

Re: Server Agent Yellow Diamond Status

Ryamry,

interesting...

--

Shaun Pond


0 Likes
tbreeden Absent Member.
Absent Member.

Re: Server Agent Yellow Diamond Status

ryamry;2071080 wrote:
Hi Guys-
I just updated a SLES11 server from 10.3.1. to 10.3.2 and I had the exact same thing going on. nslookup resolved fine both ways. I found there were two lines in /etc/hosts that would resolve to the hostname. The first was for 127.0.0.2 and the other was the actual server IP addy. If I pinged the hostname from the servers cli it resolved to the 127.0.0.2 addy. I commented out the 127.0.0.2 entry and restarted the server (maybe not necessary but its off hours). After that it came up green light on the agent status and the msgs in zcc.log show everything is fine as well.
-Rob


Thanks for the info! I was not looking forward to doing a packet trace 🙂

My SLES 10.3 server's host files also had two addresses as described.
The first was 127.0.0.1 and the second the actual ipaddress.

I tried switching the order of the two address in hosts, restarted Zenworks, and cleared Firefox's cache completely - bingo! - green lite for the server now.

Tom
0 Likes
tbreeden Absent Member.
Absent Member.

Re: Server Agent Yellow Diamond Status

Oddly, the SLES 11.1 server, which is the second primary ZCM server, also has two hosts entries, and the 127.0.0.1 entry is first on that one as well,
but I've always been green on that server.

Tom
0 Likes
gerwil1478
New Member.

Re: Server Agent Yellow Diamond Status

Hi all
Same condition and log entries but remming out the 127.0.0.1 and/or putting my only ZCM server entry first did not work. Server status still with a yellow cross symbol. It was always a bit dogy. Was working around 11.0 but now at 11.1a the issue has come back.
Server agent reports the 11.1 version.

ZCC.LOG snippet below

09 Nov 2011 12:41:51 DeviceHealthDescri..189 :Running AJAX ping for url: [url]http://myserver:7628/RURunning[/url]
09 Nov 2011 12:41:51 DeviceHealthDescrip..83 :Ping of myserver was successful.

09 Nov 2011 12:41:51 DeviceHealthDescri..189 :Running AJAX ping for url: http://IP of DNS server1:7628/RURunning
09 Nov 2011 12:41:56 DeviceHealthDescrip..93 :Unable to ping DNS IP of DNS server1 on port 7628, message: connect timed out

09 Nov 2011 12:41:56 DeviceHealthDescri..189 :Running AJAX ping for url: [url]http://IP of DNS server2:7628/RURunning[/url]
09 Nov 2011 12:42:01 DeviceHealthDescrip..93 :Unable to ping dns IP of DNS server2 on port 7628, message: connect timed out

09 Nov 2011 12:42:01 DeviceHealthDescri..189 :Running AJAX ping for url: [url]http://myserver:7628/RURunning[/url]
09 Nov 2011 12:42:01 DeviceHealthDescri..118 :Ping of my server was successful.

[url]http://myserver[/url] url/IP address:7628/RURunning" gives "ZENworks Agent is Running". but with my DNS servers they timeout. They are not under my control so no ZCM agent loaded. Is this a problem??

Of concern is that these entries are repeated every 5 minutes or so. Also the code 83 but also 118 for successful.


Cheers
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.