It wasn't a DNS failure, because it has an IP address in the message ("could not connect to 10.101.3.142"). Therefore it was a TCP or TLS level failure due to a lack of response from the upstream.
As far as I know you cannot change the date format for error messages. On Wed, Oct 31, 2018 at 1:29 AM Dk Jack <dnj0...@gmail.com> wrote: > Hi, > I am trying to understand what the following error messages mean. > > 20181030.12h21m55s CONNECT: could not connect to 10.101.3.142 for 'http:// > <http://loadbal.smle.co:4080/v2/social/followee/up>....' (setting last > failure time) > 20181030.12h21m55s RESPONSE: sent 10.101.1.156 status 504 (Connection Timed > Out) for 'http://. > < > http://loadbal.smle.co:4080/v2/social/followee/update?app=sing&appVariant=1&appVersion=7.2.1&msgId=857&session=g4_8_zf0GsCGF5tFbExwZAEVr0GvTaqtj7vBqZR2tXSEGgZ98NJS6/doVpQ%3D%3D&digest=6c52a70443b19d80dfa45395a462be60f633fc09 > > > ...' > > At a high level, I can understand, but I am trying to see if I can get more > details on what caused the connection failure i.e. was it a dns lookup > failure or the was the server itself not available. > > Are there any knobs that I can configure that'd give me additional data? I > found this page, > > > https://docs.trafficserver.apache.org/en/6.2.x/admin-guide/monitoring/error-messages.en.html > > Also, is there a way to change time format in the error log i.e. regular > 'data' command format or unix epoch timestamp format etc. Thanks. > > Dk. > -- *Beware the fisherman who's casting out his line in to a dried up riverbed.* *Oh don't try to tell him 'cause he won't believe. Throw some bread to the ducks instead.* *It's easier that way. *- Genesis : Duke : VI 25-28