Common ARE Errors

A Quick Checklist

Before we launch into the full diagnostic procedure, here is a quick checklist of common pitfalls:

• Are you using the 6-character NCI username for ARE login?
• Have you tried to login using a new browser tab / another browser / incognito mode?
• Have you joined the relevant Gadi project for job resources?
• If you just signed up / joined a project, wait 30 minutes for ARE system to update account status.
• Did you supply correct setting values when launching the session?

Unable to Log In

Error: Bad Request: Requested resource does not exist.
Possible Cause: This error is often caused by issues with browser cookies or cache.
Solution: Open another tab and log in again, or try using incognito mode.

Error: We're sorry, but something went wrong.
Possible Cause: Exceeding the /home file system quota on Gadi. ?
Diagnosis: Run the following on Gadi’s login node: quota -s du -h –max-depth=1 ~
Solution: Delete or move files from your HOME directory to stay within quota.

Error: Web application could not be started by the Phusion Passenger(R) application server...
Possible Cause: Exceeding the /home  file system quota on Gadi.
Diagnosis: Run the following on Gadi’s login node: quota -s; du -h –max-depth=1 ~ 
Solution: Delete or move files from your HOME directory to stay within quota.

Unable to Launch Session

Error: qsub: Error: You are not a member of project vp91. You must be a member of a project to submit a job under that project.
Possible Cause: You are not a member of the project yet or membership is syncing.
Solution: Wait 20 minutes, then try again.

Error: Failed to submit session with the following error: usage: qsub [...] If this job failed to submit because of an invalid job name please ask your administrator to configure OnDemand to set the environment variable OOD_JOB_NAME_ILLEGAL_CHARS.
Possible Cause: Special characters submitted via form.
Solution: Review form values on settings page and re-enter them manually.

Error: Disk quota exceeded @ dir_s_mkdir - /home/<institution_code>/<username>/ondemand/data/.../<session_ID>
Possible Cause: Exceeding /home quota on Gadi.
Diagnosis: Run on login node: quota -s du -h –max-depth=1 ~
Solution: Delete or move files from HOME directory to reduce usage.

Error: unix listener: cannot bind to path /home/<institution_code>/<username>/.ssh/<session_ID>: No such file or directory. Your connection to the remote server has been terminated.
Possible Cause: ~/.ssh folder missing or incorrect permissions.
Diagnosis: Run on login node: ls -lah ~ Solution: Run on login node: mkdir -p ~/.ssh chmod 700 ~/.ssh

Check Debug Log for Other Issues

If your issue is not resolved above, follow below steps to copy the debug log link before submitting a ticket to Helpdesk:

Report an Issue to NCI Helpdesk

If your issue isn’t listed above, contact the NCI Helpdesk.

Existing users: submit a request at help.nci.org.au.

Anyone: email help@nci.org.au.

Before you submit

• Copy the Debug Log link, or the Session ID if the job is still running (see "Check Debug Log for Other Issues" for instructions).

• Note any error messages and the time the issue occurred.

How to submit