Data Storage and Processing

Data Storage and Processing

Any PI who has active project can apply cluster access for himself/herself and his/her associates.  The users of CSIC cluster are independently managed and are not bonded with Emory ID.  Please send full name, official email address, and the project name to the CSIC cluster administrator for new user creation.

Users will be suspended either by PI's request, by abusing behavior, or due to long time inactivity.  If an associate left your project, please inform the CSIC cluster administrator to suspend his/her access.  If a PI does not do so, the user will still have access to the CSIC cluster even if his/her Emory ID has been suspended, unless,

1) abuse activity is detected;

2) the account is inactive for over a year.

CSIC cluster has minimal down time, which usually is no more than a few hours per year.  There are four typical cases that could cause this.

1) Some public domain wifi, like EmoryGuest wifi, is only a WWW proxy, which does not support ssh and sftp.  Please use a reliable ISP to connect CSIC cluster.

2) CSIC cluster has multiple login nodes, but only csic.som.emory.edu is accessible from outside Emory.  To directly connect to other login nodes, please log in your Emory VPN first.

3) You get a warning like:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for xxx.xxx.emory.edu has changed,
and the key for the corresponding IP address aaa.bbb.ccc.ddd
is unchanged. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
Offending key for IP in /home/username/.ssh/known_hosts:xx
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!

If you see this, it is usually not that serious.  This is usually caused by us to either switched a different node as log in node, or by a significant operating system upgrade.  Please edit your local  ~/.ssh/known_hosts, and delete the offending line xx, and try log in again.  You will be asked to accept a new key, and everything will be back to normal. 

However, if such thing comes back again in a short time, say a few days or shorter, your computer may really have been hacked or the route is hijacked.  Please inform the CSIC cluster administrator if you experience repeated such behavior. 

4) Your connection was refused by the remote host.  This usually means that your IP was blacklisted by a hacking prevention mechanism on the cluster.  Please contact the CSIC cluster administrator.