Hi, I am testing out NITRC-CE on AWS, but I seem to be running continuously in a problem: I launch a simple FEAT (FSL) analysis (literally running a block 30on-30off design with no frills) but it keeps errorieng out ("child process exited abnormally"). I know this has nothing to do with the set-up (e.g., missing files or mis-specified paths), and when I run the command on which the process errors out (according to the log) at the terminal it runs correctly. Is there something else I have to do to get FSL to work after I launch the current NITRC-CE in AWS? (Note: I'm currently using the free trial t2.micro)

The same is true if I run Melodic (it also errors out right away, just like FEAT), and I've also tried downloading some data from NITRC-IR (an AnnHarbor subject dataset), just in case the problem was with my data, but I get the very same error again - so it seems to me this must have to do with the system set-up itself.

I'd appreciate any help!

Cheers

 Martin

Hi Martin,

I've run into similar errors using FreeSurfer on a t2.micro -- even a simple mri_convert can fail.  A larger instance does the trick for me, certainly a medium, maybe even a small (I don't recall offhand).  It won't be free use eligible, but you might give that a try.

Christian

Dear NITRC-CE experts,

I would appreciate to know if someone found the solution to this problem posted by Martin.
I am running into the same problem. Not able to run Feat in a NITRC-CE in AWS (t2.small).
Error: "... child process exited abnormally"

By the way, I am able to run the same script (*.fsf) in my local machine without any issues.
Apologies if I missed any relevant post.

Thank you very much,
Jaime

A number of tools will fail unceremoniously on the smaller instance types.  Please try a larger instance -- a medium might be sufficient, but a large should definitely work.

Thank you for the information!
Yes, it worked perfectly with a c3.large