I added a eoan task, and marked it as fix released, let's see how our
tooling displays this bug.
** Also affects: clamav (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: clamav (Ubuntu Eoan)
Status: New => Fix Released
--
You received this bug notification
Acknowledging that the bug still exists and is in our queue, but not at
high priority.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1832182
Title:
systemd unable to detect running apache
** Also affects: clamav (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: clamav (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: clamav (Ubuntu Eoan)
Importance: Undecided
Status: New
** No longer affects: clamav (Ubuntu Eoan)
**
Thanks for filing this bug in Ubuntu.
This was fixed in 0.101.1+dfsg-1 (debian bug http://bugs.debian.org/913020),
and is therefore fixed in Ubuntu eoan and later.diff --git
a/debian/usr.bin.freshclam b/debian/usr.bin.freshclam
index 90490ac6..df5cb5be 100644
--- a/debian/usr.bin.freshclam
+++
Thanks for filing this bug in ubuntu.
Could you please check in, or attach, /var/log/postgresql/ to see if
there is a record of this crash?
I note also that there have been further updates to postgresql 10 in
Ubuntu 18.04 since this bug report, have you upgraded, and did you see
this crash again
Hello Marcos,
sorry that it took this long to get this bug. Since then, many Ubuntu releases
have happened. If this is still happening with a more recent Ubuntu release,
please post an update here, in particular, with apache log files (from
/var/log/apache*/). I can also perfectly understand
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1425165
Title:
apache2 crashed with SIGSEGV in zend_accel_info()
To manage notifications about this
Hi Petrida,
could you please elaborate on why you changed the bug status from
incomplete to confirmed without providing the requested information from
comment #95?
** Changed in: openssh (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a
There seems to be a non-infinite open files limit in containerd in eoan
(checked in a vm, not lxd, just to be sure):
root@eoan-containerd:~# cat /proc/$(pidof containerd)/limits |grep "Max open
files"
Max open files1048576 1048576 files
