iscsi_trgt: module verification failed
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| iscsitarget (Ubuntu) |
Expired
|
High
|
Unassigned | ||
Bug Description
I am on 64-bit Lubuntu Trusty Tahr (development branch)
(64-bit Lubuntu nighlty build of 2014-03-14 with updates)
(this machine is set up with RAID-1, LVM, Encryption, iSCSI Target
and iSCSI client, in case that matters.)
Versions of iSCSI:
ii iscsitarget 1.4.20.
ii iscsitarget-dkms 1.4.20.
I have successfully set up an iSCSI target (and client).
But if I peek inside the /var/log/syslog,
I see this snippet:
Mar 26 17:56:29 bee005 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="710" x-info="http://
...
Mar 26 17:57:03 bee005 ntpd_intres[1148]: parent died before we finished, exiting
[89 second gap]
Mar 26 17:58:32 bee005 kernel: [ 191.597648] iscsi_trgt: module verification failed: signature and/or required key missing - tainting kernel
Mar 26 17:58:32 bee005 kernel: [ 191.598233] iSCSI Enterprise Target Software - version trunk
Mar 26 17:58:32 bee005 kernel: [ 191.598297] iscsi_trgt: Registered io type fileio
Mar 26 17:58:32 bee005 kernel: [ 191.598299] iscsi_trgt: Registered io type blockio
Mar 26 17:58:32 bee005 kernel: [ 191.598301] iscsi_trgt: Registered io type nullio
...
The machine is taking a noticeable a mount of time to boot up. (2+ minutes).
This snippet in syslog, makes me want to say that the iscsi_targt module in the kernel has delayed
the booting up of the machine by 90-120 seconds due to the 89 second gap in the
syslog file, and that it's been 2 minutes 3 seconds since beginning of the syslog.
Did some signature/key not get packaged in the latest and greatest packages of
iscsitarget and iscsitarget-dkms?
(and the kernel waits (or retires) for 120 seconds before continuing on?)
| Changed in iscsitarget (Ubuntu): | |
| importance: | Undecided → High |
| Serge Hallyn (serge-hallyn) wrote | #1 |
| gmoore777 (guy-moore) wrote | #2 |
| gmoore777 (guy-moore) wrote | #3 |
| Nish Aravamudan (nacc) wrote | #4 |
| Changed in iscsitarget (Ubuntu): | |
| status: | New → Incomplete |
| Launchpad Janitor (janitor) wrote | #5 |
| Changed in iscsitarget (Ubuntu): | |
| status: | Incomplete → Expired |
Thanks for reporting this bug.
The syslog messages in question were not themselves followed by a long delay before the next message, so this may or may not be the cause of your boot slowdown. Is it possible for you to install the bootchart package? It will create a .png image which should show how long each job is taking, and which jobs are blocking which others.