[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
Ok, so I found the bug. The problematic code is in
sysfs_attr_set_value() in libmultipath/sysfs.c:
devpath = udev_device_get_syspath(dev);
condlog(4, "open '%s'/'%s'", devpath, attr_name);
if (stat(devpath, ) != 0) {
condlog(4, "stat '%s' failed: %s", devpath, strerror(errno));
return 0;
}
/* skip directories */
if (S_ISDIR(statbuf.st_mode))
return 0;
The problem here is that stat() gets called on the containing directory
in devpath (as opposed to devpath+attr_name). Then the code proceeds to
check if that is a directory (which obviously it is going to be) and
before returning without having done anything. The rest of the function
also seems to assume that "devpath" contains the full path to the sysfs
attribute as opposed to the containing directory.
How the verification in comment #22 could have found this code to be
working is beyond me, as the only place where the attr_name variable is
actively being used for anything in the function is in the condlog()
call.
It appears this got fixed upstream by
http://git.opensvc.com/gitweb.cgi?p=multipath-
tools/.git;a=commit;h=050b24b33d3c60e29f7820d2fb75e84a9edde528 . This
patch applies fine to the multipath-tools 0.4.9-3ubuntu7.9 sources from
trusty (with --fuzz=3), and I can confirm that it does fix the problem
for me - the sysfs timeout attributes gets set correctly when the maps
is being created (both when using multipathd and the multipath tool).
Tore
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1435706
Title:
DevLossTO, FastIoFailTO settings do not match multipath.conf expected
values
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
Okay, sorry about the irrelevant verification on Vivid then. But I'd like to point out that Trusty behaves exactly the same, i.e., the bug is *not* fixed. Using the exact same multipath.conf as I mentioned in comment #31 with multipath-tools on 0.4.9-3ubuntu7.9, I get the exact same behaviour. That is, it is apparent that multipathd does read the settings from the config file (as they're visible in output from "multipathd -k'show config'"), but they're not being applied/written to sysfs. If I run use the command line utility in verbose mode to create the map, it does claim that it opens the sysfs files in question, but strace shows no sign of that actually happening: root@ucstest:~# /etc/init.d/multipath-tools stop * Stopping multipath daemon multipathd [ OK ] root@ucstest:~# multipath -F root@ucstest:~# strace -ff -eopen multipath -v4 |& egrep 'create:|_tmo' Mar 08 07:48:38 | 3600c0ff0001204a9d12b75510100: fast_io_fail_tmo = 16 (controller default) Mar 08 07:48:38 | 3600c0ff0001204a9d12b75510100: dev_loss_tmo = 2048 (controller default) Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:01.0/:07:00.0/host1/rport-1:0-1/fc_remote_ports/rport-1:0-1'/'dev_loss_tmo' ort-1:0-1'/'fast_io_fail_tmo' Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:01.0/:07:00.0/host1/rport-1:0-2/fc_remote_ports/rport-1:0-2'/'dev_loss_tmo' Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:01.0/:07:00.0/host1/rport-1:0-2/fc_remote_ports/rport-1:0-2'/'fast_io_fail_tmo' Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:02.0/:08:00.0/host2/rport-2:0-1/fc_remote_ports/rport-2:0-1'/'dev_loss_tmo' Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:02.0/:08:00.0/host2/rport-2:0-1/fc_remote_ports/rport-2:0-1'/'fast_io_fail_tmo' Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:02.0/:08:00.0/host2/rport-2:0-2/fc_remote_ports/rport-2:0-2'/'dev_loss_tmo' Mar 08 07:48:38 | open '/sys/devices/pci:00/:00:02.0/:02:00.0/:03:00.0/:04:00.0/:05:02.0/:08:00.0/host2/rport-2:0-2/fc_remote_ports/rport-2:0-2'/'fast_io_fail_tmo' create: 3600c0ff0001204a9d12b75510100 undef HP ,P2000G3 FC/iSCSI Note that this is a lab system, so if you'd like, you can have a look yourself, Mathieu. Just send me a SSH pubkey on IRC and I'll set up a user account for you. Tore -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1435706 Title: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
I tested it on Vivid, and it does not work. The dev_loss_tmo and
fast_io_fail_tmo sysfs settings do *not* get set. More information on my
test environment below:
root@ucstest:~# cat /etc/multipath.conf
defaults {
fast_io_fail_tmo 8
dev_loss_tmo 1024
}
devices
device {
vendor "HP.*"
product "P2000G3.*"
path_grouping_policy "multibus"
fast_io_fail_tmo 16
dev_loss_tmo 2048
}
}
root@ucstest:~# multipath -ll
3600c0ff0001204a9d12b75510100 dm-0 HP ,P2000G3 FC/iSCSI
size=30G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 1:0:0:1 sdb 8:16 active ready running
|- 1:0:1:1 sdc 8:32 active ready running
|- 2:0:0:1 sdd 8:48 active ready running
`- 2:0:1:1 sde 8:64 active ready running
I know for a fact that the device{} section is being applied, because if
I remove the path_grouping_policy keyword and restart multipathd, the
topology changes to one path per group:
root@ucstest:~# sed -i 's/path_grouping/#path_grouping/' /etc/multipath.conf
root@ucstest:~# systemctl restart multipath-tools.service
root@ucstest:~# multipath -ll
3600c0ff0001204a9d12b75510100 dm-0 HP ,P2000G3 FC/iSCSI
size=30G features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 1:0:0:1 sdb 8:16 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 1:0:1:1 sdc 8:32 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 2:0:0:1 sdd 8:48 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
`- 2:0:1:1 sde 8:64 active ready running
After reverting that change and restarting again, I can confirm that my
config file timeout settings are being read by multipathd:
root@ucstest:~# multipathd -k'show config' | grep -B5 -A1 dev_loss_tmo
defaults {
verbosity 2
wwids_file /etc/multipath/wwids
fast_io_fail_tmo 8
dev_loss_tmo 1024
}
--
device {
vendor "HP.*"
product "P2000G3.*"
path_grouping_policy multibus
fast_io_fail_tmo 16
dev_loss_tmo 2048
}
However, they are *not* being applied to sysfs:
root@ucstest:~# grep . /sys/class/fc_remote_ports/rport-*/*tmo
/sys/class/fc_remote_ports/rport-1:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-2/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-2/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-2/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-2/fast_io_fail_tmo:off
Versions:
root@ucstest:~# dpkg -l kpartx multipath-tools
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
ArchitectureDescription
+++-=-===-===-
ii kpartx
0.4.9-3ubuntu12.15.04.2 amd64 create device
mappings for partitions
ii multipath-tools
0.4.9-3ubuntu12.15.04.2 amd64 maintain
multipath block device access
Tore
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1435706
Title:
DevLossTO, FastIoFailTO settings do not match multipath.conf expected
values
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1548306] [NEW] Attempts to load non-existent module dm-emc
Public bug reported:
The scripts in the multipath-tools-boot referer to a non-existent module
"dm-emc":
/usr/share/initramfs-tools/hooks/multipath:
for x in dm-multipath dm-round-robin dm-emc; do
manual_add_modules ${x}
done
/usr/share/initramfs-tools/scripts/local-top/multipath:
MP_MODULES="dm-multipath dm-emc"
[...]
for module in ${MP_MODULES}; do
if modprobe --syslog "$module"; then
verbose && log_success_msg "loaded module ${module}."
else
log_failure_msg "failed to load module ${module}."
fi
done
The latter code block causes a harmless error message to appear on each
boot.
I believe the references to "dm-emc" can be simply removed.
** Affects: multipath-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1548306
Title:
Attempts to load non-existent module dm-emc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1548306/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1548303] [NEW] Stale references to /lib/udev/rules.d/95-multipath.rules linger
Public bug reported:
/lib/udev/rules.d/95-multipath.rules was removed in multipath-tools
0.4.9-3ubuntu7.5.
While researching an unrelated issue, I noticed that /usr/share
/initramfs-tools/hooks/multipath still refer to this file:
add_udev_rules()
{
for rules in 95-multipath.rules; do
if [ -e /lib/udev/rules.d/$rules ]; then
cp -p /lib/udev/rules.d/$rules $DESTDIR/lib/udev/rules.d/
fi
done
}
This is dead code that it would probably be best to remove.
** Affects: multipath-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1548303
Title:
Stale references to /lib/udev/rules.d/95-multipath.rules linger
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1548303/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547206] Re: Boot stalls on mountall "disk drive not ready" question in multipath-tools >= 0.4.9-3ubuntu7.5
After reviewing the changes between -3ubuntu7.4 and -3ubuntu7.5, I have found that the problem is caused by the removal of the file /lib/udev/rules.d/95-multipath.rules. In -3ubuntu7.4, it contained the following: # # udev rules for multipathing. # The persistent symlinks are created with the kpartx rules # # socket for uevents RUN+="socket:/org/kernel/dm/multipath_event" # Coalesce multipath devices before multipathd is running (initramfs, early # boot) ACTION=="add|change", SUBSYSTEM=="block", RUN+="/sbin/multipath -v0 /dev/$name" If this file is manually reinstated (either to /lib/udev/rules.d or /etc/udev/rules.d), boot is again successful (even with the latest -3ubuntu7.9 multipath-tools package). I see from the changelog that the removal was intentional: * debian/rules: don't ship 95-multipath.rules udev rules anymore; they are not necessary with multipath-tools listening for udev events directly. * debian/multipath.udev: removed. However, in order for this to actually work with multipath-backed "auto" filesystems in /etc/fstab, it seems necessary to ensure that multipathd is started before mountall runs. I am not entirely certain how to accomplish this, though, as mountall is started from Upstart while multipath-tools is stuck using a legacy SysV-init, and I do not know if it is possible to enforce service ordering between the two init systems. For what it's worth, renaming /etc/rcS.d/S21-multipath-tools-boot as etc/rcS.d/S00-multipath-tools-boot does not work around the issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1547206 Title: Boot stalls on mountall "disk drive not ready" question in multipath- tools >= 0.4.9-3ubuntu7.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1547206/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1547206] [NEW] Boot stalls on mountall "disk drive not ready" question in multipath-tools >= 0.4.9-3ubuntu7.5
Public bug reported: System information: Cisco UCS B200M2 blade, fnic.ko HBA. The system boots from local storage, but mounts the following file system on an EMC VNX during bootup: opt_vnx (3600601603a71320022967e0a1f38e411) dm-0 DGC,VRAID size=50G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw |-+- policy='round-robin 0' prio=1 status=active | |- 1:0:1:0 sdd 8:48 active ready running | `- 0:0:0:0 sda 8:0 active ready running `-+- policy='round-robin 0' prio=0 status=enabled |- 0:0:1:0 sdb 8:16 active ready running `- 1:0:0:0 sdc 8:32 active ready running /etc/fstab contains: /dev/mapper/opt_vnx /opt/vnx ext4 noatime 0 2 After upgrading the "multipath-tools" package to version 0.4.9-3ubuntu7.5 or higher, the system can no longer boot without manual intervention. Instead, the following question is asked (by mountall(8)) on the console: The disk drive for /opt/vnx is not ready yet or not present. keys:Continue to wait, or Press S to skip mounting or M for manual recovery Waiting does nothing useful. Pressing "S" allows the boot to run to completion, and the "opt_vnx" *is* present when logging in to a completely booted system. However, it seems that this is discovered *after* the mountall(8) question appears and is skipped, as this log line appears later on in the boot process: * Discovering and coalescing multipaths... [ OK ] Downgrading multipath-tools to version 0.4.9-3ubuntu7.4 does resolve the problem, and allows the system to boot normally without manual intervention. Note that the dependent "kpartx" package does *not* need to be downgraded also, if this is left on version 0.4.9-3ubuntu7.9 it will still boot fine. We experience this problem on serveral other systems apart from the one described in this bug report. ** Affects: multipath-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1547206 Title: Boot stalls on mountall "disk drive not ready" question in multipath- tools >= 0.4.9-3ubuntu7.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1547206/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
Ok, so I did some more testing. It appears that the problem isn't
specific to the dev_loss_tmo and fast_io_fail_tmo setting. This is
evidenced by the terminal log below. In multipath.conf (which we know
for certain is being read, as the created multipath map gets the correct
alias), I instruct it to use the ALUA hardware handler for all devices.
However, for some reason, this is ignored, and the EMC hardware handler
is used instead:
=
root@ucstest-osl2:~# cat /etc/multipath.conf
devices {
device {
vendor .*
product .*
hardware_handler 1 alua
}
}
multipaths {
multipath {
wwid 3600601603a71320022967e0a1f38e411
alias bootvolume
}
}
root@ucstest-osl2:~# multipath -v 2
create: bootvolume (3600601603a71320022967e0a1f38e411) undef DGC,VRAID
size=50G features='1 queue_if_no_path' hwhandler='1 emc' wp=undef
|-+- policy='round-robin 0' prio=1 status=undef
| |- 0:0:0:0 sda 8:0 undef ready running
| `- 1:0:1:0 sdd 8:48 undef ready running
`-+- policy='round-robin 0' prio=0 status=undef
|- 0:0:1:0 sdb 8:16 undef ready running
`- 1:0:0:0 sdc 8:32 undef ready running
=
This does *NOT* happen on RHEL-based distros - on those, changing the
hardware_handler in multipath.conf in this way works as expected.
So why does it use the EMC hardware_handler? Well, there's a built-in
default device section that matches the array in question. So this
appears to override my user-specified config from multipath.conf:
=
root@ucstest-osl2:~# multipathd -k'show config' | grep -B10 -A4 '1 emc'
device {
vendor DGC
product .*
product_blacklist LUNZ
path_grouping_policy group_by_prio
getuid_callout /lib/udev/scsi_id --whitelisted
--device=/dev/%n
path_selector round-robin 0
path_checker emc_clariion
checker emc_clariion
features 1 queue_if_no_path
hardware_handler 1 emc
prio emc
failback immediate
no_path_retry 60
}
=
If I copy the entire default device config into /etc/multipath.conf and
only change the hardware_handler setting, then it starts working:
=
root@ucstest-osl2:~# cat /etc/multipath.conf
devices {
device {
vendor DGC
product .*
product_blacklist LUNZ
path_grouping_policy group_by_prio
getuid_callout /lib/udev/scsi_id --whitelisted
--device=/dev/%n
path_selector round-robin 0
path_checker emc_clariion
checker emc_clariion
features 1 queue_if_no_path
hardware_handler 1 alua
prio emc
failback immediate
no_path_retry 60
}
}
multipaths {
multipath {
wwid 3600601603a71320022967e0a1f38e411
alias bootvolume
}
}
root@ucstest-osl2:~# multipath -v 2
create: bootvolume (3600601603a71320022967e0a1f38e411) undef DGC,VRAID
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=undef
|-+- policy='round-robin 0' prio=1 status=undef
| |- 0:0:0:0 sda 8:0 undef ready running
| `- 1:0:1:0 sdd 8:48 undef ready running
`-+- policy='round-robin 0' prio=0 status=undef
|- 0:0:1:0 sdb 8:16 undef ready running
`- 1:0:0:0 sdc 8:32 undef ready running
=
It would appear that for some reason, in order to override default
device settings in Ubuntu there must be an *exact* string match between
the user-supplied «vendor» and «product» settings. If I change e.g.
«product» in multipath.conf to .*.*, then it starts using the built-in
defaults again, ignoring multipath.conf. I consider this behaviour very
dangerous - consider that if the admin has a working config (due to
exact matching vendor/product settings), and then the package gets
updated and extends the built-in defaults to incorporate some new model
matching the same profile/settings). At this point the admin's working
config will stop being used, possibly causing disruptive problems. I
therefore strongly suggest you figure out why it behaves differently in
Ubuntu and RHEL, and adopt the RHEL behaviour which really is the only
sensible one.
In any case, now that I know how to ensure my multipath.conf settings
are being used, I re-tried adding dev_loss_tmo and fast_io_fail_tmo, but
it still doesn't work:
=
root@ucstest-osl2:~# cat /etc/multipath.conf
devices {
device {
vendor DGC
product .*
product_blacklist LUNZ
path_grouping_policy group_by_prio
getuid_callout /lib/udev/scsi_id --whitelisted
--device=/dev/%n
path_selector round-robin 0
path_checker emc_clariion
checker emc_clariion
features 1
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
I verified that this bug is *NOT* fixed by trying the exact identical
configuration (which is as minimal as possible) both with Ubuntu Trusty
and with Scientific Linux 6 (RHEL6 clone). The test machine is a Cisco
B200M2 blade server, using the Cisco VIC FCoE HBA (fnic.ko driver). The
storage array is an EMC VNX5300, which is reached via FCoE (inside the
Cisco UCS infrastructure) and then traditional FC fabric.
The following console output is taken with Trusty installed. Note that
it was fully upgraded. After creating /etc/multipath.conf with the
indicated contents, update-initramfs was run and the system rebooted,
just to make sure the settings had taken effect. As you can see from the
output, the dev_loss_tmo and fast_io_fail_tmo settings are *NOT*
applied:
=-=-=-=-=-=-=-=
tore@ucstest-osl2:~$ cat /etc/multipath.conf
devices {
device {
vendor .*
product .*
fast_io_fail_tmo3
dev_loss_tmo2147483647
}
}
multipaths {
multipath {
wwid 3600601603a71320022967e0a1f38e411
alias bootvolume
}
}
tore@ucstest-osl2:~$ sudo multipath -ll
bootvolume (3600601603a71320022967e0a1f38e411) dm-0 DGC,VRAID
size=50G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| |- 0:0:1:0 sdb 8:16 active ready running
| `- 1:0:1:0 sdd 8:48 active ready running
`-+- policy='round-robin 0' prio=0 status=enabled
|- 1:0:0:0 sdc 8:32 active ready running
`- 0:0:0:0 sda 8:0 active ready running
tore@ucstest-osl2:~$ grep . /sys/class/fc_remote_ports/rport-*/*tmo
/sys/class/fc_remote_ports/rport-0:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-0:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-0:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-0:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-0:0-2/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-0:0-2/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-2/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-2/fast_io_fail_tmo:off
tore@ucstest-osl2:~$ uname -r
3.13.0-62-generic
tore@ucstest-osl2:~$ md5sum /etc/multipath.conf
27a62898e80a0bcd7e62b5f2e8d675ff /etc/multipath.conf
tore@ucstest-osl2:~$ echo 3 | sudo tee
/sys/class/fc_remote_ports/rport-*/fast_io_fail_tmo
3
tore@ucstest-osl2:~$ echo 2147483647 | sudo tee
/sys/class/fc_remote_ports/rport-*/dev_loss_tmo
2147483647
tore@ucstest-osl2:~$ grep . /sys/class/fc_remote_ports/rport-*/*tmo
/sys/class/fc_remote_ports/rport-0:0-0/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-0:0-0/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-0:0-1/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-0:0-1/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-0:0-2/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-0:0-2/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-1:0-0/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-1:0-0/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-1:0-1/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-1:0-1/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-1:0-2/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-1:0-2/fast_io_fail_tmo:3
tore@ucstest-osl2:~$ dpkg -l multipath-tools
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Architecture Description
+++-==---=
ii multipath-tools0.4.9-3ubuntu7.4 amd64
maintain multipath block
=-=-=-=-=-=-=-=
This shows the exact same multipath.conf file being used on SL6, and in
this case the sysfs settings *ARE* applied when the multipath map is
registered (no reboot required):
=-=-=-=-=-=-=-=
[root@ucstest-osl2 ~]# uname -r
2.6.32-358.23.2.el6.x86_64
[root@ucstest-osl2 ~]# rpm -qa device-mapper-multipath
device-mapper-multipath-0.4.9-80.el6.x86_64
[root@ucstest-osl2 ~]# grep . /sys/class/fc_remote_ports/rport-*/*tmo
/sys/class/fc_remote_ports/rport-1:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-1:0-2/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-1:0-2/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:30
[Bug 1435706] Re: DevLossTO, FastIoFailTO settings do not match multipath.conf expected values
To me fix doesn't actually appear to work. After upgrading to multipath-
tools 0.4.9-3ubuntu7.4on an amd64 trusty and rebooting, the
fast_io_fail_tmo and dev_loss_tmo values do not get written to sysfs:
$ grep . /sys/class/fc_remote_ports/*/*_tmo
/sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-2:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-2:0-1/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-3:0-0/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-3:0-0/fast_io_fail_tmo:off
/sys/class/fc_remote_ports/rport-3:0-1/dev_loss_tmo:30
/sys/class/fc_remote_ports/rport-3:0-1/fast_io_fail_tmo:off
The device stanza from multipath.conf contains the following:
device {
vendor DGC|EMC
product RAID [0-9]*|VRAID|SYMMETRIX.*
path_grouping_policygroup_by_prio
getuid_callout /lib/udev/scsi_id --whitelisted
--device=/dev/%n
path_selector round-robin 0
path_checkeremc_clariion
features0
hardware_handler1 emc
prioemc
failbackimmediate
rr_weight uniform
no_path_retry queue
rr_min_io 100
fast_io_fail_tmo3
dev_loss_tmo2147483647
}
FWIW, I can manually set the sysfs settings to the desired values:
$ echo 3 | sudo tee /sys/class/fc_remote_ports/rport-*/fast_io_fail_tmo
3
$ echo 2147483647 | sudo tee /sys/class/fc_remote_ports/rport-*/dev_loss_tmo
2147483647
$ grep . /sys/class/fc_remote_ports/*/*_tmo
/sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-2:0-0/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-2:0-1/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-2:0-1/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-3:0-0/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-3:0-0/fast_io_fail_tmo:3
/sys/class/fc_remote_ports/rport-3:0-1/dev_loss_tmo:2147483647
/sys/class/fc_remote_ports/rport-3:0-1/fast_io_fail_tmo:3
Tore
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1435706
Title:
DevLossTO, FastIoFailTO settings do not match multipath.conf expected
values
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1435706/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1472129] [NEW] irqbalance triggers Upstart bug when started with --policyscript
Public bug reported: If irqbalance is started with the --policyscript option, Upstart is unable to manage it properly (bug #406397 is being triggered), and stopping/restarting it fails. Noticed this when the 1.0.6-2ubuntu0.14.04.2 update hit Trusty yesterday. See below: $ /sbin/stop irqbalance irqbalance stop/waiting $ echo 'OPTIONS=--policyscript=/bin/true' /etc/default/irqbalance $ /sbin/start irqbalance irqbalance start/running, process 23862 $ /sbin/status irqbalance irqbalance start/running, process 23862 $ pgrep -a irqbalance 23859 /usr/sbin/irqbalance --policyscript=/bin/true 23871 /usr/sbin/irqbalance --policyscript=/bin/true [note how the PIDs don't match what Upstart believes them to be] $ /sbin/stop irqbalance [hangs] ^C $ /sbin/status irqbalance irqbalance stop/killed, process 23862 $ pgrep -a irqbalance 23859 /usr/sbin/irqbalance --policyscript=/bin/true 23871 /usr/sbin/irqbalance --policyscript=/bin/true $ /sbin/start irqbalance [hangs] I successfully recovered from this situation by running the hack at https://raw.githubusercontent.com/ion1/workaround-upstart-snafu/master /workaround-upstart-snafu on all the servers that had attempted to upgraded the irqbalance package. One easy way to fix this issue is to remove expect fork and instead start irqbalance with the --foreground option. Patch attached. On a related note, I see that the irqbalance package ships both a SysV init script in /etc/init.d/irqbalance as well as an Upstart job definition. That's rather confusing to a sysadmin, and could possibly lead to collisions? As I understand it, the SysV init script for an Upstart-managed service is supposed be replaced by a symlink to /lib/init/upstart-job. Maybe you'll want to look into that as well. Tore ** Affects: irqbalance (Ubuntu) Importance: Undecided Status: New ** Patch added: Patch (apply to /etc/init/irqbalance.conf) https://bugs.launchpad.net/bugs/1472129/+attachment/4425604/+files/irqbalance.conf.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1472129 Title: irqbalance triggers Upstart bug when started with --policyscript To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1472129/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 406397] Re: init: job stuck with expect fork/daemon when parent reaps child
** Also affects: irqbalance (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/406397 Title: init: job stuck with expect fork/daemon when parent reaps child To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/406397/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1248054] Re: dlm package installation fails
Tanks David. Very Nice -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dlm in Ubuntu. https://bugs.launchpad.net/bugs/1248054 Title: dlm package installation fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1248054/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318317] Re: openipmi startup script removes kernel modules
This affects me, too. After boot, the necessary ipmi_{si,devintf}
modules aren't loaded, so ipmitool and related monitoring doesn't work.
However this bug cannot possibly be in the ejabberd package, so I'm
reassigning it to openipmi.
** Package changed: ejabberd (Ubuntu) = openipmi (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1318317
Title:
openipmi startup script removes kernel modules
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1318317/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 715141] Re: Default NTP servers do not have AAAA records
We notice this here as well, as we're increasingly turning up new services and VMs without IPv4. It fails with a rather cryptic error message: Jul 8 07:10:03 rpki-validator ntpdate[689]: Can't find host ntp.ubuntu.com: Name or service not known (-2) Jul 8 07:10:03 rpki-validator ntpdate[689]: no servers can be used, exiting Jul 8 07:10:03 rpki-validator ntpdate[726]: Can't find host ntp.ubuntu.com: Name or service not known (-2) Jul 8 07:10:03 rpki-validator ntpdate[726]: no servers can be used, exiting If the Ubuntu sysadmin team does not manage to dual-stack their public NTP service in three years, perhaps it is time for the ntpdate package to switch to 2.pool.ntp.org? Tore -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/715141 Title: Default NTP servers do not have records To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/715141/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322441] Re: QEMU Windows guest unstable after random amount of time
Not this exact problem but one with similar symptoms. From kernel 3.5 onwards there was a problem with guests not receiving RTC ticks which was reported here - http://lists.gnu.org/archive/html/qemu- devel/2013-02/msg03827.html The 3.2 kernel from 12.04.1 never had any issues but the 3.5 kernel from 12.04.2 onwards hit the RTC bug whoch was fixed in later releases of QEMU. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322441 Title: QEMU Windows guest unstable after random amount of time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322441/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1322441] Re: QEMU Windows guest unstable after random amount of time
Based on the fact that flush_tlb_page() appears to be taking up most of the CPU time when QEMU is 'frozen' I started playing with memory settings. Disabling automatic NUMA balancing appears to have solved the problem. echo 0 /proc/sys/kernel/numa_balancing The guest has been running 4+ hours now without an issue. I currently have KSM and transparent huge pages enabled. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1322441 Title: QEMU Windows guest unstable after random amount of time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1322441/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1099875] Re: multipathd ignores dev_loss_tmo and fast_io_fail_tmo settings
** Attachment added: Output from: multipathd -kshow config https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1099875/+attachment/3487090/+files/multipathd_-kshow_config.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1099875 Title: multipathd ignores dev_loss_tmo and fast_io_fail_tmo settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1099875/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1099875] Re: multipathd ignores dev_loss_tmo and fast_io_fail_tmo settings
** Attachment added: Output from: multipath -v4 https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1099875/+attachment/3487091/+files/multipath_-v4.txt ** Changed in: multipath-tools (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1099875 Title: multipathd ignores dev_loss_tmo and fast_io_fail_tmo settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1099875/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1099875] [NEW] multipathd ignores dev_loss_tmo and fast_io_fail_tmo settings
Public bug reported: My device section of /etc/multipath.conf contains the following (I'll attach the complete file in a bit): fast_io_fail_tmo 3 dev_loss_tmo 2147483647 This is also visible in the output from multipathd -kshow config, so it's being correctly parsed. However, the settings appears to be completely ignored by multipathd, as the corresponding sysfs settings doesn't get updated: $ grep . /sys/class/fc_remote_ports/rport-*/*tmo /sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:30 /sys/class/fc_remote_ports/rport-2:0-0/fast_io_fail_tmo:off /sys/class/fc_remote_ports/rport-3:0-0/dev_loss_tmo:30 /sys/class/fc_remote_ports/rport-3:0-0/fast_io_fail_tmo:off These are the kernel's defaults. I can easily set them manually: $ echo 3 | tee /sys/class/fc_remote_ports/rport-*/fast_io_fail_tmo 3 $ echo 2147483647 | tee /sys/class/fc_remote_ports/rport-*/dev_loss_tmo 2147483647 $ grep . /sys/class/fc_remote_ports/rport-*/*tmo /sys/class/fc_remote_ports/rport-2:0-0/dev_loss_tmo:2147483647 /sys/class/fc_remote_ports/rport-2:0-0/fast_io_fail_tmo:3 /sys/class/fc_remote_ports/rport-3:0-0/dev_loss_tmo:2147483647 /sys/class/fc_remote_ports/rport-3:0-0/fast_io_fail_tmo:3 However, this won't survive a reboot, and since SAN paths may appear at any time, adding the above to /etc/rc.local is also not a good way to fix it. I've also attempted to move the settings to the defaults section and the individual path sections. No change in behaviour. This bug prevents dm-multipath from quickly moving I/O away from a recently failed SAN path, instead stalling all I/O for 30 seconds. This defeats the purpose of using multipathing in the first place, which is to have highly available I/O access so that production can continue uninterrupted even if parts of the SAN fabric fails. The setting works on RHEL6, btw. ** Affects: multipath-tools (Ubuntu) Importance: Undecided Status: New ** Attachment added: multipath.conf from impacted Precise server https://bugs.launchpad.net/bugs/1099875/+attachment/3484064/+files/multipath.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1099875 Title: multipathd ignores dev_loss_tmo and fast_io_fail_tmo settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1099875/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1027418] [NEW] Functions from upstream missing in package
Public bug reported: The libkrb5 package in 12.04 looks like it's missing some functions. That sounds weird, so let me explain: I have the following packages installed: $ dpkg-query -l 'libkrb*' [snip] ii libkrb5-26-heimdal1.6~git20120311.dfsg.1-2 Heimdal Kerberos - libraries ii libkrb5-3 1.10+dfsg~beta1-2 MIT Kerberos runtime libraries ii libkrb5-dev 1.10+dfsg~beta1-2 Headers and development libraries for MIT Kerberos ii libkrb5support0 1.10+dfsg~beta1-2 MIT Kerberos runtime libraries - Support library The functions 'krb5_cccol_lock' and 'krb5_cccol_unlock' are declared in /usr/include/krb5/krb5.h, from libkrb5-dev. When I try to use them in a program that links against libkrb5, I get an undefined symbol error at run time. I've looked at every .so file defined in any of those packages (using nm and nm -D), and those symbols aren't mentioned in any of those files! When I build krb5-1.10.2 from the MIT source, those symbols are defined in libkrb5.so.3.3. Does anyone have any idea what's up? ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1027418 Title: Functions from upstream missing in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1027418/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 875440] Re: Cannot authenticate with saslauthd and mysql
I can confirm this effects Precise 12.04. I was able to somewhat work around this by changing the SASL auth mechanism from 'pam' to 'rimap' though I have yet to get authentication working in Roundcube. At lest testsaslauthd succeeds with the rimap mechanism. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/875440 Title: Cannot authenticate with saslauthd and mysql To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/875440/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 899823] [NEW] package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: ErrorMessage: package samba is not ready for configuration cannot configure (current status `half-installed')
Public bug reported: Machine is now in an unknown state of recovery. it is unknown at this point if the upgrade completed. ProblemType: Package DistroRelease: Ubuntu 11.10 Package: samba 2:3.5.8~dfsg-1ubuntu2.3 ProcVersionSignature: Ubuntu 2.6.38-13.52-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 BothFailedConnect: Yes Date: Sat Dec 3 22:45:59 2011 ErrorMessage: ErrorMessage: package samba is not ready for configuration cannot configure (current status `half-installed') NmbdLog: SambaServerRegression: Yes SmbConfIncluded: Yes SourcePackage: samba Title: package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: ErrorMessage: package samba is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: Upgraded to oneiric on 2011-12-04 (0 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 oneiric -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/899823 Title: package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: ErrorMessage: package samba is not ready for configuration cannot configure (current status `half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/899823/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 899823] Re: package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: ErrorMessage: package samba is not ready for configuration cannot configure (current status `half-installed')
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/899823 Title: package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: ErrorMessage: package samba is not ready for configuration cannot configure (current status `half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/899823/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 891933] [NEW] package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: ErrorMessage: package samba is not ready for configuration cannot configure (current status `half-installed')
Public bug reported: I was just doing an upgrade to 11.10 I don't know enough of what went wrong to add much information. ProblemType: Package DistroRelease: Ubuntu 11.10 Package: samba 2:3.5.8~dfsg-1ubuntu2.3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic i686 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Thu Nov 17 18:31:40 2011 ErrorMessage: ErrorMessage: package samba is not ready for configuration cannot configure (current status `half-installed') InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1) NmbdLog: OtherFailedConnect: Yes SambaServerRegression: Yes SmbConfIncluded: Yes SmbLog: SourcePackage: samba Title: package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: ErrorMessage: package samba is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: Upgraded to oneiric on 2011-11-17 (0 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 oneiric -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/891933 Title: package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: ErrorMessage: package samba is not ready for configuration cannot configure (current status `half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/891933/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 891933] Re: package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: ErrorMessage: package samba is not ready for configuration cannot configure (current status `half-installed')
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/891933 Title: package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: ErrorMessage: package samba is not ready for configuration cannot configure (current status `half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/891933/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 640654] [NEW] package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: there is no script in the new version of the package - giving up
Public bug reported: Binary package hint: samba It appears that during an upgrade from version 9 to 10 the samba-common install script was lost. I am a neophyte and have no idea as to how I can correct this error - system still works despite the error. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: samba-common 2:3.4.0-3ubuntu5.6 ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: vmblock vsock vmci vmxnet vmmemctl vmhgfs Architecture: i386 Date: Wed Sep 15 09:03:01 2010 ErrorMessage: there is no script in the new version of the package - giving up PackageArchitecture: all SambaServerRegression: Yes SourcePackage: samba Title: package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: there is no script in the new version of the package - giving up UbuntuFailedConnect: Yes ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: there is no script in the new version of the package - giving up https://bugs.launchpad.net/bugs/640654 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 640654] Re: package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: there is no script in the new version of the package - giving up
** Attachment added: AptOrdering.txt https://bugs.launchpad.net/bugs/640654/+attachment/1594432/+files/AptOrdering.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/640654/+attachment/1594433/+files/Dependencies.txt ** Attachment added: Df.txt https://bugs.launchpad.net/bugs/640654/+attachment/1594434/+files/Df.txt ** Attachment added: Dmesg.txt https://bugs.launchpad.net/bugs/640654/+attachment/1594435/+files/Dmesg.txt ** Attachment added: DpkgTerminalLog.txt https://bugs.launchpad.net/bugs/640654/+attachment/1594436/+files/DpkgTerminalLog.txt ** Attachment added: SambaInstalledVersions.txt https://bugs.launchpad.net/bugs/640654/+attachment/1594437/+files/SambaInstalledVersions.txt -- package samba-common 2:3.4.0-3ubuntu5.6 failed to install/upgrade: there is no script in the new version of the package - giving up https://bugs.launchpad.net/bugs/640654 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 247583] Re: add option to start dnsmasq with a custom configuration file
Does the network XML allow for MX records? I'd like to have an email server VM, but email servers need MX records, and I didn't see a way to specify that in the documentation linked above. -- add option to start dnsmasq with a custom configuration file https://bugs.launchpad.net/bugs/247583 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 Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 51975] Re: Fails completely if there's labeled addresses present
It's still a problem, yes. It's super-easy to reproduce, too: r...@adm:~# nmap -sP -PI 4.2.2.2 Starting Nmap 5.00 ( http://nmap.org ) at 2010-07-02 10:23 CEST Host vnsc-bak.sys.gtei.net (4.2.2.2) is up (0.030s latency). Nmap done: 1 IP address (1 host up) scanned in 0.37 seconds r...@adm:~# ip a a 169.254.1.1/16 dev eth0 label eth0foo r...@adm:~# nmap -sP -PI 4.2.2.2 Starting Nmap 5.00 ( http://nmap.org ) at 2010-07-02 10:24 CEST Failed to determine the netmask of eth0foo!: No such device (19) r...@adm:~# dpkg -l nmap Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii nmap 5.00-3 The Network Mapper Tore -- Fails completely if there's labeled addresses present https://bugs.launchpad.net/bugs/51975 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nmap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 405195] Re: When stopping a specific daemon, _all_ routes are flushed
Hi, sorry about answering so late - I had overlooked this message. What do you mean by «domains»? Tore -- When stopping a specific daemon, _all_ routes are flushed https://bugs.launchpad.net/bugs/405195 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to quagga in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 75028] Re: ospfd starts way too late in the boot process
Considering the purpose of Quagga, it would make sense to start it at the same time or immediately after the plain networking service is, which is at S40 in runlevel S. Tore -- ospfd starts way too late in the boot process https://bugs.launchpad.net/bugs/75028 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to quagga in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 405195] [NEW] When stopping a specific daemon, _all_ routes are flushed
Public bug reported: Binary package hint: quagga This misbehaviour just bit me: r...@fwtest1:~# /etc/init.d/quagga stop ospf6d Stopping Quagga daemons (prio:0): ospf6d. Removing all routes made by zebra. So I'm stopping ospf6d only, but _all_ routes, including the ones installed by still-running processes such as bgpd, ripd, and so on, are removed from the kernel's routing table. That can't be right. I suggest applying the following patch so that the flushing will only happen if all of the Quagga daemons are stopped: --- /etc/init.d/quagga 2009-05-06 23:47:31.0 +0200 +++ /tmp/quagga.new 2009-07-27 10:30:44.0 +0200 @@ -235,8 +235,10 @@ # Stop all daemons at level '0' or 'stop' stop_prio 0 $2 - echo Removing all routes made by zebra. - ip route flush proto zebra + if [ -z $2 ]; then + echo Removing all routes made by zebra. + ip route flush proto zebra + fi ;; restart|force-reload) Tore ** Affects: quagga (Ubuntu) Importance: Undecided Status: New -- When stopping a specific daemon, _all_ routes are flushed https://bugs.launchpad.net/bugs/405195 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to quagga in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 257682] Re: dig compiled without -DDIG_SIGCHASE!
This bug needs to be fixed in Intrepid, also!
# dig +sigchase
Invalid option: +sigchase
Usage: dig [...@global-server] [domain] [q-type] [q-class] {q-opt}
{global-d-opt} host [...@local-server] {local-d-opt}
[ host [...@local-server] {local-d-opt} [...]]
Use dig -h (or dig -h | more) for complete list of options
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 8.10
Release:8.10
Codename: intrepid
# apt-cache policy dnsutils
dnsutils:
Instalado: 1:9.5.0.dfsg.P2-1ubuntu3.1
Candidato: 1:9.5.0.dfsg.P2-1ubuntu3.1
Tabela de versão:
*** 1:9.5.0.dfsg.P2-1ubuntu3.1 0
500 http://debs.cefetrs.tche.br intrepid-security/main Packages
500 http://debs.cefetrs.tche.br intrepid-updates/main Packages
500 http://security.ubuntu.com intrepid-updates/main Packages
500 http://security.ubuntu.com intrepid-security/main Packages
500 http://archive.ubuntu.com intrepid-security/main Packages
500 http://archive.ubuntu.com intrepid-updates/main Packages
100 /var/lib/dpkg/status
1:9.5.0.dfsg.P2-1ubuntu2 0
500 http://debs.cefetrs.tche.br intrepid/main Packages
500 http://security.ubuntu.com intrepid/main Packages
500 http://archive.ubuntu.com intrepid/main Packages
--
dig compiled without -DDIG_SIGCHASE!
https://bugs.launchpad.net/bugs/257682
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 257682] Re: dig compiled without -DDIG_SIGCHASE!
This bug is still present in Intrepid (but not in Hardy, nor in Jaunty). ** Changed in: bind9 (Ubuntu Hardy) Status: Fix Released = New -- dig compiled without -DDIG_SIGCHASE! https://bugs.launchpad.net/bugs/257682 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 257682] Re: dig compiled without -DDIG_SIGCHASE!
Wrong selection. Sorry... ** Changed in: bind9 (Ubuntu Hardy) Status: New = Fix Released -- dig compiled without -DDIG_SIGCHASE! https://bugs.launchpad.net/bugs/257682 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 286063] Re: [SRU] slapd package cannot be installed when using bash as the default shell
Sorry for the slow response. Both slapd 2.4.11-0ubuntu6 and 2.4.11-0ubuntu6.1 installed perfectly in my virtual system, with /bin/sh pointing to bash. In my production server, slapd 2.4.11-0ubuntu6.1 also installed well... -- [SRU] slapd package cannot be installed when using bash as the default shell https://bugs.launchpad.net/bugs/286063 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 300660] [NEW] nagios3-common package should not have configuration files named as *-nagios2.cfg
Public bug reported: Binary package hint: nagios3-common In Ubuntu 9.04, Nagios version is 3.0.3-3ubuntu1 (http://packages.ubuntu.com/jaunty/i386/nagios3-common), but configuration files follows a name convention from Nagios 2.x (http://packages.ubuntu.com/jaunty/i386/nagios3-common/filelist). The files: /etc/nagios3/conf.d/contacts_nagios2.cfg /etc/nagios3/conf.d/extinfo_nagios2.cfg /etc/nagios3/conf.d/generic-host_nagios2.cfg /etc/nagios3/conf.d/generic-service_nagios2.cfg /etc/nagios3/conf.d/hostgroups_nagios2.cfg /etc/nagios3/conf.d/localhost_nagios2.cfg /etc/nagios3/conf.d/services_nagios2.cfg /etc/nagios3/conf.d/timeperiods_nagios2.cfg Should be renamed to: /etc/nagios3/conf.d/contacts_nagios3.cfg /etc/nagios3/conf.d/extinfo_nagios3.cfg /etc/nagios3/conf.d/generic-host_nagios3.cfg /etc/nagios3/conf.d/generic-service_nagios3.cfg /etc/nagios3/conf.d/hostgroups_nagios3.cfg /etc/nagios3/conf.d/localhost_nagios3.cfg /etc/nagios3/conf.d/services_nagios3.cfg /etc/nagios3/conf.d/timeperiods_nagios3.cfg ** Affects: nagios3 (Ubuntu) Importance: Undecided Status: New -- nagios3-common package should not have configuration files named as *-nagios2.cfg https://bugs.launchpad.net/bugs/300660 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 300660] Re: nagios3-common package should not have configuration files named as *-nagios2.cfg
This is also a good idea... Actually, it's better than mine. Anyway... I just wish not to mix nagios3 nagios2 terms in paths... This mix seems so strange... -- nagios3-common package should not have configuration files named as *-nagios2.cfg https://bugs.launchpad.net/bugs/300660 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 291265] Re: [SRU] Buffer overflow in check_ntp_peer - Nagios can't check time servers in Intrepid
check_ntp_peer works now: Before stopping time server... # /usr/lib/nagios/plugins/check_ntp_peer -H time.cefetrs.tche.br NTP OK: Offset -0,002 secs|offset=-0,002000s;60,00;120,00; After stopping time server... # /usr/lib/nagios/plugins/check_ntp_peer -H time.cefetrs.tche.br NTP CRITICAL: No response from NTP server After starting time server again... # /usr/lib/nagios/plugins/check_ntp_peer -H time.cefetrs.tche.br NTP CRITICAL: Server not synchronized, Offset unknown| # /usr/lib/nagios/plugins/check_ntp_peer -H time.cefetrs.tche.br NTP OK: Offset -0,002 secs|offset=-0,002000s;60,00;120,00; -- [SRU] Buffer overflow in check_ntp_peer - Nagios can't check time servers in Intrepid https://bugs.launchpad.net/bugs/291265 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 291265] Re: Buffer overflow in check_ntp_peer - Nagios can't check time servers in Intrepid
Thank you for the job, mantainers and developers! -- Buffer overflow in check_ntp_peer - Nagios can't check time servers in Intrepid https://bugs.launchpad.net/bugs/291265 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-plugins in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 134080] Re: Navigating directories for DFS shares buggy
I'm setting this back to confirmed as I am still seeing this issue, as is dsmith1974. I don't think it is fixed. ** Changed in: samba (Ubuntu) Status: Fix Released = Confirmed -- Navigating directories for DFS shares buggy https://bugs.launchpad.net/bugs/134080 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 260291] Re: Network Manager 0.7, openvpn, VPN Connection Failed
Still works for me. Tore -- Network Manager 0.7, openvpn, VPN Connection Failed https://bugs.launchpad.net/bugs/260291 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 48857] Re: OSPFd automatically adds an invalid configuration line
Haven't tried (running a Feisty backport at the moment), but I expect not. It was supposedly fixed upstream in version 0.99.3, and Intrepid currently ships with 0.99.9. It's likely still present in Dapper, though. Tore. -- OSPFd automatically adds an invalid configuration line https://bugs.launchpad.net/bugs/48857 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to quagga in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 134080] Re: Navigating directories for DFS shares buggy
Could I get some info on how this was fixed? New upstream Samba? -- Navigating directories for DFS shares buggy https://bugs.launchpad.net/bugs/134080 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 260291] Re: Network Manager 0.7, openvpn, VPN Connection Failed
You're right about that, at least it still doesn't work after the upgrade to openvpn 2.1~rc9-3ubuntu1. Still fails with the script- security error message. Tore -- Network Manager 0.7, openvpn, VPN Connection Failed https://bugs.launchpad.net/bugs/260291 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 243337] Re: slapd: search.c:970: oc_filter: Assertion `f != ((void *)0)' failed.
** Attachment added: ldap-assertionfail-unique[2].tar.bz2 http://launchpadlibrarian.net/15631829/ldap-assertionfail-unique%5B2%5D.tar.bz2 -- slapd: search.c:970: oc_filter: Assertion `f != ((void *)0)' failed. https://bugs.launchpad.net/bugs/243337 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 243337] Re: slapd: search.c:970: oc_filter: Assertion `f != ((void *)0)' failed.
I will attach a GDB backtrace, also... ** Attachment added: gdb-backtrace-slapd.txt http://launchpadlibrarian.net/15632302/gdb-backtrace-slapd.txt -- slapd: search.c:970: oc_filter: Assertion `f != ((void *)0)' failed. https://bugs.launchpad.net/bugs/243337 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 243337] Re: slapd: search.c:970: oc_filter: Assertion `f != ((void *)0)' failed.
The OpenLDAP ITS: http://www.openldap.org/its/index.cgi?findid=5581 -- slapd: search.c:970: oc_filter: Assertion `f != ((void *)0)' failed. https://bugs.launchpad.net/bugs/243337 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 243337] Re: slapd: search.c:970: oc_filter: Assertion `f != ((void *)0)' failed.
GDB backtrace with OpenLDAP 2.4.10... ** Attachment added: gdb-backtrace-slapd-2.4.10.txt http://launchpadlibrarian.net/15632467/gdb-backtrace-slapd-2.4.10.txt -- slapd: search.c:970: oc_filter: Assertion `f != ((void *)0)' failed. https://bugs.launchpad.net/bugs/243337 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 227178] Re: [SRU] Slave slapd crashes when doing syncrepl
Sorry, I didn't saw your packages before, because of version numbering. I had installed packages from Chuck's PPA, with version 2.4.9-1ubuntu1~ppa1 and packages from hardy-proposed has version 2.4.9-0ubuntu0.8.04. In order to allow automatic installation of hardy-proposed packages with a standard dist-upgrade, can version numbering be changed? -- [SRU] Slave slapd crashes when doing syncrepl https://bugs.launchpad.net/bugs/227178 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 218734] Re: (ITS#5527) slapd segfaults when using dynlist
I just installed them now... No crashes while starting services... -- (ITS#5527) slapd segfaults when using dynlist https://bugs.launchpad.net/bugs/218734 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 227178] Re: Slave slapd crashes when doing syncrepl
syncrepl is working for me, also. Thanks! -- Slave slapd crashes when doing syncrepl https://bugs.launchpad.net/bugs/227178 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 218734] Re: (ITS#5527) slapd segfaults when using dynlist
I think it's better to send my entire test base... In order to reproduce the bug: # Download my attachment and extract the BZIP archive on an existing folder '/home/amg1127'. # cd to '/home/amg1127/ldap # Create the database from the included LDIF by running './create-master-base.sh' # Got a SIGSEGV # Remove /home/amg1127/ldap folder and entire content within # Extract the BZIP archive on that folder again # Edit the file /home/amg1127/ldap/maindb-commonparams.conf and comment lines 44-45 # Create the database from the included LDIF by running './create-master-base.sh' # Edit the file /home/amg1127/ldap/maindb-commonparams.conf and uncomment lines 44-45 (that is, undo the previous edition). # Run the server: './run-master-slapd.sh' # Got another SIGSEGV ** Attachment added: ldap-crash-dynlist.tar.bz2 http://launchpadlibrarian.net/14674211/ldap-crash-dynlist.tar.bz2 -- (ITS#5527) slapd segfaults when using dynlist https://bugs.launchpad.net/bugs/218734 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 218734] Re: (ITS#5527) slapd segfaults when using dynlist
GDB backtrace and Valgrind logs, extracted using instructions from https://wiki.ubuntu.com/Backtrace and https://wiki.ubuntu.com/Valgrind . ** Attachment added: slapd-crash-dynlist-logs.tar.bz2 http://launchpadlibrarian.net/14674257/slapd-crash-dynlist-logs.tar.bz2 -- (ITS#5527) slapd segfaults when using dynlist https://bugs.launchpad.net/bugs/218734 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 227178] Re: Slave slapd crashes when doing syncrepl
Are you alive? :-) -- Slave slapd crashes when doing syncrepl https://bugs.launchpad.net/bugs/227178 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 218734] Re: slapd segfaults when using dynlist
2.4.7-6ubuntu4.1 crashes with dynlists also... -- slapd segfaults when using dynlist https://bugs.launchpad.net/bugs/218734 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 234196] [NEW] dnPrettyNormal: Assertion `pretty != ((void *)0)' failed.
Public bug reported: In slapo-unique(5) manpage, I read I was using deprecated directives in my LDAP configuration files: overlay unique unique_attributes gidNumber uid uidNumber sambaSID unique_base ou=people,dc=cefetrs,dc=tche,dc=br So, I changed to this: overlay unique unique_uri ldap:///ou=people,dc=cefetrs,dc=tche,dc=br?uid,uidnumber,sambasid,mail?sub And now, I get a failed assertion: $ ./create-master-base.sh slapadd: /build/buildd/openldap2.3-2.4.7/servers/slapd/dn.c:724: dnPrettyNormal: Assertion `pretty != ((void *)0)' failed. ./create-master-base.sh: line 2: 28237 Cancelado slapadd -f slapd.conf -l data.ldif -b 'dc=cefetrs,dc=tche,dc=br' This line shows the assertion fail in slapadd command, but it occurs in slapd, if I use my main base. Steps to reproduce (almost same steps in #227178): # Download my attachment and extract the BZIP archive on an existing folder '/home/amg1127'. # cd to '/home/amg1127/ldap # Create the database from the included LDIF by running './create-master-base.sh' # Got a SIGABRT slapadd: /build/buildd/openldap2.3-2.4.7/servers/slapd/dn.c:724: dnPrettyNormal: Assertion `pretty != ((void *)0)' failed. # Remove /home/amg1127/ldap folder and entire content within # Extract the BZIP archive on that folder again # Edit the file /home/amg1127/ldap/maindb-commonparams.conf, comment line 45 and uncomment lines 42 and 43. # Create the database from the included LDIF by running './create-master-base.sh' # Edit the file /home/amg1127/ldap/maindb-commonparams.conf, uncomment line 45 and comment lines 42 and 43 (that is, undo the previous edition). # Run the server: './run-master-slapd.sh' # Got another SIGABRT slapd: /build/buildd/openldap2.3-2.4.7/servers/slapd/dn.c:724: dnPrettyNormal: Assertion `pretty != ((void *)0)' failed. ** Affects: openldap2.3 (Ubuntu) Importance: Undecided Status: New ** Tags: abort assert sigabrt slapo-unique unique -- dnPrettyNormal: Assertion `pretty != ((void *)0)' failed. https://bugs.launchpad.net/bugs/234196 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 234196] Re: dnPrettyNormal: Assertion `pretty != ((void *)0)' failed.
** Attachment added: ldap-assertionfail-unique.tar.bz2 http://launchpadlibrarian.net/14666008/ldap-assertionfail-unique.tar.bz2 -- dnPrettyNormal: Assertion `pretty != ((void *)0)' failed. https://bugs.launchpad.net/bugs/234196 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 230466] Re: Likewise uninstall, Lock login to system
The problem seems to be installing likewise changes /etc/nsswitch.conf and pam, but doesn't revert them if you uninstall, leaving the system in a state where you can't log in. I'd say this is a pretty big problem ** Changed in: likewise-open (Ubuntu) Status: New = Confirmed -- Likewise uninstall, Lock login to system https://bugs.launchpad.net/bugs/230466 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to likewise-open in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 220724] Re: [SRU] Assertion error in schema_init.c:366: octetStringIndexer
My server does not crash now. :-) -- [SRU] Assertion error in schema_init.c:366: octetStringIndexer https://bugs.launchpad.net/bugs/220724 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 220724] Re: Assertion error in schema_init.c:366: octetStringIndexer
The patch fixed things here also... -- Assertion error in schema_init.c:366: octetStringIndexer https://bugs.launchpad.net/bugs/220724 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 220724] Re: Assertion error in schema_init.c:366: octetStringIndexer
I can't provide a way to reproduce, but I can reproduce this error in my server. I have a GOsa 2.5.15 installation using OpenLDAP 2.4.7 and it crashes when I try to add a mail server. I hope my backtrace can track the problem. ** Attachment added: slapd-crash.txt http://launchpadlibrarian.net/13906537/slapd-crash.txt -- Assertion error in schema_init.c:366: octetStringIndexer https://bugs.launchpad.net/bugs/220724 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap2.3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 210461] Re: PHP crashes when running my sample script
** Attachment added: Script that crashes PHP http://launchpadlibrarian.net/13030894/php-SIGSEGV.php -- PHP crashes when running my sample script https://bugs.launchpad.net/bugs/210461 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 210461] Re: PHP crashes when running my sample script
Sorry. This crash is a behavior documented in PHP site... http://br2.php.net/manual/en/language.functions.php ** Changed in: php5 (Ubuntu) Status: New = Invalid -- PHP crashes when running my sample script https://bugs.launchpad.net/bugs/210461 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
