Affects Version/s: None
Target Release Version/s: None
Call files with 1.8-rc2 with Issue
ASTERISK-16608 patch works for me.
The problem reported here are two warning logs that are generated for each successful call file. (See Additional Information)
Each warning log occurs at "RetryTime" seconds after the call-file completion or previous warning log.
While these warnings seem harmless, it indicates the queue is maintaining multiple instances of the call file, (or inotify is generating them during the processing).
If HAVE_INOTIFY is undefined in pbx_spool.c, the problem goes away.
- ADDITIONAL INFORMATION ******
In "demo" context:
exten => 502,1,Answer
exten => 502,n,Hangup
$ mv call-file.txt /var/spool/asterisk/outgoing/
== Verbosity 5 console ==
– Attempting call on Local/502@demo for s@:1 (Retry 1)
– Executing [502@demo:1] Answer("Local/502@demo-0964;2", "") in new stack
> Channel Local/502@demo-0964;1 was answered.
– Executing [s@demo:1] Wait("Local/502@demo-0964;1", "1") in new stack
– Executing [502@demo:2] Hangup("Local/502@demo-0964;2", "") in new stack
== Spawn extension (demo, 502, 2) exited non-zero on 'Local/502@demo-0964;2'
== Spawn extension (demo, s, 1) exited non-zero on 'Local/502@demo-0964;1'
[Oct 4 10:17:24] NOTICE: pbx_spool.c:357 attempt_thread: Call completed to Local/502@demo
[Oct 4 10:17:34] WARNING: pbx_spool.c:400 scan_service: Unable to open /var/spool/asterisk/outgoing/call-file.txt: No such file or directory, deleting
[Oct 4 10:17:44] WARNING: pbx_spool.c:400 scan_service: Unable to open /var/spool/asterisk/outgoing/call-file.txt: No such file or directory, deleting
HAVE_INOTIFY is defined in pbx_spool.c
Related to Issue
ASTERISK-16097 Reported description.