This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Wireless accesspoints rebooting

Hi,

In our office we use the ASG220 hardware appliance (software version v8.200) with wireless subscription.
We're facing a problem where the 5 accesspoints (AP30) wil reboot about twice per day, disconnecting all clients for 20 to 30 seconds. This has lead to many complaints at our helpdesk, since most users have no other way of connecting, and lose connectivity.

To fix this I've done the following:
- I've upgraded the firmware to v8.200, which promised major wireless improvements.

-As a workaround for the rebooting AP's, I have set all updates to manual, but in the logs I see the Asatro still mentioning new firmware, and issuing reboot commands, see below:


2011:08:02-09:45:11 192.168.125.20 sysinit: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1alrm_handler(): timeout

2011:08:02-09:45:11 192.168.125.20 init: starting pid 25287, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-09:45:11 192.168.125.20 sysinit: interface not found.

2011:08:02-09:45:14 192.168.125.19 sysinit: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=1alrm_handler(): timeout

2011:08:02-09:45:14 192.168.125.19 init: starting pid 24002, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-09:45:14 192.168.125.17 sysinit: CTRL-EVENT-EAP-STARTED 00:24[:D]7:93:6c:a0alrm_handler(): timeout

2011:08:02-09:45:14 192.168.125.17 init: starting pid 24095, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-09:45:14 192.168.125.19 sysinit: interface not found.

2011:08:02-09:45:14 192.168.125.17 sysinit: interface not found.

2011:08:02-09:45:16 firewall awed[25537]: Awed version 1.4.2.57.2.19 starting

2011:08:02-09:45:16 firewall awed[25537]: access point firmware available: AP10:1034 AP30:1034

Is there a way of preventing these reboots during daytime?

thanks,
Michiel Beumer

This thread was automatically locked due to age.

Parents

0 Scott_Klassen over 13 years ago

If there's firmware available to the AP's, then no, they are going to suck it in and reboot.

Are the AP's applying the firmware, rebooting, then applying the same firmware and rebooting again?

Is the twice/day AP reboots only when there is firmware waiting to be installed, or is this all the time?

__________________
ACE v8/SCA v9.3

...still have a v5 install disk in a box somewhere.

http://xkcd.com
http://www.tedgoff.com/mb
http://www.projectcartoon.com/cartoon/1
Cancel
Vote Up 0 Vote Down

Cancel

0 Michiel Beumer over 13 years ago in reply to Scott_Klassen

Hi Scott,

I've taken a more detailed look on the wireless logs, and it seems that some of the AP's (Not all!) indeed try to reapply firmware version 1034.

Below's a stripped version of today's log, both events are visible:


2011:08:02-09:45:11 192.168.125.20 init: starting pid 25287, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-09:45:14 192.168.125.19 init: starting pid 24002, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-09:45:14 192.168.125.17 init: starting pid 24095, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-09:45:16 firewall awed[25537]: Awed version 1.4.2.57.2.19 starting

2011:08:02-09:45:16 firewall awed[25537]: access point firmware available: AP10:1034 AP30:1034

2011:08:02-09:45:16 192.168.125.15 init: starting pid 23784, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-09:45:17 firewall awed[25537]: AP 'A40001D6F26F8AC': configuration change detected

2011:08:02-09:45:17 firewall awed[25537]: AP 'A40001B9CD2D6A1': configuration change detected

2011:08:02-09:45:17 firewall awed[25537]: AP 'A40001EB7A40B66': configuration change detected

2011:08:02-09:45:17 firewall awed[25537]: AP 'A400016152701E1': configuration change detected

2011:08:02-09:45:17 firewall awed[25537]: AP 'A400017199A3EEF': configuration change detected

2011:08:02-09:45:37 firewall awed[25537]: new connection from 192.168.125.19:39246

2011:08:02-09:45:37 firewall awed[25537]: new connection from 192.168.125.17:51204

2011:08:02-09:45:37 firewall awed[25537]: AP 'A400017199A3EEF': configuration change detected

2011:08:02-09:45:37 firewall awed[25537]: new connection from 192.168.125.26:33978

2011:08:02-09:45:37 firewall awed[25537]: AP 'A40001B9CD2D6A1': configuration change detected

2011:08:02-09:45:37 firewall awed[25537]: AP 'A400016152701E1': configuration change detected

2011:08:02-09:45:38 firewall awed[25537]: new connection from 192.168.125.20:56531

