Re: Linux 4.18.9 update -> sendfax: 460 Failed to submit job 110: Unable to open scheduler FIFO
"David C. Rankin" <[email protected]> Wed, 26 Sep 2018 23:32:42 -0500
| Newsgroups | gmane.comp.telephony.fax.hylafax.user |
|---|---|
| Organization | Rankin Law Firm, PLLC |
| Message-ID | <[email protected]> |
On 09/26/2018 06:44 PM, David C. Rankin wrote: > All, > > On Archlinux, after recent updates (linux 4.18.9, hylafax 6.0.7), > hylafax/sendfax fails with the error: > > sendfax: 460 Failed to submit job 110: Unable to open scheduler FIFO: No such > device or address. > > it had been working find up until the last week or two. Reverting to the LTS > kernel resolves the issue. There are no obvious errors in the journal. > > (the error is reported by Avantfax) > > Does anyone know why sendfax would begin failing with "Unable to open > scheduler FIFO: No such device or address." with the 4.18.9 kernel, but work > fine on LTS (4.14.71)? > > The last successful outbound fax before this failure began was 9/19. Since > that time the only relevant updates have been: > > linux (4.18.8.arch1-1 -> 4.18.9.arch1-1) > hylafax (6.0.6-8 -> 6.0.7-1) > > Since hylafax 6.0.7-1 works fine with LTS, that points to linux 4.18.9 being > the problem. > > What would I check to determine why sendfax is unable to open scheduler FIFO > (No such device or address) when running on linux 4.18.9? Permissions under > /var/spool/hylafax are the same under both kernels: > > > # l /var/spool/hylafax/ > total 76 > drwxr-xr-x 17 uucp uucp 4096 Sep 25 22:16 . > drwxr-xr-x 10 root root 4096 Dec 29 2013 .. > drwx------ 2 uucp uucp 4096 May 21 2013 archive > drwxr-xr-x 2 uucp uucp 4096 Sep 25 22:16 bin > drwxr-xr-x 2 uucp uucp 4096 Sep 26 15:49 client > drwxr-xr-x 2 uucp uucp 4096 Sep 25 22:16 config > drwxr-xr-x 2 uucp uucp 4096 Oct 23 2017 dev > drwx------ 2 uucp uucp 4096 Sep 26 15:49 docq > drwx------ 2 uucp uucp 4096 Sep 20 00:00 doneq > drwxr-xr-x 3 uucp uucp 4096 Sep 26 00:00 etc > drwxr-xr-x 2 uucp uucp 4096 Sep 19 15:12 info > drwxr-xr-x 2 uucp uucp 4096 Sep 26 10:25 log > drwx------ 2 uucp uucp 4096 May 21 2013 pollq > drwxr-xr-x 2 uucp uucp 4096 Sep 26 10:25 recvq > drwx------ 2 uucp uucp 4096 Sep 26 15:49 sendq > drwxr-xr-x 2 uucp uucp 4096 Oct 23 2017 status > drwx------ 2 uucp uucp 4096 Sep 26 15:49 tmp > -r--r--r-- 1 root root 5426 Sep 25 07:29 COPYRIGHT > prw------- 1 uucp uucp 0 Sep 25 07:29 FIFO > prw------- 1 uucp uucp 0 Sep 20 19:57 FIFO.ttyS0 > > The FIFO is there owned by uucp:uucp in both cases (as it has been for > years). Did the latest kernel tighten some type of security that would effect > mkfifo for hylafax in some way? > > An example submission from the command line with kernel 4.18.9 results in the following failure -- while rebooting the same machine to 4.14.71 sends just fine: sendfax -vv -n -d 560xxxx /home/samba/scans/david_20180924_154926.pdf Trying localhost [10] (::1) at port 4559... Trying localhost [2] (127.0.0.1) at port 4559... Connected to (null). 220 mydomain.com server (HylaFAX (tm) Version 6.0.7) ready. -> USER david 230 User david logged in. match against (..., 512) rule: offset 0 string = "%!" -- failed (comparison) rule: offset 0 short = 0x4d4d -- failed (comparison) rule: offset 0 short = 0x4949 -- failed (comparison) rule: offset 0 short = 0x1da -- failed (comparison) rule: offset 0 short = 0x1f1e -- failed (comparison) rule: offset 0 short = 0x1f9d -- failed (comparison) rule: offset 0 short = 0x506 -- failed (comparison) rule: offset 0 short = 0x5343 -- failed (comparison) rule: offset 0 short = 0xf702 -- failed (comparison) rule: offset 0 string = "GIF" -- failed (comparison) rule: offset 0 long = 0x59a66a95 -- failed (comparison) rule: offset 0 short = 0x1b45 -- failed (comparison) rule: offset 0 short = 0x1b25 -- failed (comparison) rule: offset 0 short = 0x1b26 -- failed (comparison) rule: offset 0 short = 0x1b2a -- failed (comparison) rule: offset 0 string = "%PDF" -- success (result pdf, rule "") Apply DisplayNumber rules to "560xxxx" --> return result "560xxxx" -> FORM PDF 200 Format set to PDF. -> TYPE I 200 Type set to Image. SEND data, 44247 bytes -> EPRT |1|127.0.0.1|38095| 200 EPRT command successful. -> STOT 150 FILE: /tmp/doc124.pdf (Opening new data connection). 226 Transfer complete (FILE: /tmp/doc124.pdf). -> JNEW 200 New job created: jobid: 130 groupid: 130. -> JPARM FROMUSER "David C. Rankin" 213 FROMUSER set to "David C. Rankin". -> JPARM LASTTIME 000259 213 LASTTIME set to 000259. -> JPARM MAXDIALS 12 213 MAXDIALS set to 12. -> JPARM MAXTRIES 3 213 MAXTRIES set to 3. -> JPARM SCHEDPRI 127 213 SCHEDPRI set to 127. -> JPARM DIALSTRING "560xxxx" 213 DIALSTRING set to "560xxxx". -> JPARM NOTIFYADDR "[email protected]" 213 NOTIFYADDR set to "[email protected]". -> JPARM VRES 98 213 VRES set to 98. -> JPARM PAGEWIDTH 215 213 PAGEWIDTH set to 215. -> JPARM PAGELENGTH 279 213 PAGELENGTH set to 279. -> JPARM NOTIFY "none" 213 NOTIFY set to "none". -> JPARM PAGECHOP "default" 213 PAGECHOP set to "default". -> JPARM CHOPTHRESHOLD 3 213 CHOPTHRESHOLD set to 3. -> JPARM DOCUMENT /tmp/doc124.pdf 200 Added document /tmp/doc124.pdf as docq/doc124.pdf.130. -> JSUBM 460 Failed to submit job 130: Unable to open scheduler FIFO: No such device or address. 460 Failed to submit job 130: Unable to open scheduler FIFO: No such device or address. Same command, same machine, just rebooted on 4.14.71 succeeds just fine. Help? Mimms? Anybody? I'm left scratching my head. What else to look at? -- David C. Rankin, J.D.,P.E. ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe [email protected] < /dev/null *To learn about commercial HylaFAX(tm) support, mail [email protected].*