HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: Fax queuer stopped sending out faxes on BSD/OS
I have had this happen to me before also.
I re-added the modem (faxaddmodem command) and it has worked fine since.
Try that. I don't know why.... but it works for me.
Mike
-------------------------------------------------------------
Mike Pistone pistone@eurekanet.com
Systems Administrator ph 614.593.5052
Eureka Networks, Ltd. fx 614.594-3632
On Thu, 30 Jan 1997, Vivek Khera wrote:
> Yesterday I came in and my fax server machine was locked up due to some
> process running out of memory (haven't figured that one out yet) so I rebooted
> it. Now anything sent to HylaFAX just gets queued up. I've since power
> cycled and rebooted, even restored all the HylaFAX programs and configuration
> from a tape made two weeks ago.
>
> My configuration is this: BSD/OS 2.0.1 with 20Mb RAM. I'm running HylaFAX
> 3.0p1. The queuer reports this to the log when it starts:
>
> HylaFAX (tm) Version 3.0pl1113
>
> and my current fax queue looks like this:
>
> [fax@zax]# faxstat -a
> Server on faxmachine:FIFO for all modems: Running.
> Server on faxmachine:tty05 for +1.301.548.4366: Running and idle.
> Server on faxmachine:tty06 for +1.301.548.4367: Running and idle.
>
> Job Modem Destination Time-To-Send Sender Status
> 2245 any 18002726505 System Adminis Queued and waiting
> 2242 any 12148550219 cbd Queued and waiting
> 2244 any 14122882407 cbd Queued and waiting
> 2243 any 7032568618 cbd Queued and waiting
> 2229 any 7039126204 www Queued and waiting
> 2234 any 7039126204 www Queued and waiting
> 2233 any 7039126204 www Queued and waiting
> 2241 any 7039126204 www Queued and waiting
> 2232 any 18002726505 12:49 1997/01/30 System Adminis Queued and waiting
>
> and has been sort of stuck like this for a mighty long time now.
>
> I manually deleted some jobs since running faxrm failed to physically delete
> the files. Running faxrm looks like this:
>
> [uucp@zax]# faxrm 2232
> Job 2232 removed.
>
> but faxstat shows the job still there. However, faxalter does seem to do
> something. I ran "faxalter -p 2232" at 12:49 as evidenced by the time on the
> job above.
>
> This had been working great for sending out dialy faxes for the last 6 months,
> and text pages for over a year. Now I'm silenced...
>
> What does work is a data dialin. That gets logged and handled properly by the
> faxgetty process. Also, everything else on that machine works: the web proxy,
> IP routing/filtering, etc.
>
> I've destroyed and re-created the FIFO files. I don't see any lock files.
> I've power-cycled the modems. I've restored the files from disk.
>
> Any ideas on what else I might try to make the faxes go out? I'm desperate!
>
> Thanks.
>
> v.
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Vivek Khera, Ph.D. Khera Communications, Inc.
> Internet: khera@kciLink.com Rockville, MD +1-301-258-8292
> PGP/MIME spoken here http://www.kciLink.com/home/khera/
>