2011:08:02-09:45:38 firewall awed[25537]: AP 'A40001EB7A40B66': configuration change detected

2011:08:02-09:45:40 firewall awed[25537]: new connection from 192.168.125.15:60850

2011:08:02-09:45:40 firewall awed[25537]: AP 'A40001D6F26F8AC': configuration change detected





2011:08:02-14:42:14 firewall awed[23693]: Awed version 1.4.2.57.2.19 starting

2011:08:02-14:42:14 firewall awed[23693]: access point firmware available: AP10:1034 AP30:1034

2011:08:02-14:42:15 firewall awed[23693]: AP 'A40001D6F26F8AC': configuration change detected

2011:08:02-14:42:15 firewall awed[23693]: AP 'A40001B9CD2D6A1': configuration change detected

2011:08:02-14:42:15 firewall awed[23693]: AP 'A40001EB7A40B66': configuration change detected

2011:08:02-14:42:15 firewall awed[23693]: AP 'A400016152701E1': configuration change detected

2011:08:02-14:42:15 firewall awed[23693]: AP 'A400017199A3EEF': configuration change detected

2011:08:02-14:42:19 192.168.125.26 init: starting pid 27046, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-14:42:19 192.168.125.19 init: starting pid 25860, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-14:42:21 192.168.125.17 init: starting pid 26170, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-14:42:25 192.168.125.15 init: starting pid 30696, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-14:42:42 firewall awed[23693]: new connection from 192.168.125.20:56531

2011:08:02-14:42:42 firewall awed[23693]: new connection from 192.168.125.26:33978

2011:08:02-14:42:43 firewall awed[23693]: new connection from 192.168.125.19:39246

2011:08:02-14:42:44 firewall awed[23693]: new connection from 192.168.125.17:51204

2011:08:02-14:42:49 firewall awed[23693]: new connection from 192.168.125.15:60850

About your second question: Is there a certain message in the log-files I can look up to confirm/disconfim your question?

Reply

0 Michiel Beumer over 13 years ago in reply to Scott_Klassen


2011:08:02-09:45:11 192.168.125.20 init: starting pid 25287, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-09:45:14 192.168.125.19 init: starting pid 24002, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-09:45:14 192.168.125.17 init: starting pid 24095, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-09:45:16 firewall awed[25537]: Awed version 1.4.2.57.2.19 starting

2011:08:02-09:45:16 firewall awed[25537]: access point firmware available: AP10:1034 AP30:1034

2011:08:02-09:45:16 192.168.125.15 init: starting pid 23784, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-09:45:17 firewall awed[25537]: AP 'A40001D6F26F8AC': configuration change detected

2011:08:02-09:45:17 firewall awed[25537]: AP 'A40001B9CD2D6A1': configuration change detected

2011:08:02-09:45:17 firewall awed[25537]: AP 'A40001EB7A40B66': configuration change detected

2011:08:02-09:45:17 firewall awed[25537]: AP 'A400016152701E1': configuration change detected

2011:08:02-09:45:17 firewall awed[25537]: AP 'A400017199A3EEF': configuration change detected

2011:08:02-09:45:37 firewall awed[25537]: new connection from 192.168.125.19:39246

2011:08:02-09:45:37 firewall awed[25537]: new connection from 192.168.125.17:51204

2011:08:02-09:45:37 firewall awed[25537]: AP 'A400017199A3EEF': configuration change detected

2011:08:02-09:45:37 firewall awed[25537]: new connection from 192.168.125.26:33978

2011:08:02-09:45:37 firewall awed[25537]: AP 'A40001B9CD2D6A1': configuration change detected

2011:08:02-09:45:37 firewall awed[25537]: AP 'A400016152701E1': configuration change detected

2011:08:02-09:45:38 firewall awed[25537]: new connection from 192.168.125.20:56531

2011:08:02-09:45:38 firewall awed[25537]: AP 'A40001EB7A40B66': configuration change detected

2011:08:02-09:45:40 firewall awed[25537]: new connection from 192.168.125.15:60850

2011:08:02-09:45:40 firewall awed[25537]: AP 'A40001D6F26F8AC': configuration change detected





2011:08:02-14:42:14 firewall awed[23693]: Awed version 1.4.2.57.2.19 starting

2011:08:02-14:42:14 firewall awed[23693]: access point firmware available: AP10:1034 AP30:1034

