Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Icecast-Server Icecast-Server
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 104
    • Issues 104
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Xiph.Org
  • Icecast-ServerIcecast-Server
  • Issues
  • #2292
Closed
Open
Created Sep 27, 2016 by Raz Yalov@razyalov

Relay slave fails to connect over Amazon ELB

Trying to configure a slave Icecast server through an Amazon Elastic Load Balancer (ELB), the socket never connects. Log shows this error: WARN slave/update_from_master Relay slave failed to contact master server to fetch stream list

using strace it seems like the connection never establishes on the socket's opening level, but there is not description of the exact error.

Replacing the load balancer DNS with the IP of one of the servers that are behind the ELB does seems to work.

login as the icecast user I was able to verify that the same information does work directly via telnet and curl. Only the icecast connection fails through the ELB.

Assignee
Assign to
Time tracking