2 Respostas
- Mais recentes
- Mais votos
- Mais comentários
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.
respondido há 6 meses
Conteúdo relevante
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 2 anos