{5} Assigned, Active Tickets by Owner (Full Description) (21 matches)

We're trying to figure out the configuration settings for the CAPS data service created via Introduce so that it is advertised to caBIG correctly.

An overview of the architecture we are using for our initial deployment can be found on the CpasArchitecture page.

Rough notes about the configuration of this environment can be found on the CPAS configuration rough notes

It seems docs.uabgrid doesn't have a button to attach files to wiki pages. I'm trying to attach the bootcamp presentations to our bootcamp page and don't see a way to do this.

If out choose the "log back in" link from the Logout page after logout is completed, Confluence will use that as target page to return to. This leads to a confusing message and state for the user. The logout page says you are logged out, but the state is clearly "logged in" as evidenced from the user id and preference links at the top of the page.

Problems encountered with Gridway-5.2.2 on a sporadic basis.

1. Submission of a 10-array job to Gridway finishes successfully at one time, and at other times the same job stays in 'prolog' state indefinitely.

2. Job fails when Gridway is unsuccessful in copying some of the staged input files to the remote resource, even though the input files exist in the current working directory

The above same two problems were encountered by Enis Afgan(afgane@uab.edu) and reported to gridway-users mailing list http://www.globus.org/mail_archive/gridway-user/2007/10/msg00007.html

These two problems still exist in the Gridway-5.3 stable release, bugs 5718 and 5719.
Bug 5718 mentions the same mail sent by Enis afgan to gridway-users mailing list http://www.gridway.org/documentation/development/rn/index.html#s-gridway-Release_Notes_413-bugfixes

Two users have reported that that gridway jobs submitted from stage.uabgrid with a requirement to execute on olympus.cis.uab.edu are being migrated to cheaha.ac.uab.edu. The assumption is that GridWay not execute a job restricted to a specific host on any other host.

In the first case, the user's job is immediately being submitted to cheaha rather than olympus. The job script is:

EXECUTABLE  = /bin/ls
ARGUMENTS   =     -la
STDIN_FILE  =   /dev/null
STDOUT_FILE =   ls.out.${JOB_ID}
STDERR_FILE =   ls.err.${JOB_ID}
REQUIREMENTS = HOSTNAME = "olympus.cis.uab.edu"
REQUIREMENTS = LRMS_NAME = "SGE"

In the second case the job is being awaiting execution on olympus but then eventually times out and is submitted to cheaha.

Corrections or clarifications are needed to explain this behavior.

The "edit" link found on the sub-sections of pages on docs.uabgrid leads to an error result page that tells the user they need to login before they can edit the page. The "log in" text is, incorrectly, pointing to the default login URL for mediawiki and not the SSO login link.This needs to be updated to point to the SSO link instead.

Note: this should be found in the page layout text and be similar to the change made for removing the default login from the main login options at the top of the page.

We need to set up a myproxy server to assist with credential management.

I'm trying to better understand our performance expectations for our various clusters using PCI-X and PCI-e.

The speed specs in the Wikipedia entry for PCI-e seem accurate. PCI-e is described as an assembly of 2.5Gbs (Gigabit per second) channels. Assuming a 10bit byte, that gives 250MBs (mega-bytes per second). The article seems consistent with these numbers. The channels are assembled in x1 x2 x4 x8 x16 or x32 configurations. So our Dell 1950 with an x8 PCI-e card will support 2.5Gbs x 8 = 20Gbs (20 Gigabits per channel). That is, 2 x 10Gbs. In otherwords the PCI-e segment is twice as fast as our 10Gbs ethernet backplane. And, since PCI-e cards can negotiate their speed independently of other cards, we shouldn't see any negative impacts for other cards that might be connected to the same PCI-e segment.

The entry that describes PCI-X is not as clear, at least to me. There is a helpful side bar that list the top speed of PCI-X as 1GBs, that is giga-bytes per second. If we're assuming a 10bit byte, that would mean PCI-X can support 10 giga-bits per second. Is this accurate?

If PCI-X can indeed do 10Gbs, then we should be able to consider 10Gbs cards for our PCI-X hosts as well. PCI-X is a parallel bus and its max performance is impacted by the weakest spec'd card on the bus. If we put a 10Gbs card in those hosts, we should be sure to configure the PCI-X bus to maximize performance.

I need clarification on these specs, and if they are accurate we can adjust our assumptions. If they are not, we may need to adjust Wikipedia. ;)

Power to LHL was lost due to a severe thunderstorm at approximately 5:00pm on 2008-06-12.

Notes from the incident are in UABgrid Incident Report 2008-001

After the tasks related to the incident are identified and added to dev.uabgrid, this ticket may be closed.

Please record a link to each identified task as a comment to this ticket.

The caTissue VM for production release 'catissue.uabgrid.uab.edu' was successfully deployed on to the caGrid Production portal. The querying of this same service, results in the following error:

The service that you are attempting to query encountered an error.

AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
 faultSubcode: 
 faultString: 
 faultActor: 
 faultNode: 
 faultDetail: 
	{http://gov.nih.nci.cagrid.data/DataServiceExceptions}QueryProcessingException:2009-07-09T19:19:14.750Zhttp://catissue.uabgrid.uab.edu:18080/wsrf/services/cagrid/CaTissueSuiteQueryProcessingException -- Error initializing CSM security: Error in authenticating user credentials2009-07-09T19:19:14.746Z
	at gov.nih.nci.cagrid.data.service.DataServiceImpl.query(DataServiceImpl.java:58)
	at gov.nih.nci.cagrid.data.service.globus.DataServiceProviderImpl.query(DataServiceProviderImpl.java:28)

Caused by: gov.nih.nci.system.applicationservice.AuthenticationException: Error in authenticating user credentials
	at gov.nih.nci.system.comm.client.ClientSession.startSession(ClientSession.java:173)
	at gov.nih.nci.cagrid.data.sdk32query.HQLCoreQueryProcessor.applyUserSecurity(HQLCoreQueryProcessor.java:123)
	... 39 more
gov.nih.nci.cagrid.data.QueryProcessingException
	{http://xml.apache.org/axis/}exceptionName:gov.nih.nci.cagrid.data.faults.QueryProcessingExceptionType
	{http://xml.apache.org/axis/}hostname:catissue.uabgrid.uab.edu