On Wed, 2021-08-18 at 21:58 +0100, Jose M Calhariz wrote: > Giving that I have seen this bug before with my machines, it is only > the first time I am reporting and being the first reporter so I am > with you, this is some setting in my site or my machine. > > With more reasearch with help from the local specialist I found a > an extra iSCSI setup to a local appliance that I not longer need. So > I remove it from /etc/iscsi. Doing again a: > > dpkg --configure -a > > Setting up open-iscsi (2.1.3-5) ... > open-iscsi postinst: since the check in preinst some iSCSI sessions > have > failed. -> will wait 30s for automatic recovery > Processing triggers for initramfs-tools (0.140) ... > update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64 > > > This time it succeeds. So this probably is a problem on my machine. > May I suggest for you to increase the timeout from 30s to 60 or 120s? >
Great. Thanks for the testing on another setup. The thing about timeouts is that there's no sweet spot. 30s must have been chosen keeping the Linux SCSI Mid-Layer in mind. > Mine reasoning is that my machine boots fast enough for me not > investigate more my iSCSI connections, but probably the iSCSI > appliance is giving authentication timeout and so the increased need > for a longer timeout on open-iscsi postinst. Making the package more > robust. > This is all TCP so the recovery should be instantaneous on the transport side. On top of that, iSCSI with its default settings, will do a ping health check every 5 seconds. > We may talk more about this problem and I offer my time and machine > to > do research on to improve the package if you see benefit on that. > But > I will not keep the bug open if you want to close it. No rush as such. I just proposed so, after brief validation on my setup. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
