Just using /etc/profile to set the environment for a user's cron job probably isn't going to help much. There is a good chance you'll also need the user $HOME/.profile, $HOME/.bashrc, or some other user specific initialization script that the script being executed (and any commands it invokes) depend upon. The problem is that you are running a shell script that uses relative pathnames to find scripts to run:

Code:

./startMeasuring.sh
./collectStats.sh

and there is nothing in your script to move into the directory that would make those relative pathnames valid. And, we don't know whether or not those scripts depend on being invoked from a certain directory so they can find other files.

The directory in which cron runs a job is implementation specific, but the likelihood that it will be the current working directory at the time that the user invoked crontab to add that job to the list of jobs cron will execute is extremely small.

Any script being executed by cron needs to be capable of setting up whatever environment variables and it needs to run and needs to be capable of making its current working directory appropriate for it to access any files it needs to access and to put any files it may create in a place where the user will be able to find them when the script completes.