Bug#849884: qemu-kvm: USB host device pass through causes instant VM poweroff

2017-01-03 Thread Kyle Gordon
Hi again!

Managed to get 2.8 installed, and all the dependencies. I also grabbed the
2.8 version of everything else qemu* related 'just in case'

Unfortunately...

qemu-system-x86_64: /build/qemu-2.8/qemu-2.8+dfsg/hw/usb/core.c:584:
usb_packet_copy: Assertion `p->actual_length + bytes <= iov->size' failed.

I did try 2.7 with another USB device, this time just a '1a86:7523
QinHeng Electronics HL-340 USB-Serial adapter' on an ESP8266, and it worked
just fine.

I'm also wondering if it's hardware related, and will be swapping cables,
etc over the coming days. However, an unreliable USB deivce shouldn't kill
a VM, so maybe some protection is still required in the USB redirection
handling code?

Cheers

Kyle

On Tue, Jan 3, 2017 at 12:55 AM Kyle Gordon <k...@lodge.glasgownet.com>
wrote:

Hey,

I've managed to reproduce it on 2.7 from jessie-backports again, and the
assert is...

qemu-system-x86_64: /build/qemu-1VqMQS/qemu-2.7+dfsg/hw/usb/core.c:584:
usb_packet_copy: Assertion `p->actual_length + bytes <= iov->size' failed.

Also, this has been known to happen when adding the USB device, leaving the
VM in a 'Shutoff (Crashed)' state. I'm not sure if it's related.

*** Error in `qemu-system-x86_64': double free or corruption (!prev):
0x7f45d2b3a200 ***

and ...

*** Error in `qemu-system-x86_64': double free or corruption (!prev):
0x7fa2cd10b560 ***

I'll try the 2.8 version shortly!

Cheers

Kyle

On Mon, Jan 2, 2017 at 11:06 AM Michael Tokarev <m...@tls.msk.ru> wrote:

02.01.2017 13:57, Kyle Gordon wrote:
> Hi Michael,
>
> Thanks for the response. I have tried upgrading qemu* to
> 2.7+dfsg-3~bpo8+2 from jessie-backports, and the behaviour is
> unfortunately the same. I haven't tried upgrading the system to Stretch
> yet, as that might be a bit of a one way road!

Hmm... I see.

I re-read you first message, and it turns out I missed the info
about the bpo version. Please excuse me for that, that's ENOCOFFEE :)

This smells like something specific to this usb device. Did you
try other devices? The thing is that usb passthrough generally
works.

Can you also please show where it asserts out in case of 2.7 version
from bpo?

Also there's 2.8 version built for bpo (but not uploaded yet, since
2.8 hasn't been entered -testing), available at
http://www.corpit.ru/debian/tls/qemu/qemu-system-x86_2.8+dfsg-1~bpo8+1_amd64.deb
which can be of interest in this context too, but this might be
too much for you to try (this version is built with gtk and
virgl support, so there will be other deps).

Thanks,

/mjt


Bug#849884: qemu-kvm: USB host device pass through causes instant VM poweroff

2017-01-02 Thread Kyle Gordon
Hey,

I've managed to reproduce it on 2.7 from jessie-backports again, and the
assert is...

qemu-system-x86_64: /build/qemu-1VqMQS/qemu-2.7+dfsg/hw/usb/core.c:584:
usb_packet_copy: Assertion `p->actual_length + bytes <= iov->size' failed.

Also, this has been known to happen when adding the USB device, leaving the
VM in a 'Shutoff (Crashed)' state. I'm not sure if it's related.

*** Error in `qemu-system-x86_64': double free or corruption (!prev):
0x7f45d2b3a200 ***

and ...

