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

shaggy
Nimbostratus
Sep 04, 2014
Open a support case so the issue is logged in F5's system. I see the same behavior on my 11.5 HF3 box
Torti
Altostratus
Sep 16, 2014
is there an update? same problem here with 11.5.1 HF4 in our test env
boneyard
MVP
Sep 16, 2014
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.
Daniel_19491
Nimbostratus
Sep 17, 2014
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.
Angelo_Turetta1
Nimbostratus
Sep 17, 2014
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
- ChanKing_199789
  Nimbostratus
  Apr 29, 2015
  Then,could you provide some content about your SR and support response in detail.The same problem fusses me a lot.Thanks a lot!
Daniel_19491
Nimbostratus
Sep 17, 2014
Grazie Angelo!
JG
Cumulonimbus
Sep 17, 2014
I came across a similar issue in v11.3.0, which was confirmed by F5 Support with a bug ID. I was told it was a cosmetic issue, which it was. The bug was fixed in an HF release later.
Mike_Sullivan_2
Nimbostratus
Oct 27, 2014
Same happening here, 11.5.1 EngHF-3. If I change the sort order of the nodes, you will not be able to list the pools until the node sort order is restored. I'll post a support case too.

Mike
Belanger__Yves
Altostratus
Nov 10, 2014
I have the same issue with 11.5.1 HF5, but if I clear the cache and I restart my web browser, everything comes back to normal.

Yves
Nick_T_68319
Nimbostratus
Jan 12, 2015
I have the same with with 11.5.1 HF6