2011:08:02-14:42:15 firewall awed[23693]: AP 'A40001D6F26F8AC': configuration change detected

2011:08:02-14:42:15 firewall awed[23693]: AP 'A40001B9CD2D6A1': configuration change detected

2011:08:02-14:42:15 firewall awed[23693]: AP 'A40001EB7A40B66': configuration change detected

2011:08:02-14:42:15 firewall awed[23693]: AP 'A400016152701E1': configuration change detected

2011:08:02-14:42:15 firewall awed[23693]: AP 'A400017199A3EEF': configuration change detected

2011:08:02-14:42:19 192.168.125.26 init: starting pid 27046, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-14:42:19 192.168.125.19 init: starting pid 25860, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-14:42:21 192.168.125.17 init: starting pid 26170, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-14:42:25 192.168.125.15 init: starting pid 30696, tty '': '/etc/init.d/rcS K shutdown'

2011:08:02-14:42:42 firewall awed[23693]: new connection from 192.168.125.20:56531

2011:08:02-14:42:42 firewall awed[23693]: new connection from 192.168.125.26:33978

2011:08:02-14:42:43 firewall awed[23693]: new connection from 192.168.125.19:39246

2011:08:02-14:42:44 firewall awed[23693]: new connection from 192.168.125.17:51204

2011:08:02-14:42:49 firewall awed[23693]: new connection from 192.168.125.15:60850

About your second question: Is there a certain message in the log-files I can look up to confirm/disconfim your question?

Children

0 hschaa over 13 years ago in reply to Michiel Beumer
Below's a stripped version of today's log, both events are visible:

2011:08:02-14:42:14 firewall awed[23693]: Awed version 1.4.2.57.2.19 starting

This might be a known issue with awed (the managment daemon on the ASG). Could you please check if you find messages like the following one in /var/log/selfmon.log?

2011:07:26-09:30:09 asg selfmonng[5019]: W actionCmd(+): '/var/mdw/scripts/awed restart'

Helmut
Cancel
Vote Up 0 Vote Down

Cancel

0 Michiel Beumer over 13 years ago in reply to hschaa

Hi Helmut,

I've checked yesterday's selfmon logs, and it has the errors you described, as you can see below:


2011:08:02-05:00:46 firewall selfmonng[5654]: I check Failed increment pluto_running counter 1 - 15
2011:08:02-05:00:46 firewall selfmonng[5654]: I check Failed increment starter_running counter 1 - 3
2011:08:02-05:00:46 firewall selfmonng[5654]: I check Failed increment l2tpd_running counter 1 - 3
2011:08:02-09:45:05 firewall selfmonng[5654]: I check Failed increment awed_running counter 1 - 3
2011:08:02-09:45:10 firewall selfmonng[5654]: I check Failed increment awed_running counter 2 - 3
2011:08:02-09:45:15 firewall selfmonng[5654]: W check Failed increment awed_running counter 3 - 3
2011:08:02-09:45:15 firewall selfmonng[5654]: W triggerAction: 'cmd'
2011:08:02-09:45:15 firewall selfmonng[5654]: W actionCmd(+):  '/var/mdw/scripts/awed restart'
2011:08:02-09:45:15 firewall selfmonng[5654]: W child returned status: exit='0' signal='0'
2011:08:02-14:42:03 firewall selfmonng[5654]: I check Failed increment awed_running counter 1 - 3
2011:08:02-14:42:08 firewall selfmonng[5654]: I check Failed increment awed_running counter 2 - 3
2011:08:02-14:42:13 firewall selfmonng[5654]: W check Failed increment awed_running counter 3 - 3
2011:08:02-14:42:13 firewall selfmonng[5654]: W triggerAction: 'cmd'
2011:08:02-14:42:13 firewall selfmonng[5654]: W actionCmd(+):  '/var/mdw/scripts/awed restart'
2011:08:02-14:42:14 firewall selfmonng[5654]: W child returned status: exit='0' signal='0'

As Scott suggested, I'll try to reset all accesspoints today, hopefully this fixes the firmware updating issue.

Is there something else I should try with awed? The restart messages occurred at the same time the network went down yesterday.

0 hschaa over 13 years ago in reply to Michiel Beumer

I've checked yesterday's selfmon logs, and it has the errors you described, as you can see below:

Ok, a fix for this is on its way into 8.201.

As Scott suggested, I'll try to reset all accesspoints today, hopefully this fixes the firmware updating issue.

