how to change the log level

25 views
Skip to first unread message

Bigadmin

unread,
Jun 20, 2007, 10:02:37 PM6/20/07
to Core-iSCSI, is...@unixplanet.biz
Hello

is there any way to change log level of iscsi-core initiator ?
I want to change it to debug level to see if our problem is reside
on target side of initiator side. I am not seeing any error on /var/
log/dmesg or
/var/log/messages.


Thanks

Edwin Clubb

unread,
Jun 22, 2007, 12:55:19 PM6/22/07
to Core-...@googlegroups.com, is...@unixplanet.biz
I believe all you need to do is to set "DEBUG_ISCSI = 1" in the MCONFIG file of the
initiator source and recompile.

Ed

-------------------------------------
Edwin Clubb
VMTH IT Services, UC Davis
One Shields Ave
Davis, CA 95616
530-752-5996

Bigadmin

unread,
Jun 24, 2007, 12:47:44 PM6/24/07
to Core-iSCSI
Hello Edwin,

is there any other way to change the log level to debug.
I rather not to recompile kernel on our production servers.

Thanks

Edwin Clubb

unread,
Jun 26, 2007, 12:09:55 PM6/26/07
to Core-...@googlegroups.com
Not that I know of. Sorry.

Ed

bdbl...@gmail.com

unread,
Jun 27, 2007, 1:01:19 AM6/27/07
to Core-iSCSI
Hello Edwin

Actually you would only be recompiling the core-iscsi kernel module..

What kind of problem are you having?

bdb

Bigadmin

unread,
Jul 16, 2007, 4:03:25 PM7/16/07
to Core-iSCSI
sometimes when I do scp some files from one target to other,
I get file stalled, and transfer rate decrease to 0.

initiator that I am transfering the files to, will unresponsive to ssh
but pingable
then after some time it comes back and I can ssh to it.
I can restart the scp and it goes well next time but very slow.
any suggetion ?

here is some lines from kernel log files "
Jul 16 16:39:06 Hostname kernel: CPU0 attaching sched-domain:
Jul 16 16:39:06 Hostname kernel: domain 0: span 00000003
Jul 16 16:39:06 Hostname kernel: groups: 00000001 00000002
Jul 16 16:39:06 Hostname kernel: domain 1: span 0000000f
Jul 16 16:39:06 Hostname kernel: groups: 00000003 0000000c
Jul 16 16:39:06 Hostname kernel: CPU1 attaching sched-domain:
Jul 16 16:39:06 Hostname kernel: domain 0: span 00000003
Jul 16 16:39:06 Hostname kernel: groups: 00000002 00000001
Jul 16 16:39:06 Hostname kernel: domain 1: span 0000000f
Jul 16 16:39:06 Hostname kernel: groups: 00000003 0000000c
Jul 16 16:39:06 Hostname kernel: CPU2 attaching sched-domain:
Jul 16 16:39:06 Hostname kernel: domain 0: span 0000000c
Jul 16 16:39:06 Hostname kernel: groups: 00000004 00000008
Jul 16 16:39:06 Hostname kernel: domain 1: span 0000000f
Jul 16 16:39:06 Hostname kernel: groups: 0000000c 00000003
Jul 16 16:39:06 Hostname kernel: CPU3 attaching sched-domain:
Jul 16 16:39:06 Hostname kernel: domain 0: span 0000000c
Jul 16 16:39:06 Hostname kernel: groups: 00000008 00000004
Jul 16 16:39:06 Hostname kernel: domain 1: span 0000000f
Jul 16 16:39:06 Hostname kernel: groups: 0000000c 00000003
Jul 16 16:39:06 Hostname kernel: ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0._PRT]
Jul 16 16:39:06 Hostname kernel: ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0.PALO._PRT]
Jul 16 16:39:06 Hostname kernel: ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0.PALO.DOBA._PRT]
Jul 16 16:39:06 Hostname kernel: ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0.PALO.DOBB._PR
Jul 16 16:39:06 Hostname kernel: CFI: Found no ichxrom @ffff0000
device at location zero
Jul 16 16:39:06 Hostname kernel: JEDEC: Found no ichxrom @ffff0000
device at location zero
Jul 16 16:39:06 Hostname kernel: CFI: Found no ichxrom @ffff0000
device at location zero
Jul 16 16:39:06 Hostname kernel: JEDEC: Found no ichxrom @ffff0000
device at location zero
Jul 16 16:39:06 Hostname kernel: PCI: Setting latency timer of device
0000:00:1d.7 to 64
Jul 16 16:39:06 Hostname kernel: PCI: cache line size of 128 is not
supported by device 0000:00:1d.7
Jul 16 16:39:06 Hostname kernel: PCI: Setting latency timer of device
0000:00:1d.0 to 64
Jul 16 16:39:06 Hostname kernel: PCI: Setting latency timer of device
0000:00:1d.1 to 64
Jul 16 16:39:06 Hostname kernel: PCI: Setting latency timer of device
0000:00:1d.2 to 64

Jul 16 16:39:22 Hostname kernel: eth1: no IPv6 routers present
Jul 16 16:39:22 Hostname kernel: eth0: no IPv6 routers present

Reply all
Reply to author
Forward
0 new messages