Bug#438542: add'l info

2008-02-08 Thread Dykema, Erik
Hi-
 Not sure if this was already known or not, but I have started using / 
trying to use the open-iscsi packages on Lenny, and in addition to the lack of 
boot scripts, the machine hangs when you try to reboot.
 My configuration:

XFS filesystem, on
LVM2 logical volume, with 1 PV which is a device via
open-iscsi on Lenny, which is a client of a physical
ACC Jetstor iSCSI RAID.

 The problem seems to be that the init script stops open-iscsi, THEN is 
stops lvm.  When it tries to stop LVM, the physical device is already gone, and 
it prints this message to the console

Shutting down LVM volume groupsiscsi: cannot broadcast skb(-3)

 At this point, it's necessary to physically power off / on the machine.

Erik




Bug#395408: perdition configs..

2006-10-30 Thread Dykema, Erik

Here are my configs for perdition, which cause the error to occur:

/etc/default/perdition

RUN_PERDITION=yes
POP3=no
POP3S=no
IMAP4=yes
IMAP4_FLAGS=-s 10.2.2.2 --ssl_mode tls_listen,tls_listen_force
IMAP4S=no

Where 10.2.2.2 is the address of the server I'm attempting to proxy  
for.  I attemped to do the same thing with /etc/perdition/ 
perdition.conf:

# perdition.conf
ssl_mode tls_listen,tls_listen_force

But it also causes perdition to fail.

Erik


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



Bug#395408: perdition won't accept: ssl_mode tls_listen,tls_listen_force

2006-10-29 Thread Dykema, Erik

Package: perdition
Version: 1.17-7

Perdition won't accept both ssl_mode flags tls_listen and  
tls_listen_force .  It will accept:

ssl_mode tls_listen
OR
ssl_mode tls_listen_force
or:
ssl_mode tls_listen,garbage
but not:
ssl_mode tls_listen,tls_listen_force

The program starts but hangs, it does not accept connections or  
advertise it's startup options in the logs.


thanks,
Erik


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



Bug#395408: perdition won't accept: ssl_mode tls_listen,tls_listen_force

2006-10-26 Thread Dykema, Erik

Package: perdition
Version: 1.17-7

Perdition won't accept both ssl_mode flags tls_listen and  
tls_listen_force .  It will accept:

ssl_mode tls_listen
OR
ssl_mode tls_listen_force
or:
ssl_mode tls_listen,garbage
but not:
ssl_mode tls_listen,tls_listen_force

The program starts but hangs, it does not accept connections or  
advertise it's startup options in the logs.


thanks,
Erik


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



Bug#384202: please test with recent nightly

2006-08-23 Thread Dykema, Erik

Dann-
	Thanks for the suggestion, am downloading the ISO's as we speak and  
will give it a shot immediately.


regards,
Erik


On Aug 22, 2006, at 7:41 PM, dann frazier wrote:


hey Erik,
  Since beta3 d-i has moved to using a 2.6.17 kernel, can you give one
of the daily snapshots a test to see if this problem goes away?

http://www.debian.org/devel/debian-installer/

--
dann frazier






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



Bug#384202: Installer works with daily build, post installation kernel does not

2006-08-23 Thread Dykema, Erik

Hi-
	Dann's suggestion to install with the daily build worked, excepting  
two issues:


1) The AMD64 arch (which would be preferrable in this case as the  
processor is emt64 capable) is not built using the 2.6.17 kernel, so  
I had to use the i386 arch.


2) Even though the installer runs the .17 kernel, it still installs  
the .16 kernel.


	Using the build for i386, I was able to install very cleanly, and  
reboot, at which point the USB messages started spewing again.  By  
hitting ctrl-c a few times, I was able to get to a login prompt, and  
can access the machine, although I am typing blind.  Now I am  
downloading and compiling a new kernel, which should work.
	So, at this point, I would say that the i386 arch installer daily- 
build is working great, but the kernel needs that patch from .17 to  
fix the HP problem.  This will affect many present, and all future,  
models of HP servers; any which use the iLO 2 chip: including all of  
their new Blade servers.


Erik


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