ERROR: Message: Connection to xxx.xxx.xxx.xxx on port 80 for protocol HTTP timed out

[kersi]

Hello experts,

My customer is seeing the following error while creating a volume

The error message for the job is "Failed to create new volume: vol_ofdi02n2_ps22bizg_ofg01_data10. Message: Connection to xxx.xxx.xxx.xxx on port 80 for protocol HTTP timed out.".

14:11:50.673 INFO  [] ***** Workflow Execution Started *****

14:11:50.736 INFO  [] ### Row Number 10 ###

14:11:50.736 INFO  [Create Volume] ### Command 'Create Volume' ###

14:11:52.249 INFO  [Create Volume] Executing command: ./Create_Volume8962227518105159635.ps1 -AggregateName a3_28_reserve_WFA_V107400 -Array xxx.xxx.xxx.xxx -AutoDeleteOptions 'trigger snap_reserve,commitment try,delete_order oldest_first,defer_delete user_created,state on' -AutosizeIncrementSize 1024 -AutosizeMaxSize 7864320 -Options 'create_ucode on, convert_ucode on,minra off,nvfail on,try_first snap_delete' -Size 2621440 -SnapshotScheduleOptions '0 0 0' -VolumeGuarantee file -VolumeName vol_ofdi02n2_ps22bizg_ofg01_data10

14:11:52.452 INFO  [Create Volume] Get-NaCredentials -Host xxx.xxx.xxx.xxx

14:11:52.592 INFO  [Create Volume] Connect-NaController (with credentials) -Name xxx.xxx.xxx.xxx

14:11:55.088 INFO  [Create Volume] Connected to controller

14:11:55.151 INFO  [Create Volume] Creating a new volume - name 'vol_ofdi02n2_ps22bizg_ofg01_data10' , aggregate name 'a3_28_reserve_WFA_V107400' , size '2621440m' , volume guarantee 'file'

14:12:56.990 ERROR  [Create Volume] Failed to create new volume: vol_ofdi02n2_ps22bizg_ofg01_data10. Message: Connection to xxx.xxx.xxx.xxx on port 80 for protocol HTTP timed out.

14:12:57.193 ERROR  [Create Volume] Failed to create new volume: vol_ofdi02n2_ps22bizg_ofg01_data10. Message: Connection to xxx.xxx.xxx.xxx on port 80 for protocol HTTP timed out.

14:12:57.240 INFO  [] ***** Workflow Execution Failed *****

Main error appears to be

Message: Connection to xxx.xxx.xxx.xxx on port 80 for protocol HTTP timed out.

Version of WFA 1.1

Thanks

Kersi

[goodrum]

The command being sent to the Array is actually timing out after 60sec (which is the default timeout for that command).  Has this failed more than once or just this one time?  It looks like the initial connection worked fine but sending the command to create the volume failed.  Did you check to see if the volume was created on the Array but never returned the information back to WFA?  This is possible if the Array is slow to respond to the WFA that the operation was complete.  60secs seems like an abnormally long time though.

Jeremy Goodrum, NetApp

The Pirate

Twitter: @virtpirate

Blog: www.virtpirate.com

[kersi]

Thanks Jeremy, Will check and get back.

[bdave]

Hi Kersi,

Also check that "options httpd.enable.admin" is "on" for the controller in question.

Thanks,

Dave

[kersi]

Thanks Dave, good point.

[tanzim]

Hi Kersi,

Were you able to resolve this issue?

Regards,

Tanzim

[kersi]

Hi Tanzim,

The issue remains unresolved.

Currently, customer is working on upgrading from WFA 1.1 to 2.0 and when doing so following the steps

backing up 1.1

moving backup to a different system,

installing 2.0

restoring the backup

At this stage customer gets an error

          "Failed restoring 'C:\........"

          Caused by Transaction rolled back

          Important: The DB state may be inconsistent

Thanks

[tanzim]

What is the version of the WFA 1.1 instance that you are upgrading? Upgrade to WFA 2.0 is supported from WFA 1.1.0.53.2 or later.

Regards,

Tanzim

[kersi]

Ah, that might be helpful clue.

Will check the version in this case, for sure.

Thanks

[kersi]

The version

The legacy wfa system that the db backup was from was version 1.1.1.22.5-7752

Customer trying to take backup of the system above and restore it to version

2.0.0.391.2-B11275

Therefore, we should be good as far as compatibility to upgrade is concerned.

[yaronh]

Hi Kersi,

Not neccesarily. As far as I know an extensive PS effort was invested in your customer's 1.1.1 implementation.

Workflows based on the core certified components are automatically upgraded as part of the upgrade process by the platform itself.

Additional packages - we do a best effort which depends on the content. The difference between 1.1.1 and 2.0 is in terms of approach, of simplification. I suspect the upgrade may not be automatic in that case, and some changes might be required.

BTW - The approach of exporting the flows and importing them into 2.0 (with automatic upgrade) may be a better approach. Upgrade of the flows tends to be easier for flows than cache objects (should you have customized ones).

In short, we can take a look and try to point at the right direction. Depending on the original implementation, it is possible that this upgrade may not be automatic.

Best,

Yaron

[yaronh]

Hi Kersi,

Not neccesarily. As far as I know an extensive PS effort was invested in your customer's 1.1.1 implementation.

Workflows based on the core certified components are automatically upgraded as part of the upgrade process by the platform itself.

Additional packages - we do a best effort which depends on the content. The difference between 1.1.1 and 2.0 is in terms of approach, of simplification. I suspect the upgrade may not be automatic in that case, and some changes might be required.

BTW - The approach of exporting the flows and importing them into 2.0 (with automatic upgrade) may be a better approach. Upgrade of the flows tends to be easier for flows than cache objects (should you have customized ones).

In short, we can take a look and try to point at the right direction. Depending on the original implementation, it is possible that this upgrade may not be automatic.

Best,

Yaron