While I agree that this may never have been guaranteed, it has been
working with all previous init systems. For me, the implied policy of
using rc.local is: Run after all other init stuff has finished.
For example, https://github.com/puppetlabs/razor-server uses modifying
rc.local in order to
Public bug reported:
The current definition in `/lib/systemd/system/rc-local.service` uses
`After=network.target`, which is pretty useless, as `network.target`
according to
http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ only has
relevance during shutdown, which never happens for
Thanks for the fast fix, is there already a package built from the patch
somewhere that I could test?
Also you might want to amend the title of the bug, as enabling the
service is in fact performed properly, systemctl just throws an error in
the end when it should simply terminate successfully
*** This bug is a duplicate of bug 1447807 ***
https://bugs.launchpad.net/bugs/1447807
** This bug has been marked a duplicate of bug 1447807
systemctl enable fails to enable a SysV service
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I wouldn't agree that this is purely cosmetical, as it breaks things
like Chef automation: https://github.com/gmiranda23/ntp/issues/105
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447807
Title:
*** This bug is a duplicate of bug 1447807 ***
https://bugs.launchpad.net/bugs/1447807
** This bug has been marked a duplicate of bug 1447807
systemctl enable fails to enable a SysV service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Tested and confirmed working, thanks again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447807
Title:
systemctl enable shows error on enabling a SysV service
To manage notifications about this
Did you define ERL_EPMD_ADDRESS in your rabbitmq-env.conf?
Then you would be hitting
https://bugs.launchpad.net/ubuntu/+source/erlang/+bug/1374109 and you
can find a possible workaround there.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Did you define ERL_EPMD_ADDRESS in your rabbitmq-env.conf?
Then you would be hitting
https://bugs.launchpad.net/ubuntu/+source/erlang/+bug/1374109 and you
can find a possible workaround there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Looking at the source code a bit, I see that in
systemctl.c:enable_sysv_units there is a comment that it should
reshuffle the args array, but it seems it never does that? So
strv_isempty(names) in enable_unit never matches, causing the call to
systemd which is failing, because there is no unit
Public bug reported:
root@node10:~# systemctl enable ntp
Public bug reported:
root@node10:~# systemctl enable ntp
wont-fixing the nova side will leave it broken for quite some time
until the backport has made its way into all relevant distro images. I'd
prefer to add your patch into nova code as workaround for older libvirt
versions.
--
You received this bug notification because you are a member of Ubuntu
wont-fixing the nova side will leave it broken for quite some time
until the backport has made its way into all relevant distro images. I'd
prefer to add your patch into nova code as workaround for older libvirt
versions.
--
You received this bug notification because you are a member of Ubuntu
I think there is still something wrong with the packaging here, I get:
~# apt-get install percona-xtradb-cluster-5.6/proposed-updates
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'percona-xtradb-cluster-5.6-dbg' for regex
Ah, right, that works better now, thanks and sorry for disturbing. ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448533
Title:
Packaging bug prevents install of PXC 5.6
To manage notifications
@Andy: So 3.16.0-34 is the kernel with the fix? Any chance that it will
also be backported to the 3.13 series?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413540
Title:
Trusty soft lockup issues
I tested http://launchpadlibrarian.net/208123057/rabbitmq-
server_3.5.1-2_all.deb and it works fine for me.
It would be great to see this backported to vivid.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
I tested http://launchpadlibrarian.net/208123057/rabbitmq-
server_3.5.1-2_all.deb and it works fine for me.
It would be great to see this backported to vivid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: python-glanceclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1342080
Title:
glance api is tracebacking with error: [Errno
Still seeing this in Ubuntu Vivid with python-
glanceclient=1:0.15.0-0ubuntu1, any chance to get this backported?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1342080
Title:
glance api is
** Also affects: python-glanceclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-glanceclient in Ubuntu.
https://bugs.launchpad.net/bugs/1342080
Title:
glance api is
Tested
https://launchpad.net/ubuntu/+source/neutron/1:2015.1.1-0ubuntu2/+build/7782259/+files
/neutron-plugin-neutron-agent_2015.1.1-0ubuntu2_all.deb and it solves
the issue for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification
Tested
https://launchpad.net/ubuntu/+source/neutron/1:2015.1.1-0ubuntu2/+build/7782259/+files
/neutron-plugin-neutron-agent_2015.1.1-0ubuntu2_all.deb and it solves
the issue for me.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification
@Dariusz: The package for Vivid works fine for me, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374109
Title:
epmd does not support binding to an IPv4 address anymore
To manage
Dariusz: I'm seeing the same issue, but running on Vivid, could you add
packages for that to your repo so I could test your solution?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374109
Title:
Public bug reported:
There seems to be some issue with the udev triggers, either they do not
happen properly for partitions or they happen too early in the boot
process.
If I do a "ceph-disk activate /dev/sdXX" after the system has booted,
the OSD is starting just fine.
If I do a "udevadm
Public bug reported:
There seems to be some issue with the udev triggers, either they do not
happen properly for partitions or they happen too early in the boot
process.
If I do a "ceph-disk activate /dev/sdXX" after the system has booted,
the OSD is starting just fine.
If I do a "udevadm
Public bug reported:
The systemd service generated from /etc/init.d/apache2 via systemd-sysv-
generator contains the line
RemainAfterExit=yes
causing systemd to ignore crashes of the service. In order to reproduce
this, add a non-existing address to /etc/apache2/ports.conf, which will
cause the
Public bug reported:
The systemd service generated from /etc/init.d/apache2 via systemd-sysv-
generator contains the line
RemainAfterExit=yes
causing systemd to ignore crashes of the service. In order to reproduce
this, add a non-existing address to /etc/apache2/ports.conf, which will
cause the
Public bug reported:
There is a symlink in /lib/systemd/system from udev.service to systemd-
udevd.service, however, running systemctl is-active udev returns
unknown instead of active initially. This can be solved by running
systemctl status udev once, but for monitoring the service it would be
This may in fact be a bug of systemd in general, as is seems to affect
all service aliases created via symlinks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488954
Title:
systemctl is-active
** Also affects: systemd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488954
Title:
systemctl is-active udev returns unknown
To manage notifications
Public bug reported:
When upgrading libvirt-bin after adding the stable/liberty cloud-ppa,
I'm getting this error:
ubuntu@jr2:~$ sudo apt-get install libvirt-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were
Public bug reported:
When upgrading libvirt-bin after adding the stable/liberty cloud-ppa,
I'm getting this error:
ubuntu@jr2:~$ sudo apt-get install libvirt-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were
I think there is some confusion here. As I understand it, the part that
was fixed in libvirt was changing the API so that now it is possible to
define a subset of block devices to be copied during migration. Now to
fix the original issue, another patch in nova will be needed, that uses
this
I think there is some confusion here. As I understand it, the part that
was fixed in libvirt was changing the API so that now it is possible to
define a subset of block devices to be copied during migration. Now to
fix the original issue, another patch in nova will be needed, that uses
this
This is the expected behaviour if your DHCP server also specifies a
classless static route, see RFC 3442:
If the DHCP server returns both a Classless Static Routes option and a
Router option, the DHCP client MUST ignore the Router option.
** Changed in: isc-dhcp (Ubuntu)
Status: Confirmed
Public bug reported:
This fixes the username deprecation issue, see
https://bugs.launchpad.net/python-keystoneclient/+bug/1552634
** Affects: python-keystoneauth1 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Running with 1:18.3-dfsg-1ubuntu3 on Xenial, the issue seems to have
been fixed for me, can anyone confirm this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374109
Title:
epmd does not support
** Changed in: keepalived (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403137
Title:
service keepalived reload leaks file descriptors
To manage
I am seeing the same issue on some of my OpenStack compute nodes,
interestingly those which seem to have a newer CPU than others.
Affected CPU: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
Mapped in guest to: Intel Core i7 9xx (Nehalem Class Core i7)
Unaffected Host CPU: Intel(R) Xeon(R) CPU
Sorry for the delay, I must admin that I'm not sure about that anymore.
I tried reproducing this issue with a current installation of Wily, but
failed. So I guess we can assume this to be invalid now.
** Changed in: ceph (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
You can set "osd pool default pg num" and "osd pool default pgp num" to
some higher value in your ceph.conf before creating pools if you want
some higher values than the default and do not want to specify it on the
command line every time.
For more complex setups however, you want to match the pg
I can reproduce this on Wily with
# apt-cache policy ceph
ceph:
Installed: 0.94.5-0ubuntu0.15.10.1
Candidate: 0.94.5-0ubuntu0.15.10.1
Version table:
*** 0.94.5-0ubuntu0.15.10.1 0
500 http://eu.archive.ubuntu.com/ubuntu/ wily-updates/main amd64
Packages
100
** Also affects: os-prober (Ubuntu)
Importance: Undecided
Status: New
** Changed in: os-prober (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
Forgot to mention that the Ceph cluster has to be under write load in
order to reproduce, i.e. running something like
rados -p rbd bench 600 write -t 1 --show-time --run-length 60
There is no effect of running os-prober if the cluster is idle. Based
with that information, though, I can also
Function ro_partition in /usr/share/os-prober/common.sh makes a
partition read-only. This is called in /usr/lib/os-probes/50mounted-
tests before trying to mount the partition being probed with all
possible fs-types. Obviously this will break all other processes trying
to write to this partition
Sorry for the delay, I must admin that I'm not sure about that anymore.
I tried reproducing this issue with a current installation of Wily, but
failed. So I guess we can assume this to be invalid now.
** Changed in: ceph (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
You can set "osd pool default pg num" and "osd pool default pgp num" to
some higher value in your ceph.conf before creating pools if you want
some higher values than the default and do not want to specify it on the
command line every time.
For more complex setups however, you want to match the pg
I can reproduce this on Wily with
# apt-cache policy ceph
ceph:
Installed: 0.94.5-0ubuntu0.15.10.1
Candidate: 0.94.5-0ubuntu0.15.10.1
Version table:
*** 0.94.5-0ubuntu0.15.10.1 0
500 http://eu.archive.ubuntu.com/ubuntu/ wily-updates/main amd64
Packages
100
** Also affects: os-prober (Ubuntu)
Importance: Undecided
Status: New
** Changed in: os-prober (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384062
Forgot to mention that the Ceph cluster has to be under write load in
order to reproduce, i.e. running something like
rados -p rbd bench 600 write -t 1 --show-time --run-length 60
There is no effect of running os-prober if the cluster is idle. Based
with that information, though, I can also
Function ro_partition in /usr/share/os-prober/common.sh makes a
partition read-only. This is called in /usr/lib/os-probes/50mounted-
tests before trying to mount the partition being probed with all
possible fs-types. Obviously this will break all other processes trying
to write to this partition
IMHO this is a bug for ceph-deploy, which is a separate project from
ceph itself. It should be solved with a new upstream version, probably
1.5.29, see also bug #1550853.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
IMHO this is a bug for ceph-deploy, which is a separate project from
ceph itself. It should be solved with a new upstream version, probably
1.5.29, see also bug #1550853.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This only affects the xenial package, in /lib/systemd/system/ceph-
osd@.service there is
ExecStartPre=/usr/lib/ceph/ceph-osd-prestart.sh --cluster ${CLUSTER}
--id %i --setuser ceph --setgroup ceph
where the options were just copied from the ExecStart but this triggers
Public bug reported:
This only affects the xenial package, in /lib/systemd/system/ceph-
osd@.service there is
ExecStartPre=/usr/lib/ceph/ceph-osd-prestart.sh --cluster ${CLUSTER}
--id %i --setuser ceph --setgroup ceph
where the options were just copied from the ExecStart but this triggers
** Description changed:
The main reason I would want this upgrade is the confusion regarding the
deprecation of the "username" vs. "user-name" options. This was only
resolved in upstream version 2.4.0 or later.
+ Current status is that when using "username" as option name in a config
+
Public bug reported:
When using OpenStack, we do not want the default network from installing
libvirt-bin to exist. We can remove the network after installing the
package, but that will remove the file
/etc/libvirt/qemu/networks/default.xml that is included in the package
and it might also
In my case I'm not starting vms directly, but via OpenStack nova, not
sure what happens there in detail and whether that might be a special
case. In my current setup, I can start 4 cirros instances and get about
490 out of 512 tasks used, starting a 5th instance fails.
--
You received this bug
Public bug reported:
When starting virtual machines under libvirt, the qemu process is
accounted for in the TasksAccounting by systemd, see
http://paste.ubuntu.com/15667656/
This should probably not happen, similar to
https://bugs.launchpad.net/systemd/+bug/1564451 the proper solution IMHO
Right, this seems to be something local, I'll have to check where is
comes from. Still it behaves correctly for the "old" service name
without ".service" appended, so this still looks like a bug in deb-
systemd-invoke to me:
root@controller-node11:~# /usr/sbin/policy-rc.d ceph-mon start
Just found out there is also a discussion on this issue going on
upstream:
http://permalink.gmane.org/gmane.comp.file-systems.ceph.devel/30552
Though that should be no argument not to fix it locally first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, but this is not fixed for me, maybe I wasn't expressing clearly
enough my intentions:
root@controller-node13:~# systemctl status ceph-create-keys
* ceph-create-keys.service - Create Ceph client.admin key when possible
Loaded: loaded (/lib/systemd/system/ceph-create-keys.service; static;
I think doing socket based activation properly is non-trivial, as there
are people wanting apache to run only on non-standard ports, e.g. when
deploying OpenStack services. So having a default setup that causes
systemd to listen on port 80, without checking whether the apache config
really does
Public bug reported:
There are other options for providing volume backends like RBD, so
having a hard dependency on open-iscsi seems bad, as it prevents admins
from deinstalling the unneeded package. Please remove the dependency or
at least downgrade to Recommends: or Suggests:
** Affects: nova
Public bug reported:
Keystone PKI tokens have been deprecated for security reasons,
deployments should switch to using Fernet tokens instead.
So please remove the call to "keystone-manage pki_setup" from
keystone.postinst at least for Xenial.
** Affects: keystone (Ubuntu)
Importance: Low
Public bug reported:
The service definition in /lib/systemd/system/nova-compute.service
contains
After=libvirtd.service
however that service does not exist, the correct service name would be
libvirt-bin.service. As a result, nova-compute is started too early and
fails because it cannot talk to
Version 1.5.31-0ubuntu1 is now in Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550853
Title:
package upgrade request
To manage notifications about this bug go to:
I'm now seeing the warnings also in the postinst for dmeventd, so
probably deb-systemd-invoke should be fixed as being the common
denominator.
** Also affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ceph (Ubuntu)
Status: New => Invalid
--
** Description changed:
- This log is from installing the pre-release packages, but I got the same
- warnings when installing 10.0.5 earlier:
+ When having a custom /usr/sbin/policy-rc.d, there are various warnings
+ during installation, like:
Preparing to unpack
Public bug reported:
Currently there is some output from usermod during postinst, even if
there is no change to the user:
Setting up ceph-common (10.1.1-0ubuntu1) ...
usermod: no changes
So just add a "2> /dev/null" to the call to usermod like it is done with
all the other user management calls
Public bug reported:
If the config for the dashboard or apache2 in general is not working,
the removal of openstack-dashboard-ubuntu-theme fails because there is
no graceful error handling in the postrm script. E.g. I am getting:
# apt-get -q -y purge openstack-dashboard-ubuntu-theme
STDOUT:
Public bug reported:
If the config for the dashboard or apache2 in general is not working,
the removal of openstack-dashboard-ubuntu-theme fails because there is
no graceful error handling in the postrm script. E.g. I am getting:
# apt-get -q -y purge openstack-dashboard-ubuntu-theme
STDOUT:
Public bug reported:
This log is from installing the pre-release packages, but I got the same
warnings when installing 10.0.5 earlier:
Preparing to unpack
.../ceph_10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201_amd64.deb ...
deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code
Public bug reported:
This log is from installing the pre-release packages, but I got the same
warnings when installing 10.0.5 earlier:
Preparing to unpack
.../ceph_10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201_amd64.deb ...
deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code
I just found out that the limit is not applied after a reboot, it
appears that this only happens when the service is (re-)started manually
from the shell.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
I just found out that the limit is not applied after a reboot, it
appears that this only happens when the service is (re-)started manually
from the shell.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The main reason I would want this upgrade is the confusion regarding the
deprecation of the "username" vs. "user-name" options. This was only
resolved in upstream version 2.4.0 or later.
Debian has just created a new version, it would also be nice to try to
stay in sync
Hmm, on a cloud instance this looks different, even when logged in
multiple time, the output only shows the master process:
# systemctl status ssh
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset:
enabled)
Active: active
Hmm, on a cloud instance this looks different, even when logged in
multiple time, the output only shows the master process:
# systemctl status ssh
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset:
enabled)
Active: active
Thanks to some help in #systemd I could find the cause: On the affected
systems libpam-systemd was not installed. So maybe it would make sensu
to turn this into a stronger dependency than "recommended", at least in
combination with openssh-server.
--
You received this bug notification because
Thanks to some help in #systemd I could find the cause: On the affected
systems libpam-systemd was not installed. So maybe it would make sensu
to turn this into a stronger dependency than "recommended", at least in
combination with openssh-server.
--
You received this bug notification because
Public bug reported:
Cinder, Neutron and Nova use rootwrappers that allow selected commands
to be executed with root privileges via sudo. If an adminstrator chooses
to enable sudo logging for security reasons, this will cause a lot of
files being created, leading to filled up file systems pretty
Public bug reported:
Cinder, Neutron and Nova use rootwrappers that allow selected commands
to be executed with root privileges via sudo. If an adminstrator chooses
to enable sudo logging for security reasons, this will cause a lot of
files being created, leading to filled up file systems pretty
>From a hardening perspective, it certainly hurts having unneeded
packages installed, so please re-raise the priority of this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cinder in Ubuntu.
https://bugs.launchpad.net/bugs/1079466
>From a hardening perspective, it certainly hurts having unneeded
packages installed, so please re-raise the priority of this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079466
Title:
Public bug reported:
This may be useful for an unexperienced user trying to run ceph on a
small setup, but for an automated deployment of a ceph cluster, it is
pretty annoying that there may be daemons trying to create credentials
that will allow access to the whole cluster if only the new
Public bug reported:
This may be useful for an unexperienced user trying to run ceph on a
small setup, but for an automated deployment of a ceph cluster, it is
pretty annoying that there may be daemons trying to create credentials
that will allow access to the whole cluster if only the new
How did you install ceph and which version exactly? Running as ceph
should only happen with >= 9.2, which is available on Xenial.
If I install ceph=10.0.3-0ubuntu1 on a new machine, /var/lib/ceph and
/var/run/ceph have ceph:ceph as owner, which looks fine to me. One could
discuss the ownership of
Public bug reported:
When started via systemd, there is a default limit of 512 Tasks, and it
seems that each thread counts as a different task:
# systemctl status ceph-osd@2
Public bug reported:
When started via systemd, there is a default limit of 512 Tasks, and it
seems that each thread counts as a different task:
# systemctl status ceph-osd@2
How did you install ceph and which version exactly? Running as ceph
should only happen with >= 9.2, which is available on Xenial.
If I install ceph=10.0.3-0ubuntu1 on a new machine, /var/lib/ceph and
/var/run/ceph have ceph:ceph as owner, which looks fine to me. One could
discuss the ownership of
Do your sleep processes show up in the output of "systemctl status
ssh.service" in the CGroup section? For me they do (sample with just one
process backgrounded):
# systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service;
Do your sleep processes show up in the output of "systemctl status
ssh.service" in the CGroup section? For me they do (sample with just one
process backgrounded):
# systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
Loaded: loaded (/lib/systemd/system/ssh.service;
This is still true for the Mitaka packages in Xenial, making it rather
difficult to create a working installation for new installations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506665
Title:
Public bug reported:
I have installed percona-xtradb-cluster-server-5.6 on my Xenial server
and try to set the root password with mysqladmin:
# mysqladmin --user=root --password='' password 'secure'
mysqladmin: [Warning] Using a password on the command line interface can be
insecure.
Warning:
Neutron version is Mitaka, in my case 2:8.0.0-0ubuntu1 from Ubuntu
Xenial, but looking at the code the behaviour still seems to be
unmodified in master.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With version 2:8.1.0-0ubuntu0.16.04.2 from xenial-proposed the stale pid
file is removed and the l3-agent can start the new keepalived
successfully.
Maybe we could also get rid of this error that is still being logged:
2016-05-20 10:43:00.913 16153 ERROR neutron.agent.linux.utils [-] Unable
to
1 - 100 of 156 matches
Mail list logo
