Any chance of a patch to at least quiet this down? Or some additional
info we can provide to try to fix the problem??
These are writing to log every 15 seconds:
Dec 25 23:25:27 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed
int64.c:419 netsnmp_c64_check32_and_update()
Dec 25
I'm not the reporter but I am a daily user of DRBD on precise.
If someone is running the old kernel then they should use the matching older
version of drbd8-utils.
So if the module in the kernel is 8.3.11 then the tools should be also or if
the module is 8.3.13 then the tools should be 8.3.13
I have tested this a couple times a week since the fix was proposed and I have
had no ill effects and it has fixed the problem.
Hopefully we can get this update out to all!
If there is any other info I can provide please let me know.
** Tags removed: verification-needed
** Tags added:
Public bug reported:
Upgrading from 10.04 LTS to 12.04 LTS. Upgrade failed after slapd
failed to install.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: slapd 2.4.21-0ubuntu5.7
ProcVersionSignature: Ubuntu 2.6.32-40.87-server 2.6.32.57+drm33.23
Uname: Linux 2.6.32-40-server x86_64
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/994837
Title:
package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade:
ErrorMessage: subprocess new pre-installation script
I have my server in that state now unfortunately so I should be able to
test.
How would I tested proposed while trying to do-release-upgrade?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in Ubuntu.
I was finally able to get the half upgraded system fixed using the
proposed package.
After that was running for a bit I went ahead and upgraded another server in my
cluster running the same services.
I used the proposed libsasl2-2 package and the upgrade completed start to
finish without a
Public bug reported:
Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8
Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this
bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685
This causes the drbd fencing script's exit codes to be incorrectly
interpreted which
Unfortunately unable to collect such log files due to the nature of the
bug and changes since to bring systems back to working order.
I might have further info I could give - if there are specific questions
I will try to answer.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Description changed:
Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8
Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this
bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685
This causes the drbd fencing script's exit codes to be incorrectly
** Changed in: drbd8 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/1000355
Title:
drbd fence-peer breaks when using kernel 2.6.32-41
To
Hans - The patch is awaiting verification testing. I was unable to test
the proposed fix since I had mitigated the bug already on my servers by
the time it was available.
Looks like tmortensen has tested it so I would expect you to see the
patch available soon!
--
You received this bug
Public bug reported:
After upgrading from 10.04 to 12.04 samba logs no longer show up in
logwatch reports.
There was a change to /usr/share/logwatch/default.conf/logfiles/samba.conf
between 10.04 and 12.04:
LogFile=samba/* was changed to LogFile=samba/*.log
In the samba package the default
** Attachment added: Fix to revert back to prior working settings
https://bugs.launchpad.net/bugs/1010602/+attachment/3181066/+files/samba.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in Ubuntu.
Here is the source commit that changed the samba.conf. The reason listed was:
samba.conf patch to deal with cores dir -mgt
I have no idea what that means honestly but maybe it would be of help to know...
http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revisionrevision=5
--
You
Public bug reported:
After upgrading from 10.04 to 12.04 named logs no longer show up in logwatch
reports.
Not sure if this should be filed as a bug against rsyslog or logwatch.
There was a change to /etc/rsyslog.d/50-default.conf between 10.04 and
12.04 and a bunch of the seperate log files
I will give it a whirl... not sure the exact (best) steps but I assume:
Submit a bug against Logwatch at SourceForge.net
Follow/answer questions there as needed.
If it gets patched then would I need to try to get Debian to pickup the
patch before Ubuntu would consider an SRU to 12.04?
--
You
I will look into it this week and respond accordingly
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to logwatch in Ubuntu.
https://bugs.launchpad.net/bugs/1010625
Title:
named logs are not being reported in logwatch
To manage
Just for the record and if anyone wants to check on it.
Upstream bug submitted:
http://sourceforge.net/tracker/?func=detailaid=3536008group_id=312875atid=1316824#
** Bug watch added: SourceForge.net Tracker #3536008
http://sourceforge.net/support/tracker.php?aid=3536008
--
You received this
No log files available - known issue that was patched in 8.3.13 as noted
in comment #3 above.
Especially important since the new default scheduler of cfq in Precise
is known to cause the bug.
** Changed in: drbd8 (Ubuntu)
Status: Triaged = Confirmed
** Changed in: linux (Ubuntu)
Andres,
This is a real pain for those of us who would like to ensure that we
don't lose data due to a failure during re-sync. If we don't take a
snapshot prior to a re-sync of the secondary and there was a failure it
could be catastrophic. I'm pretty sure Lars put out a patch which is
mentioned
Excellent!
Thank you Andres
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/744293
Title:
Infinite loop in helper LVM script for DRBD 8 in Lucid
--
Ubuntu-server-bugs mailing list
You have a location constraint for msDrbd2 that requires it to be master
on node 1 only. I would assume it's leftover from your master/slave
setup:
location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1
I would remove that and see what happens. Also a few other things:
In
Whoops! I put them backwards too!
In this ordering statement I think you meant to put before not after...
:-)
order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm
I meant it should be after not before!
--
You received this bug notification because you are a member of Ubuntu
Hi Andres,
So I gave it a try and now I'm racking my brain because I thought I knew
what I was doing but it didn't behave as I expected and I don't know if
it's my ignorance or a problem so I'll let you be the judge!
Executed the following on both nodes, one after the other finished:
Added your
Andres - have you had a chance to review my last update?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/744293
Title:
Infinite loop in helper LVM script for DRBD 8 in Lucid
To
Still the same thing - zombie processes for lvm snapshots with 100% cpu.
Script still doesn't have the changes in the patch applied - still looks
identical as my post #8.
root@Vulture:~# apt-cache policy drbd8-source
drbd8-source:
Installed: 2:8.3.7-1ubuntu2.3
Candidate: 2:8.3.7-1ubuntu2.3
Thanks Adam - thought that was weird.
Only update available was drbd8-source after adding your ppa.
Maybe because I use amd64 builds? I noticed it says need to be built next to
those in your ppa.
I'll check again in the morning.
--
You received this bug notification because you are a member
I know how it might not look like a Pacemaker problem but I believe it
is. Pacemaker is in charge of everything. As I put in the comment
before I believe this line disallows Drbd2 to be master on node 2:
location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1
Since everything else
Ok looks good. No zombie processes. I updated and restarted node 1 -
drbd initiated snapsho on startup, synced properly (wouldn't get that
far before) and then removed them. After doing that on node 1 I updated
and restarted node 2 (causing everything to fail to node 1) and
everything moved and
Thanks Adam/Andres
I've got to remember: Google first, ask second - always not just mostly!
I'll report in again in about a week on this. I am doing a lot of
reconfig, add resources, testing, and failing of my pacemaker cluster so
I will report on how the snapshot patch holds up. It *should*
Still working good - no issues. I've changed/rebooted both nodes and it
takes snapshots, re-syncs, then removes snapshots (at least 30 times
since applying the patch) without a hitch.
Thanks again for your help!
--
You received this bug notification because you are a member of Ubuntu
Server
Henning
You are probably right that this isn't the right place to continue with
non-bug questions though Andres or others could answer that more
acurately.
I would recommend drbd-users mailing list as there are many experts
there for config and troubleshooting. Also the pacemaker mailing lists
Public bug reported:
Binary package hint: samba
When you have 'force group = xxx' you receive Network path not found
error in a WinXP client trying to access share that contains the force
group directive.
Description:Ubuntu 8.04.1 Release:8.04
samba:
Installed: 3.0.28a-1ubuntu4.5
Attachment is the error message received in WinXP.
--
force group breaks share
https://bugs.launchpad.net/bugs/269627
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
** Attachment added: err1.jpg
http://launchpadlibrarian.net/17568803/err1.jpg
--
force group breaks share
https://bugs.launchpad.net/bugs/269627
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs
Found syntactical error:
force group = +group-name should be
force group = group-name
No problem any longer. I hope that no one had spent much time as of yet.
** Changed in: samba (Ubuntu)
Status: New = Invalid
--
force group breaks share
https://bugs.launchpad.net/bugs/269627
You
Public bug reported:
When I try to start a Windows XP virtual machine (kvm) it fails with the
following error:
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 493, in run_domain
vm.startup()
File /usr/share/virt-manager/virtManager/domain.py,
** Attachment added: Guest XML definition file
http://launchpadlibrarian.net/36260352/winXPpro.xml
--
Cannot start guest when apparmor is running
https://bugs.launchpad.net/bugs/490370
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Host:
Linux IT02 2.6.31-14-server #48-Ubuntu SMP Fri Oct 16 15:07:34 UTC 2009
x86_64 GNU/Linux
Package versions:
libvirt-bin 0.7.0-1ubuntu13.1
libvirt0 0.7.0-1ubuntu13.1
python-libvirt 0.7.0-1ubuntu13.1
No files in /var/log/apparmor/
Entry in kern.log:
(Repeats everytime I tried to start guest - pid/parent varied but the rest is
identical - if more are needed let me know)
Nov 30 10:11:12 IT02 kernel: [ 405.887561] type=1503
audit(1259593872.142:29): operation=exec pid=2402 parent=1933
That is where the XML definitions resides on my system...
r...@it02:/home/jsmith# ls /etc/libvirt/
libvirtd.conf qemu qemu.conf storage
r...@it02:/home/jsmith# ls /etc/libvirt/qemu
autostart KarmicBeta1.xml kvm networks winXPpro.xml
r...@it02:/home/jsmith#
A bit of history (and maybe my
Whoops that isn't correct - thats not where my XML resides. And I
figured out what it is.
I was trying to get auto-connect USB recognition to work (back when it
was 9.04) and the instructions here (http://david.wragg.org/blog/2009/03
/usb-pass-through-with-libvirt-and-kvm.html) said to make this
Thanks!
--
Cannot start guest when apparmor is running
https://bugs.launchpad.net/bugs/490370
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
44 matches
Mail list logo
