Differences

This shows you the differences between two versions of the page.

--- acq:edi_sftp [2024/04/08 14:04] – ↷ Page name changed from acq:ed_sftp to acq:edi_sftp dyrcona
+++ acq:edi_sftp [2024/04/12 13:30] (current) – [Other Bad Accounts Cause a Crash] add link to Launchpad bug dyrcona
@@ Line 38: / Line 38: @@
 > Another screenshot would be useful here.
+[[https://bugs.launchpad.net/evergreen/+bug/2060702|There is a Launchpad bug for this issue.]]
 ==== Other Bad Accounts Cause a Crash ====
@@ Line 43: / Line 44: @@
 If the EDI fetcher crashes unexpectedly, you can check for these accounts in a similar manner to those with bad credentials.  The difference is that once you get logged in, your SFTP tool should report a message about a nonexistent directory, and in the case of the command line SFTP used by Evergreen and Linux, the program will likely crash.  The solution for these accounts is the same as for those with bad credentials: set the provider's active field to a false value.
+[[https://bugs.launchpad.net/evergreen/+bug/2060707|There is a Launchpad bug for this issue.]]
+===== Trouble Shooting =====
+The best way to trouble shoot issues with the switch to SFTP is to get the full output from the EDI fetcher program.  This can be done by your server administrator or hosting provider.  If the scheduled jobs service (usually "cron") can send emails, then configure it to email someone and remove any redirects or other filters on the entry for the edi_fetcher.pl program.
+If the fetcher hangs, as in the case of [[acq:edi_sftp#bad_credentials_accounts_cause_a_hang|the bad credentials caveat above]], then it may be necessary to remove it from the scheduled jobs, stop the running fetcher, and run it manually to see exactly which account causes the hang.