*** Error in `qemu-system-x86_64': double free or corruption (!prev):
0x7fa2cd10b560 ***

I'll try the 2.8 version shortly!

Cheers

Kyle

On Mon, Jan 2, 2017 at 11:06 AM Michael Tokarev <m...@tls.msk.ru> wrote:

02.01.2017 13:57, Kyle Gordon wrote:
> Hi Michael,
>
> Thanks for the response. I have tried upgrading qemu* to
> 2.7+dfsg-3~bpo8+2 from jessie-backports, and the behaviour is
> unfortunately the same. I haven't tried upgrading the system to Stretch
> yet, as that might be a bit of a one way road!

Hmm... I see.

I re-read you first message, and it turns out I missed the info
about the bpo version. Please excuse me for that, that's ENOCOFFEE :)

This smells like something specific to this usb device. Did you
try other devices? The thing is that usb passthrough generally
works.

Can you also please show where it asserts out in case of 2.7 version
from bpo?

Also there's 2.8 version built for bpo (but not uploaded yet, since
2.8 hasn't been entered -testing), available at
http://www.corpit.ru/debian/tls/qemu/qemu-system-x86_2.8+dfsg-1~bpo8+1_amd64.deb
which can be of interest in this context too, but this might be
too much for you to try (this version is built with gtk and
virgl support, so there will be other deps).

Thanks,

/mjt


Bug#849884: qemu-kvm: USB host device pass through causes instant VM poweroff

2017-01-02 Thread Kyle Gordon
Hi Michael,

Thanks for the response. I have tried upgrading qemu* to 2.7+dfsg-3~bpo8+2
from jessie-backports, and the behaviour is unfortunately the same. I
haven't tried upgrading the system to Stretch yet, as that might be a bit
of a one way road!

Regards

Kyle

On Mon, Jan 2, 2017 at 7:57 AM Michael Tokarev <m...@tls.msk.ru> wrote:

> Control: severity -1 normal
> Control: reassign -1 qemu-system-x86
>
> 02.01.2017 02:54, Kyle Gordon wrote:
> > Package: qemu-kvm
> > Version: 1:2.1+dfsg-12+deb8u6
> > Severity: critical
> > Justification: breaks the whole system
> >
> > Dear Maintainer,
> >
> > Over the course of the past few weeks, a guest KVM instance that relies
> on USB pass through has been found in the powered off state. Restarting it
> shows that it has been hard powered off.
>
> Please verify whenever the same issue exists with a more recent
> qemu version, for example the one which is available in
> jessie-backports.
>
> Qemu is a fast-moving target, and in particular, usb passthrough
> has been revisited 2 times since 2.1 version.
>
> Lowering the severity to normal, since this problem does not
> _break_ anything per se, especially it does not break host
> system, it merely cases guest system to be turned off after
> a well-defined sequence of events which, as a work-around,
> can be avoided.
>
> Thanks,
>
> /mjt
>
> --
> To unsubscribe, send mail to 849884-unsubscr...@bugs.debian.org.
>


Bug#849884: Additional testing

2017-01-01 Thread Kyle Gordon
Hi,

This also causes guest Debian Stretch machines to terminate unexpectedly,
and can also be triggered by an alternative home automation package called
home-assistant.

I think this is certainly pointing at the KVM/QEMU host being faulty in
some way.

Kyle


Bug#849884: qemu-kvm: USB host device pass through causes instant VM poweroff

2017-01-01 Thread Kyle Gordon
Package: qemu-kvm
Version: 1:2.1+dfsg-12+deb8u6
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

Over the course of the past few weeks, a guest KVM instance that relies on USB 
pass through has been found in the powered off state. Restarting it shows that 
it has been hard powered off.

This is now reproducible with the connected RFXCom hardware. 

Guest OS = Debian Jessie
Host OS = Debian Jessie

Start guest machine, and configure USB pass through. In this case, it's for an 
RFXCom USB radio transceiver. Device is correctly detected in the guest, and 
shows up as expected in lsusb.
Start software that accesses the device. In this case, Domoticz home automation 
software.
Within a few minutes, the machine will be hard powered off. The following logs 
are present on the host.

2017-01-01 23:40:27.179+: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
QEMU_AUDIO_DRV=spice /usr/bin/kvm -name homeauto -S -machine 
pc-i440fx-2.1,accel=kvm,usb=off -m 6144 -realtime mlock=off -smp 
2,sockets=2,cores=1,threads=1 -uuid a79858f4-274e-425f-aece-98c14dc8fbc6 
-no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/homeauto.monitor,server,nowait 
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew 
-global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global 
PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device 
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive 
file=/media/store/KVM_VMs/homeauto-new.qcow2,if=none,id=drive-virtio-disk0,format=qcow2
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -drive file=/media/store/KVM_VMs/homeauto-new-1.qcow2,if=none,id=drive-virti
 o-disk1,format=qcow2 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x9,drive=drive-virtio-disk1,id=virtio-disk1
 -drive 
file=/media/store/KVM_VMs/homeauto-new-3.qcow2,if=none,id=drive-virtio-disk2,format=qcow2
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0xa,drive=drive-virtio-disk2,id=virtio-disk2
 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:38:01:2d,bus=pci.0,addr=0x3 
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-chardev spicevmc,id=charchannel0,name=vdagent -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
 -device usb-tablet,id=input0 -spice 
port=5904,addr=127.0.0.1,disable-ticketing,seamless-migration=on -device 
qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,bus=pci.0,addr=0x2 
-device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device 
hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev 
spicevmc,id=charredir0,name=usbr
 edir -device usb-redir,chardev=charredir0,id=redir0 -chardev 
spicevmc,id=charredir1,name=usbredir -device 
usb-redir,chardev=charredir1,id=redir1 -chardev 
spicevmc,id=charredir2,name=usbredir -device 
usb-redir,chardev=charredir2,id=redir2 -chardev 
spicevmc,id=charredir3,name=usbredir -device 
usb-redir,chardev=charredir3,id=redir3 -device 
usb-host,hostbus=6,hostaddr=4,id=hostdev0 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on
char device redirected to /dev/pts/1 (label charserial0)
main_channel_link: add main channel client
main_channel_handle_parsed: net test: latency 2.497000 ms, bitrate 41698055 bps 
(39.766364 Mbps)
red_dispatcher_set_cursor_peer: 
inputs_connect: inputs channel client create

=== Normal behaviour until Domoticz is started...  ===

qemu-system-x86_64: /build/qemu-XXUWBP/qemu-2.1+dfsg/hw/usb/core.c:600: 
usb_packet_copy: Assertion `p->actual_length + bytes <= iov->size' failed.
2017-01-01 23:42:30.995+: shutting down

I have tried 2.7+dfsg-3~bpo8+2 from jessie-backports, but the behaviour is the 
same.

Unsure where to try next. 

Regards

Kyle

-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qemu-kvm depends on:
ii  qemu-system-x86  1:2.1+dfsg-12+deb8u6

qemu-kvm recommends no packages.

qemu-kvm suggests no packages.

-- no debconf information



