Ticket #5455 (closed Bugs: fixed)

Opened 1 year ago

Last modified 1 year ago

Conflicting entries in incrond

Reported by: mrgoblin Assigned to: mbrevda
Priority: minor Milestone: Undetermined
Component: System Admin Version: 2.9-branch
Keywords: incrond Cc:
Confirmation: Unreviewed Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description

Running the Distro 2.9.0.7, Asterisk Ver. 1.8.6.0, Patch Level 1.87.29.55-2

I'm seeing an error in /var/log/messages 

 Nov 26 16:42:10 ippbx incrond[854]: cannot create watch for user root: (16) Device or resource busy
 Nov 26 16:42:10 ippbx incrond[854]: cannot create watch for user root: (16) Device or resource busy

Which I would assume is coming from these entries. 

/var/spool/asterisk/sysadmin/intrusion_detection_stop IN_CLOSE_WRITE /etc/init.d/fail2ban stop
/var/spool/asterisk/sysadmin/intrusion_detection_start IN_CLOSE_WRITE /etc/init.d/fail2ban restart
/var/spool/asterisk/sysadmin/intrusion_detection_stop IN_CLOSE_WRITE /etc/init.d/fail2ban stop
/var/spool/asterisk/sysadmin/intrusion_detection_start IN_CLOSE_WRITE /usr/sbin/sysadmin_intrusion_detection_restart

According to the incrond documentation you cannot have more than one entry monitoring the same file/directory.

Full list from "incrontab -e" is as follows 

/var/spool/asterisk/sysadmin/network IN_CLOSE_WRITE /usr/sbin/sysadmin_network -a
/var/spool/asterisk/sysadmin/dns IN_CLOSE_WRITE /usr/sbin/sysadmin_dns
/var/spool/asterisk/sysadmin/reboot IN_CLOSE_WRITE /sbin/reboot
/var/spool/asterisk/sysadmin/poweroff IN_CLOSE_WRITE /sbin/poweroff
/var/spool/asterisk/sysadmin/tz IN_CLOSE_WRITE /usr/sbin/sysadmin_time_zone
/var/spool/asterisk/sysadmin/vpnstop IN_CLOSE_WRITE /etc/init.d/openvpn stop
/var/spool/asterisk/sysadmin/vpnstart IN_CLOSE_WRITE /usr/sbin/sysadmin_openvpn
/var/spool/asterisk/sysadmin/vpnget IN_CLOSE_WRITE /usr/sbin/sysadmin_openvpn -d
/var/spool/asterisk/sysadmin/phone_configs IN_CLOSE_WRITE /usr/sbin/sysadmin_phone_config
/var/spool/asterisk/sysadmin/intrusion_detection_stop IN_CLOSE_WRITE /etc/init.d/fail2ban stop
/var/spool/asterisk/sysadmin/intrusion_detection_start IN_CLOSE_WRITE /etc/init.d/fail2ban restart
/var/spool/asterisk/sysadmin/mdadm IN_CLOSE_WRITE /usr/sbin/sysadmin_mdadm
/var/spool/asterisk/sysadmin/intrusion_detection_stop IN_CLOSE_WRITE /etc/init.d/fail2ban stop
/var/spool/asterisk/sysadmin/intrusion_detection_start IN_CLOSE_WRITE /usr/sbin/sysadmin_intrusion_detection_restart
/var/spool/asterisk/sysadmin/intrusion_detection_banned IN_CLOSE_WRITE /usr/sbin/sysadmin_intrusion_detection_banned
/var/spool/asterisk/sysadmin/intrusion_detection IN_CLOSE_WRITE /usr/sbin/sysadmin_intrusion_detection
/var/spool/asterisk/sysadmin/email_setup IN_CLOSE_WRITE /usr/sbin/sysadmin_email_setup
/var/spool/asterisk/sysadmin/update_system IN_CLOSE_WRITE /usr/sbin/sysadmin_update_system -a
/var/spool/asterisk/sysadmin/ftp_setup IN_CLOSE_WRITE /usr/sbin/sysadmin_ftp
/var/spool/asterisk/sysadmin/ups_setup IN_CLOSE_WRITE /usr/sbin/sysadmin_ups
/var/spool/asterisk/sysadmin/update_system_cron IN_CLOSE_WRITE /usr/sbin/sysadmin_update_set_cron
/var/spool/asterisk/sysadmin/restart_httpd IN_CLOSE_WRITE /usr/sbin/sysadmin_restart_httpd

Change History

01/09/12 11:07:01 changed by tonyclewis

  • owner changed from tonyclewis to mbrevda.

01/09/12 12:16:43 changed by tonyclewis

  • status changed from new to closed.
  • resolution set to fixed.

This has been fixed and included in the next release. You can yum update sysadmin. Should be published shortly.