Network Management

Reply
Contributor II

Airwave Restarting service Client Monitor Worker messages

Hello

 

Just had a minor blip with Airwave in that it stopped showing connected clients for a short period. After a minor panic and logging into each local controller I can see we had no break in service.

 

Around the same time we got this message:

 

Mon Jul 10 10:20:08 2017 System System Restarting service Client Monitor Worker

 

Looking through the event log I can see that we get a lot of these messages, sometimes one after another. Any ideas why these crop up please?

 

Thanks


Alexander. 

University Information Services
University of Cambridge
Contributor I

Re: Airwave Restarting service Client Monitor Worker messages

Same here. We're getting them every 15 seconds. Screen Shot 2017-08-30 at 11.06.36 AM.png

Occasional Contributor I

Re: Airwave Restarting service Client Monitor Worker messages

I'm seeing these regularly, with intervals varying between a few seconds and about 15 minutes. I can't see any other events or actions that might be related to it. I've seen this both in my clean 8.2.4 installation and my previous 8.2.3. The latter has been updated several times over the years but I couldn't say which version it started on.

 

My devices:

- 238 switches (Cisco 3560, Aruba S1500 and Aruba 2930F)

- 715 access points (AP-105, AP-115, AP-134, AP-135, AP-205, AP-225 and RAP3)

- Aruba 7220 running ArubaOS 8.1.0.1.

 

I got the Client Monitor Worker messages while I was running ArubaOS 6.x and minimal SNMP traps on the 7220 as well. As I'm unsure when the problem started, I can't say whether adding new types of switches and access points might have triggered it.

 

As far as i know it doesn't cause any trouble, but it's filling up my event log. And I'm not too comfortable with ignoring seemingly inconsequential errors.

Occasional Contributor I

Re: Airwave Restarting service Client Monitor Worker messages

I am having this problem as well and have a case open with Aruba TAC. We will be working on this more tomorrow and I will post any progress we make. Anyone else find a solution to this? I am not sure if it is related but my client counts are fluctuating every 5 minutes by 500-1000 clients and that is not normal behavior.

 

Tue Oct 10 20:28:32 2017 System System Restarting service Client Monitor Worker
Tue Oct 10 20:28:15 2017 System System Restarting service Client Monitor Worker
Tue Oct 10 20:28:00 2017 System System Restarting service Client Monitor Worker
Tue Oct 10 20:27:32 2017 System System Restarting service Client Monitor Worker
Tue Oct 10 20:27:15 2017 System System Restarting service Client Monitor Worker
Tue Oct 10 20:26:15 2017 System System Restarting service Client Monitor Worker
Tue Oct 10 20:26:00 2017 System System Restarting service Client Monitor Worker
Tue Oct 10 20:25:45 2017 System System Restarting service Client Monitor Worker
Tue Oct 10 20:25:16 2017 System System Restarting service Client Monitor Worker 

Capture.PNG

 

 

Contributor II

Re: Airwave Restarting service Client Monitor Worker messages

I'd be really interested to hear about what you find as, as mentioned, we are getting bucket loads of these messages. 

 

The other reason it is not great is that it means that it is obscuring the genuine messages that I'm checking the audit log for.

University Information Services
University of Cambridge
Highlighted
Moderator

Re: Airwave Restarting service Client Monitor Worker messages

The restart messages show up in the service_watcher log.  There's probably more info about the specific process if you look in the async_logger_client log (should be an option on the System -> Status page).


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
Occasional Contributor I

Re: Airwave Restarting service Client Monitor Worker messages

The async_logger_client log certainly helps in troubleshooting this. Thanks! I'm attaching a snippet of mine with MAC addresses semi-anonymized.

 

The messages about uninitialized value in DiscoveredViaProxy.pm always come in groups of four, with two errors in line 61 followed by two errors in line 80. There seems to always be 572 lines, or 143 groups, before they stop for a few minutes. Although the recurring number of lines seemed promising I cant' make 572 or 143 fit with AP model or anything else in my system.

 

After the first pause the <$__ANONIO__> line reference is appended, and the line number updates after each pause. When the service restarts the ANOINO reference is gone again. I haven't been able to find anything relating to this in any other logs.

Moderator

Re: Airwave Restarting service Client Monitor Worker messages

The uninit values are negligible since it's coming from device discovery.  The more concerning lines are the ones w/ 'illegal attempt to update' since the timings identical.

 

I would probably follow a path thinking that it may be a performance issue on the system.  What's the system specs, and then number of devices monitored/managed?  Also, this is probably the right point to engage with TAC so that they can investigate further, add additional debug logging, and fine tune performance or file defect as needed.


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
Occasional Contributor I

Re: Airwave Restarting service Client Monitor Worker messages

I am not sure what to make of that log at all on my system.. Attached..

Occasional Contributor I

Re: Airwave Restarting service Client Monitor Worker messages

I have about 1750 access points and have it installed on a pretty beefy server..

 

CPU
Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz Hyper-Threaded 8 Cores 20480 KB cache (2600.224 MHz actual)
Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz Hyper-Threaded 8 Cores 20480 KB cache (2600.224 MHz actual)

Memory
Installed Physical RAM: 62.80 GB
Configured Swap Space: 4.00 GB

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: