Project

General

Profile

Bug #5571

iSCSI failed to start after turning on experimental iSCSI - version 9.2.1.6

Added by James Austin over 6 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Important
Assignee:
William Grzybowski
Category:
OS
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

iSCSI failed to start after turning on experimental iSCSI - version 9.2.1.6
We are deploying a pair of 2012 clustered file servers.
After the upgrade to .6 I turned on experimental iSCSI, then upon NAS reboot the service would not start.

Jul 17 10:05:41 EDCFNAS05 notifier: Will not 'reload' ctld because ctld_enable is NO.
Jul 17 10:05:54 EDCFNAS05 notifier: ctld not running? (check /var/run/ctld.pid).
Jul 17 10:05:54 EDCFNAS05 notifier: ctld not running? (check /var/run/ctld.pid).
Jul 17 10:05:54 EDCFNAS05 notifier: Starting ctld.
Jul 17 10:05:54 EDCFNAS05 notifier: ctld: unknown portal-group "pg1" for target "iqn.XXXXXX"
Jul 17 10:05:54 EDCFNAS05 ctld7771: unknown portal-group "pg1" for target "iqn.XXXXXX"
Jul 17 10:05:54 EDCFNAS05 ctld7771: configuration error; exiting
Jul 17 10:05:54 EDCFNAS05 notifier: ctld: configuration error; exiting
Jul 17 10:05:54 EDCFNAS05 root: /etc/rc.d/ctld: WARNING: failed to start ctld
Jul 17 10:05:54 EDCFNAS05 notifier: /etc/rc.d/ctld: WARNING: failed to start ctld

Stop refresh

Associated revisions

Revision 6447fa2f (diff)
Added by William Grzybowski over 6 years ago

Fix portal group number in clt.conf generation Ticket: #5571

Revision 173cd340 (diff)
Added by William Grzybowski over 6 years ago

Fx ctl.conf generation for when iscsi_target_extent_type is a Disk Ticket: #5571

History

#1 Updated by Josh Paetzel over 6 years ago

  • Status changed from Unscreened to Screened

Can you attach /etc/ctl.conf please?

#2 Updated by Josh Paetzel over 6 years ago

Also,

We didn't fix a persistent reservation issue with w2k12 until Tuesday, so you may want to run a nightly of 9.3 from last night. The experimental target in 9.2.1.6 wasn't experimental enough.

#4 Updated by Josh Paetzel over 6 years ago

That won't fix the problem you're having right now though that is preventing ctl from starting. That's the config file generator going sideways.

#5 Updated by James Austin over 6 years ago

Okay I will try the nightly... I have been watching this pretty closely, but I did not think to use a nightly - I am using a the beta from the download page.

I am not highly skilled with linux type shell yet, learning how get the file exported in a way that allows me to attach it - but here is a copy of the file's contents:

portal-group pg2 {
discovery-auth-group no-authentication
listen 172.27.15.250:3260
}

target iqn.2011-03.com.EDCFNAS05.dccentral:data {
alias data
auth-group no-authentication
portal-group pg1

lun 0 {                                                                                                             
option unmap on
path /dev/2
blocksize 512
serial 00219ba1887b00
device-id "iSCSI Disk 00219ba1887b000 "
option vendor "FreeBSD"
option product "iSCSI Disk"
option revision "0123"
}
}

target iqn.2011-03.com.EDCFNAS05.dccentral:witness {
alias witness
auth-group no-authentication
portal-group pg1

lun 0 {                                                                                                             
option unmap on
path /dev/1
blocksize 512
serial 00219ba1887b01
device-id "iSCSI Disk 00219ba1887b010 "
option vendor "FreeBSD"
option product "iSCSI Disk"
option revision "0123"
}
}

#6 Updated by Josh Paetzel over 6 years ago

NP. I see the config file is wrong in a couple places.

I need one of a couple things to fix this:

1) Either save your config file and email it to me at DO NOT attach it to this ticket.

2) A screensharing session with you so I can poke at the system and see why it's screwing up. (I'm in Pacific time)

#7 Updated by James Austin over 6 years ago

I get the file sent to you.

What is the easiest way to pull the file from the system ?

I have an SSH connection to it using a terminal.

#8 Updated by Josh Paetzel over 6 years ago

Just go to system settings in the GUI and click the save config button. That will download a file to your computer. Send me an email with that file attached.

#9 Updated by James Austin over 6 years ago

sent, please note that I have not applied the nightly update yet.

#10 Updated by Josh Paetzel over 6 years ago

  • Status changed from Screened to Fix In Progress
  • Assignee changed from Josh Paetzel to William Grzybowski

Well, we are fixing it right now, so maybe wait until tonight's nightly and the problem will be resolved. :)

#11 Updated by James Austin over 6 years ago

Is it something that I have configured incorrectly, or something outside of my control ?

#12 Updated by William Grzybowski over 6 years ago

  • Status changed from Fix In Progress to Resolved

No, its a problem in the config file generation. Please try the nightly image tomorrow and let us know if its fixed.

Thanks!

#13 Updated by James Austin over 6 years ago

Did the nightly get made as planned ?
If so, which one should I be looking for?
I did not see an fresh files in the 9.2.1.6 folder.

#14 Updated by Josh Paetzel over 6 years ago

It's seems there was no nightly from last night. I'll make sure one kicks off tonight.

#15 Updated by Jordan Hubbard over 6 years ago

There was indeed a nightly done last night (see http://download.freenas.org/nightlies/9.3/ALPHA) - there has been a nightly done every night since July 8th (I could actually go back further to the 1st, but July 7th was skipped for some reason).

The poster is looking in the wrong place - we're not doing 9.2.1.6 nightlies anymore since 9.2.1.6 has been released. We do 9.3 nightlies now.

#16 Updated by James Austin about 6 years ago

update:

I was, in fact, able to download the nightly from mid July. After it's installation, I was able to turn on the iscsi service and configure the targets.

We are now successfully running a pair of Windows Server 2012 virtual machines in a fail-over cluster with a 4TB hardware raid with hot spare protection - of course using FreeNAS as the shared storage for both the data and witness drives.

We did immediately begin receiving an e-mail alert though listed below... perhaps a new ticket should be made.

Checking for packages with security vulnerabilities:
pkg: http://www.vuxml.org/freebsd/vuln.xml.bz2: Unauthorized
pkg: Cannot fetch vulnxml file!

-- End of security output --

#17 Updated by Dru Lavigne almost 3 years ago

  • Target version set to Master - FreeNAS Nightlies
  • Seen in changed from to Unspecified

Also available in: Atom PDF