Bug#569289: Also affected...

2011-01-04 Thread Kyle Gordon

Hi,

I can confirm this bug is also present on Ubuntu 10.04 and has been 
reported here 
https://bugs.launchpad.net/ubuntu/+source/irda-utils/+bug/697265


Regards

Kyle

--
Kyle Gordon - 2M1DIQ
Web: http://lodge.glasgownet.com
Jabber/Email/SIP: k...@lodge.glasgownet.com




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



Bug#470706: Acknowledgement (xfsprogs: xfs_repair crashes during attempted repair)

2008-03-14 Thread Kyle Gordon
Hi folks,

In my continuing efforts to reclaim my storage, I finished downgrading to 
etch. This included downgrading libc6 and everything dependant on it to the 
versions provided in etch (lots of package=x.x.x.x statements)

Rerunning xfs_repair with the etch versions of linux-image and libc6 appears 
to allow it to complete successfully.

I guess the problem still stands with the testing version of libc6 / xfsprogs, 
but that's your call :-)

Regards

Kyle

On Thursday 13 March 2008 00:03, you wrote:
 Thank you for filing a new Bug report with Debian.

 This is an automatically generated reply to let you know your message
 has been received.

 Your message is being forwarded to the package maintainers and other
 interested parties for their attention; they will reply in due course.

 Your message has been sent to the package maintainer(s):
  Nathan Scott [EMAIL PROTECTED]

 If you wish to submit further information on this problem, please
 send it to [EMAIL PROTECTED], as before.

 Please do not send mail to [EMAIL PROTECTED] unless you wish
 to report a problem with the Bug-tracking system.



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



Bug#470706: xfsprogs: xfs_repair crashes during attempted repair

2008-03-12 Thread Kyle Gordon
Package: xfsprogs
Version: 2.8.11-1
Severity: normal

Hi,

Recently there was a very short power failure, which seems to have corrupted my 
XFS filesystem. xfs_check crashes in a manner similar to that described in 
#465733, but sadly xfs_repair fails completely.

This machine used to be running lenny, but in an attempt to resolve this issue, 
sources.list has been changed to etch and the kernel-image and xfsprogs 
packages have been downgraded to the versions supplied in etch.

After a while, xfs_repair /dev/md0 spits out the following...

Phase 5 - rebuild AG headers and trees...
*** glibc detected *** xfs_repair: munmap_chunk(): invalid pointer:
0xb092c008 ***
=== Backtrace: =
/lib/i686/cmov/libc.so.6(cfree+0x1bb)[0xb7de24ab]
xfs_repair[0x8061f2d]
xfs_repair[0x806b311]
xfs_repair[0x807cb28]
/lib/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7d89450]
xfs_repair[0x8049541]
=== Memory map: 
08048000-080ce000 r-xp  03:01 195863 /sbin/xfs_repair
080ce000-080cf000 rw-p 00085000 03:01 195863 /sbin/xfs_repair
080cf000-0aadc000 rw-p 080cf000 00:00 0  [heap]
aeba9000-aebaa000 ---p aeba9000 00:00 0
aebaa000-b0c73000 rw-p aebaa000 00:00 0
b7884000-b789 r-xp  03:01 97922  /lib/libgcc_s.so.1
b789-b7891000 rw-p b000 03:01 97922  /lib/libgcc_s.so.1
b789a000-b7d1c000 rw-p b789a000 00:00 0
b7d1c000-b7d71000 r--p  03:01 440947
/usr/lib/locale/locale-archive
b7d71000-b7d73000 rw-p b7d71000 00:00 0
b7d73000-b7eba000 r-xp  03:01 98168
/lib/i686/cmov/libc-2.7.so
b7eba000-b7ebb000 r--p 00147000 03:01 98168
/lib/i686/cmov/libc-2.7.so
b7ebb000-b7ebd000 rw-p 00148000 03:01 98168
/lib/i686/cmov/libc-2.7.so
b7ebd000-b7ec rw-p b7ebd000 00:00 0
b7ec-b7ec7000 r-xp  03:01 98239
/lib/i686/cmov/librt-2.7.so
b7ec7000-b7ec9000 rw-p 6000 03:01 98239
/lib/i686/cmov/librt-2.7.so
b7ec9000-b7edd000 r-xp  03:01 98237
/lib/i686/cmov/libpthread-2.7.so
b7edd000-b7edf000 rw-p 00013000 03:01 98237
/lib/i686/cmov/libpthread-2.7.so
b7edf000-b7ee1000 rw-p b7edf000 00:00 0
b7ee1000-b7ee4000 r-xp  03:01 98031  /lib/libuuid.so.1.2
b7ee4000-b7ee5000 rw-p 2000 03:01 98031  /lib/libuuid.so.1.2
b7ee5000-b7ee6000 rw-p b7ee5000 00:00 0
b7eef000-b7ef rw-p b7eef000 00:00 0
b7ef-b7ef1000 r-xp b7ef 00:00 0  [vdso]
b7ef1000-b7f0d000 r-xp  03:01 97947  /lib/ld-2.7.so
b7f0d000-b7f0f000 rw-p 0001b000 03:01 97947  /lib/ld-2.7.so
bf8cf000-bf8e5000 rw-p bf8cf000 00:00 0  [stack]
Aborted
senior:~#

Any help would be appreciated

Regards

Kyle

