2 Answers
- Newest
- Most votes
- Most comments
0
Stopping and restarting won't help unless you solve the underlying issue.
Normally that means, something in the configuration magics is broken, normally a library path, connection with invalid VPC or similar.
Try to remove any magics you have until it starts, if it still doesn't start, it's likely you are using a role that cannot start sessions.
0
Thanks Gonzalo. It was a Library path which was not configured correctly.
answered 5 months ago
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago