Mirroring using Load Balanced Server.

Vote:
 

Hi,

When my destination mirroring web service is load balanced. I am getting following error.

 

Mirroring state: Failure during page package transfer
The following errors occured:
Failed to call StartChunkPackage with context c62a9e21-5e42-4b76-8aee-35e0b95e8c34 becuase there is not Header info in Mirroring job
SourceService: Exported 0 pages
TargetService: Imported 0 pages, moved 0 pages, deleted 0 pages

 

Can you please help me figuring out the problem.

Thanks & Regards,

Sujit

#53204
Aug 31, 2011 23:51
Vote:
 

Are both load balanced web servers sharing the same database, or does each server have it's own database?

One thing I would suggest is if you can get a direct route to one of the servers (either DNS entry or the IP address of the server) and point your mirroring job at that rather then the shared URL/IP and see if that works. If the load balanced servers are sharing a database, mirroring to one of the servers will get the data to both of them, though you'll need Remote Events enabled.

#53729
Sep 21, 2011 11:09
Vote:
 

I'm experiencing a similar issue uploading to one server in a load balancing pair with shared database.

The first job sometimes fails but the subsequent one will always succeed. 

I've set the job up with a different server name AND port so there's no way the load balancer is getting involved.

same error as above:

Failed to call StartChunkPackage with context2d517044-a20d-4161-81a8-736e51a98969 becuase there is not Header info in Mirroring job.

 

I can confirm that this is not to do with the load balancing as it returns the same error even when the load balancer is switched off.

 

Can anyone from EPiServer confirm what causes this error?

#61925
Edited, Oct 05, 2012 17:04
Vote:
 

I get the following entries in my log file...

 

2012-10-08 11:00:54,800 DEBUG [TransferingThread] EPiServer.MirroringService.MirroringTransferProtocol.Common.TransferQueueManager.HandleStatus - Context = 2d517044-a20d-4161-81a8-736e51a98969 State = TransferingError Starting Errors Failed to call StartChunkPackage with context 2d517044-a20d-4161-81a8-736e51a98969 becuase there is not Header info in Mirroring job
End of Errors 
DestinationRoot=3  ,DestinationPath=C:\Windows\TEMP\episerver\cms6\mirroring\targetfiles\2d517044-a20d-4161-81a8-736e51a98969  ,DestinationPageGuid=3dba82ce-1a4a-446a-b8f1-b67f0e8e4b64  ,TypeOfData=Page  ,SourcefilePath=C:\Windows\TEMP\episerver\cms6\mirroring\sourcefiles\2d517044-a20d-4161-81a8-736e51a98969\P2012108_10-0-37-971_0.TMP  ,TargetfilePath=P2012108_10-0-37-971_0.TMP  ,FileSize=210732  ,SizeOfSentData=0 ,SizeOfReceiveData=0

2012-10-08 11:01:03,082 ERROR [58] EPiServer.MirroringService.MirroringProviderBase.ErrorHandling - Context = 2d517044-a20d-4161-81a8-736e51a98969 State = TransferingError Starting Errors Failed to call StartChunkPackage with context 2d517044-a20d-4161-81a8-736e51a98969 becuase there is not Header info in Mirroring job
End of Errors 
DestinationRoot=3  ,DestinationPath=C:\Windows\TEMP\episerver\cms6\mirroring\targetfiles\2d517044-a20d-4161-81a8-736e51a98969  ,DestinationPageGuid=3dba82ce-1a4a-446a-b8f1-b67f0e8e4b64  ,TypeOfData=Page  ,SourcefilePath=C:\Windows\TEMP\episerver\cms6\mirroring\sourcefiles\2d517044-a20d-4161-81a8-736e51a98969\P2012108_10-0-37-971_0.TMP  ,TargetfilePath=P2012108_10-0-37-971_0.TMP  ,FileSize=210732  ,SizeOfSentData=0 ,SizeOfReceiveData=0

    

#61950
Oct 08, 2012 13:57
Vote:
 

I have the same issue, no load balancer... EPiServer are investigating it...

#62287
Oct 19, 2012 12:16
Vote:
 

Cool, thanks for letting me know. I am having some VERY high CPU % in relation to this problem, which results in needing to recycle the application pool. Is that another symptom you are experiencing?

#62290
Oct 19, 2012 12:34
Vote:
 

No, not really.. well I am getting high CPU usage, but guess that's just the mirroring job doing it's thing. Both cores seems to be working at about 50% when the mirroring job is creating the package.

#62300
Oct 19, 2012 14:48
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.