I didn't know about default_client_keytab_name. That's definitely handy,
so no more k5start needed!
Thanks for your explanation, it makes sense. I'll give it a whirl,
because I'll need to add testing instructions to the change that will be
proposed.
** Changed in: openldap (Ubuntu)
This was fixed with https://usn.ubuntu.com/3722-1/
** Changed in: clamav (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1782695
Title:
And you got that information from the catalina log file I presume? We
are wanting to add that to the log collecting tool, so we would have
this info right from the start, instead of having to ask for it.
--
You received this bug notification because you are a member of Ubuntu
Server, which is
"/etc/krb5/user/389/client.keytab" feels like a local modification you
made, to store keytab files somewhere under /etc/krb5. I suggest you add
an apparmor exception in /etc/apparmor.d/local/usr.sbin.slapd.
Unless I'm wrong and that directory is being used as a standard location
by some package.
Thanks for filing this bug in Ubuntu.
I just tried an Ubuntu release upgrade from Trusty to Xenial with mysql
5.5 installed and configured, and it finished without issues. I even
selected that option to not restart services automatically, thinking
that would mess up the upgrade, but it still
The change from pssh to parallax was done by upstream in Jan 2015:
* Fri Jan 9 2015 Kristoffer Grönlund and many others
...
- high: crm_pssh: Switch to python-parallax over pssh (bnc#905116)
This wasn't caught by the packager, nor by the automatic dependency
generator when building the package.
Thanks
This is being handled by the security team as we speak, and should be
released in a few days. I'll close this bug when that happens.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to clamav in Ubuntu.
Trusty verification
Confirming the problem:
ubuntu@trusty-smart-1209085:~$ sudo apt-get install smartmontools
--no-install-recommends
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no
Logs from /var/log/rabbitmq might be useful here
** Also affects: rabbitmq-server (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Upgrade to Queens causing crashing
+ Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment
--
You received this bug
