[
https://issues.apache.org/jira/browse/AIRAVATA-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Heejoon Chae updated AIRAVATA-940:
--
Description:
Intuitively the output component's view button seems to show output but now it
Heejoon Chae created AIRAVATA-973:
-
Summary: Improving XBays.java '-workflow' option to accept URL as
well
Key: AIRAVATA-973
URL: https://issues.apache.org/jira/browse/AIRAVATA-973
Project: Airavata
https://issues.apache.org/jira/browse/AIRAVATA-972
Thanks
Amila
On Mon, Dec 23, 2013 at 4:01 PM, Amila Jayasekara
wrote:
> I just tried 0.9 distribution and was able to successfully submit jobs to
> trestles. So it seems, cause has nothing to do with resource (SHA2 or
> community credential pol
Amila Jayasekara created AIRAVATA-972:
-
Summary: Unable to submit jobs to GRID machines
Key: AIRAVATA-972
URL: https://issues.apache.org/jira/browse/AIRAVATA-972
Project: Airavata
Issue T
I just tried 0.9 distribution and was able to successfully submit jobs to
trestles. So it seems, cause has nothing to do with resource (SHA2 or
community credential policy). Seems this is due to a change in airavata.
Did we do any JGlobus or myproxy related changes in RC2 ?
Thanks
Amila
On Mon,
I'm also getting the same issue that Lahiru mentioned with latest
certificates when submitting a job in trestles.
Reards,
Chathuri
On Mon, Dec 23, 2013 at 1:00 PM, Amila Jayasekara
wrote:
> This could be due to 2 reasons.
>
> 1. Your my proxy credentials are incorrect
> 2. Your certificates are
Ok, I am also getting the same error Lahiru got with latest certificates.
Suresh, do you know whether XSEDE updated their resource to use SHA2 ? If
so when ?
Thanks
Amila
On Mon, Dec 23, 2013 at 1:00 PM, Amila Jayasekara
wrote:
> This could be due to 2 reasons.
>
> 1. Your my proxy credentials
This could be due to 2 reasons.
1. Your my proxy credentials are incorrect
2. Your certificates are outdated. Recently there was a mail in xsede to
update certs. (See the mail with subject "Updates to the XSEDE CA Tarball"
from her...@illinois.edu.
You can latest certs from [1].
[1] https://soft
Lahiru, I could be wrong, but could this be because of the recent changes
in XSEDE policy for community accounts? (I don't know whether they've being
on effect yet)
On Mon, Dec 23, 2013 at 9:03 AM, Lahiru Gunathilake wrote:
> May be my certificates are bad.
>
> Suresh, do we have new certs to us
Hi Amila, I was able to run the client sample and the 10 min tutorial
successfully with a tomcat deployment of Airavata after doing a fresh
reboot. So I think for the time-being we can consider this as not a problem
for the release.
On Mon, Dec 23, 2013 at 5:11 AM, Chathuri Wimalasena
wrote:
> H
Hi Chathuri,
I tried to run a simple job in trestles and got following error. But I
haven't seen this error before.
org.globus.gram.internal.gramerrors.properties not found
[ERROR] An error occurred while submitting a job, job id = null
Error code: 10. Caused by unwrap failed. Caused by Token ha
May be my certificates are bad.
Suresh, do we have new certs to use ?
Regards
Lahiru
On Mon, Dec 23, 2013 at 12:01 PM, Lahiru Gunathilake wrote:
> Hi Chathuri,
>
> I tried to run a simple job in trestles and got following error. But I
> haven't seen this error before.
>
> org.globus.gram.inte
Hi Saminda,
We also specify that even in our deployment guide in the wiki [1]. For
paramchem, we do increase the memory in tomcat deployment. I'm not sure
whether it only occurs in this release.
Regards,
Chathuri
[1]
https://cwiki.apache.org/confluence/display/AIRAVATA/Airavata+Deployment+Guide
Increase in memory usage probably mean we may have to do the same for our
servers in production when upgrading. So it will affect at some point. I
will test again with a fresh reboot to see if i can reproduce the error and
if so how much additional memory is used and why.
On Sun, Dec 22, 2013 at
14 matches
Mail list logo
