The StarWind iSCSI SAN service did not shut down properly

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
User avatar
flcdrg
Posts: 2
Joined: Thu Nov 14, 2013 6:51 am
Contact:

Thu Nov 14, 2013 6:56 am

I'm seeing the following error in my System event log:

"The StarWind iSCSI SAN service did not shut down properly after receiving a preshutdown control."

It appears to be related to the fact that it's taking my machine about 30 minutes to reboot.

Happy to provide more details if required. I'm running 6.0.5713

-david
User avatar
anton (staff)
Site Admin
Posts: 4021
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Thu Nov 14, 2013 7:35 am

It can happen when we run a huge cache and don't have time enough to flush it. Can you provide more configuration details?
flcdrg wrote:I'm seeing the following error in my System event log:

"The StarWind iSCSI SAN service did not shut down properly after receiving a preshutdown control."

It appears to be related to the fact that it's taking my machine about 30 minutes to reboot.

Happy to provide more details if required. I'm running 6.0.5713

-david
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
User avatar
flcdrg
Posts: 2
Joined: Thu Nov 14, 2013 6:51 am
Contact:

Fri Nov 15, 2013 12:16 am

anton (staff) wrote:It can happen when we run a huge cache and don't have time enough to flush it. Can you provide more configuration details?
StarWind is configured with a single ram drive (250Megs)

An extract from the Starwind server log includes the following (the time corresponds to when I had told Windows to restart)

Code: Select all

11/14 15:59:19.746 11d8 C[1], LOGOUT_REQUESTED: Event - LOGOUT.
11/14 15:59:19.746 11d8 C[1], IN_LOGOUT: T9/10.
11/14 15:59:19.746 11bc C[1], IN_LOGOUT: Event - LOGOUT_ACCEPT.
11/14 15:59:19.746 11bc C[1], FREE: T13.
11/14 15:59:19.746 11d0 C[1], FREE: recvData returned 10054
11/14 15:59:19.746 11d8 Tgt: close 'iqn.2008-08.com.starwindsoftware:rfm': 0 session(s) opened, 65536 more allowed.
11/14 15:59:19.746 1164 Srv: Service stopping. Reject iSCSI connection from 127.0.0.1:61904 to 127.0.0.1:3260.
11/14 15:59:19.746 1164 Srv: iSCSI listener stopped.
11/14 15:59:19.746 117c conf: Stop listening to control connections.
11/14 15:59:19.746 1180 bc: Socket error: 10004
11/14 15:59:19.746 1180 bc: Stop listening to UDP packets.
11/14 15:59:19.746 1164 Srv: Shutting down...
11/14 15:59:19.746 1164 Plugin: Empty control response.
11/14 15:59:19.746 1164 Tgt: iqn.2008-08.com.starwindsoftware:rfm: device 'RamDrive1' is detached.
11/14 15:59:19.746 1164 error: assertion failed: c:\_starwind\_release_60\starwind\service\common\fn_common.cpp:28 (isEmpty())
11/14 15:59:19.746 1164 PerformanceDB: CPerformanceCounter::WriteOperationalData called on uninitialized counter(DB entry: 0000000000000000, Record: 0000000000000000).
11/14 15:59:19.746 1164 PerformanceDB: CPerformanceCounter::Close exiting with error: WriteOperationalData failed.
11/14 15:59:19.746 1164 error: assertion failed: c:\_starwind\_release_60\starwind\service\common\fn_common.cpp:28 (isEmpty())
11/14 15:59:19.746 1164 PerformanceDB: CPerformanceCounter::WriteOperationalData called on uninitialized counter(DB entry: 0000000000000000, Record: 0000000000000000).
11/14 15:59:19.746 1164 PerformanceDB: CPerformanceCounter::Close exiting with error: WriteOperationalData failed.
11/14 15:59:19.746 1164 error: assertion failed: c:\_starwind\_release_60\starwind\service\common\fn_common.cpp:28 (isEmpty())
11/14 15:59:19.746 1164 Srv: Waiting for 5 seconds for SSC devices to close...
11/14 15:59:24.754 1164 Srv: Waiting for 5 seconds for SSC devices to close...
11/14 15:59:29.761 1164 Srv: Waiting for 5 seconds for SSC devices to close...
11/14 15:59:34.769 1164 Srv: Waiting for 5 seconds for SSC devices to close...
11/14 15:59:36.251 366c ntsrv: watchdog: service is still stopping... Updating service status.
11/14 15:59:39.777 1164 Srv: Waiting for 5 seconds for SSC devices to close...
11/14 15:59:44.784 1164 Srv: Waiting for 5 seconds for SSC devices to close...
11/14 15:59:49.792 1164 Srv: Waiting for 5 seconds for SSC devices to close...
11/14 15:59:52.756 366c ntsrv: watchdog: service is still stopping... Updating service status.
11/14 15:59:54.800 1164 Srv: Waiting for 5 seconds for SSC devices to close...
11/14 15:59:59.807 1164 Srv: Waiting for 5 seconds for SSC devices to close...
11/14 16:00:04.815 1164 Srv: Waiting for 5 seconds for SSC devices to close...
11/14 16:00:09.261 366c ntsrv: watchdog: service is still stopping... Updating service status.
11/14 16:00:09.823 1164 Srv: Waiting for 5 seconds for SSC devices to close...
11/14 16:00:14.830 1164 Srv: Waiting for 5 seconds for SSC devices to close...
11/14 16:00:19.838 1164 Srv: Waiting for 5 seconds for SSC devices to close...
The "ntsrv: watchdog" and 3 "Srv: Waiting" messages then continued for approximately 30 minutes - at which time that log ends (and i assume Windows probably gave up waiting for the service to stop).

-david
User avatar
Anatoly (staff)
Staff
Posts: 1675
Joined: Tue Mar 01, 2011 8:28 am
Contact:

Mon Nov 18, 2013 9:19 am

We`ll appreciate if you could drop the complete log to support@starwindsoftware.com (please put the reference to this topic in your email).

Thank you
Best regards,
Anatoly Vilchinsky
Global Engineering and Support Manager
www.starwind.com
av@starwind.com
Post Reply