...
Monitoring is set up under the obsbench user to check the current running workflows for task failures. If a task fails, a slack message will be sent to the mvp channel. This script runs via cron after the daily experiments complete. Monitoring scripts and logs can be found at /home/obsbench/nrtdev/monitoring
Adding separate R2D2 dbs for each user:
When running with many users on one machine, each using R2D2 localhost, we need to separate out each R2D2 database. If the user builds with jedi-tools and uses the default they will end up trying to access obsbench's R2D2. These are steps I took to start Victor's own R2D2 database:
- Add user to docker permissions as ubuntu user:
sudo usermod -aG docker vmarchais - As the new user, create user mysql directory:
mkdir -p ~/mysql-data && chmod 777 ~/mysql-data - Kick off docker with new ports and names (ie setting: HOST_PORT_HTTP=8081 HOST_PORT_HTTPS=444 HOST_PORT_MYSQL=3309 R2D2_SERVER_NAME=r2d2-server-vmarchais R2D2_DB_NAME=r2d2-db-vmarchais) Then run:
docker compose -p r2d2-vmarchais -f server/docker/compose.yaml up -d - User updates R2D2 env vars (in the user's setup.sh):
export R2D2_SERVER_PORT=8081