Thanks for quick reply.
I don't need a cluster in my configuration...

>grep cluster /data/opt/trafficserver/etc/trafficserver/records.confi
   # cluster type requires restart to change
   # 1 is full clustering, 2 is mgmt only, 3 is no clustering
LOCAL proxy.local.cluster.type INT 3
CONFIG proxy.config.cluster.cluster_port INT 0
CONFIG proxy.config.cluster.rsport INT 0
CONFIG proxy.config.cluster.mcport INT 0
CONFIG proxy.config.cluster.mc_group_addr STRING 224.0.1.37
CONFIG proxy.config.cluster.mc_ttl INT 0
CONFIG proxy.config.cluster.log_bogus_mc_msgs INT 0
CONFIG proxy.config.cluster.ethernet_interface STRING lo0
CONFIG proxy.config.cluster.cluster_configuration STRING cluster.config


>tail -3 manager.log
[Dec 1 11:28:18.671] Manager {0x803007400} ERROR: (last system error 49: Can't assign requested address) [Dec 1 11:28:18.671] Manager {0x803007400} ERROR: [ClusterCom::sendOutgoingMessage] Message send failed [Dec 1 11:28:18.671] Manager {0x803007400} ERROR: (last system error 49: Can't assign requested address)


With default value "LOCAL proxy.local.cluster.type INT 0" I have the same issue.

My ATS version:
/data/opt/trafficserver/bin/traffic_line -V
Apache Traffic Server - traffic_line - 3.3.1-dev - (build # 103022 on Nov 30 2012 at 22:31:42)


On 12/01/2012 10:43 AM, [email protected] wrote:
well, it should not flooding in this way if you don't enable cluster.
please 'grep cluster records.config' in your config dir.

I haven't done any testing for the cluster in OSes other than Linux :(

I think you can try the git/master version, which fixed the Raw disk
supporting issue, maybe released as a V3.3.1 soon.

FYI

在 2012-12-01六的 09:00 +0200,Vladyslav Bachynskyi写道:
Hi All,


I've compiled the latest versions (3.2 and 3.3) on FreeBSD 9.1.
When ATS is starting, it's flooding in logs below errors and stops to
work:


[Nov 30 12:45:30.719] Manager {0x803007400} ERROR:
[ClusterCom::sendOutgoingMessage] Message send failed
[Nov 30 12:45:30.719] Manager {0x803007400} ERROR:  (last system error
49: Can't assign requested address)
[Nov 30 12:45:30.719] Manager {0x803007400} ERROR:
[ClusterCom::sendOutgoingMessage] Message send failed


I have had hope, that issues from my previous email were fixed in
these new versions, but unfortunately, I can't check it because of
these errors.


Please advise.
Thanks in advance.


Reply via email to