Hi all, I just replaced our 11.2.1 8900 pair with a brand new pair of 11.5.1 7250v I noticed a very repeatable bug on the web interface. I go to "Local traffic/Nodes" and click on the 'Address' column header to change the sort order, from now on the page "Local traffic/Pools" shows only an error "General database error retrieving information." If I restore the sort order of the Nodes list by clicking on the 'Name' column heading, the 'Pools' page resumes working. My system has 104 pools and 168 nodes, and I have set to 300 the list length in preferences. It seems a rather simple bug somewhere in the web interface code. Thanks, Angelo.

Open a support case so the issue is logged in F5's system. I see the same behavior on my 11.5 HF3 box

is there an update? same problem here with 11.5.1 HF4 in our test env

i can only advise everyone to log the ticket with F5 support, as more as it gets reported the better the chance it gets resolved. also please report back with bug ID so others can hint to it.

Hi All Ive also seen this exact behaviour, in 11.5.1. Initial troubleshooting done, nothing shouting out at me in the logs, so I logged a ticket with F5 in line with what was said in this article. However, it seems that if you sort the pools by Name, this seems to solve the issue and the error disappears...Would be interesting to see if this works with others too. I also did ask my customer to restart the tomcat and httpd daemons as well, awaiting results. Looks like a bug in this version to me.

Yes, the bug is revertable together with the sort. My support request is C1649054 One more bit of information: the bug is not present in version 11.6.0

Annoying bug on LTM nodes/pools list (11.5.1 HF4)

37 Replies

Victor_142239
Nimbostratus
Jan 19, 2015
Running 11.5.0.6.0.258-HF6 with this issue.
Jerry_Lees_4280
Historic F5 Account
Jan 21, 2015
Workaround (11.5.1 HF7, and probably others):

bigstart restart httpd tomcat
- Misty_Spillers
  Nimbostratus
  Jan 26, 2015
  Can you fairly safely run this command during production hours? I'm having this problem on 11.5.1 HF7
- Jerry_Lees_4280
  Historic F5 Account
  Jan 26, 2015
  Yes, I believe so. It will cause the configuration manager to restart. So on a high traffic box it may be best to wait. However, it's as safe as most services you could restart.
- Jerry_Lees_4280
  Historic F5 Account
  Jan 26, 2015
  Also, Open a case please as shaggy says below.
flipperfil
Nimbostratus
Jan 22, 2015
I also have the same issue in 11.5.1 Build 7.0.167 Hotfix HF7. Anyone have a bugid or should I open a case?
- shaggy
  Nimbostratus
  Jan 22, 2015
  even if there is a bugid, you should open a case so it gets more attention. more cases = more likely it will get fixed
oscar_s_filipe_
Nimbostratus
Jan 22, 2015
I also have the same issue in 11.5.1 Build 7.0.167 Hotfix HF7. Anyone have a bugid or should I open a case?
- shaggy
  Nimbostratus
  Jan 22, 2015
  even if there is a bugid, you should open a case so it gets more attention. more cases = more likely it will get fixed
iamczar_12961
Cirrus
Feb 17, 2015
This is now tracked under Bug ID481003 - TMUI -- Browsing to "Pool List" menu throws SQL Exception because of invalid column

Tested against versions we had in handy: •11.5.1-final failed (problem repro-ed), •11.5.1-hf5 failed •11.5.1-hf7 failed •11.5.1-hf8 failed •11.6.0-final passed •11.6.0-hf1 passed

Please continue to open a support case so the issue is logged in F5's system. Then F5 Support can then add/link your case to the bug ID.
- ChanKing_199789
  Nimbostratus
  Apr 29, 2015
  Could you do me a favour to provide URL that describe the Bug (ID481003) in detail or paste some core content.Our version is 9.4.7,Pitty that our device is out of service.Thanks a lot!
Bob_Lyons_14865
Nimbostratus
May 07, 2015
Please be aware this is also happening in 11.5.2 Hotfix 1. I have opened a case as well, but re-sorting the Nodes does correct this issue.
- Carlos_Alperin
  Nimbostratus
  Mar 14, 2016
  And also on 11.5.3 HF2
Amit_Karnik
Nimbostratus
Jul 08, 2015
Here is a workaround which does not require a service/process restart.

Browse to LTM->Nodes, and change the sort order to Name (ascending)

Go back to the pool list and it should display as before.
eroach5
Nimbostratus
May 19, 2016
Same issue on 11.5.4 HF 2. As mentioned above, re-sorting the nodes corrects the issue.
eroach5
Nimbostratus
May 19, 2016
Same issue on 11.5.4 HF 2. As mentioned above, re-sorting the nodes corrects the issue.
eroach5
Nimbostratus
May 19, 2016
Same issue on 11.5.4 HF 2. As mentioned above, re-sorting the nodes corrects the issue.