HP3000-L Archives

July 2009, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Stanfield, Randy (Carrollton, TX)" <[log in to unmask]>
Reply To:
Stanfield, Randy (Carrollton, TX)
Date:
Tue, 7 Jul 2009 23:30:46 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
Does anyone have a suggestion for aborting a hung inbound FTP process,
that is causing the JINETD job to just chew up CPU. This is about the
4th or 5th time this has happened and against the same file set. 

 This inbound FTP process seems to be doing a loop for each file in a
Posix directory.
[log in to unmask]
 
Ren /filea.rdy /filea.trn
Get /filea.trn
Ren /filea.trn /filea.snt 



We've tried aborting the JINETD job using ABORTJOB command and tried
ABORTPROC with PIN of hog CPU FTP process. Neither process will kill the
job or process. Also if you do a listf on the POSix file it will hang
the process doing the listf.

We've had to SHUTDOWN the machine and restart just to clear the problem.
When this has occurred it has impeded our backup from running. That is
how the process has been discovered. Because it doesn't seem to totally
stop inbound or outbound FTP processing from working. This last incident
occurred at 2:00pm in the afternoon but didn't cause any system issues
until 10:30pm when backups were trying to run.

HP responses center took a memory dump during the first two with no fix
yet. We've had lots of little tweeks but resolution yet.

Any suggestions are welcome
Randy Stanfield
Unisource
972-982-3621

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2