Bug#964908:

2020-08-13 Thread Thomas Kotzian 
Success report.
tomcat 9.0.37-3 works fine now.
Thank you!

Bug#964908:

2020-08-03 Thread Thomas Kotzian 
package: tomcat9
version: 9.0.37-2

the problem is still there - now with other missing files … the problems start 
to be visible after deploying some applications 

2 new missing files :

java.lang.ClassNotFoundException: 
org.apache.tomcat.websocket.pojo.PojoEndpointClient
java.lang.ClassNotFoundException: 
org.apache.tomcat.util.http.fileupload.impl.InvalidContentTypeException

backporting the bnd files on every tomcat-release seems to be major task 
compared to a bnd upgrade…



log output:

[2020-08-03 05:28:39] [info] Initialisiere ProtocolHandler["http-nio-8080"]
[2020-08-03 05:28:39] [info] Server initialization in [491] milliseconds
[2020-08-03 05:28:39] [info] Starting service [Catalina]
[2020-08-03 05:28:39] [info] Starting Servlet engine: [Apache Tomcat/9.0.37 
(Debian)]
[2020-08-03 05:28:39] [info] Deploying deployment descriptor 
[/etc/tomcat9/Catalina/localhost/host-manager.xml]
[2020-08-03 05:28:39] [warning] The path attribute with value [/host-manager] 
in deployment descriptor [/etc/tomcat9/Catalina/localhost/host-manager.xml] has 
been ignored
[2020-08-03 05:28:40] [info] jsp.tldCache.noTldSummary
[2020-08-03 05:28:40] [crit] Error deploying deployment descriptor 
[/etc/tomcat9/Catalina/localhost/host-manager.xml]
[2020-08-03 05:28:40] [crit] java.lang.IllegalStateException: Error starting 
child
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:720)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:631)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1830)
[2020-08-03 05:28:40] [crit] at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
[2020-08-03 05:28:40] [crit] at 
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
[2020-08-03 05:28:40] [crit] at 
org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
[2020-08-03 05:28:40] [crit] at 
java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:526)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:425)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1576)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:936)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
[2020-08-03 05:28:40] [crit] at 
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
[2020-08-03 05:28:40] [crit] at 
org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
[2020-08-03 05:28:40] [crit] at 
java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.core.StandardService.startInternal(StandardService.java:421)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
[2020-08-03 05:28:40] [crit] at 
org.apache.catalina.startup.Catalina.start(Catalina.java:738)
[2020-08-03 0

Bug#964908:

2020-07-17 Thread Thomas Kotzian 
i have narrowed to problem down to an old version of the bnd tool.

bnd in the debian repos is 3.5.0 - which seemed to work for tomcat9 up to 
9.0.36.

tomcat9 9.0.37 changed the format of the bnd-file 
res/bnd/tomcat-coyote.jar.tmp.bnd to use the instruction "-includepackage:" 
which is only found in bnd 4.x and newer.

the solution to the problem seems an update to bnd debian package or using 
tomcat bnd 5.1.1 which gets downloaded in the official builds.

Bug#964908:

2020-07-16 Thread Thomas Kotzian 
Dear maintainer,

i have the same problem. - i tried to replace the tomcat-jars from the official 
distribution but that didn’t work - another class missing error appears.

The missing class 
org.apache.tomcat.util.modeler.modules.MbeansDescriptorsIntrospectionSource is 
in the file tomcat-coyote.jar of the official distribution but not in the 
packaged jars.

The file MbeansDescriptorsIntrospectionSource is also in the 
debian-package-git-repo but it somehow doesn’t get built or packaged.

The package is currently broken, so please consider upgrading the bug priority 
to grave.

Please help!

Bug#958532: (no subject)

2020-04-23 Thread Thomas Kotzian 
I have tried the latest linux kernel - now i see corrupted altnames on
the bridge interface ...


$ uname -a

Linux targo.home.intra 5.6.0-trunk-amd64 #1 SMP Debian 5.6.4-1~exp1
(2020-04-17) x86_64 GNU/Linux)


$ ip a

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eno1:  mtu 1500 qdisc mq
master bond0 state UP group default qlen 1000
    link/ether 5a:ba:84:53:bd:fb brd ff:ff:ff:ff:ff:ff permaddr
0c:c4:7a:6b:2f:ac
    altname enp6s0
3: eno2:  mtu 1500 qdisc mq
master bond0 state UP group default qlen 1000
    link/ether 5a:ba:84:53:bd:fb brd ff:ff:ff:ff:ff:ff permaddr
0c:c4:7a:6b:2f:ad
    altname enp7s0
4: bond0:  mtu 1500 qdisc
noqueue state UP group default qlen 1000
    link/ether 5a:ba:84:53:bd:fb brd ff:ff:ff:ff:ff:ff
    inet6 fe80::58ba:84ff:fe53:bdfb/64 scope link
   valid_lft forever preferred_lft forever
5: bond0.10@bond0:  mtu 1500 qdisc
noqueue master br10 state UP group default qlen 1000
    link/ether 5a:ba:84:53:bd:fb brd ff:ff:ff:ff:ff:ff
6: br10:  mtu 1500 qdisc noqueue state
UP group default qlen 1000
    link/ether 42:ba:1e:e8:38:9e brd ff:ff:ff:ff:ff:ff
    altname 0Ü??U
    altname -
    inet 192.168.80.21/24 brd 192.168.80.255 scope global br10
   valid_lft forever preferred_lft forever
    inet6 fd99:f74:6b13:ca16::1:15/64 scope global
   valid_lft forever preferred_lft forever
    inet6 fe80::40ba:1eff:fee8:389e/64 scope link
   valid_lft forever preferred_lft forever

Bug#958532: linux-image-5.5.0-2-amd64: ip shows corrupt altname for bonding interfaces

2020-04-23 Thread Thomas Kotzian 
Package: src:linux
Version: 5.5.17-1
Severity: important


the problem started with linux kernel 5.5 (using package 
linux-image-5.5.0-1-amd64).
it showed up when trying to start the service salt-minion which parses the ip 
configuration on startup and fails because of an utf-8 parsing error..
all interfaces have a valid altname applied except bonding interfaces. the 
value shown in altname changes on restart to some different, still invalid 
value.
i have found the problem on 2 different machines.



-- Package-specific info:
** Version:
Linux version 5.5.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-10)) #1 SMP Debian 5.5.17-1 (2020-04-15)

** Command line:
BOOT_IMAGE=/vmlinuz-5.5.0-2-amd64 root=/dev/mapper/targo_vg-root_lv ro quiet

** Not tainted

