Bug 449296 - monit can't proper check file /proc/net/dev
Summary: monit can't proper check file /proc/net/dev
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: monit
Version: 9
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Stewart Adam
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-01 21:53 UTC by Peter Bieringer
Modified: 2009-07-14 16:25 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-14 16:25:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Peter Bieringer 2008-06-01 21:53:28 UTC
Description of problem:
Looks like current version of monit can't proper check file /proc/net/dev

Version-Release number of selected component (if applicable):
monit-4.10.1-7.fc9.i386

How reproducible:
Always

Steps to Reproduce:
1. Create a check to monitor the existence of a network interface:

# Check for sixxs interface
check file dev with path /proc/net/dev
	if not match
		"sixxs:"
	then exec "/sbin/service aiccu restart"

2. Restart monit
3. Restart network (service network restart), this usually remove the device
"sixxs" created by aiccu. aiccu is still running, but IPv6 tunnel interface is gone.

Actual results:
monit does not restart aiccu

Expected results:
monit should restart aiccu, if interface "sixxs" is missing

Additional info:
Probably monit checks the file size before checking contents of file, but files
in /proc/net always have the size 0

Comment 1 Stewart Adam 2008-06-03 21:26:39 UTC
I can reproduce this bug, but it doesn't seem to be specific to paths in /proc -
Monit doesn't seem to care about any "if match" commands I specify. Are you
seeing this too?

Comment 2 Peter Bieringer 2008-06-03 21:33:50 UTC
Haven't test whether "if match" works at all...I only create one test according
to the man page. If "if match" does not work at all, summary should be adjusted.

Comment 3 Stewart Adam 2008-06-08 23:05:28 UTC
Could you report a bug upstream and link to this report please?

Comment 4 Bug Zapper 2009-06-10 01:20:33 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 WONTFIX if it remains open with a Fedora 
'version' of '9'.

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 prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2009-07-14 16:25:10 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.

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


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