Welcome!

Honestly, this looks like a mess. Not based on the screenshots you provided, but rather based on the description.
When making changes to your production environment, always test them in a development / staging system first!
Next thing to ensure: Always have a backup ready for when things go south (like in your case).
Note regarding backups: A backup you haven't restored to test whether your backup procedure works is basically worthless.

Keep these things in mind before proceeding with any of the following advice!
If you haven't done a backup yet, do one now! (At least a full mysqldump of the databases you're interested in.)

You should check that the packages you installed have been removed completely.
It's always worth checking whether the problem might be due to some misconfiguration in any one of your services (webserver, php, database). This can be arbitrarily hard to troubleshoot - in doubt try restoring default configurations. (Again, backup your config files first!)
Then try to restart your webserver, database and php-engine (in case it isn't embedded into the webserver). To avoid any persistance of cached contents and/or config files, you should always do:
$ sudo systemctl stop openlitespeed mysqld && sudo killall -9 lsphp
$ sudo systemctl start mysqld openlitespeed
The exact commands may differ based on the brand / version of your Operating System and the webserver you use. I just did a quick Google search for how lsphp should be restarted / stopped and it seems to me you're running lsphp in detached mode.

If any of those services refuse to start back up, check the corresponding config files for any errors.
If they do start up but the problem persists, you should try a full server restart.
If that fails, too, it might be time to restore a backup.

Optimally, you should have a backup of both the Moodle files and the Moodle database from before you changed anything.
You could then go ahead and:
- Stop the webserver
- Connect to the database via command prompt as root / admin.
- Drop all databases *except* those named "mysql", "information_schema" or "performance_schema".
- Create the new Moodle database (don't forget to grant permissions again!) and quit the database command prompt
- Restore the database-backup via command line
- Delete Moodle files from webdir and restore with backup (ensure you have a working config.php in your backup)
- Start webserver

If all this fails, you might want to try restoring your backup on a new server.

Cheers

Saw your SOS in the other forum: https://moodle.org/mod/forum/discuss.php?d=413293. So you are making a new start?

In the post above your described What you were doing. For the next round, it would be useful if you describe What you were trying to achieve? Once we have a clear picture of Where you want to go, may be you'll find somebody who could tell your How to go there.