-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature #5125
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you have an active AWS support contract, please open a case with AWS Premium Support team using the below documentation to report the issue:
https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
Before submitting a new issue, please search through open GitHub Issues and check out the troubleshooting documentation.
Please make sure to add the following data in order to facilitate the root cause detection.
Required Info:
pcluster describe-cluster
command.Bug description and how to reproduce:
A clear and concise description of what the bug is and the steps to reproduce the behavior.
If you are reporting issues about scaling or job failure:
We cannot work on issues without proper logs. We STRONGLY recommend following this guide and attach the complete cluster log archive with the ticket.
For issues with Slurm scheduler, please attach the following logs:
/var/log/parallelcluster/clustermgtd
,/var/log/parallelcluster/clusterstatusmgtd
(if version >= 3.2.0),/var/log/parallelcluster/slurm_resume.log
,/var/log/parallelcluster/slurm_suspend.log
,/var/log/parallelcluster/slurm_fleet_status_manager.log
(if version >= 3.2.0) and/var/log/slurmctld.log
./var/log/parallelcluster/computemgtd.log
and/var/log/slurmd.log
.If you are reporting issues about cluster creation failure or node failure:
If the cluster fails creation, please re-execute
create-cluster
action using--rollback-on-failure false
option.We cannot work on issues without proper logs. We STRONGLY recommend following this guide and attach the complete cluster log archive with the ticket.
Please be sure to attach the following logs:
/var/log/cloud-init.log
,/var/log/cfn-init.log
and/var/log/chef-client.log
/var/log/cloud-init-output.log
.Additional context:
Any other context about the problem. E.g.:
~/.parallelcluster/pcluster-cli.log
The text was updated successfully, but these errors were encountered: