Thanks Simon, that would indeed work. However, I consider it a
workaround for a problem in openswan. With the older version, openswan
itself sends with the correct sending IP specified in left=, without
having to add explicit routing rules.
--
You received this bug notification because you are a
And another one:
Jan 4 08:29:13 laptop-rm kernel: [ 113.354520] CIFS VFS: could not allocate
crypto API arc4
Jan 4 08:29:13 laptop-rm kernel: [ 113.354524]
Jan 4 08:29:13 laptop-rm kernel: [ 113.354526] CIFS VFS: could not allocate
crypto API arc4
Jan 4 08:29:13 laptop-rm kernel: [ 113.3
Syslog for server2, the same testrun also on kernel 3.5.0
** Attachment added: "syslog.server2"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3473175/+files/syslog.server2
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Syslog of the last testrun on kernel 3.5.0. Test started @ 10:15
** Attachment added: "syslog.server1"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3473174/+files/syslog.server1
--
You received this bug notification because you are a member of Ubuntu
Bu
Peter,
First: happy new year!
I've been doing some more tests to track down the cause of this bug.
Since it looks like a kernel bug, I tried reproducing this with kernel
3.5.0, version 3.5.0-21.32~precise1. I could reproduce the faulty paths
that multipathd was unable to remove, however: there we
The normal state of the disks is as follows:
LUN-DATABASE (36006016061e02e003cf1aca4ae07e211) dm-2 DGC,VRAID
size=200G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
|-+- policy='round-robin 0' prio=130 status=active
| |- 4:0:0:1 sdg 8:96 active ready running
| `- 3:0:0:1 sdc 8:32 active
vmcore file of crashed kernel.
** Attachment added: "vmcore-crash.tgz"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3465398/+files/vmcore-crash.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I've uploaded the vmcore file separately, because I have some doubts
about the dumpfile created by apport beging complete. Please find it
here: http://www.rmoesbergen.nl/vmcore-crash.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Peter,
I got it to crash again, this time with a nice kernel dump. The dump can
be fetched here:
http://www.rmoesbergen.nl/linux-image-3.2.0-34-generic.0.crash.gz
The crash itself looked like this:
Dec 21 11:07:32 ealxs00161 kernel: [63272.392812] sd 4:0:1:1: emc: ALUA
failover mode detected
D
Public bug reported:
Ubuntu release: 12.04.1
Openswan version: 2.6.37-1
It appears that the openswan version in ubuntu 12.04 does not honor the
'left=' parameter when used on a host with multiple external IP
addresses on one 'public' interface. For example: I have a host with 2
IP's bound to eth0
Removing the 'reset_devices' and 'irq_poll' in /etc/init.d/kdump did the
trick, both machines now generate a nice vmcore file when they crash.
I'll re-test with all your settings applied and report back. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Peter, is there another way to get you a kernel crash-dump? Whatever I
try, the crashdump tools don't produce a crashdump.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032550
Title:
[multipath] f
The problem is not making the kernel crash, that's easy :) The issue is
that no crash dump is ever generated. The whole kexec dump stuff just
doesn't seem to work. I already went through all the troubleshooting
tips and tricks, but it the kernel just crashed and hangs forever and
only a reset work
I've been trying to get the crashdump stuff to work, but it just won't
generate a dump, or do anything at all when the kernel crashes... Is
there another way to get the info you want? Would a console screenshot
with a high res console work?
About the hanging processes: The only processes I saw in
** Attachment added: "syslog.test2.survived.gz"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3457383/+files/syslog.test2.survived.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I just retested with the multipath-tools version
'0.4.9-3ubuntu5+lp1032250dbg1', on 2 systems simulatiously. The test
consisted of repeatedly shutting down the fibre port in the switch for
one of the paths. One system survived (see syslog.test2.survived.gz),
one system did not (syslog.test2.broken.
@Peter: I'll try do reproduce on our acceptance systems with crashdump
installed and report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032550
Title:
[multipath] failed to get sysfs inform
** Attachment added: "My multipath.conf"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3456042/+files/multipath.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I'm seeing the same issue with an EMC clariion, see attached syslog. On
my systems this problem leads to hanging processes and a server crash
that can only be fixed with a reboot ..
** Attachment added: "syslog of multipath failure"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bu
19 matches
Mail list logo
