Bugzilla – Bug 676803
iscsi enterprise target just hangs
Last modified: 2012-10-15 21:41:09 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 At first I tried 1.4.19 from Factory - when I started ietd it would just hang, strace showing the last call being "ioctl(4, I2OPARMGET ...)". Then I tried the 1.4.20 tarball from sourceforge, also didn't work. The current ietd seems to be out-of-date wrt the kernel. At first I fixed some of the issues myself, but decided it was better getting the development version and trying that out instead. And that works. BTW, when you start iscsitarget, crc32c_intel complains it can't be loaded (-ENODEV = no such device) (because this CPU doesn't have sse4.2). Doesn't cause a problem, but it doesn't look very nice. Reproducible: Always
*** Bug 677560 has been marked as a duplicate of this bug. ***
Matthias, could you please have a look here?
I am having the same issues with iet as mentioned here. Same crc32s_intel error, same locking up when it loads. Along with this, I'm also having similar issues with tgt as well, slightly different issues though. tgt loads, works in providing iSCSI targets, but unloading it is impossible. For one it doesn't drop the pid file from startproc, and 2 it can't unload the scsi_tgt kernel module as something keeps it active despite nothing using it.
I have upped the severity and importance of this particular bug because as mentioned in 677560, it can and has caused data corruption from this occurance. I had two openSUSE 11.3 servers running dual-NAS with multipath'd iSCSI targets and upgrading to 11.4 caused complete corruption of the data on both servers.
Have also run into this bug (including the crc module issue). Running 11.4, ietd hangs. Updated to 2.6.37.6-0.5 kernel and sources Checked out dev copy of ietd (iscsi-target), built and installed as root. Was able to load iscsi target without hang.
While I was able to get the current developer version of ietd to run without hanging, I am unable to initiate connections with a kernel error emitted on the target immediately when I start an initiator connection: ... invalid opcode: 0000 [#1] PREEMPT SMP ... Fell back to stable release iscsitarget-1.4.20.2, had to apply patches to fix build errors related to "copy_io_context" and "NIPQUAD". Once built, was able to then access iscsi targets under 11.4. (In reply to comment #5) > Have also run into this bug (including the crc module issue). Running 11.4, > ietd hangs. > > Updated to 2.6.37.6-0.5 kernel and sources > Checked out dev copy of ietd (iscsi-target), built and installed as root. > Was able to load iscsi target without hang.
After testing iet/iscsitarget stable 1.4.20.2 with patches to make it compile under the 2.6.37.6-0.5 kernel, it was extremely unstable. Would _not_ recommend running 11.4 with iscsitarget at this time. Running 11.3 + iscsitarget (the release that comes with 11.3) on the same hardware works fine. (In reply to comment #6) > While I was able to get the current developer version of ietd to run without > hanging, I am unable to initiate connections with a kernel error emitted on the > target immediately when I start an initiator connection: > > ... > invalid opcode: 0000 [#1] PREEMPT SMP > ... > > Fell back to stable release iscsitarget-1.4.20.2, had to apply patches to fix > build errors related to "copy_io_context" and "NIPQUAD". Once built, was able > to then access iscsi targets under 11.4. > > (In reply to comment #5) > > Have also run into this bug (including the crc module issue). Running 11.4, > > ietd hangs. > > > > Updated to 2.6.37.6-0.5 kernel and sources > > Checked out dev copy of ietd (iscsi-target), built and installed as root. > > Was able to load iscsi target without hang.
Hi, i am also running into this bug. I just want to inform you how i got around: opensuse: 11.4 kernel: newest default-kernel from update-repository kernel-default-2.6.37.6-0.5.1.x86_64 iscsi-target: downloaded the trunk from iscsi-target-svn i am running svn revision 431, which currently is not the newest available anymore. compiling this revision is working fine (and patches some source files automatically while the build process runs). According to my findings, this setup is working fine on two of my servers where i tested this, and so i am using this in production without any errors so far.
Any ETA yet ?
Whee. CritSit for OpenSUSE.
That bug cost me the better half of a Friday evening when upgrading from 11.3-> 11.4 (already some time ago). My solution was to follow comment #8 and since then iscsitarget was working stable so far. I also noticed the following: Previous kernels contained 3 crc32c related kernel modules: .../kernel/arch/x86/crypto/crc32c-intel.ko .../kernel/crypto/crc32c.ko .../kernel/lib/libcrc32c.ko The kernels shipped with opensuse 11.4 (incl the vanilla kernel) only contain .../kernel/arch/x86/crypto/crc32c-intel.ko It looks like libcrc32c.ko/crc32c.ko do contain a generic crc computation not depending on any hardware, while crc32c-intel.ko naturally requires specific CPU extensions to be present. Could it be, that the kernel build-process omitted libcrc32c.ko/crc32c.ko by mistake and that this is at the heart of the problem? Neither libcrc32c.ko nor crc32c.ko are declared as being obsolete at kernel.org and in the sources for crc32c.ko it is exlicitly stated that it is required for icsi-target. A final remark: That this is being seemingly ignored by opensuse/novell for months now is a shame.
I perfectly agree. I was under the impression we had somebody responsible for bug-assignment. Apparently that doesn't work as designed.
wheee.... 12.1 is out and nothing changed on this one, need I be worried, it might be a problem when updating from 11.4 to 12.1?
No, no need to worry, it worked very well in RC1.
Well... in 12.1 GM it does not work.
Weird. I have a running system on 12.1beta1, I'm pretty certain I didn't fix anything. Which iscsitarget do you have installed? Mine is 1.4.20-10.2.i586.
(In reply to comment #16) > Well... in 12.1 GM it does not work. It works just fine on my 12.1 system. Rui, could you please provide more information? - what and where exactly fails/hangs/does not work - /etc/ietd.conf - /var/log/messages - rpm -qa '*iscsi*|*kernel*' - uname -a Thanks.
I've just been checking the versions - the 12.1 repo has 1.4.20-9.2.1, whereas 1.4.20-10.2 is in Factory.
Hi Per and Petr, I believe this will answer both your questions: ~ # cat /etc/ietd.conf Target iqn.2011-11.com.grupopie:ecdf9246-57a3-43e3-b001-f8917fd867b5 Lun 0 Path=/srv/test.raw,Type=fileio,ScsiId=vstorage03 ~ # rciscsitarget start; sleep 10 ~ # cat /var/log/messages Nov 24 11:17:16 vstorage03 iscsitarget[1042]: Starting iSCSI target service: FATAL: Error inserting crc32c_intel (/lib/modules/3.1.0-1.2-desktop/kernel/arch/x86/crypto/crc32c-intel.ko): No such device Nov 24 11:17:16 vstorage03 kernel: [ 74.594864] iSCSI Enterprise Target Software - version trunk Nov 24 11:17:16 vstorage03 kernel: [ 74.594908] iscsi_trgt: Registered io type fileio Nov 24 11:17:16 vstorage03 kernel: [ 74.594910] iscsi_trgt: Registered io type blockio Nov 24 11:17:16 vstorage03 kernel: [ 74.594912] iscsi_trgt: Registered io type nullio Nov 24 11:17:16 vstorage03 ietd: /etc/ietd.conf's location is depreciated and will be moved in the next release to /etc/iet/ietd.conf Nov 24 11:17:16 vstorage03 iscsitarget[1042]: ..done (using openSUSE-12.1 GM + Updates) ~ # rpm -qa '*iscsi*|*kernel*' yast2-iscsi-client-2.21.9-1.1.1.noarch yast2-iscsi-server-2.21.5-2.1.1.noarch iscsitarget-kmp-desktop-1.4.20_k3.1.0_1.1-9.1.2.i586 kernel-desktop-3.1.0-1.2.1.i586 iscsitarget-1.4.20-9.1.2.i586 ~ # uname -a Linux vstorage03.grupopie.com 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov 3 14:45:45 UTC 2011 (187dde0) i686 i686 i386 GNU/Linux A few extra information: - This machine is a VM on a ESXi 5.0 server - openSUSE 11.3 GM + Updates works on this machine. openSUSE 11.4 does not. - After trying to connect to it from, for example, ESXi 5.0 iSCSI initiator, the following errors are displayed, some at console, some at /var/log/messages: console: Message from syslogd@vstorage03 at Nov 24 11:19:58 ... kernel:[ 236.537012] ------------[ cut here ]------------ Message from syslogd@vstorage03 at Nov 24 11:19:58 ... kernel:[ 236.537418] invalid opcode: 0000 [#1] PREEMPT SMP Message from syslogd@vstorage03 at Nov 24 11:19:58 ... kernel:[ 236.541655] Process istiod1 (pid: 1061, ti=dd200000 task=dd7d00b0 task.ti=dd200000) Message from syslogd@vstorage03 at Nov 24 11:19:58 ... kernel:[ 236.541877] Stack: Message from syslogd@vstorage03 at Nov 24 11:19:58 ... kernel:[ 236.544304] Call Trace: Message from syslogd@vstorage03 at Nov 24 11:19:58 ... kernel:[ 236.545645] Code: ff ff c7 44 24 0c 42 6f 9e e0 c7 44 24 08 88 01 00 00 c7 44 24 04 24 78 9e e0 c7 04 24 6c 78 9e e0 e8 08 8a d1 df e8 85 6c d1 df <0f> 0b 8d b6 00 00 00 00 8d bc 27 00 00 00 00 55 57 56 53 89 c3 Message from syslogd@vstorage03 at Nov 24 11:19:58 ... kernel:[ 236.549860] EIP: [<e09db901>] send_data_rsp+0xb1/0xc0 [iscsi_trgt] SS:ESP 0068:dd201f40 Message from syslogd@vstorage03 at Nov 24 11:20:38 ... kernel:[ 276.516679] Oops: 0010 [#2] PREEMPT SMP Message from syslogd@vstorage03 at Nov 24 11:20:38 ... kernel:[ 276.521378] Process istd1 (pid: 1053, ti=dd7ce000 task=dbee2530 task.ti=dd7ce000) Message from syslogd@vstorage03 at Nov 24 11:20:38 ... kernel:[ 276.521679] Stack: Message from syslogd@vstorage03 at Nov 24 11:20:38 ... kernel:[ 276.524064] Call Trace: Message from syslogd@vstorage03 at Nov 24 11:20:38 ... kernel:[ 276.524213] Inexact backtrace: Message from syslogd@vstorage03 at Nov 24 11:20:38 ... kernel:[ 276.524214] Message from syslogd@vstorage03 at Nov 24 11:20:38 ... kernel:[ 276.527788] Code: Bad EIP value. Message from syslogd@vstorage03 at Nov 24 11:20:38 ... kernel:[ 276.528066] EIP: [<b7812254>] 0xb7812254 SS:ESP 0068:dd7cfe9c Message from syslogd@vstorage03 at Nov 24 11:20:38 ... kernel:[ 276.528399] CR2: 00000000b7812254 /var/log/messages: Nov 24 11:19:58 vstorage03 kernel: [ 236.536469] iscsi_trgt: BUG at /home/abuild/rpmbuild/BUILD/iscsitarget-1.4.20-svn/obj/desktop/iscsi.c:392 assert(req->tio) Nov 24 11:19:58 vstorage03 kernel: [ 236.536786] Pid: 1061, comm: istiod1 Not tainted 3.1.0-1.2-desktop #1 Nov 24 11:19:58 vstorage03 kernel: [ 236.536788] Call Trace: Nov 24 11:19:58 vstorage03 kernel: [ 236.536831] [<c0205433>] try_stack_unwind+0x163/0x180 Nov 24 11:19:58 vstorage03 kernel: [ 236.536843] [<c0204167>] dump_trace+0x47/0xf0 Nov 24 11:19:58 vstorage03 kernel: [ 236.536848] [<c020549b>] show_trace_log_lvl+0x4b/0x60 Nov 24 11:19:58 vstorage03 kernel: [ 236.536852] [<c02054c8>] show_trace+0x18/0x20 Nov 24 11:19:58 vstorage03 kernel: [ 236.536859] [<c06f25f3>] dump_stack+0x6d/0x72 Nov 24 11:19:58 vstorage03 kernel: [ 236.536877] [<e09db901>] send_data_rsp+0xb1/0xc0 [iscsi_trgt] Nov 24 11:19:58 vstorage03 kernel: [ 236.536897] [<e09e3084>] disk_execute_cmnd.part.0+0xd4/0x1a0 [iscsi_trgt] Nov 24 11:19:58 vstorage03 kernel: [ 236.536924] [<e09e3167>] disk_execute_cmnd+0x17/0x20 [iscsi_trgt] Nov 24 11:19:58 vstorage03 kernel: [ 236.536950] [<e09de85d>] worker_thread+0x11d/0x270 [iscsi_trgt] Nov 24 11:19:58 vstorage03 kernel: [ 236.536964] [<c0266c99>] kthread+0x69/0x70 Nov 24 11:19:58 vstorage03 kernel: [ 236.536972] [<c070f966>] kernel_thread_helper+0x6/0xd Nov 24 11:19:58 vstorage03 kernel: [ 236.537012] ------------[ cut here ]------------ Nov 24 11:19:58 vstorage03 kernel: [ 236.537157] kernel BUG at /home/abuild/rpmbuild/BUILD/iscsitarget-1.4.20-svn/obj/desktop/iscsi.c:392! Nov 24 11:19:58 vstorage03 kernel: [ 236.537418] invalid opcode: 0000 [#1] PREEMPT SMP Nov 24 11:19:58 vstorage03 kernel: [ 236.537745] Modules linked in: iscsi_trgt vmsync vmblock ppdev parport_pc parport floppy sr_mod sg cdrom pcspkr vmw_balloon ac button container mptctl vmxnet3 shpchp pci_hotplug i2c_piix4 vmci autofs4 dm_mod linear processor thermal_sys ata_generic mptsas mptscsih mptbase scsi_transport_sas Nov 24 11:19:58 vstorage03 kernel: [ 236.540158] Nov 24 11:19:58 vstorage03 kernel: [ 236.540245] Pid: 1061, comm: istiod1 Not tainted 3.1.0-1.2-desktop #1 VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform Nov 24 11:19:58 vstorage03 kernel: [ 236.540744] EIP: 0060:[<e09db901>] EFLAGS: 00010282 CPU: 0 Nov 24 11:19:58 vstorage03 kernel: [ 236.540922] EIP is at send_data_rsp+0xb1/0xc0 [iscsi_trgt] Nov 24 11:19:58 vstorage03 kernel: [ 236.541097] EAX: ffffffff EBX: db45fbc0 ECX: 00000000 EDX: 00000000 Nov 24 11:19:58 vstorage03 kernel: [ 236.541289] ESI: 00000000 EDI: df90f000 EBP: dd009bd0 ESP: dd201f40 Nov 24 11:19:58 vstorage03 kernel: [ 236.541481] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Nov 24 11:19:58 vstorage03 kernel: [ 236.541655] Process istiod1 (pid: 1061, ti=dd200000 task=dd7d00b0 task.ti=dd200000) Nov 24 11:19:58 vstorage03 kernel: [ 236.541877] Stack: Nov 24 11:19:58 vstorage03 kernel: [ 236.542028] e09e786c e09e7824 00000188 e09e6f42 db45fbc0 dd009bc0 e09e3084 e09e26c7 Nov 24 11:19:58 vstorage03 kernel: [ 236.542786] 0000000e db45fbc0 dd009bc0 db45fbc0 e09e3167 db45fbc0 e09de85d dd201fa0 Nov 24 11:19:58 vstorage03 kernel: [ 236.543547] c022e80f 00000000 00000000 dd7d00b0 dd7d00b0 dd009bd8 00000000 dd7d00b0 Nov 24 11:19:58 vstorage03 kernel: [ 236.544304] Call Trace: Nov 24 11:19:58 vstorage03 kernel: [ 236.544468] [<e09e3084>] disk_execute_cmnd.part.0+0xd4/0x1a0 [iscsi_trgt] Nov 24 11:19:58 vstorage03 kernel: [ 236.544744] [<e09e3167>] disk_execute_cmnd+0x17/0x20 [iscsi_trgt] Nov 24 11:19:58 vstorage03 kernel: [ 236.545003] [<e09de85d>] worker_thread+0x11d/0x270 [iscsi_trgt] Nov 24 11:19:58 vstorage03 kernel: [ 236.545244] [<c0266c99>] kthread+0x69/0x70 Nov 24 11:19:58 vstorage03 kernel: [ 236.545435] [<c070f966>] kernel_thread_helper+0x6/0xd Nov 24 11:19:58 vstorage03 kernel: [ 236.545645] Code: ff ff c7 44 24 0c 42 6f 9e e0 c7 44 24 08 88 01 00 00 c7 44 24 04 24 78 9e e0 c7 04 24 6c 78 9e e0 e8 08 8a d1 df e8 85 6c d1 df <0f> 0b 8d b6 00 00 00 00 8d bc 27 00 00 00 00 55 57 56 53 89 c3 Nov 24 11:19:58 vstorage03 kernel: [ 236.549860] EIP: [<e09db901>] send_data_rsp+0xb1/0xc0 [iscsi_trgt] SS:ESP 0068:dd201f40 Nov 24 11:19:58 vstorage03 kernel: [ 236.556572] ---[ end trace e5400ac44c870c00 ]--- Nov 24 11:20:38 vstorage03 kernel: [ 276.514694] iscsi_trgt: Abort Task (01) issued on tid:1 lun:0 by sid:282574492336640 (Function Complete) Nov 24 11:20:38 vstorage03 kernel: [ 276.515593] BUG: unable to handle kernel paging request at b7812254 Nov 24 11:20:38 vstorage03 kernel: [ 276.515924] IP: [<b7812254>] 0xb7812253 Nov 24 11:20:38 vstorage03 kernel: [ 276.516200] *pdpt = 000000001fb3b001 *pde = 000000001b533067 *pte = 0000000000000000 Nov 24 11:20:38 vstorage03 kernel: [ 276.516679] Oops: 0010 [#2] PREEMPT SMP Nov 24 11:20:38 vstorage03 kernel: [ 276.517033] Modules linked in: iscsi_trgt vmsync vmblock ppdev parport_pc parport floppy sr_mod sg cdrom pcspkr vmw_balloon ac button container mptctl vmxnet3 shpchp pci_hotplug i2c_piix4 vmci autofs4 dm_mod linear processor thermal_sys ata_generic mptsas mptscsih mptbase scsi_transport_sas Nov 24 11:20:38 vstorage03 kernel: [ 276.519594] Nov 24 11:20:38 vstorage03 kernel: [ 276.519724] Pid: 1053, comm: istd1 Tainted: G D 3.1.0-1.2-desktop #1 VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform Nov 24 11:20:38 vstorage03 kernel: [ 276.520318] EIP: 0060:[<b7812254>] EFLAGS: 00010083 CPU: 0 Nov 24 11:20:38 vstorage03 kernel: [ 276.520534] EIP is at 0xb7812254 Nov 24 11:20:38 vstorage03 kernel: [ 276.520700] EAX: dd201f98 EBX: fffffff4 ECX: 00000000 EDX: 00000003 Nov 24 11:20:38 vstorage03 kernel: [ 276.520932] ESI: dd201f98 EDI: c024c93e EBP: dd7cfebc ESP: dd7cfe9c Nov 24 11:20:38 vstorage03 kernel: [ 276.521165] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Nov 24 11:20:38 vstorage03 kernel: [ 276.521378] Process istd1 (pid: 1053, ti=dd7ce000 task=dbee2530 task.ti=dd7ce000) Nov 24 11:20:38 vstorage03 kernel: [ 276.521679] Stack: Nov 24 11:20:38 vstorage03 kernel: [ 276.521818] c022e80f 00000000 00000001 00000003 dd009bdc dd009bd8 00000003 00000001 Nov 24 11:20:38 vstorage03 kernel: [ 276.522567] dd7cfee0 c022fe0c 00000000 00000000 00000000 00000292 db45fe60 dd009bc0 Nov 24 11:20:38 vstorage03 kernel: [ 276.523315] 00000012 db4d307c e09deaa8 00000000 db45fe60 db45fe60 00000000 df90f000 Nov 24 11:20:38 vstorage03 kernel: [ 276.524064] Call Trace: Nov 24 11:20:38 vstorage03 kernel: [ 276.524213] Inexact backtrace: Nov 24 11:20:38 vstorage03 kernel: [ 276.524214] Nov 24 11:20:38 vstorage03 kernel: [ 276.524515] [<c022e80f>] ? __wake_up_common+0x3f/0x70 Nov 24 11:20:38 vstorage03 kernel: [ 276.524727] [<c022fe0c>] ? __wake_up+0x3c/0x60 Nov 24 11:20:38 vstorage03 kernel: [ 276.524932] [<e09deaa8>] ? wthread_queue+0x58/0x120 [iscsi_trgt] Nov 24 11:20:38 vstorage03 kernel: [ 276.525165] [<e09d9efa>] ? iscsi_scsi_queuecmnd+0x9a/0x100 [iscsi_trgt] Nov 24 11:20:38 vstorage03 kernel: [ 276.525409] [<c023192c>] ? finish_task_switch+0x3c/0xc0 Nov 24 11:20:38 vstorage03 kernel: [ 276.525624] [<e09dc424>] ? iscsi_session_push_cmnd+0x104/0x1a0 [iscsi_trgt] Nov 24 11:20:38 vstorage03 kernel: [ 276.525878] [<e09ddc47>] ? recv+0x1b7/0x470 [iscsi_trgt] Nov 24 11:20:38 vstorage03 kernel: [ 276.526096] [<c05f819b>] ? release_sock+0x1b/0x70 Nov 24 11:20:38 vstorage03 kernel: [ 276.526299] [<c063d8af>] ? tcp_ioctl+0x7f/0x1a0 Nov 24 11:20:38 vstorage03 kernel: [ 276.526499] [<e09de3c5>] ? process_io+0x25/0x100 [iscsi_trgt] Nov 24 11:20:38 vstorage03 kernel: [ 276.526726] [<e09de535>] ? istd+0x95/0x100 [iscsi_trgt] Nov 24 11:20:38 vstorage03 kernel: [ 276.526941] [<e09de4a0>] ? process_io+0x100/0x100 [iscsi_trgt] Nov 24 11:20:38 vstorage03 kernel: [ 276.527169] [<c0266c99>] ? kthread+0x69/0x70 Nov 24 11:20:38 vstorage03 kernel: [ 276.527361] [<c0266c30>] ? kthread_worker_fn+0x150/0x150 Nov 24 11:20:38 vstorage03 kernel: [ 276.527577] [<c070f966>] ? kernel_thread_helper+0x6/0xd Nov 24 11:20:38 vstorage03 kernel: [ 276.527788] Code: Bad EIP value. Nov 24 11:20:38 vstorage03 kernel: [ 276.528066] EIP: [<b7812254>] 0xb7812254 SS:ESP 0068:dd7cfe9c Nov 24 11:20:38 vstorage03 kernel: [ 276.528399] CR2: 00000000b7812254 Nov 24 11:20:38 vstorage03 kernel: [ 276.528567] ---[ end trace e5400ac44c870c01 ]--- Nov 24 11:20:38 vstorage03 kernel: [ 276.528765] note: istd1[1053] exited with preempt_count 1 I also have one extra question: As you've noticed, when i start iscsitarget, it complains that crc32c_intel module could not be loaded. Is this module a requirement ? If you need any extra information and/or testing, please just let me know. Thanks for all you help, Rui
(In reply to comment #20) > Hi Per and Petr, > > I believe this will answer both your questions: > > ~ # cat /etc/ietd.conf > Target iqn.2011-11.com.grupopie:ecdf9246-57a3-43e3-b001-f8917fd867b5 > Lun 0 Path=/srv/test.raw,Type=fileio,ScsiId=vstorage03 You don't have the rest? : MaxConnections 2 MaxSessions 0 QueuedCommands 64 Wthreads 2 ImmediateData Yes (I haven't checked the defaults, maybe they're sufficient). > Nov 24 11:17:16 vstorage03 kernel: [ 74.594864] iSCSI Enterprise Target > Software - version trunk That sounds like you've got a working version at least. > A few extra information: > - This machine is a VM on a ESXi 5.0 server > - openSUSE 11.3 GM + Updates works on this machine. openSUSE 11.4 does not. > - After trying to connect to it from, for example, ESXi 5.0 iSCSI initiator, > the following errors are displayed, some at console, some at /var/log/messages: Is there any possibility/risk that this is some unknown incompatibility? I'm only using the openscsi initiator. > /var/log/messages: > Nov 24 11:19:58 vstorage03 kernel: [ 236.536469] iscsi_trgt: BUG at > /home/abuild/rpmbuild/BUILD/iscsitarget-1.4.20-svn/obj/desktop/iscsi.c:392 > assert(req->tio) The only assert(req->tio) I see in the code I have is in iscsi.c:1408. I would suggest you upgrade iscsitarget from Factory, if you don't mind. I have a suspicion we're looking at some old code here. > I also have one extra question: > As you've noticed, when i start iscsitarget, it complains that crc32c_intel > module could not be loaded. Is this module a requirement ? No, it works fine without, but the warning does look a little too serious. See the explanation in my initial comment.
Hi Per, (In reply to comment #21) > > You don't have the rest? : > > MaxConnections 2 > MaxSessions 0 > QueuedCommands 64 > Wthreads 2 > ImmediateData Yes > > (I haven't checked the defaults, maybe they're sufficient). I have other lines but, they are all as comment... > > That sounds like you've got a working version at least. > That was probably "the thunk back then" :) > Is there any possibility/risk that this is some unknown incompatibility? I'm > only using the openscsi initiator. > I''ve now tested with openiscsi initiator and it seems to work correctly. However ESXi 5.0 does work on openSUSE 11.3 with iscsi-target... > > The only assert(req->tio) I see in the code I have is in iscsi.c:1408. I would > suggest you upgrade iscsitarget from Factory, if you don't mind. I have a > suspicion we're looking at some old code here. > Done. iscsi-target in now the factory one. ~ # rpm -qa '*iscsi*|*kernel*' yast2-iscsi-client-2.21.9-1.1.1.noarch yast2-iscsi-server-2.21.5-2.1.1.noarch iscsitarget-1.4.20-10.2.i586 kernel-desktop-3.1.0-1.2.1.i586 The behavior seems the same. ~ # cat /var/log/messages Nov 24 15:24:53 vstorage03 kernel: [ 123.604452] iscsi_trgt: BUG at /home/abuild/rpmbuild/BUILD/iscsitarget-1.4.20-svn/obj/desktop/iscsi.c:392 assert(req->tio) Nov 24 15:24:53 vstorage03 kernel: [ 123.604767] Pid: 1044, comm: istiod1 Not tainted 3.1.0-1.2-desktop #1 Nov 24 15:24:53 vstorage03 kernel: [ 123.604770] Call Trace: Nov 24 15:24:53 vstorage03 kernel: [ 123.604813] [<c0205433>] try_stack_unwind+0x163/0x180 Nov 24 15:24:53 vstorage03 kernel: [ 123.604825] [<c0204167>] dump_trace+0x47/0xf0 Nov 24 15:24:53 vstorage03 kernel: [ 123.604830] [<c020549b>] show_trace_log_lvl+0x4b/0x60 Nov 24 15:24:53 vstorage03 kernel: [ 123.604834] [<c02054c8>] show_trace+0x18/0x20 Nov 24 15:24:53 vstorage03 kernel: [ 123.604841] [<c06f25f3>] dump_stack+0x6d/0x72 Nov 24 15:24:53 vstorage03 kernel: [ 123.604859] [<f7bc3901>] send_data_rsp+0xb1/0xc0 [iscsi_trgt] Nov 24 15:24:53 vstorage03 kernel: [ 123.604880] [<f7bcb084>] disk_execute_cmnd.part.0+0xd4/0x1a0 [iscsi_trgt] Nov 24 15:24:53 vstorage03 kernel: [ 123.604907] [<f7bcb167>] disk_execute_cmnd+0x17/0x20 [iscsi_trgt] Nov 24 15:24:53 vstorage03 kernel: [ 123.604934] [<f7bc685d>] worker_thread+0x11d/0x270 [iscsi_trgt] Nov 24 15:24:53 vstorage03 kernel: [ 123.604948] [<c0266c99>] kthread+0x69/0x70 Nov 24 15:24:53 vstorage03 kernel: [ 123.604956] [<c070f966>] kernel_thread_helper+0x6/0xd Nov 24 15:24:53 vstorage03 kernel: [ 123.604996] ------------[ cut here ]------------ Nov 24 15:24:53 vstorage03 kernel: [ 123.605140] kernel BUG at /home/abuild/rpmbuild/BUILD/iscsitarget-1.4.20-svn/obj/desktop/iscsi.c:392! Nov 24 15:24:53 vstorage03 kernel: [ 123.605402] invalid opcode: 0000 [#1] PREEMPT SMP Nov 24 15:24:53 vstorage03 kernel: [ 123.605725] Modules linked in: iscsi_trgt vmsync vmblock ppdev floppy parport_pc parport sr_mod sg vmxnet3 cdrom vmci vmw_balloon pcspkr shpchp pci_hotplug i2c_piix4 mptctl container button ac autofs4 dm_mod linear processor thermal_sys ata_generic mptsas mptscsih mptbase scsi_transport_sas Nov 24 15:24:53 vstorage03 kernel: [ 123.608115] Nov 24 15:24:53 vstorage03 kernel: [ 123.608201] Pid: 1044, comm: istiod1 Not tainted 3.1.0-1.2-desktop #1 VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform Nov 24 15:24:53 vstorage03 kernel: [ 123.608695] EIP: 0060:[<f7bc3901>] EFLAGS: 00010282 CPU: 0 Nov 24 15:24:53 vstorage03 kernel: [ 123.608871] EIP is at send_data_rsp+0xb1/0xc0 [iscsi_trgt] Nov 24 15:24:53 vstorage03 kernel: [ 123.609045] EAX: ffffffff EBX: f6d05bc0 ECX: 00000000 EDX: 00000000 Nov 24 15:24:53 vstorage03 kernel: [ 123.609236] ESI: 00000000 EDI: f6a64000 EBP: f6e36750 ESP: f6919f40 Nov 24 15:24:53 vstorage03 kernel: [ 123.609426] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Nov 24 15:24:53 vstorage03 kernel: [ 123.609598] Process istiod1 (pid: 1044, ti=f6918000 task=f6d1a530 task.ti=f6918000) Nov 24 15:24:53 vstorage03 kernel: [ 123.609818] Stack: Nov 24 15:24:53 vstorage03 kernel: [ 123.609968] f7bcf86c f7bcf824 00000188 f7bcef42 f6d05bc0 f6e36740 f7bcb084 f7bca6c7 Nov 24 15:24:53 vstorage03 kernel: [ 123.610721] 00000246 f6d05bc0 f6e36740 f6d05bc0 f7bcb167 f6d05bc0 f7bc685d f6919fa0 Nov 24 15:24:53 vstorage03 kernel: [ 123.611471] c022e80f 00000000 00000000 f6d1a530 f6d1a530 f6e36758 00000000 f6d1a530 Nov 24 15:24:53 vstorage03 kernel: [ 123.612223] Call Trace: Nov 24 15:24:53 vstorage03 kernel: [ 123.612387] [<f7bcb084>] disk_execute_cmnd.part.0+0xd4/0x1a0 [iscsi_trgt] Nov 24 15:24:53 vstorage03 kernel: [ 123.612662] [<f7bcb167>] disk_execute_cmnd+0x17/0x20 [iscsi_trgt] Nov 24 15:24:53 vstorage03 kernel: [ 123.612920] [<f7bc685d>] worker_thread+0x11d/0x270 [iscsi_trgt] Nov 24 15:24:53 vstorage03 kernel: [ 123.613159] [<c0266c99>] kthread+0x69/0x70 Nov 24 15:24:53 vstorage03 kernel: [ 123.613357] [<c070f966>] kernel_thread_helper+0x6/0xd Nov 24 15:24:53 vstorage03 kernel: [ 123.613567] Code: ff ff c7 44 24 0c 42 ef bc f7 c7 44 24 08 88 01 00 00 c7 44 24 04 24 f8 bc f7 c7 04 24 6c f8 bc f7 e8 08 0a b3 c8 e8 85 ec b2 c8 <0f> 0b 8d b6 00 00 00 00 8d bc 27 00 00 00 00 55 57 56 53 89 c3 Nov 24 15:24:53 vstorage03 kernel: [ 123.617742] EIP: [<f7bc3901>] send_data_rsp+0xb1/0xc0 [iscsi_trgt] SS:ESP 0068:f6919f40 Nov 24 15:24:53 vstorage03 kernel: [ 123.626037] ---[ end trace 3f64c3c2aad82ff3 ]--- Nov 24 15:25:32 vstorage03 kernel: [ 163.583445] iscsi_trgt: Abort Task (01) issued on tid:1 lun:0 by sid:282574492336640 (Function Complete) Nov 24 15:25:32 vstorage03 kernel: [ 163.584109] BUG: unable to handle kernel paging request at b76da254 Nov 24 15:25:32 vstorage03 kernel: [ 163.584466] IP: [<b76da254>] 0xb76da253 Nov 24 15:25:32 vstorage03 kernel: [ 163.584737] *pdpt = 0000000036e30001 *pde = 000000005e8c1067 Nov 24 15:25:32 vstorage03 kernel: [ 163.585072] Oops: 0010 [#2] PREEMPT SMP Nov 24 15:25:32 vstorage03 kernel: [ 163.585423] Modules linked in: iscsi_trgt vmsync vmblock ppdev floppy parport_pc parport sr_mod sg vmxnet3 cdrom vmci vmw_balloon pcspkr shpchp pci_hotplug i2c_piix4 mptctl container button ac autofs4 dm_mod linear processor thermal_sys ata_generic mptsas mptscsih mptbase scsi_transport_sas Nov 24 15:25:32 vstorage03 kernel: [ 163.587986] Nov 24 15:25:32 vstorage03 kernel: [ 163.588116] Pid: 1039, comm: istd1 Tainted: G D 3.1.0-1.2-desktop #1 VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform Nov 24 15:25:32 vstorage03 kernel: [ 163.588737] EIP: 0060:[<b76da254>] EFLAGS: 00010006 CPU: 0 Nov 24 15:25:32 vstorage03 kernel: [ 163.588956] EIP is at 0xb76da254 Nov 24 15:25:32 vstorage03 kernel: [ 163.589122] EAX: f6919f98 EBX: fffffff4 ECX: 00000000 EDX: 00000003 Nov 24 15:25:32 vstorage03 kernel: [ 163.589354] ESI: f6919f98 EDI: c024c93e EBP: f6f09ebc ESP: f6f09e9c Nov 24 15:25:32 vstorage03 kernel: [ 163.589587] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Nov 24 15:25:32 vstorage03 kernel: [ 163.589801] Process istd1 (pid: 1039, ti=f6f08000 task=f68ec330 task.ti=f6f08000) Nov 24 15:25:32 vstorage03 kernel: [ 163.590101] Stack: Nov 24 15:25:32 vstorage03 kernel: [ 163.590240] c022e80f 00000000 00000001 00000003 f6e3675c f6e36758 00000003 00000001 Nov 24 15:25:32 vstorage03 kernel: [ 163.590996] f6f09ee0 c022fe0c 00000000 00000000 00000000 00000292 f6d05e60 f6e36740 Nov 24 15:25:32 vstorage03 kernel: [ 163.591746] 00000012 f6f4a07c f7bc6aa8 00000000 f6d05e60 f6d05e60 00000000 f6a64000 Nov 24 15:25:32 vstorage03 kernel: [ 163.592495] Call Trace: Nov 24 15:25:32 vstorage03 kernel: [ 163.592644] Inexact backtrace: Nov 24 15:25:32 vstorage03 kernel: [ 163.592645] Nov 24 15:25:32 vstorage03 kernel: [ 163.592938] [<c022e80f>] ? __wake_up_common+0x3f/0x70 Nov 24 15:25:32 vstorage03 kernel: [ 163.593149] [<c022fe0c>] ? __wake_up+0x3c/0x60 Nov 24 15:25:32 vstorage03 kernel: [ 163.593350] [<f7bc6aa8>] ? wthread_queue+0x58/0x120 [iscsi_trgt] Nov 24 15:25:32 vstorage03 kernel: [ 163.593586] [<f7bc1efa>] ? iscsi_scsi_queuecmnd+0x9a/0x100 [iscsi_trgt] Nov 24 15:25:32 vstorage03 kernel: [ 163.593832] [<c023192c>] ? finish_task_switch+0x3c/0xc0 Nov 24 15:25:32 vstorage03 kernel: [ 163.594047] [<f7bc4424>] ? iscsi_session_push_cmnd+0x104/0x1a0 [iscsi_trgt] Nov 24 15:25:32 vstorage03 kernel: [ 163.594301] [<f7bc5c47>] ? recv+0x1b7/0x470 [iscsi_trgt] Nov 24 15:25:32 vstorage03 kernel: [ 163.594518] [<c05f819b>] ? release_sock+0x1b/0x70 Nov 24 15:25:32 vstorage03 kernel: [ 163.594721] [<c063d8af>] ? tcp_ioctl+0x7f/0x1a0 Nov 24 15:25:32 vstorage03 kernel: [ 163.594921] [<f7bc63c5>] ? process_io+0x25/0x100 [iscsi_trgt] Nov 24 15:25:32 vstorage03 kernel: [ 163.595148] [<f7bc6535>] ? istd+0x95/0x100 [iscsi_trgt] Nov 24 15:25:32 vstorage03 kernel: [ 163.595363] [<f7bc64a0>] ? process_io+0x100/0x100 [iscsi_trgt] Nov 24 15:25:32 vstorage03 kernel: [ 163.595591] [<c0266c99>] ? kthread+0x69/0x70 Nov 24 15:25:32 vstorage03 kernel: [ 163.595783] [<c0266c30>] ? kthread_worker_fn+0x150/0x150 Nov 24 15:25:32 vstorage03 kernel: [ 163.595999] [<c070f966>] ? kernel_thread_helper+0x6/0xd Nov 24 15:25:32 vstorage03 kernel: [ 163.596211] Code: Bad EIP value. Nov 24 15:25:32 vstorage03 kernel: [ 163.596488] EIP: [<b76da254>] 0xb76da254 SS:ESP 0068:f6f09e9c Nov 24 15:25:32 vstorage03 kernel: [ 163.596839] CR2: 00000000b76da254 Nov 24 15:25:32 vstorage03 kernel: [ 163.597007] ---[ end trace 3f64c3c2aad82ff4 ]--- Nov 24 15:25:32 vstorage03 kernel: [ 163.597205] note: istd1[1039] exited with preempt_count 1 > > No, it works fine without, but the warning does look a little too serious. See > the explanation in my initial comment. Got it. Thanks. Regards, Rui
(In reply to comment #22) > > Is there any possibility/risk that this is some unknown incompatibility? I'm > > only using the openscsi initiator. > > > I''ve now tested with openiscsi initiator and it seems to work correctly. > However ESXi 5.0 does work on openSUSE 11.3 with iscsi-target... That is at least some progress. Interesting that it used to work, and then stopped. > > The only assert(req->tio) I see in the code I have is in iscsi.c:1408. I > > would suggest you upgrade iscsitarget from Factory, if you don't mind. I > > have a suspicion we're looking at some old code here. > > > Done. iscsi-target in now the factory one. > ~ # rpm -qa '*iscsi*|*kernel*' > yast2-iscsi-client-2.21.9-1.1.1.noarch > yast2-iscsi-server-2.21.5-2.1.1.noarch > iscsitarget-1.4.20-10.2.i586 > kernel-desktop-3.1.0-1.2.1.i586 > > The behavior seems the same. Hmm, any chance you forgot to restart ietd after upgrading? I still can't find that assert() in the code.
(In reply to comment #23) > > That is at least some progress. Interesting that it used to work, and then > stopped. > Yes... > > Hmm, any chance you forgot to restart ietd after upgrading? I still can't find > that assert() in the code. > I've restarted the VM.
I can also confirm that iscsitarget (ietd) does not start under 12.1 (Final version). Error message is (as previously mentioned): # rciscsitarget start Starting iSCSI target service: FATAL: Error inserting crc32c_intel (/lib/modules/3.1.0-1.2-desktop/kernel/arch/x86/crypto/crc32c-intel.ko): No such device # rpm -qa '*iscsi*|*kernel*' kernel-desktop-3.1.0-1.2.1.x86_64 kernel-desktop-base-3.1.0-1.2.1.x86_64 yast2-iscsi-server-2.21.5-2.1.1.noarch iscsitarget-kmp-desktop-1.4.20_k3.1.0_1.1-9.1.2.x86_64 iscsitarget-1.4.20-9.1.2.x86_64 yast2-iscsi-client-2.21.9-1.1.1.noarch iscsitarget-kmp-default-1.4.20_k3.1.0_1.1-9.1.2.x86_64 open-iscsi-2.0.870-41.39.2.x86_64 BTW this report needs to be extended/copied/transferred to openSUSE 12.1 it still sails under 11.4
(In reply to comment #25) > I can also confirm that iscsitarget (ietd) does not start under 12.1 (Final > version). > > Error message is (as previously mentioned): > > # rciscsitarget start > Starting iSCSI target service: FATAL: Error inserting crc32c_intel > (/lib/modules/3.1.0-1.2-desktop/kernel/arch/x86/crypto/crc32c-intel.ko): No > such device Stefan, can you confirm that ietd does not in fact start? The error message is just about an optional module, but ietd should be able to start and should also work with with openscsi initiator.
Disclaimer: I'm not an iscsi expert at all, just another user. Rui, the assert() you're seeing seems to be related to something called NOP-in and the ietd manpage says "KNOWN ISSUES: NOP-In is incomplete.". If you want to your setup to work, maybe you could disable Nop-In somewhere?
CORRECTION!!! In fact ietd starts under 12.1, apologies for not looking closer on Friday. I checked the status of ietd on Friday with /etc/init.d/iscsitarget status which returned (and still returns) "unused" That left me believing it did not start after the error message re the crc32c_intel module. This is/was caused by /sbin/startproc -p /var/run/iscsi_trgt.pid /usr/sbin/ietd not writing the pid file "/var/run/iscsi_trgt.pid". Instead /var/run/ietd.pid is written by ietd itself. strace tells me that startproc only stats /var/run/iscsi_trgt.pid and does not open it. This also prevents a correct shutdown or restart of ietd via /etc/init.d/iscsitarget. The message: FATAL: Error inserting crc32c_intel (/lib/modules/3.1.0-1.2-desktop/kernel/arch/x86/crypto/crc32c-intel.ko): No such device is generated by "modprobe crc32c-intel" in /etc/init.d/iscsitarget and is in fact - as Per already wrote - not related directly to the start of ietd itself. So I can confirm that ietd actually starts despite the error message. Again my apologies for for not looking closer on Friday.
I had this same problem. What I did is modified iscsitarget script in /etc/init.d I modified the variable PIDFILE in /var/run/ietd.pid Now it wil start and stop as it should do. Rob
Lee, could you please have a look?
I am able to get the latest subversion sources (r466) of iscsitarget to compile and run on openSUSE 12.1 with 2.6.37.6 kernel, but I have not yet verified that target is working correctly, since it does not seem to be responding correcting to a send-targets for discovery. The same discovery command works as advertised when discovering a "tgt" target.
I have sent email to the iscsi-target mailing list to try to find out why I cannot discover my iscsitarget target. I am assuming I do not have it set up correctly, but I have to verify correct target operation before I can try to integrate latest iscsitarget code into our iscsitarget package.
(In reply to comment #32) > I have sent email to the iscsi-target mailing list to try to find out why I > cannot discover my iscsitarget target. I am assuming I do not have it set up > correctly, but I have to verify correct target operation before I can try to > integrate latest iscsitarget code into our iscsitarget package. Exactly which problem are you trying to solve here? Apart from the lack of support for NOP-In, iscitarget is working fine on 12.1. I have a test setup with a blade center, it's been working fine since some time December last year.
(In reply to comment #33) > Exactly which problem are you trying to solve here? Apart from the lack of > support for NOP-In, iscitarget is working fine on 12.1. I have a test setup > with a blade center, it's been working fine since some time December last year. I need to verify you assertion for myself before I can update the code. I assume you are correct, i.e. that iscsitarget is working fine. To do that, I want to discover and then use an iscsitarget target from my open-iscsi initiator. Perhaps you can help me understand why the "sendtargets=all" request is not returning any targets?
Excellent news: with help from iscsi-target mailing list, figured out I had a bogus initiators.allow file (from a previous installation). Now I will contact the iscsitarget package owner and see about updating the openSUSE 12.1 version.
I would like to update the iscsitarget package for openSUSE 12.1 to the latest iscsitarget from the (stable) trunk, which I have successfully tested for this bug. The current iscsitarget is broken in several ways in openSUSE 12.1. See also bnc#743562. Note that this would be an update from iscsitarget version 1.4.20 (from April 2010) to 1.4.20.3 (from March 18, 2011). From the Changes file in 1.4.20.3: |Summary of changes from v1.4.20 to Current |================================= |Arne Redlich | o adapt backward compat mechanism in Makefile to kernels >= 2.6.33 | o uninitialized data fixes pointed out by valgrind | o fix invalid read in iSNS code pointed out by valgrind | o Fixed iSNS initialization issue, thanks to majianpeng@gmail.com | o The NIPQUAD macro has been removed, instead "%pI4" is used | o Converted semaphores to mutexes | o Fixed printing IPv4 addresses in /proc/net/iet/session for kernels >= 2.6.33 | o Fixed block device handling for kernels >= 2.6.38 | |Ross Walker | o restore SCSI SN behaviour of IET < 1.4.20 (VMWare compatibility) | o check buffer boundaries in iSNS code (CVE-2010-2221) | o fix memleak in iSNS ACL code | o clean up iSCSI login response error handling | o rework ietd startup to avoid concurrent ietds | o fix soft lockup during UA allocation | o change DISTDIR to DESTDIR | o avoid deletion of targets with active sessions | o byte swap fix in MD5 / SHA1 code | o Updated initd scripts to reflect PID file name change | o Removed stray RPM build dependency on openssl from spec file | o Fixed crypto API error handling (ERR_PTR instead of a NULL) | o Fixed small memory leak in volume args buffer on BSD | o Fixed io context handling on kernels >= 2.6.25 | o Fixed max_cmd_sn not being set for the session | o Fixed issue where StatSN was being updated when a command was ignored | o Fixed connection accounting in ietd for session reinstatements | o Fixed MaxOutStandingR2T handling | o Stripped zone id off ipv6 addresses in SendTargets | o Time2Retain fixed at 0 since it isn't implemented | |Chris Siebenmann, Wido den Hollander | o 2.6.36 compile fix | |Craig | o Makefile respects LDFLAGS | |Jason Zhang | o Fixed re-enabling listening after max connections was exceeded | o Fix NULL-pointer dereference due to race in UA handling | |Martin Hicks | o Added variable for depmod | o Don't install kernel module executable | o Don't use bash for initd script
this minor version update would be fine. please submitreq against openSUSE:12.1:Update:Test
*** Bug 743562 has been marked as a duplicate of this bug. ***
Submitted to osc as request id 102938.
unfortunately the target package name is wrong please use "osc sr openSUSE:12.1:Update:Test iscsitarget"
(In reply to comment #44) > unfortunately the target package name is wrong > please use "osc sr openSUSE:12.1:Update:Test iscsitarget" Done. Request id 103080. I should have suspected previous submit did not work, since diff was empty. This one looked better.
This is an autogenerated message for OBS integration: This bug (676803) was mentioned in https://build.opensuse.org/request/show/103080 12.1 / iscsitarget
Please don't forget Factory
Resubmitted to osc as request id 104850, after removing incorrect patch configuration file.
This is an autogenerated message for OBS integration: This bug (676803) was mentioned in https://build.opensuse.org/request/show/104850 12.1 / iscsitarget
Submitted to Factory from branch home:lee_duncan:branches:hardware/iscsitarget.
Marking this bug as resolved since updated package has been submitted to build service and is pending for 12.1.
*** Bug 738536 has been marked as a duplicate of this bug. ***
(In reply to comment #55) > Marking this bug as resolved since updated package has been submitted to build > service and is pending for 12.1. Resolved ? So 11.4 is "out on the cold" ?
(In reply to comment #57) > (In reply to comment #55) > > Marking this bug as resolved since updated package has been submitted to build > > service and is pending for 12.1. > Resolved ? So 11.4 is "out on the cold" ? Gary: what do you mean? By "11.4", do you mean SLE 11 SP4? That does not make sense, since SLE 11 SP3 is not yet out.
Lee, the initial bug report was against openSUSE 11.4. It's still listed in the OS section of the bug report and in the history of the bug. If the fix applies to openSUSE 11.4, please apply it there as well. It's still supported for another month and change.
Exactly Jeff Thanks
No problem. 11.4 updated to use correct PIDFILE, but other more invasive changes (i.e. moving log files and delivering new config files) not done. Request submitted to build service. I also submitted a request to update openSUSE factory.