** Kernel log:
[74998.128281] device vnet1 left promiscuous mode
[74998.128288] br10: port 3(vnet1) entered disabled state
[74998.544253] audit: type=1400 audit(1587556551.628:49): apparmor="STATUS" 
operation="profile_remove" profile="unconfined" 
name="libvirt-e2fbc3b1-9394-4627-85a9-83c4ed7c0627" pid=42590 
comm="apparmor_parser"
[75000.212168] br10: port 4(vnet2) entered disabled state
[75000.212523] device vnet2 left promiscuous mode
[75000.212534] br10: port 4(vnet2) entered disabled state
[75000.646011] audit: type=1400 audit(1587556553.728:50): apparmor="STATUS" 
operation="profile_remove" profile="unconfined" 
name="libvirt-1db48d16-aee8-4fd2-844d-924a648732f2" pid=42627 
comm="apparmor_parser"
[75001.007854] br10: port 5(vnet3) entered disabled state
[75001.008065] device vnet3 left promiscuous mode
[75001.008069] br10: port 5(vnet3) entered disabled state
[75001.439979] audit: type=1400 audit(1587556554.523:51): apparmor="STATUS" 
operation="profile_remove" profile="unconfined" 
name="libvirt-299b4305-952f-4b00-8fe6-9884573c1a6d" pid=42646 
comm="apparmor_parser"
[75002.812132] br10: port 6(vnet4) entered disabled state
[75002.812479] device vnet4 left promiscuous mode
[75002.812485] br10: port 6(vnet4) entered disabled state
[75003.234588] audit: type=1400 audit(1587556556.315:52): apparmor="STATUS" 
operation="profile_remove" profile="unconfined" 
name="libvirt-bf890b82-67ea-47da-92d1-ae5852713784" pid=42675 
comm="apparmor_parser"
[75008.564035] br10: port 8(vnet6) entered disabled state
[75008.564255] device vnet6 left promiscuous mode
[75008.564261] br10: port 8(vnet6) entered disabled state
[75008.989397] audit: type=1400 audit(1587556562.071:53): apparmor="STATUS" 
operation="profile_remove" profile="unconfined" 
name="libvirt-36a53cc9-cb6a-4c29-96ae-53e2433432f6" pid=42757 
comm="apparmor_parser"
[75010.448086] br10: port 7(vnet5) entered disabled state
[75010.448324] device vnet5 left promiscuous mode
[75010.448329] br10: port 7(vnet5) entered disabled state
[75010.870509] audit: type=1400 audit(1587556563.951:54): apparmor="STATUS" 
operation="profile_remove" profile="unconfined" 
name="libvirt-a3f86f9c-93ed-4c35-b460-1b1a0251c879" pid=42764 
comm="apparmor_parser"
[75173.341550] audit: type=1400 audit(1587556726.420:55): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="virt-aa-helper" pid=45824 comm="apparmor_parser"
[75173.393566] audit: type=1400 audit(1587556726.472:56): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="libvirtd" pid=45827 
comm="apparmor_parser"
[75173.408578] audit: type=1400 audit(1587556726.488:57): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="libvirtd//qemu_bridge_helper" pid=45827 comm="apparmor_parser"
[77644.039177] audit: type=1400 audit(1587559197.062:58): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="libvirt-c4a2111e-7c4e-42d4-938d-ffc866cf149a" pid=48892 
comm="apparmor_parser"
[77644.178905] audit: type=1400 audit(1587559197.202:59): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="libvirt-c4a2111e-7c4e-42d4-938d-ffc866cf149a" pid=48896 
comm="apparmor_parser"
[77644.315364] audit: type=1400 audit(1587559197.338:60): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="libvirt-c4a2111e-7c4e-42d4-938d-ffc866cf149a" pid=48900 
comm="apparmor_parser"
[77644.452402] audit: type=1400 audit(1587559197.474:61): apparmor="STATUS" 
operation="profile_replace" info="same as current profile, skipping" 
profile="unconfined" name="libvirt-c4a2111e-7c4e-42d4-938d-ffc866cf149a" 
pid=48904 comm="apparmor_parser"
[77644.459461] br10: port 2(vnet0) entered blocking state
[77644.459464] br10: port 2(vnet0) entered disabled state
[77644.459545] device vnet0 entered promiscuous mode
[77644.459712] br10: port 2(vnet0) entered blocking state
[77644.459715] br10: port 2(vnet0) entered forwarding state
[77644.624522] audit: type=1400 audit(1587559197.646:62): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="libvirt-c4a2111e-7c4e-42d4-938d-ffc866cf149a" pid=48915 
comm="apparmor_pars

Bug#918107: Random boot failure using VMware Paravirtual Adapter

2019-01-03 Thread Thomas Kotzian 
Package: linux-image-4.19.0-1-amd64
Version: 4.19.12-1

Random boot failures on VMware when VM uses the Paravirtual Adapter. I drop 
into a busybox shell after the first line from the kernel. No disk found. 
Normally the 2nd line mentions the disk - this line doesn’t appear on failing 
boots - no disk is accessible. Rebooting sometimes works.

Kernel 4.18.0-3-amd64 work all the time. 4.19.3-1 is also broken.

LSI SCSI controller works fine on every reboot.

I have looked through the changelog of 4.19.12. it mentions code re-arrangement 
in pv_scsi driver - maybe something broke there?

Bug#768922: pacemaker: stopped working after upgrade to 1.1.10+git20130802-4.1

2014-11-12 Thread Thomas Kotzian 
Hello!

Pacemaker was compiled in unstable to a newer version of libqb0 (0.14 or 0.17). 
In testing/jessie there's only libqb0 (0.11).

fix would be to add a libqb0 (>=0.14) as dependency in package libcrmcommon3.

manually updating libqb0  to the version in unstable and restart of pacemaker 
fixes the problem.


