obsidian charm
Having some issues getting the panel back going after a sudo reboot
░░ Subject: A start job for unit mariadb.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit mariadb.service has finished with a failure.
░░
░░ The job identifier is 28708 and the job result is failed.```
abstract grove
Fetch the last few lines of your MariaDB logs from somewhere in /var/log
Might be under mariadb or mysql
To be clear, did you get Redis to start successfully?
obsidian charm
nope
and nothing in the mysql logs
That is redis log
twas a permission issue
abstract grove
They both look like permission issues
abstract grove
ChatGPT is very useful if you can check if what you did worked afterwards, but just in case I'd recommend always including at the end of your prompt
"Also, give me the steps I would need to take to un-do this if it doesn't work or has unintended consequences. If I need to give you more information for you to know how to undo it, let me know what information you need."
obsidian charm
okay great cause my next plan is to somehow move the panel to my AWS instance and connect it back to this server it's currently on
but i dont want to lose servers that are spun up
abstract grove
Panel and Wings are completely separate. You can migrate the panel without worrying about losing servers; you'll just need to connect it to Wings again.
obsidian charm
yeah i gotta figure out how to move the panel and blueprint and all that and then connect it back.
Im trying to do this in production soooo danger
abstract grove
Just don't remove anything from your current server until AFTER everything's working on the new one.
abstract grove
This look right?
No, that looks like AI hallucinations. Use the migrate guide for the panel.
https://gist.github.com/trenutoo/c18258658bef28e73b24d11d02d24915#migrating-panel
You'll have to update your Database Host user's host and your Wings machine's firewall afterwards as well.
Wings machine:
mariadb -u root -p
ALTER USER 'pterodactyluser'@'127.0.0.1' RENAME TO 'pterodactyluser'@'new_panel_ip';
ufw allow from new_panel_ip to any port 3306 proto tcp
Panel:
obsidian charm
Okay so far I got the node setup and green heartbeat. Im working on allocations now. After I finish that I should run those commands above correct?
to clarify I have the node on the main server connected to the panel on the aws
abstract grove
Yes, but obviously replacing new_panel_ip with the actual IP of your AWS panel.
obsidian charm
got it
i'll give it a shot. i messed up and put the public ip in the ip portion so now i have to delete 89 pages of allocations
a command for this would be goals
obsidian charm
container@pterodactyl~ Server marked as offline...
[Pterodactyl Daemon]: Server crash was detected but an error occurred while handling it.
[Pterodactyl Daemon]: ---------- Detected server process in a crashed state! ----------
[Pterodactyl Daemon]: Exit code: 128
[Pterodactyl Daemon]: Out of memory: false
[Pterodactyl Daemon]: Aborting automatic restart, last crash occurred less than 60 seconds ago.```What potentially can cause this?
Error Event [47383a41-5dab-4d84-b2b9-9c47f7c99a59]: environment/docker: failed to start container: Error response from daemon: driver failed programming external connectivity on endpoint cfe434e9-7a9b-4fb9-beea-b98b3b1130fa (7945d1bc63e6f60f5aac4cd901dd3c5ff28414da49940c5ecb1309ed6a5cc787): Bind for 192.168.1.170:25565 failed: port is already allocated
oh i see. so i have to set the ip of the node machine or the panel machine?