1556979 - Supermicro IPMI not accessible after a few weeks usage

Status: RESOLVED DUPLICATE of bug 1551177

(Core :: Performance, defect)

Description

[hjmallon]

Attachment: Firefox 2019-06-04 12.53 profile.json.gz

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:67.0) Gecko/20100101 Firefox/67.0

Steps to reproduce:

• Use Firefox to access Supermicro https IPMI (e.g. https://IP-ADDRESS).
• It asks to trust the certificate
• Allow the certificate and login, everything is normal
• Repeat this for multiple machines over multiple weeks

Actual results:

• After a few weeks of using these machines I will try to access one and some requests will take > 60seconds, meaning that the login page is accessible but the main page seems never to fully load.

Expected results:

• It should continue to work at the speed of the first time (or the speed of Safari on the same PC).

A new Firefox profile fixes the issue. Deleting the profile's certificate store also fixes it. It is as if the certificate store gets too big or maybe has more than one cert for an ip address (the IPMIs are on DHCP so may move around)?

I captured a trace using the performance profile tool which I have attached. I originally reported this through web-compat here https://github.com/webcompat/web-bugs/issues/32325

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:Jamie, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 2

[hjmallon]

I have changed the topic to performance, though that doesn't really cover it. It was set to 'disability access APIs' which is certainly not right.

Comment 3

[Georg Müller]

I have the same issue with our supermircro servers here

Comment 4

[James Teh [:Jamie]]

Not an a11y bug as per comment 2.

Comment 5

[Vicky Chin [:vchin]]

Sounds like could be related to certificate checks?

Comment 6

[Dana Keeler (she/her) (use needinfo) [:keeler]]

What's the performance like if you use Firefox 69? This may have been fixed by bug 1551177.

Comment 7

[hjmallon]

I will not be able to test this now as I am away from that equipment. Maybe Georg can confirm fixed?

Comment 8

[Georg Müller]

I downloaded the latest beta (69.0b14).

Since the beta generates a new profile, I rsync'ed the whole default profile into the new default-beta profile directory to keep the certificate cache.

Opening the IPMI interface worked as expected in fractions of a second, so I would say the issue is fixed.

Comment 9

[Dana Keeler (she/her) (use needinfo) [:keeler]]

Great - thanks!