So, I took the source from Unbound main site for version 1.15 and made a
package out of it using the deb-source.
Guess what, it is now running for a week and we didn't see a single crash.
Just my 2 cents but I think that Debian maintainers should consider
going for better than 1.13 now.
Package: tomcat9
Version: 9.0.16-4
In debian 10 (buster)
/usr/share/tomcat9/bin/catalina.sh is ignoring the CATALINA_PID
variable therefore does not generate a PID file accordingly.
example startup command :
set -a; JAVA_HOME="/usr/lib/jvm/java-11-openjdk-amd64"; source
"/etc/default/tomcat9";
Hi,
You are right Ben, this was the culprit.
The bottom line is, in a previous version of the debian distribution the
busybox package was called "busybox-cvs-static".
But at a time it just gone to "busybox-static", so when doing the normal
procedure of
apt-update
apt-upgrade
apt-distupgrade
it i
I did test once again with a different machine, same result.
It seems really that initramfs is the culprit here, the old 3.2 kernel from
debian7 boots fine.
when thrown back in busybox with the (initramfs) prompt you can do vgchange
-ay and access partitions.
So there's no valid reason to get an
Hello,
Thanks for your concern.
On 27 September 2018 at 10:32, Ben Hutchings wrote:
>
> What is the kernel command line? (Run "cat /proc/cmdline" to show it.)
>
With the bootable kernel 3.2
# uname -a
Linux ahs-clone 3.2.0-6-686-pae #1 SMP Debian 3.2.102-1 i686 GNU/Linux
# cat /etc/debian_v
5 matches
Mail list logo
