I think the best way forward here is to get a core dump, so we can have
a better idea of where the crash is happening.
I induced a crash in my test sssd container, and since I have apport installed,
a crash file was produced in /var/crash:
# ll /var/crash/
total 644
drwxrwxrwt 2 root root
Looking at this again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to sssd in Ubuntu.
https://bugs.launchpad.net/bugs/1684295
Title:
sssd fails with 'Exiting the SSSD. Could not restart critical service
[tpad].
To manage
Thanks for filing this bug in Ubuntu.
Could you please share your /etc/default/tftpd-hpa file? I believe it
may contain a syntax error
** Changed in: tftp-hpa (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Description changed:
There have been a number of microreleases of PHP 7.0 upstream since the
last update to Xenial (which corresponded to the last update in Zesty). As
it has been a few months, it feels appropriate to provide another
MRE update to php7.0. A number of critical security
** Also affects: php7.0 (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: php7.0 (Ubuntu Zesty)
Assignee: (unassigned) => Nish Aravamudan (nacc)
** Changed in: php7.0 (Ubuntu Zesty)
Status: New => In Progress
--
You received this bug notification because you
** Summary changed:
- [MRE] Please update to latest upstream release 7.0.24
+ [MRE] Please update to latest upstream release 7.0.25
** No longer affects: php7.0 (Ubuntu Trusty)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.0
Thanks for your config, @metze.
@hh68300, could you please try with the config options from @metze's
comment #13?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1585111
Title:
net
Yes, recommends are installed by default in this out-of-the box xenial
container I used. And yes, postgresql (server) is a recommends only.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
On Wed, Nov 1, 2017 at 7:26 AM, Andreas Hasenack wrote:
> It worked out of the box in artful, so the fix is somewhere in between
> xenial and artful.
I would check the changes in 7.4.1~dfsg-1 or 7.4.2+dfsg-1 or
7.4.3+dfsg-1.
Also, iirc (only vaguely possibly true),
On Wed, Nov 1, 2017 at 7:15 AM, Jan Gutter <1720...@bugs.launchpad.net> wrote:
> @arges
>
> Hi, would you need any more testing from us?
Nope, your part is done. All SRUs have to bake for 7 days in -proposed
to shake out regressions.
--
You received this bug notification because you are a
It worked out of the box in artful, so the fix is somewhere in between
xenial and artful.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/1729064
Title:
package bacula-director-pgsql
Thanks for filing this bug in Ubuntu.
I was able to confirm the problem on a fresh xenial container by just
running:
sudo apt install bacula-director-pgsql
That pulls in the postgresql 9.5 server.
What happens is that bacula tries to reach out to postgresql on the
localhost (if you accepted
I'm also unable to reproduce this on a fresh artful lxd container. We
need to find out what's different in that environment from yours.
The next person who reproduces this problem, could you please attach a
full "ps fauxw" output to this bug? Not filtering by the "openvpn"
string via grep,
I also tried an artful VM, with and without network (installed from the
cached download deb in the latter case).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1725525
Title:
This was fixed in 3.1.4-2 which was synced into ubuntu for zesty and
later.
Xenial does indeed show this behavior, but I don't think it's worth an
SRU to fix it. The exit code is still 0, and it's just a warning.
Maybe if there was another bug worth of an SRU, this fix could piggy
back on it.
Thanks for filing this bug in Ubuntu.
I believe what's happening is similar, if not identical, to bug
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1635491 which we
thought was resolved. I also filed an upstream bug with samba about it
because it looks like some cases are not yet sorted
16 matches
Mail list logo