-- System Information:
Debian Release: lenny/sid
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-6-k7 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages xfsprogs depends on:
ii  libc6 2.7-6  GNU C Library: Shared libraries
ii  libreadline5  5.2-3  GNU readline and history libraries
ii  libuuid1  1.40.6-1   universally unique id library

xfsprogs recommends no packages.

-- no debconf information



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



Bug#403863: initscripts: Stray file /lib/init/rw/.ramfs not in package list

2008-03-03 Thread Kyle Gordon
Is this bug going to be worked? Either by initscripts or chrootkit? Does it go 
down as a DebianWontfixDueToInternalBickering and leave the user to hack 
together a workaround?

If it's the latter, then 
http://stereo.lu/chkrootkit-finds-libinitrwramfs-on-debian-etch has some 
information that will be useful.

Regards

Kyle



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



Bug#452984: drupal5: Drupal defaults to aliasing for all virtualhosts

2007-12-02 Thread Kyle Gordon
Hi Luigi,

You've convinced me when you say it like that :-)

Let's close this bug and have a good weekend.

Kyle :-)

On Wednesday 28 November 2007 00:39:11 Luigi Gangitano wrote:
 Hi Kyle,
 let's make some analysis and maybe we'll agree on agreeing. :-)

 - Drupal has it's own view of virtual hosting (sites). Each site has
 to be configured with files in different directives. If no site is
 configured the default configuration applies to all sites. So you
 don't really have all sites vulnerable with the default debian
 install. You just have one site that is available on different virtual
 hosts (www.foo.com/drupal5 is just the same as www.bar.com/drupal5).
 There is no vulnerability multiplication.

 - Virtual hosting itself is not a secure way to separate 'data
 domains'. Since all virtual hosts run in the same webserver process
 with the same rights, exploiting an hole in one virtual hosts usually
 leads to access all other virtual hosts. Obviously this is true only
 for serious holes. Trivial holes like SQL injection only apply to the
 single webapp database. See previous point for this: if drupal5 is
 vulnerable to SQL injection the default debian install will only make
 the single site vulnerable. On the other hand, if the vulnerability
 leads to file system access or, worse, to arbitrary code execution
 other virtual hosts will not be protected any way.

 So again this is, as usual, a compromise between security and ease-of-
 use. I choose not to provide any third-party module for drupal in
 debian package, avoiding security issues in those modules. At the same
 time I choose to make it easy for unexperienced people to set up a
 drupal site as experienced admins would always know how to trim access
 down to their own needs. The same choice applies to many other
 packages in debian (think phpmyadmin, phppgadmin, acidbase and any
 package using wwwconfig-common).

 Hope I could make ti more clear to you. :-)

 Regards,

 L

 --
 Luigi Gangitano -- [EMAIL PROTECTED] -- [EMAIL PROTECTED]
 GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972  C24A F19B A618 924C 0C26





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



Bug#452984: drupal5: Drupal defaults to aliasing for all virtualhosts

2007-11-27 Thread Kyle Gordon
Hi Luigi,

Surely it is safest for all if an item of installed software is disabled on 
all fronts unless specifically enabled for a particular site? It's all about 
reducing the 'surface area' of servers these day's isn't it? :-) If Drupal 
has a security issue, I'd rather have one vulnerable website instead of 
having all sites on a server vulnerable.

I am aware of how to disable it globally and enable for individual sites, 
which is what has been done on my server. We shall have to agree on 
disagreeing in this case.

Regards

Kyle

On Tuesday 27 November 2007 09:21:22 Luigi Gangitano wrote:
 Hi Kyle,
 I'm sure you noticed that /etc/apache2/conf.d/drupal.conf is a
 configuration file that can be easily modified or deleted and drupal
 will keep your version between upgrades. It is provided as an easy way
 to set up drupal on a single host with no virtual hosting and any
 administrator with little experience in Apache configuration can disable
 it an configure host-specific directives.


 So I don't consider this a bug, as I don't consider a bug choises I do
 in default squid configuration. You can always change them in your
 configuration file if you wish.

 Regards,

 L





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



Bug#452984: drupal5: Drupal defaults to aliasing for all virtualhosts

2007-11-26 Thread Kyle Gordon
Package: drupal5
Version: 5.3-1
Severity: important

When drupal5 is installed, it installs /etc/apache2/conf.d/drupal.conf.
This makes the /drupal5/ url become present on all virtualhosts,
including ones that are already using /drupal5/ for a custom install.
This is a major impact on functionality, and a highly undesirable on
virtual sites that neither want drupal, nor need it.

Regards

