Problem with l7d process

  • 2
  • Question
  • Updated 4 years ago
  • Answered
After being a long time reader I am finally being forced to join!

I have a problem on 2 of my 150+ AP's. While upgrading the app signature files to 3.1.6 these 2 AP's (330, FW version 6.1r6 ) failed to upgrade, also updating the config with "auto" setting enabled failed.

After a search through this community I found a suggestion that it had something to do with an error occurring after a "show run" command.

Indeed if I do a "show run" I have the following error:

ERROR: failed to send message to l7d (attempt to send 52 bytes, actually sent -1 (err = 111 - Connection refused)

A "show logging buffered" displays:

2014-09-15 15:32:52 info    kernel: [mpi]: socket is closed, pid(65655), protocol(17)
2014-09-15 15:32:52 info    l7d: enter appid init (/f/l7/plugins) on 1224934384
2014-09-15 15:32:52 info    l7d: Bind cli agent to cpu 0
2014-09-15 15:32:52 info    l7d: start cli agent: module(l7d) sub-module(cli)
2014-09-15 15:32:52 info    l7d: Recovery L7D parameters
2014-09-15 15:32:52 info    l7d: entered ah_appid_cfg_init
2014-09-15 15:32:51 info    ah_top: ready restart process:/opt/ah/bin/l7d
2014-09-15 15:32:39 info    kernel: [mpi]: socket is closed, pid(65655), protocol(17)
2014-09-15 15:32:39 info    l7d: enter appid init (/f/l7/plugins) on 1224934384
2014-09-15 15:32:39 info    l7d: Bind cli agent to cpu 0
2014-09-15 15:32:39 info    l7d: start cli agent: module(l7d) sub-module(cli)
2014-09-15 15:32:39 info    l7d: Recovery L7D parameters
2014-09-15 15:32:39 info    l7d: entered ah_appid_cfg_init
2014-09-15 15:32:38 info    ah_top: ready restart process:/opt/ah/bin/l7d
This is just a small piece of it, it's going through the same process over and over again. It think the l7d process is somehow broken since it's not showing the /opt/ah/bin/l7d after a "show system processes state" command.

I changed firmware, reset to default, clear config, pushed reset button, etc ... nothing seems to help. The AP's themself seem to work just fine, except they need a full config pushed every time. So any tips to get this service started or are these AP's really "broken"?

Anyhow thnx for taking the time to read this.
Photo of WilburK

WilburK

  • 7 Posts
  • 1 Reply Like

Posted 4 years ago

  • 2
Photo of Terence Fleming ThinkWireless

Terence Fleming ThinkWireless, Champ

  • 79 Posts
  • 27 Reply Likes

Try this:

SSH to the Ap, at the command prompt issue:

exec avc reset 

I'm not sure what it does, but it worked for me :-)


Photo of J. Goodnough

J. Goodnough, Champ

  • 266 Posts
  • 32 Reply Likes
Looks like it would reset the Application Visibility and Control system, controlled by the layer 7 daemon, which we see as l7d
Photo of Andrew Garcia

Andrew Garcia, Official Rep

  • 368 Posts
  • 120 Reply Likes
J.Good is right, the command is master reset switch for AVC which includes deleting the installed signature file.  The command is handy for just this occasion, which is likely caused by a corrupted signature file.
Photo of WilburK

WilburK

  • 7 Posts
  • 1 Reply Like
Hmm, not sure either but it does the trick!

Looks like it resets the l7d process:

2014-09-16 08:42:36 info    l7d: Opened /f/l7/plugins/apps.txt for reading applications
2014-09-16 08:42:36 info    l7d: enter appid init (/f/l7/plugins) on 1224934384
2014-09-16 08:42:36 info    l7d: Bind cli agent to cpu 0
2014-09-16 08:42:36 info    l7d: start cli agent: module(l7d) sub-module(cli)
2014-09-16 08:42:36 info    l7d: Recovery L7D parameters
2014-09-16 08:42:36 info    l7d: entered ah_appid_cfg_init
2014-09-16 08:42:35 info    ah_top: ready restart process:/opt/ah/bin/l7d
2014-09-16 08:42:26 info    ah_cli: admin:<exec avc reset>

Maybe document this somewhere (it's here now of course ;) ) because I can't imagine we are the only ones to encounter this?

Thank you Terence! :)
(Edited)
Photo of Bill W.

Bill W.

  • 222 Posts
  • 35 Reply Likes
That's good to know.  I've encountered this in the past and just RMA'ed the AP.  I'll have to try this the next time I encounter this problem.
Photo of Steven Bateman

Steven Bateman

  • 65 Posts
  • 12 Reply Likes
Anyone know what the same command would be for the 370/390 platform? 

I have a 390 exhibiting this exact behavior, but "exec avc reset" is not a valid command.