It would be helpful if you could narrow down the specific request that
is triggering the log message, or perhaps the log message occurs for
every request after a certain point? If it is for a specific request,
use the 'dig' tool to look at the DNS record for that hostname.
The hostdb is TS's DNS cache (TS does not use gethostbyname). The out
of room message indicates that the DNS lookup will not be cached, so the
proxy will do additional DNS queries in the future. This might impact
performance if your name server is not nearby.
--Steve
Zeller, Jan (ID) wrote, on 7/27/10 11:44 AM:
Hi Steve,
Are you passing a lot of traffic with unique hostnames through TS or is
it an issue with some hostnames having a large number of DNS A records?
to be honest I don't know what you mean by that.
I have a cache-only bind which is listening on localhost installed on the same
box.
the resolv.conf looks like this :
domain my.domain
nameserver 127.0.0.1
nameserver myprimarynameserver
nameserver mysecondarynameserver
Is there any relationship ? and what consequences does 'out of room...' finally
have ?
Can you try adding the above line to your records.config and maybe doubling the
size?
I've pasted 'CONFIG proxy.config.hostdb.storage_size INT 67108864' into
records.config and reloaded the config by applying 'traffic_line -x'
Unfortunately the message persists.
oops I restarted TS and
Jul 27 20:23:33 traffic_server[19942]: {47887539635696} WARNING: configuration
changed: [hostdb.config] : reinitializing database
Jul 27 20:23:33 traffic_server[19942]: {47887539635696} NOTE: reconfiguring
host database
Jul 27 20:23:33 traffic_server[19942]: {47887539635696} WARNING: Configured
store too small, unable to reconfigure
Jul 27 20:23:33 traffic_server[19942]: {47887539635696} WARNING: unable to
initialize database (too little storage) : [hostdb.config] : disabling database
You may need to 'reconfigure' your cache manually. Please refer to the
'Configuration' chapter in the manual.
Jul 27 20:23:33 traffic_server[19942]: {47887539635696} WARNING: could not
initialize host database. Host database will be disabled
Jul 27 20:23:33 traffic_server[19942]: {47887539635696} WARNING: bad hostdb or
storage configuration, hostdb disabled
Jul 27 20:23:33 traffic_server[19942]: {47887539635696} NOTE: cache clustering
disabled
Jul 27 20:23:33 traffic_server[19942]: {47887539635696} NOTE: logging
initialized[7], logging_mode = 3
Jul 27 20:23:33 traffic_server[19942]: {47887539635696} NOTE: traffic server
running
Jul 27 20:23:33 traffic_server[19942]: {1080052048} NOTE: cache enabled
Jul 27 20:23:44 traffic_cop[19718]: (http test) received non-200 status(502)
Jul 27 20:23:44 traffic_cop[19718]: server heartbeat failed [1]
.
.
That was because I set CONFIG proxy.config.hostdb.size INT 500000 before without having set CONFIG proxy.config.hostdb.storage_size
Now I actually have
CONFIG proxy.config.hostdb.size INT 200000
CONFIG proxy.config.hostdb.storage_size INT 67108864
these values seem to be alright despite the fact that I don't really understand
that parametres.
thanks,
---
Jan