Kyle

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-k7 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages drupal5 depends on:
ii  apache2   2.2.4-3Next generation, scalable, extenda
ii  apache2-mpm-prefork [httpd]   2.2.4-3Traditional model for Apache HTTPD
ii  curl  7.17.1-1   Get a file from an HTTP, HTTPS or 
ii  dbconfig-common   1.8.36 common framework for packaging dat
ii  debconf   1.5.17 Debian configuration management sy
ii  exim4 4.63-17metapackage to ease exim MTA (v4) 
ii  exim4-daemon-heavy [mail-tran 4.63-17exim MTA (v4) daemon with extended
ii  mysql-client-4.1 [virtual-mys 4.1.15-1   mysql database client binaries
ii  php5  5.2.3-1server-side, HTML-embedded scripti
ii  php5-gd   5.2.3-1+b1 GD module for php5
ii  php5-mysql5.2.3-1+b1 MySQL module for php5
ii  wwwconfig-common  0.0.48 Debian web auto configuration

Versions of packages drupal5 recommends:
ii  mysql-server-4.1 [mysql-serve 4.1.15-1   mysql database server binaries

-- debconf information:
  drupal5/mysql/admin-user: root
* drupal5/webserver: apache2
  drupal5/mysql/method: unix socket
  drupal5/install-error: abort
  drupal5/passwords-do-not-match:
  drupal5/pgsql/method: unix socket
  drupal5/dbconfig-remove:
  drupal5/internal/skip-preseed: false
  drupal5/pgsql/authmethod-user:
  drupal5/remote/newhost:
  drupal5/dbconfig-upgrade: true
  drupal5/remote/port:
  drupal5/pgsql/changeconf: false
  drupal5/db/app-user: drupal5
  drupal5/pgsql/authmethod-admin: ident
* drupal5/database-type: mysql
  drupal5/upgrade-backup: true
  drupal5/dbconfig-reinstall: false
  drupal5/pgsql/admin-user: postgres
  drupal5/internal/reconfiguring: false
  drupal5/remote/host:
  drupal5/db/basepath:
* drupal5/dbconfig-install: true
  drupal5/pgsql/manualconf:
  drupal5/pgsql/no-empty-passwords:
  drupal5/remove-error: abort
  drupal5/purge: false
  drupal5/db/dbname: drupal5
  drupal5/missing-db-package-error: abort
  drupal5/upgrade-error: abort



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



Bug#425312: nagios-plugins-basic: ssh_disk config fails to be interpreted properly

2007-05-20 Thread Kyle Gordon
Package: nagios-plugins-basic
Version: 1.4.5-2.1
Severity: important

By default, the ssh_disk configuration has the following command line...

/usr/lib/nagios/plugins/check_by_ssh -H $HOSTADDRESS$ -C
'/usr/lib/nagios/plugins/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$'

This creates the following error when trying to check a remote system...

[1179694002] SERVICE ALERT: tagboard;/dev/hda1 Free
Space;UNKNOWN;SOFT;1;Could not open pipe: /usr/bin/ssh 172.24.32.1
'/usr/lib/nagios/plugins/check_disk -w 5% -c 3% -p /dev/hda1'

Changing the single quotes to be double quotes in the config resolves
this problem.

Regards

Kyle

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages nagios-plugins-basic depends on:
ii  iputils-ping3:20020927-6 Tools to test the reachability of 
ii  libc6   2.5-7GNU C Library: Shared libraries
ii  libssl0.9.8 0.9.8e-4 SSL shared libraries
ii  procps  1:3.2.7-3/proc file system utilities
ii  ucf 3.001Update Configuration File: preserv

nagios-plugins-basic recommends no packages.

-- no debconf information


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



Bug#399832: Bug is still present

2007-03-19 Thread Kyle Gordon

Peter Eisentraut wrote:

Am Dienstag, 13. März 2007 23:30 schrieb Kyle Gordon:
  

Then why doesn't the package conflict with it then? This is poor package
management if the user is left to battle through bugs. Egroupware should
not be allowed to depend on this version of php5 if it causes issues. If
php5.2 _has_ to be installed as part of Debian, then Egroupware should be
modified to use the patches that were made available *4 months ago!*



Which version of egroupware are you using and what is your specific problem?
  

Hi Peter,

Sorry for the delay.

We're running egroupware 1.2-105.dfsg-4 on Debian testing here. It's 
accompanied by php5 5.2.0-8+etch1 and php4 4.4.4-8+etch1 (although only 
php5 is enabled against Apache)


The errors can be seen at 
http://lovelace.midden.org.uk/egroupware/login.php, it's basically the 
same as the previous posters. Empty haystack, cannot redeclare class 
datetime, etc


Many thanks,

Kyle


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



Bug#399832: Bug is still present

2007-03-19 Thread Kyle Gordon

Peter Eisentraut wrote:

Am Montag, 19. März 2007 17:12 schrieb Kyle Gordon:
  

We're running egroupware 1.2-105.dfsg-4



That version doesn't exist in Debian anymore, so I can't support that.  If you 
want to discuss a bug, please use a version currently in the archive.
  

Hi Peter,

My mistake, apologies for the hassle and confusion. I thought it was 
still in testing, but it appears to be only in stable and unstable now.


I guess this bug can be closed after all :-)

Regards

Kyle




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



Bug#399832: Bug is still present

2007-03-13 Thread Kyle Gordon
Am Dienstag, 6. Februar 2007 20:11 schrieb Anja Slowinski:
 egroupware does not work with php5.2

 Then you are not using the right package version.

Then why doesn't the package conflict with it then? This is poor package 
management if the user is left to battle through bugs. Egroupware should not 
be allowed to depend on this version of php5 if it causes issues. If php5.2 
_has_ to be installed as part of Debian, then Egroupware should be modified 
to use the patches that were made available *4 months ago!*

This bug should not be closed.

Regards

Kyle
-- 
Kyle Gordon
[EMAIL PROTECTED]
http://lodge.glasgownet.com


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



Bug#344220: gallery2: Gallery2 installs to all VirtualHosts

2005-12-20 Thread Kyle Gordon
Package: gallery2
Version: 2.0.2-1
Severity: important


Hi,

When Gallery2 installs, it symlinks /etc/apache2/conf.d/gallery to
/etc/gallery/apache.conf.

This, whilst having the nice effect of making things 'just work' for 
single hosts also means that the /gallery2/ alias gets presented for 
all vhosts on the system. This breaks for anyone that already has a 
custom installation of Gallery2 in their website. The default action 
for webapps should bedisabled, not enabled. If you use the multisite 
option that is provided with gallery2, you need to remove this systemwide 
alias before you can get your own multisite installs to work on each vhost.

If anything, would it not be better for the install script to parse
sites in /etc/apache2/sites-available/, and ask which one the users
wants the alias set up for?

Regards

Kyle

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-2-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages gallery2 depends on:
ii  apache22.0.55-3  next generation, scalable, extenda
ii  apache2-mpm-prefork [apach 2.0.55-3  traditional model for Apache2
ii  debconf [debconf-2.0]  1.4.62Debian configuration management sy
ii  imagemagick6:6.2.4.5-0.2 Image manipulation programs
ii  libapache-mod-php4 4:4.4.0-4 server-side, HTML-embedded scripti
ii  libapache2-mod-php44:4.4.0-4 server-side, HTML-embedded scripti
ii  mysql-client-4.1 [mysql-cl 4.1.14-6  mysql database client binaries
ii  netpbm 2:10.0-9  Graphics conversion tools
ii  php4   4:4.4.0-4 server-side, HTML-embedded scripti
ii  php4-mysql 4:4.4.0-4 MySQL module for php4
ii  wwwconfig-common   0.0.44Debian web auto configuration

Versions of packages gallery2 recommends:
pn  dcraw none (no description available)
pn  ffmpegnone (no description available)
ii  jhead 2.44-1 manipulate the non-image part of E
ii  libjpeg-progs 6b-10  Programs for manipulating JPEG fil
ii  mysql-server-4.1 [mysql-serve 4.1.14-6   mysql database server binaries
ii  php4-gd   4:4.4.0-4  GD module for php4
pn  postgresql-7.4 | postgresql-8 none (no description available)
ii  unzip 5.52-5 De-archiver for .zip files

-- debconf information:
* gallery2/webserver_type: apache2
* gallery2/mysql/dbname: gallery2
* gallery2/mysql/dbserver: localhost
* gallery2/mysql/configure: true
* gallery2/restart-webserver: true
* gallery2/purge: true
* gallery2/mysql/dbadmin: root


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



Bug#343110: Wordpress installs but has nothing usable in /etc/wordpress/

2005-12-13 Thread Kyle Gordon
On Tuesday 13 December 2005 00:32, Kai Hendry wrote:
 On 2005-12-12T20:50+ Kyle Gordon wrote:
  After visiting /blog/ on the website, I get repeated 404 errors for

 This is where you probably went wrong. The current system only takes
 HTTP_HOST into account.

 So yourdomain.com would work (with the multiple blog setup).

 Though, yourdomain.com/blog wouldn't.

 You could make /blog work with a symlink, though the default
 wp-config.php would have to be replaced. And a multiple blog setup would
 become very difficult.

 Consider a subdomain on your domain? blog.yourdomain.com. That would
 work.

 I don't consider this a bug, so I'll be closing it shortly.

Hi Kai,

Thanks for the info, and I've now set it up with  
VirtualDocumentRoot /usr/share/wordpress/. It's a brand new domain, so I can 
break it as much as I like just now :-)

However, it is still failing when looking for /etc/wordpress/wp-settings.php 
and /etc/wordpress/wp-includes/

The file /etc/wordpress/wp-config.php hunts for HTTP_HOST in /etc/wordpress/, 
which in turn gets config-www.sharebear.me.uk.php (for my setup anyway). This 
file, taken from /usr/share/wordpress/wp-config-sample.php, has the following 
code at the end

define('ABSPATH', dirname(__FILE__).'/');
require_once(ABSPATH.'wp-settings.php');

My PHP skills aren't the best, but it would appear that this 
searches /etc/wordpress/ for wp-settings.php, which it can't find. This could 
be due to ABSPATH being set to /etc/wordpress/ instead 
of /usr/share/wordpress/

So, I've edited config-www.sharebear.me.uk.php to define ABSPATH 
as /usr/share/wordpress/ instead of dirname(__FILE__).'/', and it all works 
perfectly!

I'd still consider this to be a bug, but it may come down to a setting I had 
wrong somewhere.

Many thanks,

Kyle
-- 
Kyle Gordon
[EMAIL PROTECTED]
http://lodge.glasgownet.com


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



Bug#343066: lvm2: LVM fails to work without running vgscan first

2005-12-12 Thread Kyle Gordon
Package: lvm2
Version: 2.01.04-5
Severity: normal

Hi folks,

After upgrading to 2.6.14-2-686-smp, I get errors when trying to start
my LVM2 array. It claims it is unable to find the UUID of two disks,
and pvdisplay shows the disks but without their UUID or device name.
After vgscan is run, pvdisplay shows the correct UUID and device
information
and the array can be loaded as normal. Examples are below.

Minor glitch aside, keep up the great work guys :-)

Regards

Kyle

flat:~# uname -a
Linux flat 2.6.14-2-686-smp #2 SMP Fri Dec 9 10:20:41 UTC 2005 i686 GNU/Linux
flat:~# uptime
 10:45:51 up 3 min,  1 user,  load average: 0.24, 0.15, 0.06
flat:~# /etc/init.d/lvm restart
Shutting down LVM Volume Groups...
  Couldn't find device with uuid 'vahqgP-c45r-QTDR-o522-FFrR-H7Xv-Sbs6n8'.
  Couldn't find all physical volumes for volume group vg_store1.
  Couldn't find device with uuid 'vahqgP-c45r-QTDR-o522-FFrR-H7Xv-Sbs6n8'.
  Couldn't find all physical volumes for volume group vg_store1.
  Unable to find volume group vg_store1
flat:~# vgdisplay
  Couldn't find device with uuid 'vahqgP-c45r-QTDR-o522-FFrR-H7Xv-Sbs6n8'.
  Couldn't find all physical volumes for volume group vg_store1.
  Couldn't find device with uuid 'vahqgP-c45r-QTDR-o522-FFrR-H7Xv-Sbs6n8'.
  Couldn't find all physical volumes for volume group vg_store1.
  Volume group vg_store1 doesn't exist
flat:~# pvdisplay
  Couldn't find device with uuid 'vahqgP-c45r-QTDR-o522-FFrR-H7Xv-Sbs6n8'.
  Couldn't find device with uuid 'vjl5Mq-21B6-gmg9-zXEP-c3uy-kFKv-U6l0zz'.
  Couldn't find device with uuid 'vahqgP-c45r-QTDR-o522-FFrR-H7Xv-Sbs6n8'.
  Couldn't find device with uuid 'vjl5Mq-21B6-gmg9-zXEP-c3uy-kFKv-U6l0zz'.
  --- Physical volume ---
  PV Name   /dev/hdb
  VG Name   vg_store1
  PV Size   57.23 GB / not usable 0
  Allocatable   yes (but full)
  PE Size (KByte)   4096
  Total PE  14651
  Free PE   0
  Allocated PE  14651
  PV UUID   7cryMN-plCs-YuF2-fpxn-BcIJ-OKpG-t3yRQf

  --- Physical volume ---
  PV Name   /dev/hda6
  VG Name   vg_store1
  PV Size   64.26 GB / not usable 0
  Allocatable   yes (but full)
  PE Size (KByte)   4096
  Total PE  16451
  Free PE   0
  Allocated PE  16451
  PV UUID   QYXz9O-6ySA-aTEM-Y6GY-GrHS-5q2C-NQoePQ

  --- Physical volume ---
  PV Name   unknown device
  VG Name   vg_store1
  PV Size   76.69 GB / not usable 0
  Allocatable   yes (but full)
  PE Size (KByte)   4096
  Total PE  19633
  Free PE   0
  Allocated PE  19633
  PV UUID   vahqgP-c45r-QTDR-o522-FFrR-H7Xv-Sbs6n8

  --- Physical volume ---
  PV Name   unknown device
  VG Name   vg_store1
  PV Size   279.48 GB / not usable 0
  Allocatable   yes
  PE Size (KByte)   4096
  Total PE  71547
  Free PE   4
  Allocated PE  71543
  PV UUID   vjl5Mq-21B6-gmg9-zXEP-c3uy-kFKv-U6l0zz

flat:~# vgscan
  Reading all physical volumes.  This may take a while...
  Found volume group vg_store1 using metadata type lvm2
flat:~# pvdisplay
  --- Physical volume ---
  PV Name   /dev/hdb
  VG Name   vg_store1
  PV Size   57.23 GB / not usable 0
  Allocatable   yes (but full)
  PE Size (KByte)   4096
  Total PE  14651
  Free PE   0
  Allocated PE  14651
  PV UUID   7cryMN-plCs-YuF2-fpxn-BcIJ-OKpG-t3yRQf

  --- Physical volume ---
  PV Name   /dev/hda6
  VG Name   vg_store1
  PV Size   64.26 GB / not usable 0
  Allocatable   yes (but full)
  PE Size (KByte)   4096
  Total PE  16451
  Free PE   0
  Allocated PE  16451
  PV UUID   QYXz9O-6ySA-aTEM-Y6GY-GrHS-5q2C-NQoePQ

  --- Physical volume ---
  PV Name   /dev/hdg
  VG Name   vg_store1
  PV Size   76.69 GB / not usable 0
  Allocatable   yes (but full)
  PE Size (KByte)   4096
  Total PE  19633
  Free PE   0
  Allocated PE  19633
  PV UUID   vahqgP-c45r-QTDR-o522-FFrR-H7Xv-Sbs6n8

  --- Physical volume ---
  PV Name   /dev/hdh
  VG Name   vg_store1
  PV Size   279.48 GB / not usable 0
  Allocatable   yes
  PE Size (KByte)   4096
  Total PE  71547
  Free PE   4
  Allocated PE  71543
  PV UUID   vjl5Mq-21B6-gmg9-zXEP-c3uy-kFKv-U6l0zz

flat:~# /etc/init.d/lvm restart
Shutting down LVM Volume Groups...
  0 logical volume(s) in volume group vg_store1 now active
Setting up LVM Volume Groups...
  Reading all physical volumes.  This may take a while...
  Found volume group vg_store1 using metadata type lvm2
  /dev/vg_store1: 

Bug#343110: Wordpress installs but has nothing usable in /etc/wordpress/

2005-12-12 Thread Kyle Gordon
Package: wordpress
Version: 1.5.2-2
Severity: grave
Justification: renders package unusable


Hi folks,

I've just installed wordpress on Etch, and have been left with a system
with only wp-config.php and htaccess in /etc/wordpress/.

Following the instructions, I created 
/etc/wordpress/config-www.sharebear.me.uk.php and
put in the relevant database info. This was based on the sample config
file at /usr/share/wordpress/wp-config-sample.php.

After visiting /blog/ on the website, I get repeated 404 errors for
various files that it is trying to load from /etc/wordpress/ - all
listed below. I symlinked them in, in an effort to make it work, and I
was met with a reasonable degree of success.

wp-admin - /usr/share/wordpress/wp-admin/
wp-includes - /usr/share/wordpress/wp-includes/
wp-settings.php - /usr/share/wordpress/wp-settings.php

After this munging, I went to the admin interface and was able to
succesfully log in and edit posts. However, upon trying to view the
blog, I am met with a blank page. 

I have read the 5 relevant lines in /usr/share/doc/wordpress/README.Debian, 
and followed them religiously. It is a multiple blog site, but the
configuration doesn't really seem to allow for a single blog
installation anyway. Have I missed a really crucial step, or is there
something rather wrong with the initial install configuration?

Many thanks,

Kyle

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-2-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages wordpress depends on:
ii  apache2-mpm-prefork [httpd]  2.0.54-5traditional model for Apache2
ii  libapache2-mod-php4  4:4.3.10-16 server-side, HTML-embedded scripti
ii  mysql-client-4.1 [virtual-my 4.1.14-6mysql database client binaries
ii  php4 4:4.3.10-16 server-side, HTML-embedded scripti
ii  php4-mysql   4:4.3.10-16 MySQL module for php4

wordpress recommends no packages.

-- no debconf information


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



Bug#310310: gallery: Gallery installs to all VirtualHosts

2005-05-22 Thread Kyle Gordon
Package: gallery
Severity: normal


Hey,

When Gallery installs itself, it symlinks /etc/apache2/conf.d/gallery to
/etc/gallery/apache.conf.

This, whilst having the nice effect of making things 'just work' also
means that the /gallery alias gets presented for all vhosts on the
system. This breaks for anyone that already has a custom installation 
of Gallery in their website. The default action for webapps should be
disabled, not enabled. 

If anything, would it not be better for the install script to parse
sites in /etc/apache2/sites-available/, and ask which one the users
wants the alias set up for?

Regards

Kyle

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


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



Bug#309988: Proposed solution doesn't work

2005-05-22 Thread Kyle Gordon
Hi,

Sorry, but my proposed solution is actually completely wrong. My fault.

Unfortunately the problem still stands though. Not sure what can be done about 
it, there doesn't seem to be an option anywhere to skip that prompt.

Regards

Kyle
-- 
Kyle Gordon
http://lodge.glasgownet.com
[EMAIL PROTECTED]


pgpk68RlaPCLU.pgp
Description: PGP signature


Bug#309988: sourcerer-kernel-builder: Automated build fails when initrd selected

2005-05-20 Thread Kyle Gordon
Package: sourcerer-kernel-builder
Version: 0.4
Severity: normal

Hi,

When set up with default options, and building an initrd enabled kernel,
the automated build fails every hour as make-kpkg is prompting the user
with the following text...

Warning: You are using the initrd option, that may not
work, depending on your kernel version and architecture,
unless you have applied the initrd cramfs patch to
the kernel, or modified mkinitrd not to use cramfs by
default. The  cramfs initrd patch, is included in the
Debian supplied kernel sources. New kernels on most
architectures do work fine.
By default, I assume you know what you are doing, and I
apologize for being so annoying. Should I abort[Ny]?

This can be avoided by adding warn_initrd = No to /etc/kernel-img.conf

Regards

Kyle

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages sourcerer-kernel-builder depends on:
ii  kernel-package  8.135A utility for building Linux kerne
ii  libc6-dev [libc-dev]2.3.2.ds1-22 GNU C Library: Development Librari
ii  libncurses5-dev [libncurses 5.4-4Developer's libraries and docs for
ii  module-init-tools   3.2-pre1-2   tools for managing Linux kernel mo
ii  whiptail0.51.6-23Displays user-friendly dialog boxe

-- no debconf information


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



Bug#299914: irm: New upstream package

2005-03-17 Thread Kyle Gordon
Package: irm
Version: 1.5.1.1-2
Severity: normal


Hi,

There appears to be a new upstream source package for version 1.5.3,
compared to the 1.5.1.1-2 version in unstable. 

Regards

Kyle

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages irm depends on:
ii  apache [httpd]1.3.33-4   versatile, high-performance HTTP s
ii  debconf   1.4.30.11  Debian configuration management sy
ii  mysql-client  4.0.23-7   mysql database client binaries
ii  php4  4:4.3.10-8 server-side, HTML-embedded scripti
ii  php4-cli  4:4.3.10-8 command-line interpreter for the p
ii  php4-mysql4:4.3.10-8 MySQL module for php4
ii  wwwconfig-common  0.0.42 Debian web auto configuration

-- debconf information:
* irm/webserver: apache
  irm/web_prefix: /irm
* irm/dbserver: aurora
* irm/purge_db: false
  irm/webservers: apache
* irm/url: http://support.absolutestudios.co.uk/irm
* irm/dbadmin: root
* irm/dbuser: irm


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