aws / aws/amazon-sagemaker-examples
[Bug Report] cp: cannot stat '/root/.keras/keras_mxnet.json': No such file or directory
- Dominant language
- Jupyter Notebook
- Stars
- 11k
- Forks
- 7k
- Avg merge
- 8h 29m
- Merged PRs (30d)
- 8
Description
**Link to the notebook**
https://github.com/aws-samples/reinvent2018-srv404-lambda-sagemaker/blob/master/training/sms_spam_classifier_mxnet.ipynb
**Describe the bug**
I am writing a lifecycle configuration script, I can run the script well on a notebook terminal:

However, when I try to run it on lifecycle, it failed with the line`source "/home/ec2-user/anaconda3/bin/activate" mxnet_p36`,
the log reports:

**To reproduce**
The lifecycle script is:
```
set -e
NOTEBOOK_FILE="/home/ec2-user/SageMaker/smlambdaworkshop/training/sms_spam_classifier_mxnet.ipynb"
echo "activate mxnet_p36"
source "/home/ec2-user/anaconda3/bin/activate" mxnet_p36
echo "execute jupyter notebook"
jupyter trust "$NOTEBOOK_FILE"
nohup jupyter nbconvert --to notebook --inplace --execute "$NOTEBOOK_FILE" --ExecutePreprocessor.kernel_name=python3 --ExecutePreprocessor.timeout=-1&
echo "finish executing jupyter notebook"
```
**Logs**

Contributor guide
Research direction
Start with the lifecycle script in the issue and the linked training/sms_spam_classifier_mxnet.ipynb notebook. Compare the notebook-terminal execution with the lifecycle logs, beginning at the environment activation and subsequent Jupyter commands. Done means the lifecycle configuration executes the notebook without the missing-file failure, with the cause and verification recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, jupyter-notebook, shell
- Domain
- cloud, devops, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100