Thanks Kenneth for the input. I have implemented pattern matching after running 
several tests and hope it will take care of current issue. I also looked into 
return codes and will see if that something i need to implement.

Raminder
On Aug 13, 2014, at 6:34 PM, K Yoshimoto <[email protected]> wrote:

> 
> I'm not sure what's in NSG/Cipres.  For MCP and GUR, I had to deal
> with odd stderr/stdout return text all the time.  Seems like each platform
> could have different text patterns and possibly return codes, so
> it's necessary to have better tests of completion than pattern-matching
> or return code checks.
> 
> On Wed, Aug 13, 2014 at 05:21:20PM -0400, Marlon Pierce wrote:
>> Thanks, Kenneth. Are you doing something like this in NSG?
>> 
>> Marlon
>> 
>> On 8/13/14, 4:03 PM, K Yoshimoto wrote:
>>> You might want to not throw an exception.  Instead, output
>>> any stderr/stdout if in debug mode.  To check for success,
>>> do a second ssh ls -ld of the new dir (or some similar dir
>>> check).  Even better, ssh touch newdir/testfile; ls -l newdir/testfile,
>>> to validate write permissions.
>>> 
>>> On Wed, Aug 13, 2014 at 07:36:12PM +0000, Marlon Pierce (JIRA) wrote:
>>>>    [ 
>>>>    
>>>> https://issues.apache.org/jira/browse/AIRAVATA-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095988#comment-14095988
>>>>  ]
>>>> 
>>>> Marlon Pierce commented on AIRAVATA-1382:
>>>> -----------------------------------------
>>>> 
>>>> Another possibility (not sure how) is to suppress these sorts of warning 
>>>> messages so that standard error only includes errors.
>>>> 
>>>>> GSISSH provider giving error to make directory if stdout is returning a 
>>>>> warning.
>>>>> --------------------------------------------------------------------------------
>>>>> 
>>>>>                Key: AIRAVATA-1382
>>>>>                URL: https://issues.apache.org/jira/browse/AIRAVATA-1382
>>>>>            Project: Airavata
>>>>>         Issue Type: Bug
>>>>>           Reporter: Raminderjeet Singh
>>>>> 
>>>>> In GSISSHDirectorySetupHandler.makeDirectory() call to 
>>>>> cluster.makeDirectory calls SSHUtils.makeDir(), if a stdout have some 
>>>>> warning messages the API throws an exception even the directory is 
>>>>> getting created. We need to handle return types better. Following is the 
>>>>> problem code.
>>>>> if (!stdOutReader.getStdErrorString().equals("")) {
>>>>>            throw new SSHApiException(stdOutReader.getStdErrorString());
>>>>>        }
>>>>> On stampede following is returned which is not important but we throw an 
>>>>> exception
>>>>> "Lmod Warning: The following modules have changed: TACC-paths, amber, 
>>>>> cluster, cluster-paths, intel, mvapich2
>>>>> Lmod Warning: Please re-create this collection.
>>>>> Restoring modules to system default"
>>>>> 
>>>>> Incase of directory creation failure we will get something like "mkdir: 
>>>>> cannot create directory `/home1/01437/test': Permission denied"
>>>>> These conditions need to be handled in GSISSH library.
>>>> 
>>>> 
>>>> --
>>>> This message was sent by Atlassian JIRA
>>>> (v6.2#6252)

Reply via email to