[Home]

Summary:ASTERISK-25841: pbx_spool fails
Reporter:Private Name (falves11)Labels:
Date Opened:2016-03-11 22:03:55.000-0600Date Closed:2016-03-12 10:13:32.000-0600
Priority:CriticalRegression?
Status:Closed/CompleteComponents:PBX/pbx_spool
Versions:11.21.2 Frequency of
Occurrence
Related
Issues:
Environment:Linux 4.0.0-1.el7.elrepo.x86_6, Centos 7Attachments:
Description:[Mar 11 22:54:51] ERROR[16361]: pbx_spool.c:679 scan_thread: Unable to initialize inotify(7)
Comments:By: Asterisk Team (asteriskteam) 2016-03-11 22:03:55.854-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

By: Joshua C. Colp (jcolp) 2016-03-12 10:13:32.382-0600

This is not a bug with Asterisk. There is a configurable fixed size to the limit of inotify watchers available on the system. As you are starting a lot of Asterisk instances you are exceeding this. You will need to research how to increase this limit for your environment.