I haven't seen any firmware updates in your log snippets, so I don't think this is an issue. The major problem you're seeing is that awed dies and therefore all APs lose their ASG connection and as a result trigger a reboot.

Helmut
Cancel
Vote Up 0 Vote Down

Cancel
0 beth over 13 years ago in reply to hschaa

i ve the same problem (Astaro V8.2 Vmware and two ap 10 )
any idea?

2011:08:09-11:31:57 192.168.32.68 init: starting pid 1181, tty '': '/etc/init.d/rcS K shutdown'
2011:08:09-11:31:57 192.168.32.68 sysinit: interface not found.
2011:08:09-11:32:23 astarolan awed[13784]: ll_read: short read or connection error: Connection reset by peer
2011:08:09-11:32:23 astarolan awed[13784]: error handling client 192.168.32.68, cutting connection.
2011:08:09-11:32:23 astarolan awed[13784]: >=========================================================================
2011:08:09-11:32:23 astarolan awed[13784]: low-level recv error: sysread failed
2011:08:09-11:32:23 astarolan awed[13784]:
2011:08:09-11:32:23 astarolan awed[13784]: 1. Internal::AP:[:P]rocess_request:736() awed.pl
2011:08:09-11:32:23 astarolan awed[13784]: 2. main::top-level:215() awed.pl
2011:08:09-11:32:23 astarolan awed[13784]: set antenna | all |
2011:08:09-11:27:40 192.168.32.68 sysinit: Set a bitmap of allowed antennas to use for TX and RX.
2011:08:09-11:27:40 192.168.32.68 sysinit: The driver may reject antenna configurations it cannot support.
2011:08:09-11:27:40 192.168.32.68 sysinit: Options:
2011:08:09-11:27:40 192.168.32.68 sysinit: --debug enable netlink debugging
2011:08:09-11:32:42 astarolan awed[13784]: send msg: ip:'192.168.32.68', id:'A40000A9FC9C896', type:'3', length:'48'
2011:08:09-11:32:57 192.168.32.68 sysinit: read_awed(): reading message header failed, errno 131
2011:08:09-11:32:57 192.168.32.68 init: starting pid 1181, tty '': '/etc/init.d/rcS K shutdown'
2011:08:09-11:32:57 192.168.32.68 sysinit: interface not found.
Cancel
Vote Up 0 Vote Down

Cancel
0 beth over 13 years ago in reply to hschaa

i ve the same problem (Astaro V8.2 Vmware and two ap 10 )
any idea?

2011:08:09-11:31:57 192.168.32.68 init: starting pid 1181, tty '': '/etc/init.d/rcS K shutdown'
2011:08:09-11:31:57 192.168.32.68 sysinit: interface not found.
2011:08:09-11:32:23 astarolan awed[13784]: ll_read: short read or connection error: Connection reset by peer
2011:08:09-11:32:23 astarolan awed[13784]: error handling client 192.168.32.68, cutting connection.
2011:08:09-11:32:23 astarolan awed[13784]: >=========================================================================
2011:08:09-11:32:23 astarolan awed[13784]: low-level recv error: sysread failed
2011:08:09-11:32:23 astarolan awed[13784]:
2011:08:09-11:32:23 astarolan awed[13784]: 1. Internal::AP:[:P]rocess_request:736() awed.pl
2011:08:09-11:32:23 astarolan awed[13784]: 2. main::top-level:215() awed.pl
2011:08:09-11:32:23 astarolan awed[13784]: set antenna | all |
2011:08:09-11:27:40 192.168.32.68 sysinit: Set a bitmap of allowed antennas to use for TX and RX.
2011:08:09-11:27:40 192.168.32.68 sysinit: The driver may reject antenna configurations it cannot support.
2011:08:09-11:27:40 192.168.32.68 sysinit: Options:
2011:08:09-11:27:40 192.168.32.68 sysinit: --debug enable netlink debugging
2011:08:09-11:32:42 astarolan awed[13784]: send msg: ip:'192.168.32.68', id:'A40000A9FC9C896', type:'3', length:'48'
2011:08:09-11:32:57 192.168.32.68 sysinit: read_awed(): reading message header failed, errno 131
2011:08:09-11:32:57 192.168.32.68 init: starting pid 1181, tty '': '/etc/init.d/rcS K shutdown'
2011:08:09-11:32:57 192.168.32.68 sysinit: interface not found.
Cancel
Vote Up 0 Vote Down

Cancel