For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Brian_Gupta_115's avatar
Brian_Gupta_115
Icon for Nimbostratus rankNimbostratus
Sep 26, 2005

Wierd iRule update issue. May be a bug.

I made changes to an iRule and the changes show up in the GUI and the bigip.conf, but it seems that the system is still using the old rule.

The following TMM errors are being logged to /var/log/ltm

Sep 26 16:33:15 tmm tmm[30000]: 01220001:3: TCL error: Rule peopleapps_parse - can't read "usessl": no such variable while executing "if { $usessl == 0 } { SSL::disable }"

I completely removed the SERVER_RESPONSE and RULE_INIT sections from the rule.

The rule is just this now:


rule peopleapps_parse {
  when HTTP_REQUEST {
    pool people_apps_http
  }
}

Any help would be appreciated.

Thanks,

Brian
application delivery
dev
devops
iRules

5 Replies

  • Colin_Walker_12's avatar
    Colin_Walker_12
    Historic F5 Account
    Sep 26, 2005
    Did you make the changes manually to the config file? Did you run the b load command?

     

     

    -Colin
  • unRuleY_95363's avatar
    unRuleY_95363
    Historic F5 Account
    Sep 26, 2005
    We actually discovered a problem about a month back thanks to hunter32. The problem occurs when you have more than one rule on a virtual and the order of the rules gets changed. This would cause one of the rules to get "lost" on the virtual (CR54042).

     

    To recover you need to either completely remove the virtual or issue a "bigstart restart tmm".
  • Brian_Gupta_115's avatar
    Brian_Gupta_115
    Icon for Nimbostratus rankNimbostratus
    Sep 26, 2005
    One note: I didn't have more than one iRule configured on the VIP. I suspect it might have something to do with the fact that I removed the "when RULE_INIT" block.

     

     

    (It seems that removing a RULE_INIT clause might be tricky, as the TMM will be executing the RULE_INIT block that you are trying to remove)

     

     

    What do you think?

     

     

    -Brian

     

     

    P.S. - The bigstart restarm tmm did the trick.

     

  • unRuleY_95363's avatar
    unRuleY_95363
    Historic F5 Account
    Sep 27, 2005
    I doubt that was the cause. It actually doesn't run the RULE_INIT when you delete it. I'm sure it's the same problem, you've probably just figured out another way to get it to occur...

     

  • unRuleY_95363's avatar
    unRuleY_95363
    Historic F5 Account
    Sep 27, 2005
    Yeah, I wasn't thinking you deleted the whole rule. However, when you deleted the RULE_INIT event, it will get removed from the system before the system determines whether to run a RULE_INIT event. So, even though the RULE_INIT would have otherwise been run, it was removed and so won't run.

     

     

    Did you possibly modify one of the other events at the same time you removed the RULE_INIT? That could be the other trigger that I mentioned.

     

     

    If you do figure out what steps you did to make it happen, just let us know and we'll verify that it's now fixed.