[Bug 1902744] [NEW] MariaDB Update changes ProtectHome option, breaking MySQL
Public bug reported: Unpacking mariadb-common (1:10.1.47-0ubuntu0.18.04.1) over (1:10.1.44-0ubuntu0.18.04.1) ...^M Setting up mariadb-common (1:10.1.47-0ubuntu0.18.04.1) ...^M Log ended: 2020-11-03 06:04:27 We have "ProtectHome=false" because we've relocated mysql data to /home/mysql An automatic update this morning proceeded to overwrite the entire file /etc/systemd/system/multi-user.target.wants/mariadb.service, reverting the option back to default of "true". As a result, MariaDB would no longer start and the server was down for over 1000 customers for 3 hours. I really don't want to chattr +i that file. Please stop over-writing an updated file with user configurable options! ** Affects: mariadb-10.1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902744 Title: MariaDB Update changes ProtectHome option, breaking MySQL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1902744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902744] Re: MariaDB Update changes ProtectHome option, breaking MySQL
Where is the drop-in directory supposed to exist in Ubuntu? Supposedly you can find out with the systemctl status command, but there is nothing in the output. Nor can I find anything in the default service file that "includes" a specific folder. # systemctl status mariadb.service ● mariadb.service - MariaDB 10.1.47 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-11-03 09:09:17 MST; 2h 47min ago Docs: man:mysqld(8) https://mariadb.com/kb/en/library/systemd/ Process: 20863 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 20860 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS) Process: 20723 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS) Process: 20721 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 20720 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS) Main PID: 20833 (mysqld) Status: "Taking your SQL requests now..." Tasks: 36 (limit: 4915) CGroup: /system.slice/mariadb.service └─20833 /usr/sbin/mysqld -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902744 Title: MariaDB Update changes ProtectHome option, breaking MySQL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1902744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902744] Re: MariaDB Update changes ProtectHome option, breaking MySQL
Disregard. Creating the file in /etc/systemd/system/mariadb.service.d/ works fine. On Ubuntu you must mkdir -p first, since /etc/systemd/system does not exist If anyone else stumbles across this annoying issue: mkdir -p /etc/systemd/system/mariadb.service.d cat > /etc/systemd/system/mariadb.service.d/dontprotecthome.conf << EOL [Service] ProtectHome=false EOL systemctl daemon-reload systemctl restart mariadb That's what I get for googling how to disable ProtectHome in Ubuntu. First answer was to modify a system file that is overwritten when the package is updated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902744 Title: MariaDB Update changes ProtectHome option, breaking MySQL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1902744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873186] [NEW] knockd does not work on additional IP address of a NIC
Public bug reported: systemd networkd in use. OVH server. I've been pulling my hair out for an hour trying to get knockd to work on a secondary IP assigned to the primary NIC. (It works fine if I change the IP to the primary when knocking, but that is not the required or desired use.) I've tried adding the secondary IP as a virtual NIC named "failover", then configuring knockd to use the NIC "failover". This does not work, and "ifconfig failover" actually shows no packets going through the NIC, even though the IP configured on the virtual NIC is working fine. I can't find any docs or answered questions about this issue. I was hoping to stumble upon an undocumented option to force knockd to listed on a particular IP. If knockd is really attached to the NIC and supposedly just listening to syn for a particular port, then it should work. Instead, it appears to be latching on the the primary IP of the NIC and ignoring all other IP's on that NIC. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" Kernel 4.15.0-96-generic knockd package: 0.7-1ubuntu1.18.04.2 amd64 Any help is much appreciated. ** Affects: knockd (Ubuntu) Importance: Undecided Status: New ** Tags: ip secondary -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873186 Title: knockd does not work on additional IP address of a NIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1873186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873186] Re: knockd does not work on additional IP address of a NIC
To clarify "does not work", the TCP (or UDP) knock on the configured port is never detected when using the secondary IP. If I switch to the primary IP, it works exactly as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873186 Title: knockd does not work on additional IP address of a NIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1873186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873186] Re: knockd does not work on additional IP address of a NIC
Debug mode on, the PCAP rule shows the correct secondary IP, but it will not actually detect the knock on that IP. Adding pcap expression for door '25568': (dst host xx.xx.xx.76 and (((tcp dst port 25568 or 25568 or 25568) and tcp[tcpflags] & tcp-syn != 0))) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873186 Title: knockd does not work on additional IP address of a NIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1873186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873186] Re: knockd does not work on additional IP address of a NIC
YES! That fixed the issue! THANK YOU! I was up until 3 AM trying to sort that out. No clue how I missed that directive in the man page. Zombie eyes, I guess. One this that still bothers me - As I stated in the debug comment, the PCAP filters are INDEED CORRECT and show the correct (supposed) IP in the expression when I tried using a virtual NIC, so why wasn't that actually working as expected? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873186 Title: knockd does not work on additional IP address of a NIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1873186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
