Public bug reported:
during the distribution upgrade to ubuntu 9.10 a message appeared that
dhcp3-server could not be installed
I guess this happend because i renamed the dhcp3-server start script in the
init.d directory
ProblemType: Package
Architecture: amd64
Date: Sun Nov 1 16:20:47 2009
Di
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34875261/Dependencies.txt
** Attachment added: "VarLogDistupgradeAptlog.gz"
http://launchpadlibrarian.net/34875262/VarLogDistupgradeAptlog.gz
** Attachment added: "VarLogDistupgradeApttermlog.gz"
http://launchpadlibra
ls /etc/init.d:
acpid
acpi-support
alsa-utils
alsa-utils~
anacron
apparmor
apport
atd
atieventsd
avahi-daemon
binfmt-support
bluetooth
bootlogd
brltty
console-setup
cron
cups
dbus
ddclient
dhcp3-server_manual
dkms_autoinstaller
dmesg
dns-clean
firewall
gdm
grub-common
gssd
hal
halt
hotkey-setup
hw
Public bug reported:
Binary package hint: rabbitmq-server
I'm using Ubuntu 10.10 on Dell Precision M4500. If rabbitmq-server is
running and I start shutdown it halts and never shutdown. Last text on
the screen is:
--
init: Disconnected from system bus
init: dbus main process (1240) killed by TER
*** This bug is a duplicate of bug 670289 ***
https://bugs.launchpad.net/bugs/670289
This bug is a duplicate of bug #670289.
** This bug has been marked a duplicate of bug 670289
Laptop won't shut down with rabbitmq running
* You can subscribe to bug 670289 by following this link:
https:
Public bug reported:
# lsb_release -rd
Description:Ubuntu 15.04
Release:15.04
# apt-cache policy mysql-server-5.6
mysql-server-5.6:
Installed: 5.6.24-0ubuntu2
Candidate: 5.6.24-0ubuntu2
Version table:
*** 5.6.24-0ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ vivid/mai
Would it probably make sense to backport the systemd-related
improvements [1] from 5.7 to 5.6. Although they're not perfect yet,
they're a huge improvement compared to the current hacks required to
make mysqld behave more or less sane in systemd environments.
[1] http://mysqlserverteam.com/mysql-5
I dug a bit deeper and it turned out the problem here is caused by port
3306 already being occupied by another local test-container and
therefore mysqld aborting on startup.
So in the end, the problem could be reduced to:
when mysqld fails to start (as defined in ExecStart=), the 'mysqladmin ping'
Public bug reported:
# lsb_release -rd
Description: Ubuntu 15.04
Release: 15.04
# apt-cache policy apache2
Installed: 2.4.10-9ubuntu1
Candidate: 2.4.10-9ubuntu1
Version table:
*** 2.4.10-9ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
Looks to me like this is more likely a problem in systemd-sysv-generator
than apache2 itself.
** Package changed: apache2 (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.laun
Hi,
I have the same problem. There is just one difference: I'm using ubuntu
12.04 with linux kernel 3.13.
When the crash happens I can no longer access virtual machines. If I
restart neutron-plugin-openvswitch-switch the communication to vms is
restored.
ProblemType: Crash
Architecture: amd64
Cr
11 matches
Mail list logo
