Your message dated Sun, 22 Nov 2020 17:08:10 +0200
with message-id
<cahj_tlcwogptxpvmresaf6ogghvhqqzxpdu3kkd5w437qen...@mail.gmail.com>
and subject line Re: [debian-mysql] Bug#966196: mariadb-server-10.3: Mariadb
10.3.22 fails to start after Stretch update, Failed at step EXEC spawning
/etc/mysql/debian-start: No such file or directory
has caused the Debian Bug report #966196,
regarding mariadb-server-10.3: Mariadb 10.3.22 fails to start after Stretch
update, Failed at step EXEC spawning /etc/mysql/debian-start: No such file or
directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
966196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966196
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mariadb-server-10.3
Version: 1:10.3.22-0+deb10u1
Severity: normal
Dear Maintainer,
After updating Stretch mariadb fails with
Jul 25 01:19:38 dog systemd[23576]: mariadb.service: Failed at step EXEC
spawning /etc/mysql/debian-start: No such file or directory
Jul 25 01:19:38 dog systemd[1]: mariadb.service: Control process exited,
code=exited, status=203/EXEC
Jul 25 01:19:40 dog systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jul 25 01:19:40 dog systemd[1]: Failed to start MariaDB 10.3.22 database server.
The file debian-start actually has some text inside it saying this file is no
longer needed, I deleted it once and got the same error.
I recreated it and it all worked again.
It seems to have vanished after the update bringing the same situation back.
A workaround is to create the file.
-- System Information:
Debian Release: 10.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mariadb-server-10.3 depends on:
ii adduser 3.118
ii debconf [debconf-2.0] 1.5.71
ii galera-3 25.3.25-2
ii gawk 1:4.2.1+dfsg-1
ii iproute2 4.20.0-2
ii libc6 2.28-10
ii libdbi-perl 1.642-1+b1
ii libgnutls30 3.6.7-4+deb10u4
ii libpam0g 1.3.1-5
ii libstdc++6 8.3.0-6
ii lsb-base 10.2019051400
ii lsof 4.91+dfsg-1
ii mariadb-client-10.3 1:10.3.22-0+deb10u1
ii mariadb-common 1:10.3.22-0+deb10u1
ii mariadb-server-core-10.3 1:10.3.22-0+deb10u1
ii passwd 1:4.5-1.1
ii perl 5.28.1-6
ii psmisc 23.2-1
ii rsync 3.1.3-6
ii socat 1.7.3.2-2
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages mariadb-server-10.3 recommends:
ii libhtml-template-perl 2.97-1
Versions of packages mariadb-server-10.3 suggests:
ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-1
pn mariadb-test <none>
pn netcat-openbsd <none>
pn tinyca <none>
-- Configuration Files:
/etc/logcheck/ignore.d.paranoid/mariadb-server-10_3 [Errno 13] Permission
denied: '/etc/logcheck/ignore.d.paranoid/mariadb-server-10_3'
/etc/logcheck/ignore.d.server/mariadb-server-10_3 [Errno 13] Permission denied:
'/etc/logcheck/ignore.d.server/mariadb-server-10_3'
/etc/logcheck/ignore.d.workstation/mariadb-server-10_3 [Errno 13] Permission
denied: '/etc/logcheck/ignore.d.workstation/mariadb-server-10_3'
/etc/mysql/debian-start [Errno 13] Permission denied: '/etc/mysql/debian-start'
/etc/mysql/mariadb.conf.d/50-server.cnf changed [not included]
-- debconf information excluded
--- End Message ---
--- Begin Message ---
Hello!
In mariadb-server-10.3.install we do have:
debian/additions/debian-start etc/mysql
Thus debian-start should exist on all systems. If you don't have it,
you've done some local change.
I will close this issue as a won't fix since there was no follow-up
from the submitter.
--- End Message ---
