Bug 1312141 - Feb/17th update of phpMyAdmin has rendered it unusable for UNM users due to debilitating slowness
Summary: Feb/17th update of phpMyAdmin has rendered it unusable for UNM users due to ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: phpMyAdmin
Version: el6
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-25 20:44 UTC by hamjavar
Modified: 2016-03-20 18:50 UTC (History)
2 users (show)

Fixed In Version: phpMyAdmin-4.0.10.15-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-06 22:27:40 UTC
Type: Bug


Attachments (Terms of Use)

Description hamjavar 2016-02-25 20:44:24 UTC
Description of problem:

On Feb/17 

phpMyAdmin-4.0.10.12-1.el6.noarch

was updated to:

phpMyAdmin-4.0.10.14-1.el6.noarch

via:

epel_rhel6_x86_64   EPEL for Red Hat Enterprise Linux 6


users have this experience starting Feb/17th:

user going on to/seeing  phpMyAdmin web page: takes 4 to 7  minutes

user login to phpMyAdmin page: it is instantaneous



on all systems , we use this Apache 
from Red Hat Server Channel: 
httpd-2.2.15-47.el6_7.3.x86_64



Version-Release number of selected component (if applicable):

See Description.


How reproducible:

By going to newer version:

    NORMAL:  phpMyAdmin-4.0.10.12-1.el6.noarch

    UNUSABLE:  phpMyAdmin-4.0.10.14-1.el6.noarch



Steps to Reproduce:
1. see previous section
2.
3.

Actual results:
slowness making phpMyAdmin unusable.


Expected results:
instantaneous appearance of phpMyadmin web page


Additional info:

Comment 1 Robert Scheck 2016-02-25 20:47:49 UTC
I am not able to confirm this here. Any idea how we could track that down?
Guess it's not possible to get access to exactly such an affected system?

Comment 2 hamjavar 2016-02-25 21:37:47 UTC
hello,

i am sure you have seen:

/usr/share/doc/phpMyAdmin-4.0.10.14/ChangeLog

and know what has happened since .12 causing problems for us.


i thought items listed there will be
helpful to you to help us  but i guess not ...


so what type of access do you need?

Comment 3 Robert Scheck 2016-02-25 21:46:23 UTC
I am aware about the changelog, actually just security fixes. Thus I am
not really sure which change should cause such issues.

Comment 4 Fedora Update System 2016-03-03 22:19:35 UTC
phpMyAdmin-4.0.10.15-1.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-331ed35e18

Comment 5 Fedora Update System 2016-03-03 22:47:15 UTC
phpMyAdmin4-4.0.10.15-1.el5 has been submitted as an update to Fedora EPEL 5. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-de8749748f

Comment 6 Fedora Update System 2016-03-05 01:47:40 UTC
phpMyAdmin4-4.0.10.15-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-de8749748f

Comment 7 Fedora Update System 2016-03-05 01:52:18 UTC
phpMyAdmin-4.0.10.15-1.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-331ed35e18

Comment 8 Fedora Update System 2016-03-06 22:27:12 UTC
phpMyAdmin-4.0.10.15-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2016-03-20 18:50:18 UTC
phpMyAdmin4-4.0.10.15-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.