Re: Unable to bind socket: 80 : Permission denied

[Reindl Harald]

Am 08.04.2013 12:02, schrieb Matthieu Bienvenüe:
> I'm currently have a problem wih setting ATS up. I'm using an OpenVZ 
> container (Proxmox 2.3) that runs debian 6.0.
>
> [Apr  8 08:51:37.519] Manager {0xb70756d0} NOTE: [ClusterCom::ClusterCom] 
> Node running on OS: 'Linux' Release:
> '2.6.32-19-pve'
> [Apr  8 08:51:37.519] Manager {0xb70756d0} ERROR: [bindProxyPort] Unable to 
> bind socket: 80 : Permission denied
> [Apr  8 08:51:37.519] Manager {0xb70756d0} ERROR:  (last system error 13: 
> Permission denied)
> [E. Mgmt] log ==> [TrafficManager] using root directory '/usr'
> [Apr  8 08:51:37.526] {0xb70386d0} STATUS: opened 
> /var/log/trafficserver/manager.log
> [Apr  8 08:51:37.526] {0xb70386d0} NOTE: updated diags config
> [Apr  8 08:51:37.526] Manager {0xb70386d0} NOTE: [appendDefaultDomain] Unable 
> to determine default domain name.
> Nodes will be know by their unqualified host name
> [Apr  8 08:51:37.527] Manager {0xb70386d0} NOTE: [ClusterCom::ClusterCom] 
> Node running on OS: 'Linux' Release:
> '2.6.32-19-pve'
> [Apr  8 08:51:37.527] Manager {0xb70386d0} ERROR: [bindProxyPort] Unable to 
> bind socket: 80 : Permission denied
> [Apr  8 08:51:37.527] Manager {0xb70386d0} ERROR:  (last system error 13: 
> Permission denied)
> 
> I don't know why I've such problems. I've tested with wheezy repository with 
> the same result. That's strange
> because this works fine with a Debian 6.0 running on an Virtual Box VM

i suspect that not much users running ATS in OpenVZ

maybe the better list would be a OpenVZ specific because it is surely some 
restriction
of the container if the same packages are working fine native and in vbox

signature.asc
Description: OpenPGP digital signature