| Issue Number | 3742 |
|---|---|
| Summary | *** Error in FtpExportData.py |
| Created | 2014-03-07 12:36:35 |
| Issue Type | Bug |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | Englisch, Volker (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2014-08-04 19:10:37 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.119397 |
This is the second time I'm seeing an error message for the program that sends the vendor data to the FTP server. However, the process did everything it's supposed to do. After looking at the log files and data I can't identify anything that broke.
I'm adding this task and will put it on hold to track how often this error gets displayed. At this point I don't think it's necessary to spend a lot of time tracking the problem down but we may have to if this keeps happening.
The problem listing the error message
Exception in thread Thread-1 (most likely raised during interpreter shutdown)came up again over the weekend.
As before, everything ran successfully except for that error message.
Here is a link discussing that error message:
http://stackoverflow.com/questions/20596918/python-exception-in-thread-thread-1-most-likely-raised-during-interpreter-shutd
Note: Edited comment with log information for QA
Based on numerous posts on the Internet the problem is a result of a bug in the Python module Paramiko which we're using in order to connect to our SFTP server. It has been reported that this problem has been fixed in Paramiko 1.12.0 - we're currently using Paramiko 1.7.7.2.
Bob has upgraded the module to the latest version available (_Paramiko 1.14.0) and added one module now required by Paramiko using the following steps:
1. Download & copy ecdsa-0.10.tar.gz to d:\downloads
2. Unpack ecdsa tar file
3. Switch to d:\downloads\ecdsa-0.10
4. Run python setup.py install
5. Download & copy paramiko-1.14.zip to d:\downloads
6. Unpack paramiko zip file
7. Switch to d:\downloads\paramiko-1.4
8. Run python setup.py installOnce the QA tier is available again (see WEBTEAM-3914) I will perform these steps on the QA-CDR server and monitor for a while to see if the error disappears. However, we're seeing this error most often on the PROD server, so we may not know for sure if upgrade of the module will fix the problem until it's been upgraded on PROD.
Here is a list of the occurrences since it first appeared in December 2013 (QA is currently unavailable):
Interpreter Shutdown Error Message
----------------------------------
Tue Oct 01 19:53:30 2013 - DEV
Mon Oct 21 20:40:03 2013 - QA
Tue Oct 22 20:57:53 2013 - QA
Thu Dec 05 20:11:16 2013 - QA
Tue Dec 10 19:43:27 2013 - DEV
Sat Dec 21 02:13:35 2013 - PROD
Sat Feb 08 02:42:36 2014 - PROD
Thu Feb 27 19:31:57 2014 - DEV
Sat Mar 01 02:28:30 2014 - PROD
Sat Mar 08 02:46:02 2014 - PROD
Sat May 10 02:30:57 2014 - PROD
Sat May 17 02:33:20 2014 - PROD
Sat May 24 02:52:15 2014 - PROD
Mon Apr 07 19:30:30 2014 - DEV
Thu Jun 05 19:43:17 2014 - QA
Sat Jun 07 02:57:22 2014 - PROD
Sat Jun 07 11:11:43 2014 - DEV
Sat Jun 21 02:52:23 2014 - PROD
Sat Jun 28 02:56:40 2014 - PROD
Sat Jul 05 02:41:37 2014 - PROD
Sat Jul 12 02:43:18 2014 - PROD
Wed Jul 16 20:25:49 2014 - QA
Sat Jul 26 02:54:00 2014 - PROD
Sat Jul 26 09:48:53 2014 - QAThe modules have been installed on QA as well and will be used from
now on.
I will enter a ticket to have the modules installed on STAGE.
The module paramiko has now been updated on DEV, QA, as well as STAGE. We will monitor the publishing jobs for a while before we can request the upgrade on PROD.
Since we upgraded the Paramiko library we had two more "failure"
messages on PROD and none on the lower tiers.
I will request CBIIT to upgrade Paramiko on the PROD server, too.
Elapsed: 0:00:00.001412