Need to stop ( abort ) all scheduled outbound faxes from being sent by the FaxFinderThe following information and procedure applies to FFx30 Fax Finder servers running firmware version 2.1.0 or higher.
Regardless of how a Fax was scheduled/submitted, or how many recipients are defined within the scheduled fax, each scheduling can be swiftly aborted by clicking on the Abort link associated with it (which is found in the Outbound Fax Status section, of the Fax Status WEB Management menu).
If however, multiple separate faxes have been scheduled incorrectly and need to be aborted (too many to do one at a time through the Fax Status menu, e.g. scores or 100s or more of pending outbound faxes) the following steps can be taken, which requires administrator command line access.
The process to abort all outbound faxes includes a system reboot. This reboot will interrupt any inbound fax currently being received. It would be up to the party sending you a fax to resend it.
This process does NOT delete Fax History contained in the 3 fax logs (Inbound, Outbound and Modem logs) accessible via the Status & Logs menu on your FaxFinder server. However, this process DOES delete Fax History (and the ability to resend Completed faxes) normally made available to and through the FaxFinder Client Software (when the client software opens a status window to the server).
The process also temporarily effects the server's ability to display the Fax Status page.
The system administrator should perform the following procedure:
1) Inform all users (& or applications) to stop sending (scheduling) faxes.
2) Open a secure shell connection (SSH based terminal program such as Putty) to the IP address of the FaxFinder on TCP port 22 (or connect to the serial console port on the back of the unit).
3) When connecting via SSH, login with your FaxFinder Administrator account username and password.
4) From the # prompt, CAREFULLY type the following commands to remove all pending and currently in progress outbound faxes:
rm -rf /usr/local/share/fsched/*
The response to the killall command may include statements of processes not found - this is okay and would be due to child processes ending before the kill command can get to them.
After the reboot command is issued, it takes about 2 minutes for the unit to come back up and provide a WEB Management login screen.
NOTE: For experienced administrators with file system knowledge.
Regarding loss of history for the FaxFinder Client Software, a less drastic range of fsched sub folders could be removed/deleted.
Before initiating the 3 step process (killall, remove and reboot), use the ls -l command to determine the time and date of when fsched sub folders were created. Delete all sub folders created near/at and after the time of when the erroneous faxes were scheduled/submitted to the server. This would leave the previous history in tact.
For each submitted/scheduled fax, a sequentially numerically named (in hexadecimal) sub folder is created (with 8 characters in the name). The fsched sub folders will be named 00000000 through FFFFFFFF
The following command lists the contents of the fsched folder with details.
ls -l /usr/local/share/fsched/
If there are too many to see the beginning of the directory listing use:
ls -l /usr/local/share/fsched/ |more
A wild card ( * ) can be used in association with the sub folder name.
The following command removes all sub folders that have a name that starts with 00001A9_.
rm -rf /usr/local/share/fsched/00001A9*
This particular example will potentially remove up to 16 folders because the 8th character in the folder name could be any hex digit 0 thru F (folders 00001A90 thru 00001A9F deleted).
The following command removes all sub folders that have a name that starts with 00001A__.
rm -rf /usr/local/share/fsched/00001A*
This particular example will potentially remove up to 257 folders because the 7th & 8th characters in the folder name could be any two hex digits 0 thru F (folders 00001A00 thru 00001AFF deleted).