On Mon, 10 Nov 2014 00:08:48 -0800 Frank Edelhaeuser  wrote:
> Package: pacemaker
> Version: 1.1.10+git20130802-4.1
> Severity: grave
> Justification: renders package unusable
> 
> Hello,
> 
> After upgrading pacemaker to 1.1.10+git20130802-4.1, the cluster doesn't work 
> any more. All resources are unavailable. Command line tools report an 
> undefined symbol in libcrmcommon.
> 
>   # pacemakerd --help
>   pacemakerd: symbol lookup error: /usr/lib/libcrmcommon.so.3: undefined 
> symbol: qb_ipcs_connection_auth_set
> 
>   # crm
>   crmd: symbol lookup error: /usr/lib/libcrmcommon.so.3: undefined symbol: 
> qb_ipcs_connection_auth_set
>   ERROR: crmd exited with 127
>   crm(live)#
> 


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#462689: apt-cacher needs to depend on libwww-perl

2008-01-26 Thread Thomas Kotzian 
Package: apt-cacher
Version: 1.6.1
Severity: normal

i did an update of apt-cacher from 1.5.x to 1.6.1 and the package terminates 
with:

Starting Apt-Cacher: apt-cacherCan't locate HTTP/Response.pm in @INC (@INC 
contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 
/usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 
/usr/local/lib/site_perl .) at /usr/sbin/apt-cacher line 57.
BEGIN failed--compilation aborted at /usr/sbin/apt-cacher line 57.
.

