This is using the DigitalOcean “one click” installer, right, not the official installation instructions? If so, there have been previous discussions about this here, but ultimately you probably want to contact DigitalOcean support, as they were the ones who setup their install in this weird way, and it’d be helpful to them if they knew how much confusion their design was creating.
Yup, this is what I see every time. Just spamming enter and letting it go through yields no data loss or hiccup in performance from the end user’s side, but takes about 30 seconds for my particular droplet speed before I can actually do anything from the terminal.
I’ll contact DigitalOcean support and see what they have to say. Thank you!
Check ~/.bashrc and comment out /var/lib/digitalocean/discourse.sh to #/var/lib/digitalocean/discourse.sh. You can probably do this with nano or FTP editing.
If not immediate, a reload should stop that line from being loaded and the script should stop.