Project akk-stack - unable to start mariadb

[Skream]

Mariadb will install fine and start itself

docker run --name mariadbtest -e MYSQL_ROOT_PASSWORD=mypass -p 3306:3306 -d docker.io/library/mariadb:10.3
Unable to find image 'mariadb:10.3' locally
10.3: Pulling from library/mariadb
08c01a0ec47e: Already exists
a2bcb14c13a1: Already exists
29c56760f879: Already exists
a95000a218fc: Already exists
a765d76e68d9: Already exists
c6945738f085: Already exists
62787b7c58c5: Already exists
c14f6657b501: Pull complete
020be96129ba: Pull complete
77a486976bcd: Pull complete
d3911f3f8652: Pull complete
Digest: sha256:a25e7c87fe20c6d035fe81003937a8d732574ecf544 66d0294da3423b64af80c
Status: Downloaded newer image for mariadb:10.3
33a8413efa502c1430fc64215cb453cb55f670dfede9af27ba f0a2c2290036e8
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
33a8413efa50 mariadb:10.3 "docker-entrypoint.s…" 8 minutes ago Up 8 minutes 0.0.0.0:3306->3306/tcp, :::3306->3306/tcp mariadbtest

At this point its really starting to look like an issue between Ubuntu 20.04 and this build.

[Skream]

Curiously enough, using 0.0.0.0 as the IP means it has worked

I await someone to tell me exactly why this is a bad idea ....

[Huppy]

Originally Posted by Skream

Curiously enough, using 0.0.0.0 as the IP means it has worked

I await someone to tell me exactly why this is a bad idea ....

Using that as a bind address ? yes, it's best to do that, especially in the mysql/maria config.

[Skream]

Originally Posted by Huppy

Using that as a bind address ? yes, it's best to do that, especially in the mysql/maria config.

No, I meant ...

make set-vars port-range-high=7030 ip-address=0.0.0.0

From https://github.com/Akkadius/akk-stack#installation


Although I am now starting to think I should run this in a VM on my local server. That way it can have exclusive use of all the ports as it will have its own IP. Altho, its only a 4 Core/32 GB box.

[Freejack]

Originally Posted by Skream

No, I meant ...



From https://github.com/Akkadius/akk-stack#installation


Although I am now starting to think I should run this in a VM on my local server. That way it can have exclusive use of all the ports as it will have its own IP. Altho, its only a 4 Core/32 GB box.

In all honesty running it in the docker container is best. Uses less resources and has less overhead. In docker you are getting the bare metal experience in performance. Also you are running UFW on this machine? is it directly on the internet? if not and it is behind a firewall for your network, remove it. All it is doing is blocking intranet traffic when your behind another existing firewall.

This could also be causing your bind issues. Even if you turned it off I have had the experience of it still blocking ports and had to remove it to be able to use said ports on the IP.

[Skream]

Originally Posted by Freejack

In all honesty running it in the docker container is best. Uses less resources and has less overhead. In docker you are getting the bare metal experience in performance. Also you are running UFW on this machine? is it directly on the internet? if not and it is behind a firewall for your network, remove it. All it is doing is blocking intranet traffic when your behind another existing firewall.

This could also be causing your bind issues. Even if you turned it off I have had the experience of it still blocking ports and had to remove it to be able to use said ports on the IP.

I fixed the bind issues once I used 0.0.0.0 as the IP. I said previously UFW was off and iptables is set correctly.

The thing about using a VM is that there are a lot of services running on this box that want different ports, running on VM isolates the PEQ server. Also I can start akk-stack up under Debian. Reading this forum it seems people have had a more stable experience with Debian than Ubuntu 20.04.

[Freejack]

Originally Posted by Skream

I fixed the bind issues once I used 0.0.0.0 as the IP. I said previously UFW was off and iptables is set correctly.

The thing about using a VM is that there are a lot of services running on this box that want different ports, running on VM isolates the PEQ server. Also I can start akk-stack up under Debian. Reading this forum it seems people have had a more stable experience with Debian than Ubuntu 20.04.

Yes you did fix the bind issue with 0.0.0.0, now do you understand why it worked? If not then you don't understand why I said you may have to remove UFW to properly fix this. UFW may be saying it is off when it actually is not.

Also switching versions of Linux that are built on each other is not really the answer, solving the issue is the answer. I have been using Linux for over 20 years and every version has a distinct purpose and way of doing things. Ubuntu is based on Debian, I use Linux Mint which is based on both. Inside my network I do not run iptables or UFW because it is all behind a pfsense firewall. Doing double duty is only necessary if I am trying to isolate a box due to it containing sensitive information. A game server in my network is not that box.

Linux is designed for you to use what is more comfortable for you. So switching flavors/versions is your choice. It does mean learning another way of doing things. Debian may work better for some people, I again am using Linux Mint and have been for 6 years successfully on all my servers from games to data.

I have used every major distro and have found issues with all, it comes down to what do you need and how comfortable are you working in it. Also each distro has a lag in updating to the newest drivers and other updates like wine which also if you need the newest for some things a rolling distro maybe required.

Also if you have a dekstop on that server you may want to install GUFW so you have a GUI for UFW. Setting your IP to 0.0.0.0 for bind allows it to bind to any IP which means more than likely UFW was blocking the IP of the box ports but not localhost/127.0.0.1.

Just some thoughts to give you some more info to ponder.