Metadata server bug

Because of another issue, I deleted metadata.db. Unfortunately the metadata service is now not responding:

HTTP/1.0 504 Gateway Time-out
Cache-Control: no-cache
Content-Type: text/html

<html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
</body></html>

Find more posts tagged with

Comments

Bradley Grainger (Logos)

We're not logging any problems with the service right now; is it still inaccessible for you?

Mark Barnes

https://community.logos.com/discussion/comment/703491#Comment_703491

We're not logging any problems with the service right now; is it still inaccessible for you?

I'm still getting the problem.

POST https://services.logos.com/resource/v3/MetadataService.svc HTTP/1.1
Content-Type: text/xml; charset=utf-8
Cookie: <redacted>
User-Agent: Logos/6.2 (6.2.0.11; en-GB; Win)
SOAPAction: "http://services.logos.com/resource/v3/MetadataService/GetMetadataInfo"
Host: services.logos.com
Content-Length: 287
Accept-Encoding: gzip, deflate

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><GetMetadataInfo xmlns="http://services.logos.com/resource/v3/"><since>2013-06-25T23:23:43Z</since><platform i:nil="true" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"/></GetMetadataInfo></s:Body></s:Envelope>

HTTP/1.0 504 Gateway Time-out
Cache-Control: no-cache
Content-Type: text/html

<html><body><h1>504 Gateway Time-out</h1> The server didn't respond in time. </body></html>

== TIMING INFO ============
ClientConnected: 23:09:53.572
ClientBeginRequest: 23:10:16.778
GotRequestHeaders: 23:10:16.778
ClientDoneRequest: 23:10:16.778
Determine Gateway: 0ms
DNS Lookup: 0ms
TCP/IP Connect: 0ms
HTTPS Handshake: 0ms
ServerConnected: 23:09:30.542
FiddlerBeginRequest: 23:11:06.959
ServerGotRequest: 23:11:06.959
ServerBeginResponse: 23:11:06.959
GotResponseHeaders: 23:11:57.135
ServerDoneResponse: 23:11:57.136
ClientBeginResponse: 23:11:57.136
ClientDoneResponse: 23:11:57.136

Overall Elapsed: 0:01:40.358

Mark Barnes

https://community.logos.com/discussion/comment/705142#Comment_705142

Bump.

It's still happening today:

2015-03-10 21:43:42.2260 8 Error WebServiceClient TimeoutException for ResourceMetadataInfo[]: System.TimeoutException: The remote server returned an error: (504) Gateway Timeout. ---> System.Net.WebException: The remote server returned an error: (504) Gateway Timeout. ~ at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) ~ at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result) ~ --- End of inner exception stack trace --- ~ ~Server stack trace: ~ at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result) ~ at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result) ~ at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result) ~ at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) ~ at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) ~ ~Exception rethrown at [0]: ~ at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) ~ at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) ~ at LDLS4.WebServices.MetadataServices.MetadataService.EndGetMetadataInfo(IAsyncResult result) ~ at Libronix.Utility.Threading.AsyncMethodAsyncAction`1.Callback(IAsyncResult ar) ~ at LDLS4.WebServiceClient.GetResult[T](AsyncMethodAsyncAction`1 action)
2015-03-10 21:43:42.2310 8 Warn ResourceMetadataUpdateServiceClient GetResourceMetadataInfo failed (error = CommunicationFailure); aborting processing.

Mark Barnes

https://community.logos.com/discussion/comment/705726#Comment_705726

Still happening…

HansK

https://community.logos.com/discussion/comment/706091#Comment_706091

Bumping here in The Netherlands for Bro. Mark.