Bug 1233262 - SNMP process check of Apache HTTPD fails if mod_perl is activated
Summary: SNMP process check of Apache HTTPD fails if mod_perl is activated
Keywords:
Status: CLOSED DUPLICATE of bug 782369
Alias: None
Product: Fedora
Classification: Fedora
Component: mod_perl
Version: 26
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-18 14:52 UTC by Panos Kavalagios
Modified: 2017-07-26 11:25 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-07-26 11:25:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Panos Kavalagios 2015-06-18 14:52:01 UTC
Description of problem: The SNMP process check for httpd processes report an error "No httpd process running"


Version-Release number of selected component (if applicable): mod_perl-2.0.8-10.20140624svn1602105.fc22.x86_64


How reproducible: Enable mod_perl in your Apache configuration.


Steps to Reproduce:
1. Set httpd in the /etc/snmp/snmpd.conf as process that needs to be checked (e.g. add a line "proc httpd 30 1")
2. Enable mod perl in the apache configuration. Ensure that the file /etc/httpd/conf.modules.d/02-perl.conf is present.
3. Restart apache by issuing: systemctl restart httpd
4. SNMP walk through MIB .1.3.6.1.4.1.2021.2 with the command: snmpwalk -v 1 localhost -c public .1.3.6.1.4.1.2021.2


Actual results: The httpd reports:
UCD-SNMP-MIB::prNames.1 = STRING: httpd
UCD-SNMP-MIB::prMin.1 = INTEGER: 1
UCD-SNMP-MIB::prMax.1 = INTEGER: 30
UCD-SNMP-MIB::prCount.1 = INTEGER: 0
UCD-SNMP-MIB::prErrorFlag.1 = INTEGER: error(1)
UCD-SNMP-MIB::prErrMessage.1 = STRING: No httpd process running


Expected results: The httpd process should have reported:
UCD-SNMP-MIB::prIndex.1 = INTEGER: 1
UCD-SNMP-MIB::prNames.1 = STRING: httpd
UCD-SNMP-MIB::prMin.1 = INTEGER: 1
UCD-SNMP-MIB::prMax.1 = INTEGER: 30
UCD-SNMP-MIB::prCount.1 = INTEGER: 6
UCD-SNMP-MIB::prErrorFlag.1 = INTEGER: noError(0)
UCD-SNMP-MIB::prErrMessage.1 = STRING: 

as there currently 6 processes running:
# ps -ef | grep -i httpd
root     26767     1  0 17:38 ?        00:00:00 /usr/sbin/httpd -DFOREGROUND
apache   26768 26767  0 17:38 ?        00:00:00 /usr/sbin/httpd -DFOREGROUND
apache   26769 26767  0 17:38 ?        00:00:00 /usr/sbin/httpd -DFOREGROUND
apache   26770 26767  0 17:38 ?        00:00:00 /usr/sbin/httpd -DFOREGROUND
apache   26771 26767  0 17:38 ?        00:00:00 /usr/sbin/httpd -DFOREGROUND
apache   26772 26767  0 17:38 ?        00:00:00 /usr/sbin/httpd -DFOREGROUND


Additional info: It seems that the issue described and solved in Bug 782369 re-occurred as:
# grep Name: /proc/{26767,26768,26769,26770,26771,26772}/status
/proc/26767/status:Name:        /usr/sbin/httpd
/proc/26768/status:Name:        /usr/sbin/httpd
/proc/26769/status:Name:        /usr/sbin/httpd
/proc/26770/status:Name:        /usr/sbin/httpd
/proc/26771/status:Name:        /usr/sbin/httpd
/proc/26772/status:Name:        /usr/sbin/httpd

Comment 1 Fedora End Of Life 2016-07-19 14:54:24 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 2 Panos Kavalagios 2016-07-20 10:45:40 UTC
The issue still occurs on Fedora 24.

Comment 3 Fedora Admin XMLRPC Client 2016-11-01 14:38:11 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora End Of Life 2017-07-25 18:57:59 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Petr Pisar 2017-07-26 10:16:17 UTC
The fix developed in bug #782369 was removed from mod_perl-2.0.7-12.20130221svn1448242.fc18 probably by an accident.

Comment 6 Panos Kavalagios 2017-07-26 11:02:50 UTC
That's good to know. It also affects F26. Can the fix be re-integrated to mod_perl?

Comment 7 Petr Pisar 2017-07-26 11:25:19 UTC
I hope it can. I will merge this bug report to the original as it is the same issue.

*** This bug has been marked as a duplicate of bug 782369 ***


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