after installing libwww-perl everything works fine.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'stable'), (500, 
'testing-proposed-updates'), (500, 'proposed-updates'), (70, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18-5-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apt-cacher depends on:
ii  bzip2 1.0.4-2high-quality block-sorting file co
ii  ed0.7-1  The classic unix line editor
ii  libwww-curl-perl  3.02-2+b3  Perl bindings to libcurl
ii  perl  5.8.8-12   Larry Wall's Practical Extraction 

Versions of packages apt-cacher recommends:
ii  libberkeleydb-perl0.31-1 use Berkeley DB 4 databases from P

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#459732: linux-image-2.6.23-1-amd64: scsi changer device not working - error in scsi subsystem

2008-01-08 Thread Thomas Kotzian 

Am 08.01.2008 um 13:18 schrieb maximilian attems:


On Tue, Jan 08, 2008 at 12:57:44PM +0100, Thomas Kotzian wrote:
the media changer device doesn't work. on startup an error -EEXIST  
for a ch kobject gets triggered.


linux-image-2.6.21-2-amd64 (2.6.21-6) works
every kernel later (even upstream) doesn't

the working snippet ...

ch0: type #1 (mt): 0x1+1 [medium transport]
ch0: type #2 (st): 0x1000+81 [storage]
ch0: type #3 (ie): 0x10+6 [import/export]
ch0: type #4 (dt): 0x100+2 [data transfer]
ch0: dt 0x100: ID/LUN unknown
ch0: dt 0x101: ID/LUN unknown
ch0: INITIALIZE ELEMENT STATUS, may take some time ...
ch0: ... finished
ch 2:0:0:1: Attached scsi changer ch0
sd 1:0:0:0: Attached scsi generic sg0 type 0
st 0:0:0:0: Attached scsi generic sg1 type 1
sd 3:0:0:0: Attached scsi generic sg2 type 0
st 2:0:0:0: Attached scsi generic sg3 type 1
ch 2:0:0:1: Attached scsi generic sg4 type 8

the failing snippet ...

scsi 2:0:0:1: Medium ChangerADIC Scalar i500  400G PQ:  
0 ANSI: 3
kobject_add failed for 2:0:0:1 with -EEXIST, don't try to register  
things with the same name in the same directory.


Call Trace:
[] kobject_shadow_add+0x16e/0x1a2
[] device_add+0x99/0x614
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: disabled,  
doesn't support DPO or FUA

[] :scsi_mod:scsi_sysfs_add_sdev+0x35/0x218
[] :scsi_mod:scsi_probe_and_add_lun+0x953/0xa95
[] :scsi_mod:scsi_execute_req+0x82/0xde
[] :scsi_mod:__scsi_scan_target+0x407/0x5c3
[] :scsi_mod:scsi_scan_target+0x96/0xbb
[] :scsi_transport_fc:fc_scsi_scan_rport+0x59/0x7a
[] :scsi_transport_fc:fc_scsi_scan_rport+0x0/0x7a
[] run_workqueue+0x7f/0x10b
[] worker_thread+0x0/0xe4
[] worker_thread+0xda/0xe4
[] autoremove_wake_function+0x0/0x2e
[] kthread+0x47/0x76
[] child_rip+0xa/0x12
[] kthread+0x0/0x76
[] child_rip+0x0/0x12

error 1
st 2:0:0:0: Unexpected response from lun 1 while scanning, scan  
aborted

sd 3:0:0:0: [sdb] 1874933760 512-byte hardware sectors (959966 MB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 23 00 00 00
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: disabled,  
doesn't support DPO or FUA

sdb: sdb4 < sdb5 >
sd 3:0:0:0: [sdb] Attached SCSI disk
SCSI Media Changer driver v0.25
ch 2:0:0:1: rejecting I/O to dead device
ch0: type #1 (mt): 0x0+0 [medium transport]
ch0: type #2 (st): 0x0+0 [storage]
ch0: type #3 (ie): 0x0+0 [import/export]
ch0: type #4 (dt): 0x0+0 [data transfer]
ch0: INITIALIZE ELEMENT STATUS, may take some time ...
ch 2:0:0:1: rejecting I/O to dead device
ch0: ... finished
ch 2:0:0:1: Attached scsi changer ch0
st 1:0:0:0: Attached scsi generic sg0 type 1
sd 0:0:0:0: Attached scsi generic sg1 type 0
st 2:0:0:0: Attached scsi generic sg2 type 1
ch 2:0:0:1: Attached scsi generic sg3 type 8
sd 3:0:0:0: Attached scsi generic sg4 type 0


nice, please check out 2.6.23-rc7 from trunk and
see if it makes a difference, see apt lines
-> http://wiki.debian.org/DebianKernel

if aboves makes *no* progress, then please holler
upstream in bugzilla.kernel.org and let us know
the upstream bug number.

debian carries no scsi specific patches, although
the changer was long time such a boy.

best regards

--
maks


I tried kernel 2.6.24-rc6 from experimental (linux-image-2.6.24-rc6- 
amd642.6.24~rc6-1~experimental.1~snapshot.10030)

and it works!!!

thanks for your time!

best regards,
thomas



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#459732: linux-image-2.6.23-1-amd64: scsi changer device not working - error in scsi subsystem

2008-01-08 Thread Thomas Kotzian 
Package: linux-image-2.6.23-1-amd64
Version: 2.6.23-2
Severity: important


the media changer device doesn't work. on startup an error -EEXIST for a ch 
kobject gets triggered. 

linux-image-2.6.21-2-amd64 (2.6.21-6) works 
every kernel later (even upstream) doesn't

the working snippet ...

ch0: type #1 (mt): 0x1+1 [medium transport]
ch0: type #2 (st): 0x1000+81 [storage]
ch0: type #3 (ie): 0x10+6 [import/export]
ch0: type #4 (dt): 0x100+2 [data transfer]
ch0: dt 0x100: ID/LUN unknown
ch0: dt 0x101: ID/LUN unknown
ch0: INITIALIZE ELEMENT STATUS, may take some time ...
ch0: ... finished
ch 2:0:0:1: Attached scsi changer ch0
sd 1:0:0:0: Attached scsi generic sg0 type 0
st 0:0:0:0: Attached scsi generic sg1 type 1
sd 3:0:0:0: Attached scsi generic sg2 type 0
st 2:0:0:0: Attached scsi generic sg3 type 1
ch 2:0:0:1: Attached scsi generic sg4 type 8

the failing snippet ...

scsi 2:0:0:1: Medium ChangerADIC Scalar i500  400G PQ: 0 ANSI: 3
kobject_add failed for 2:0:0:1 with -EEXIST, don't try to register things with 
the same name in the same directory.

Call Trace:
 [] kobject_shadow_add+0x16e/0x1a2
 [] device_add+0x99/0x614
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: disabled, doesn't support 
DPO or FUA
 [] :scsi_mod:scsi_sysfs_add_sdev+0x35/0x218
 [] :scsi_mod:scsi_probe_and_add_lun+0x953/0xa95
 [] :scsi_mod:scsi_execute_req+0x82/0xde
 [] :scsi_mod:__scsi_scan_target+0x407/0x5c3
 [] :scsi_mod:scsi_scan_target+0x96/0xbb
 [] :scsi_transport_fc:fc_scsi_scan_rport+0x59/0x7a
 [] :scsi_transport_fc:fc_scsi_scan_rport+0x0/0x7a
 [] run_workqueue+0x7f/0x10b
 [] worker_thread+0x0/0xe4
 [] worker_thread+0xda/0xe4
 [] autoremove_wake_function+0x0/0x2e
 [] kthread+0x47/0x76
 [] child_rip+0xa/0x12
 [] kthread+0x0/0x76
 [] child_rip+0x0/0x12

error 1
st 2:0:0:0: Unexpected response from lun 1 while scanning, scan aborted
sd 3:0:0:0: [sdb] 1874933760 512-byte hardware sectors (959966 MB)
sd 3:0:0:0: [sdb] Write Protect is off
sd 3:0:0:0: [sdb] Mode Sense: 23 00 00 00
sd 3:0:0:0: [sdb] Write cache: enabled, read cache: disabled, doesn't support 
DPO or FUA
 sdb: sdb4 < sdb5 >
sd 3:0:0:0: [sdb] Attached SCSI disk
SCSI Media Changer driver v0.25 
ch 2:0:0:1: rejecting I/O to dead device
ch0: type #1 (mt): 0x0+0 [medium transport]
ch0: type #2 (st): 0x0+0 [storage]
ch0: type #3 (ie): 0x0+0 [import/export]
ch0: type #4 (dt): 0x0+0 [data transfer]
ch0: INITIALIZE ELEMENT STATUS, may take some time ...
ch 2:0:0:1: rejecting I/O to dead device
ch0: ... finished
ch 2:0:0:1: Attached scsi changer ch0
st 1:0:0:0: Attached scsi generic sg0 type 1
sd 0:0:0:0: Attached scsi generic sg1 type 0
st 2:0:0:0: Attached scsi generic sg2 type 1
ch 2:0:0:1: Attached scsi generic sg3 type 8
sd 3:0:0:0: Attached scsi generic sg4 type 0


the device gets listed but has the state set to deleted.

thanks for your help!

thomas

-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'stable'), (500, 
'testing-proposed-updates'), (500, 'proposed-updates'), (70, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.21-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.23-1-amd64 depends on:
ii  e2fsprogs1.40.3-1ext2 file system utilities and lib
ii  initramfs-tools [linux-initr 0.91d   tools for generating an initramfs
ii  module-init-tools3.3-pre11-4 tools for managing Linux kernel mo

linux-image-2.6.23-1-amd64 recommends no packages.

-- debconf information excluded
Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 
4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 
2007
Command line: root=/dev/sda2 ro 
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009d000 (usable)
 BIOS-e820: 0009d000 - 000a (reserved)
 BIOS-e820: 000c2000 - 0010 (reserved)
 BIOS-e820: 0010 - bff1 (usable)
 BIOS-e820: bff1 - bff1c000 (ACPI data)
 BIOS-e820: bff1c000 - bff8 (ACPI NVS)
 BIOS-e820: bff8 - c000 (reserved)
 BIOS-e820: e000 - f000 (reserved)
 BIOS-e820: fec0 - fec00400 (reserved)
 BIOS-e820: fee0 - fee01000 (reserved)
 BIOS-e820: fff8 - 0001 (reserved)
 BIOS-e820: 0001 - 00024000 (usable)
Entering add_active_range(0, 0, 157) 0 entries of 3200 used
Entering add_active_range(0, 256, 786192) 1 entries of 3200 used
Entering add_active_range(0, 1048576, 2359296) 2 entries of 3200 used
end_pfn_map = 2359296
DMI present.
ACPI: RSDP 000F6F50, 0014 (r0 PTLTD )
ACPI: RSDT BFF17D77, 0038 (r1 PTLTDRSDT604  LTP0)
ACPI: FACP BFF1BA8E, 0074 (r1 NVIDIA CK8S  604 PTL_F4240)
ACPI: DSDT BFF

Bug#449272: Alternative (buggy, incomplete) firewire stack shipped instead of the stable one

2008-01-08 Thread Thomas Kotzian 

maks: i'm the *second* to holler due to ethernet over firewire!

only the newer stack is built in kernel 2.6.23-1 - no blacklisting  
possible - no choice!


regards,
thomas



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#445957: clarification

2008-01-08 Thread Thomas Kotzian 
snapshotting works now: the problem was a selfwritten script that  
creates and mounts a snapshot.


the pattern was:
for example 3 snapshots ...

snapshot 1:
create: ok
mount: ok

snapshot 2:
create: hang ...
cpu is busy in kernel mode on all cpus (2 cpus, 4 cores) - verified by  
htop


solution:

i have split the snapshot creation and mount part into 2 loops:

first create all 3 snapshots
sleep 3
mount all 3 snapshots

now everything works fine.

thanks for your time!

please close this bug report.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#445957: linux-source-2.6.22: creating a snapshot hangs the system

2007-10-09 Thread Thomas Kotzian 
Package: linux-source-2.6.22
Version: 2.6.22-4
Severity: grave
Justification: causes non-serious data loss

when i create a snapshot with for example

lvcreate -s -L 3g -n snap_var_lv /dev/system_vg/var_lv  

the command hangs, is uninterruptable and the system is frozen.

tested with linux-image-2.6.22-amd64, linux-image-2.6.22-486 and some systems
linux-image-2.6.21-{amd64,486} works perfectly.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'stable'), (500, 
'testing-proposed-updates'), (500, 'proposed-updates'), (70, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18-5-xen-amd64 (SMP w/1 CPU core)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#363297: backupninja: backup handler for pgsql not working

2006-04-18 Thread Thomas Kotzian 
Package: backupninja
Version: 0.9.3-6
Severity: important
Tags: patch

pgsql handler can't backup to the backupdir because the shell variables are not 
expanded
because the command string is enclosed in ' not ". - my patch changes that and 
adds eval
to the command call.


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (800, 'testing'), (700, 'stable'), (500, 'proposed-updates'), 
(70, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.6-xen
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages backupninja depends on:
ii  bash  3.1-4  The GNU Bourne Again SHell
ii  dialog1.0-20060221-1 Displays user-friendly dialog boxe
ii  mawk  1.3.3-11   a pattern scanning and text proces

backupninja recommends no packages.

-- no debconf information


--- pgsql.orig  2006-04-08 23:03:53.0 +0200
+++ pgsql   2006-04-18 12:39:04.0 +0200
@@ -72,13 +72,13 @@
 # if $databases = all, use pg_dumpall
 if [ "$databases" == "all" ]; then
 if [ $usevserver = yes ]; then
-   execstr='$VSERVER $vsname exec su - postgres -c \"$PGSQLDUMPALL > 
$backupdir/${vsname}.sql\"'
+   execstr="$VSERVER $vsname exec su - postgres -c \"$PGSQLDUMPALL > 
$backupdir/${vsname}.sql\""
 else
-   execstr='su - postgres -c \"$PGSQLDUMPALL > 
$backupdir/${localhost}-all.sql\"'
+   execstr="su - postgres -c \"$PGSQLDUMPALL > 
$backupdir/${localhost}-all.sql\""
 fi
 debug "$execstr"
 if [ ! $test ]; then
-   output=`$execstr 2>&1`
+   output=`eval $execstr 2>&1`
code=$?
if [ "$code" == "0" ]; then
debug $output
@@ -94,13 +94,13 @@
 for db in $databases; do
if [ $usevserver = yes ]
then
-   execstr='$VSERVER $vsname exec su - postgres -c \"$PGSQLDUMP $db > 
$backupdir/${db}.sql\"'
+   execstr="$VSERVER $vsname exec su - postgres -c \"$PGSQLDUMP $db > 
$backupdir/${db}.sql\""
else
-   execstr='su - postgres -c \"$PGSQLDUMP $db > $backupdir/${db}.sql\"'
+   execstr="su - postgres -c \"$PGSQLDUMP $db > $backupdir/${db}.sql\""
fi
debug "$execstr"
if [ ! $test ]; then
-   output=`$execstr 2>&1`
+   output=`eval $execstr 2>&1`
code=$?
if [ "$code" == "0" ]; then
debug $output







-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]