Forum Discussion

Angelo_Turetta1's avatar
Angelo_Turetta1
Icon for Nimbostratus rankNimbostratus
Jul 10, 2015

11.6.0 HF5 Error 010716bc:3: anybody ?

I recently upgraded one of my AWS F5, from 11.6.0.4 to 11.6.0.5

I use some complex iRules to manage my sites, including recently added procs

Now every change I try on the virtual server using the irules, I always get the error:

010716bc:3: HTTP::header command in a proc in rule (/Common/GTM) under HTTP_REQUEST event at virtual server (/Common/STAGE_MYSERVER_80) does not satisfy cmd/event/profile requirement.

I know I've not provided much details, but I don't want a validation of my irule: just want to confirm if a change breaking existing code can be expected in a HotFix? Or there simply was a problem with my upgrade.

Does anybody know if the irule runtime environment has changed in HotFix5 ??? Where can I find info about that error code?

Thank you Angelo.

6 Replies

  • OK, I rolled back (reactivated the HF4 boot location), then removed some unused stuff that generated some errors on my first upgrade, and then rolled forward (reactivated the HF5 boot location reloading the clean configuration)

     

    The error went away, so this one was maybe a bogus update.

     

    Sorry for the noise.

     

    Angelo.

     

  • We need to see more of your problematic iRule in order to investigate. Please provide a full configuration and iRule that exhibits the problem. There was a minor proc validation failure back in 11.4.0 that looked similar, otherwise we don't have any reports of this problem.
  • We are also experiencing this issue running under 11.5.3 - Unfortunately I cannot give the iRules/Procs due to commercial confidentiality. When I try to add a new iRule to the existing iRule set I get the same error - either from the CLI using TMSH or via the GUI.

     

    Interesting thing is if you edit the bigip.conf and add the iRule and then perform a tmsh load sys config it works.

     

    we'll likely need to raise an F5 case for this but wondered if anybody else had encountered this problem and if they ever had a resolution.

     

  • another thing to add is that if we delete the Procs from the F5 and then re-add them the problem goes away and we can add a new iRule to a VS.

     

    Deleting the Procs actually doesn't prevent the VS from working and they continue to process traffic without interruption so there appears to be some kind of disconnect from the F5 knowing that the Procs have gone away

     

    • James_D_Shewey_'s avatar
      James_D_Shewey_
      Icon for Nimbostratus rankNimbostratus
      Looks like this may be https://support.f5.com/kb/en-us/solutions/public/16000/300/sol16386.html. Is everyone else on this thread using management partitions? If so, check to see if there is a bad iRule in another partition.