Re: [arch-general] sendfax: 460 Failed to submit job 110: Unable to open scheduler FIFO: No such device or address.
On 09/26/2018 11:37 PM, David C. Rankin wrote: > On 09/26/2018 06:37 PM, David C. Rankin wrote: >> Any thoughts welcomed. I'll also post to the hylafax list and report back if >> there is any information there. > > I haven't heard back on the hylafax list yet, but this error is reproducible > on Arch 4.18.9 with a simple example, e.g. > > $ sendfax -vv -n -d 5551212 anyfile.pdf > ... > 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. > > Simply rebooting to LTS (4.14.71) and the command succeeds without any > problem. > > Is anyone else seeing this? > Disregard, Sorry for the noise, the post run scripts left the fax scheduler not running. Manually restarting all faxq, fax and hfaxd services worked. Following restarting everything: # faxstat -v Trying localhost [10] (::1) at port 4559... Trying localhost [2] (127.0.0.1) at port 4559... Connected to (null). 220 phoinix.mydomain.com server (HylaFAX (tm) Version 6.0.7) ready. -> USER root 230 User root logged in. -> MDMFMT 200 Modem %m (%n): %s -> EPRT |1|127.0.0.1|36321| 200 EPRT command successful. -> LIST status 150 Opening new data connection for "status". HylaFAX scheduler on phoinix.mydomain.com: Running Modem ttyS0 (+1.936.xxx.): Running and idle 226 Transfer complete. where before it was left Not running. -- David C. Rankin, J.D.,P.E.
Re: [arch-general] sendfax: 460 Failed to submit job 110: Unable to open scheduler FIFO: No such device or address.
On 09/26/2018 06:37 PM, David C. Rankin wrote: > Any thoughts welcomed. I'll also post to the hylafax list and report back if > there is any information there. I haven't heard back on the hylafax list yet, but this error is reproducible on Arch 4.18.9 with a simple example, e.g. $ sendfax -vv -n -d 5551212 anyfile.pdf ... 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. Simply rebooting to LTS (4.14.71) and the command succeeds without any problem. Is anyone else seeing this? -- David C. Rankin, J.D.,P.E.
Re: [arch-general] sendfax: 460 Failed to submit job 110: Unable to open scheduler FIFO: No such device or address.
On 09/26/2018 05:25 PM, David C. Rankin wrote: > All, > > After recent updates, 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. > > Does anyone know why sendfax would begin failing with "Unable to open > scheduler FIFO: No such device or address." with the current kernel, but work > fine on LTS? > > (I have confirmed this behavior on two separate Arch servers) > 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 uucp0 Sep 25 07:29 FIFO prw--- 1 uucp uucp0 Sep 20 19:57 FIFO.ttyS0 The FIFO is there owned by uucp:uucp in both cases. Did the latest kernel tighten some type of security that would effect mkfifo for hylafax in some way? This caught me somewhat off-guard as both Arch servers are used in a production capacity and I had a fax that needed to go to Scottsdale before close of business. Any thoughts welcomed. I'll also post to the hylafax list and report back if there is any information there. -- David C. Rankin, J.D.,P.E.
[arch-general] sendfax: 460 Failed to submit job 110: Unable to open scheduler FIFO: No such device or address.
All, After recent updates, 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. Does anyone know why sendfax would begin failing with "Unable to open scheduler FIFO: No such device or address." with the current kernel, but work fine on LTS? (I have confirmed this behavior on two separate Arch servers) -- David C. Rankin, J.D.,P.E.
Re: [arch-general] MariaDB package version
On 9/26/18 3:31 PM, Kevin Dodd via arch-general wrote: > I recently noticed Arch Linux's mariadb package is still on the 10.1 > release series, even though upstream has considered the 10.2 and 10.3 > release series to be "stable" for at least 4 months. Arch is usually so > good about keeping everything up-to-date, so I am curious what the > reason for this is. Something to do with compatibility? https://lists.archlinux.org/pipermail/arch-general/2017-September/044255.html If you have further news, feel free to share. :) -- Eli Schwartz Bug Wrangler and Trusted User signature.asc Description: OpenPGP digital signature
[arch-general] MariaDB package version
I recently noticed Arch Linux's mariadb package is still on the 10.1 release series, even though upstream has considered the 10.2 and 10.3 release series to be "stable" for at least 4 months. Arch is usually so good about keeping everything up-to-date, so I am curious what the reason for this is. Something to do with compatibility? Thanks, ~ Kevin Dodd
[arch-general] rtlwifi
Good afternoon, my log is flooded with these messages: Sep 26 09:09:45 defiant kernel: rtl8192se: switch case 0x5e not processed Sep 26 09:09:54 defiant kernel: rtlwifi: AP off, try to reconnect now Approx everey 10 sec there's a new entry. My wifi connection is quite buggy even when close to the router, so am not sure if that might be a reason. My favourite search engine came up with some links suggesting that these module options will help: options rtl8192se fwlps=0 ips=0 swlps=0 swenc=1 However, I do not see any difference with them. any ideas how to get around this? THX Frank
Re: [arch-general] [News] DigitalOcean "supporting" Arch Linux
Yes they dropped support for it which was a real blow, but luckily existing machines weren't stopped and we still have several Arch machines running. On Wed, Sep 26, 2018 at 4:13 PM Eduardo Machado via arch-general wrote: > > Hi folks, > > Firstly, i am not a digitalocean affiliated, but i use their services. > A long time ago, Arch Linux was one the supported OSes, latter they dropped > this support. > Now, although it is not officially supported again they just launched the > ability to upload Custom Images into DigitalOcean. You can now import the > OS of your choice directly into DigitalOcean and start a Droplet. [1] > > > [1] https://blog.digitalocean.com/custom-images/ > --- >Eduardo M. Machado
[arch-general] [News] DigitalOcean "supporting" Arch Linux
Hi folks, Firstly, i am not a digitalocean affiliated, but i use their services. A long time ago, Arch Linux was one the supported OSes, latter they dropped this support. Now, although it is not officially supported again they just launched the ability to upload Custom Images into DigitalOcean. You can now import the OS of your choice directly into DigitalOcean and start a Droplet. [1] [1] https://blog.digitalocean.com/custom-images/ --- Eduardo M. Machado
[arch-general] Problem install shrew vpn client
Hi, I received this error when compile the program shrew vpn client: yaourt -S shrew-vpn-client /tmp/yaourt-tmp-maykel/aur-shrew-vpn-client/src/ike/source/libike/manager.file.cpp: In member function 'bool _CONFIG_MANAGER::file_pcf_load(CONFIG&, const char*, bool&)': /tmp/yaourt-tmp-maykel/aur-shrew-vpn-client/src/ike/source/libike/manager.file.cpp:682:19: error: aggregate 'EVP_CIPHER_CTX ctx_cipher' has incomplete type and cannot be defined EVP_CIPHER_CTX ctx_cipher; ^~ make[2]: *** [source/libike/CMakeFiles/ss_ike.dir/build.make:102: source/libike/CMakeFiles/ss_ike.dir/manager.file.o] Error 1 make[2]: *** Waiting for unfinished jobs [ 24%] Linking CXX shared library libss_ip.so [ 25%] Linking CXX shared library libss_pfk.so [ 25%] Built target ss_ip [ 25%] Built target ss_pfk make[1]: *** [CMakeFiles/Makefile2:244: source/libike/CMakeFiles/ss_ike.dir/all] Error 2 make: *** [Makefile:130: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build shrew-vpn-client. Someone happened to him the same? Thanks in advanced.
