- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- Re: v5.7.0.3-11516 - several alarming log entries
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2012 05:24 AM - edited 10-19-2012 05:48 AM
10-19-2012 05:24 AM - edited 10-19-2012 05:48 AM
Hi all,
Just to let you know.
Submitted a case concerning the following.
Running the latest firmware the following log entries (subset) appear:
- Process snmpd has exceeded its data memory limit of 3600K bytes, while incr 3620K bytes
- Process statspoller has exceeded its data memory limit of 20000K bytes, while incr 20012K bytes- kernel:
xxx INFO: RCU detected CPU 0 stall (t=2500 jiffies)
kernel: xxx INFO: RCU detected CPU stalls: 0 (detected by 1, t=2503 jiffies)
kernel: xxx INFO: RCU detected CPU 0 stall (t=10000 jiffies)
kernel: xxx INFO: RCU detected CPU stalls: 0 (detected by 1, t=10005 jiffies)
- kernel: xxx -E- sflow_driver: ProcessUserSpaceMessages: Invalid Update Message from User Space!
error code 0
kernel: xxx sflow_driver: warning update message request interface 32109, however
MAX_KERNEL_SAMPLERS = 26
- dhcpd: client x:x:x:x has duplicate leases on x.x.x.x
- eapolserver: xxx Interface r1v2 doesn't exist
2012-10-18 10:38:18 Local0.Error x.x.x.x eapolserver: AP xxx Interface r1v3 doesn't exist
2012-10-18 10:38:24 Local0.Error x.x.x.x eapolserver: AP xxx Interface r1v3 doesn't exist
- Connection limit reached: src=x.x.x.x mac=x:x:x:x proto=6 dport=80 connections=204
limit=200 auth=0 in=0
PCM+
Informational 18-10-2012 5:41 No Device Access Control Default Agent Association Failure. Status of device with MAC 20:c9:d0:32:66:87 having SSID xxx-Guest is: Association failed, maximum number of associated stations exceeded
Informational 18-10-2012 5:41 No Device Access Control Default Agent Association Failure. Status of device with MAC 20:c9:d0:32:66:87 having SSID xxx-Guest is: Received association request, but not authenticated
Major 18-10-2012 0:04 No Device General Default Agent ColdStart - Device has crashed or power plug is removed or SNMP entity is re-initializing itself.
Informational 17-10-2012 19:01 No PCM General Default Agent Communication has been recovered with device MSM430 (xxx), down time was between (Wed Oct 17 18:31:16 CEST 2012) and (Wed Oct 17 19:01:23 CEST 2012).
Syslog severity trap for msg #1052059 severity 4: daemon - dhcpd: ICMP Echo Reply for x.x.x.x arrived late or is spurious.
Major 17-10-2012 15:13 No PCM Network Activity Default Agent Critical threshold violation on xxx - Wireless port 2:wifi1, Utilization Tx(egress) 100 >= 90
Major 17-10-2012 15:13 No PCM Network Activity Default Agent Critical threshold violation on xxx - Wireless port 2:wifi1, Frames/Sec Tx(egress) 41.297.480 >= 401.785,7
Major 17-10-2012 15:13 No PCM Network Activity Default Agent Critical threshold violation on xxx - Wireless port 2:wifi1, Multicasts/Sec Tx(egress) 20.648.730 >= 401.785,7
Major 17-10-2012 15:13 No PCM Network Activity Default Agent Critical threshold violation on xxx - Wireless port 2:wifi1, Errors/Sec Tx(egress) 20.648.808 >= 270
Major 17-10-2012 15:13 No PCM Network Activity Default Agent Critical threshold violation on xxx - Wireless port 1:wifi0, Utilization Rx(ingress) 100 >= 90
Major 17-10-2012 15:13 No PCM Network Activity Default Agent Critical threshold violation on xxx - Wireless port 1:wifi0, Frames/Sec Rx(ingress) 40.904.364 >= 401.785,7
Major 17-10-2012 15:13 No PCM Network Activity Default Agent Critical threshold violation on xxx - Wireless port 1:wifi0, Multicasts/Sec Rx(ingress) 20.452.162 >= 401.785,7
Major 17-10-2012 15:13 No PCM Network Activity Default Agent Critical threshold violation on xxx - Wireless port 1:wifi0, Utilization Tx(egress) 100 >= 90
Major 17-10-2012 15:13 No PCM Network Activity Default Agent Critical threshold violation on xxx - Wireless port 1:wifi0, Frames/Sec Tx(egress) 40.904.296 >= 401.785,7
Major 17-10-2012 15:13 No PCM Network Activity Default Agent Critical threshold violation on xxx Wireless port 1:wifi0, Multicasts/Sec Tx(egress) 20.452.170 >= 401.785,7
=======
Controller: MSM765zl. Software version: 5.7.0.3-11516 Hardware revision: 2:47 .
Access-points: 43 E-MSM-430, Configuration: default except channel manual, Tx beamforming, Multicast Tx rate, remote dhcp
VSC 1: configuration default except Wireles protection WPA (AES/CCMP), Key source dynamic, 802.1x authentication remote W2K3 IAS server, Bandsteering, no Broadcast SSID, DHCP from WLC (clients in same subnet as guest clients brrrr)
VSC 2: configuration default except Wireles protection WPA (AES/CCMP), Preshared key, Bandsteering.
Both VSCs: Allowed wireless rates, 802.11b 11, 802.11g from 9, 802.11b+g from 9, 802.11a from 9, 802.11n from 9
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2012 11:29 AM
10-23-2012 11:29 AM
Re: v5.7.0.3-11516 - several alarming log entries
1.) there are problems other than these log messages
and
2.) if you've opened a case with HP support.
Please advise.
--glen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2012 12:48 PM
10-28-2012 12:48 PM
Re: v5.7.0.3-11516 - several alarming log entries
Hi Glen,
I did open a case with HP support. No response yet. Had to deliver some extra info.
I didn't get complaints yet from any users with this version. But that is no suprise.
The wireless network has not really been tested yet. Partly because there have been so many problems with the last two versions that were in use and users are relunctant to have another try. On a daily bases I have about 110 users of which a 100 are users with mobile phones that use the wireless netwerk sporadically. More users than the 110 mentioned will be using wireless when it would be stable. And byod is also mentioned to be implemented on short term ....
I 'm busy with management to have a real multi user test.
To prevent another failure, I want to know the consequencies of any log message and have them fixed, if possible, before the trial.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2012 07:37 AM
11-02-2012 07:37 AM
Re: v5.7.0.3-11516 - several alarming log entries
The case manager reported back by mail that the second level of HP Support has refused the case.
The reason was that they found that these messages were configuration questions and should be handled by a consultant.
Replied I do not agree.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2012 06:24 AM
11-13-2012 06:24 AM
SolutionUpgraded to v5.7.1 otherwise HP would not deliver further support.
Most of the messages have disappeared (hope this is good:) )
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2013 01:00 PM
02-07-2013 01:00 PM
Re: v5.7.0.3-11516 - several alarming log entries
Any update on the error message:
Query error on PublicAccessUser status table
I too get tons of these and while they do not appeat to be breaking anything I would rather they not be there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2013 05:03 AM
02-12-2013 05:03 AM
Re: v5.7.0.3-11516 - several alarming log entries
Hi BriComp
PublicAccessUser error is basically a cosmetic one. In the device log it can be a nuisance just because it fills the logs, so you might want to set up an external syslog server and mirror the device log there.
HTH,
Arimo
HPE Networking Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2013 09:13 AM
04-16-2013 09:13 AM
Re: v5.7.0.3-11516 - several alarming log entries
Hi Everyone,
Who can help me with this message:
Resumiendo el Evento: 192.168.X.X : Critical threshold violation on
192.168.X.X (192.168.X.X): AP_X - Wireless port 1:wifi0, Errors/Sec
Tx(egress) 71,570,352 >= 270 "
I need to know what you're describing it.
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-23-2013 09:08 AM - edited 04-23-2013 09:09 AM
04-23-2013 09:08 AM - edited 04-23-2013 09:09 AM
Re: v5.7.0.3-11516 - several alarming log entries
I was also having issues with these "Query error on PublicAccessUser status table" messages after upgrading to 5.7.2.0-SR1-MSM765-B12859 (given to me by HP support to sort out a different issue!!!)
I managed to stop them appearing by disabling Access Control (Under "Public Access" uncheck box and save)
Once I had disabled it I got a different error continuously!!! I then re-enabled and saved and, touch wood, have not had any error messages since!!!!
Hope this helps someone!!!
Tim