Public bug reported:
while applying latest ubuntu server x86_64 mysql-
server-5.5.35-0ubuntu0.12.04.2 update, mysql-server becomes completely
broken, bruised, battered, botched and b0rked. Unable to start mysql. No
lock files, no stale sockets, all tables were working fine prior to
update. dpkg
Public bug reported:
while applying latest ubuntu server x86_64 mysql-
server-5.5.35-0ubuntu0.12.04.2 update, mysql-server becomes completely
broken, bruised, battered, botched and b0rked. Unable to start mysql. No
lock files, no stale sockets, all tables were working fine prior to
update. dpkg
UPDATE: it appears that removing apparmor allows mysql to start!
Apparmor was reinstalled after mysql-server was running correctly and
all seems to be working now.
# aptitude purge apparmor
The following packages will be REMOVED:
apparmor{p}
The following partially installed packages will be
Nice work guys, thanks!! I just updated to Tbird 24.1.0 and Lighting
2.6.2 and all is working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1244619
Title:
Thunderbird must be
:: could you confirm that these would be various different kernel
versions over time, and not ONLY on the 46 to 47 update?
That's probable. IIRC, my RAID1 MD devices have been blowing up
inexplicably over the past year, and I tend to stay quite current on
patches, applying them each week
I was expecting the RAID system to blow up so I saved the scroll-back of
the terminal. This is the state of the disk subsystem and RAID info
prior to rebooting. Of particular note, /dev/md0p1 is marked as Linux
Raid Autodetect but it's supposed to be an LVM partition!
$ ssh root@newbox
Linux
This is the state of the disk subsystem after rebooting from 10.04 live
media an bringing up /dev/md0 on one disk (to make backups) and then re-
adding the second disk to rebuild the array. Notice /dev/md0p1 is Gone
and pvs says it's using /dev/md0 now!
[08:06 06/13/13]
[root@usb-live
Prior to rebooting the system, these were the contents of
/var/cache/apt/archives showing which patches had just been applied.
This system had been running and rebooting for months prior to applying
these patches.
[11:42 06/12/13]
[root@usb-live /mnt/slash]
# dir var/cache/apt/archives/
total
Public bug reported:
Been running 10.04 LTS on 8 similar AMD Opteron x86_64 servers for
several years. The servers have been kept up-to-date with patches as
they come out. These servers have been running 2.6.x kernels. Each
server has some form of Linux software RAID running on it as well as
Just an update from someone installing fresh onto Lucid, yes this
helped. Thanks. Next issue is giving www-data rw access to
/etc/ocsinventory/dbconfig.inc.php. by default, it's only read and
ocsreports hurls.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This irritated me so I created a fixed /usr/lib/postfix/postfix-files
here. Commented out the manpages and html files as well as the files I
do not have. This is from a basic Ubuntu Lucid postfix install.
http://pastebin.com/Cgcn23mZ
--
You received this bug notification because you are a
This irritated me so I created a fixed /usr/lib/postfix/postfix-files
here. Commented out the manpages and html files as well as the files I
do not have. This is from a basic Ubuntu Lucid postfix install.
http://pastebin.com/Cgcn23mZ
--
You received this bug notification because you are a
FWIW ran into another guest today which wouldn't boot through virt-
mangler. Kept getting error message: operation failed: failed to
retrieve chardev info in qemu with 'info chardev' *sigh*
It was the only guest left wounded from the Lucid upgrade. I could still
start it using the script above,
FWIW ran into another guest today which wouldn't boot through virt-
mangler. Kept getting error message: operation failed: failed to
retrieve chardev info in qemu with 'info chardev' *sigh*
It was the only guest left wounded from the Lucid upgrade. I could still
start it using the script above,
Fixed for me using: touch /etc/apparmor.d/disable/usr.sbin.libvirtd
and then reboot. Also had a non-existent CDROM defined under the
Details section which I removed. I don't think it had anything to do
with the original problem. I removed the file created above and rebooted
and things were back
Fixed for me using: touch /etc/apparmor.d/disable/usr.sbin.libvirtd
and then reboot. Also had a non-existent CDROM defined under the
Details section which I removed. I don't think it had anything to do
with the original problem. I removed the file created above and rebooted
and things were back
Just upgraded my x86_64 12 core opteron hypervisor to Ubuntu 10.04.2 LTS
and am now unable to start any guests using virt-manager.
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 588, in run_domain
vm.startup()
File
Just upgraded my x86_64 12 core opteron hypervisor to Ubuntu 10.04.2 LTS
and am now unable to start any guests using virt-manager.
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 588, in run_domain
vm.startup()
File
I have the same problem running dual monitors. Thought it was my video
card because it only did it on one dvi channel, even when I swapped
monitors around so sold the video card on ebay as defective but
working. $5 bucks for an 8600GT. Got a new card and it does THE EXACT
SAME THING -- WTF!!?
Public bug reported:
Binary package hint: lvm2
I created two software raid devices using mdadm (md0 and md1). Then,
using LVM2, I created a PV from md0 and md1. Then created a Volume
Group and finally a Logical Volume. I formated the LV using mkfs.xfs
with no other options (eg: sunit, swidth
PS: cat /proc/mdstat shows both raid devices are active and healthy
# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4]
[raid10]
md1 : active raid1 sde1[1] sdd1[0]
976760768 blocks [2/2] [UU]
md0 : active raid1 sdb1[1] sda1[0]
Hi all,
I'm not using sudo-ldap as it's apparenlty screwed up as well. Another way
around is to use the NOPASSWD option in your sudoers file. Yeah it sucks. A
user will be able to sudo without a password. They've already authenticated as
their real selves in order to get in and it gets
nslcd is a fail on lucid for me. Trying to start from upstart fails.
Running it by hand in debug mode works but when trying to su from one
LDAP user to another it again fails:
# service nslcd start
* Starting LDAP connection daemon nslcd nslcd: unable to daemonize: No
such device
nslcd is a fail on lucid for me. Trying to start from upstart fails.
Running it by hand in debug mode works but when trying to su from one
LDAP user to another it again fails:
# service nslcd start
* Starting LDAP connection daemon nslcd nslcd: unable to daemonize: No
such device
same problem here on karmic hypervisor. Seems to be something with the
-S switch which virt-manager uses to start the guests (as seen from ps
output). If I try and start the XP guest with -S, it just sits forever.
Issuing 'c' from kvm console (alt+2) just fails the boot process.
Trying to start
Just got same error here after upgrading to 2.6.31-22 kernel. The machine is a
KVM virtual guest and has been running well for a couple months with no issues.
While rsync'ing from the host over ssh, I got:
Corruption of in-memory data detected
grep BOOT syslog
Still there even after editing code
--
kopete with Jabber: unrecoverable error in the protocol, frequent disconnection
https://bugs.launchpad.net/bugs/486518
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdenetwork in ubuntu.
--
Line 788 in file protocols/jabber/jabberaccount.cpp of kdenetwork-4.3.5:
...
/* get rid of psychotic error popup
case XMPP::Stream::ErrProtocol:
errorClass = Kopete::Account::Unknown;
errorText = i18n(There was an
Why would you include a package (in a server system nonetheless) which
doesn't allow you to put /var on a separate partition? Separating /var
is a basic sysadmin task, otherwise you can have services fill up /var
(logs) and DoS the box.
# sudo aptitude purge ureadahead sreadahead
bug fixed
--
Looks like it's still busted with latest 'aptiude upgrade' in karmic 64bit
Server.
I tried to work-around by copying /lib/libnss_ldap-2.8.so /lib/libnss_ldap.so.2
and /usr/lib/libnss_ldap.so
from Jaunty host to karmic host (as questioned above) but 'su -' still failed.
from root, 'su -' to a
Something definitely funky with ldap users and thunderbid (tested
versions = 2.0.0.23). I can run thunderbird as a non-ldap user just
fine, but as soon as trying it with and ldap user it seg faults.
I've tried 3.6 all the way down to 2.0.0.23 and it's the same thing for
each version.
dmesg
Me too. I've been using Kopete on kubuntu 9.04 with the same openfire
server for at least a year. After upgrading to 9.10 yesterday, I am
having the same issue.
--
kopete with Jabber: unrecoverable error in the protocol, frequent disconnection
https://bugs.launchpad.net/bugs/486518
You received
Public bug reported:
Binary package hint: dpkg
Using dpkg -e and extracting to /tmp causes the directory permissions to
be changed to 0755. This causes an immediate denial of service for any
user/process trying to write to /tmp (man pages, etc).
[EMAIL PROTECTED]:/var/cache/apt/archives$ stat
33 matches
Mail list logo
