- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Not a solution, but I ended up just copying down all of the files from the server that I could access in Cloud9's environment pane, and then I restored my clean volume backup and copied the files back over.
Not sure how my instance ended in described situation. I might have expanded the EBS but it was a long time previous to this issue occuring.
I ended up following the suggestions here https://docs.aws.amazon.com/cloud9/latest/user-guide/troubleshooting.html#tmux-terminal-error
I was able to start a shell using systems manager config described above.
Check the locale
locale -a
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
C.utf8
POSIX
Some how UTF8 is no longer there ? Looked in /usr/share/i18n/locales - the locales appear to be there.
localedef -i en_US -f UTF-8 en_US.UTF-8
locale -a
C
C.utf8
POSIX
en_US.utf8
Find tmux, in my instance /opt/c9/local/bin/tmux
Verify tmux will start up without error.
Restarted the instance and was able to launch the Cloud9 GUI and terminals were working again.
This also resolved a few other issues on the instance.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren