Forum Discussion

Brian_O_Kelley_'s avatar
Brian_O_Kelley_
Icon for Nimbostratus rankNimbostratus
Jan 07, 2008

Can't delete monitors added via API with is_read_only flag

I created a few monitors using the API, and for some reason perl translated is_read_only => "false" to a boolean with value "true". I now have these monitors lying around in the UI, and I can't delete them using the API or the UI. Thoughts?

 

 

Thanks,

 

Brian

5 Replies

  • Colin_Walker_12's avatar
    Colin_Walker_12
    Historic F5 Account
    When you try to delete these via the API, what error are you receiving? Is the UI outputting any info?

     

     

    Thanks,

     

    Colin
  • I hadn't seen that one before. I just tried it and am in the same boat as you are. Once I find out where the root monitors are stored in the system, I'll find you a way to manually delete it.

     

     

    -Joe
  • Very lame solution but it works (at least for me...)

     

     

    1. starting with your template "badtemplate"

     

    2. Log into the GUI and create another template "badtemplate1" of the same type as "badtemplate"

     

    3. Save

     

    4. Open a console shell and edit the /config/bigip.conf

     

    5. rename the "monitor badtemplate1 {" line to "monitor badtemplate {"

     

    6. Save and exit the editor.

     

    7. issue a "b load".

     

     

    Then login to the GUI and you'll be able to delete monitor template "badtemplate"

     

     

    -Joe
  • Hello from 2014, 6 years later... was this ever fixed? I'm experiencing the same thing and would like not to have to hack on bigip.conf to resolve...

     

    thanks!