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 automa
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
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.se
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
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
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
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
