Find the answer to your Linux question:
Results 1 to 3 of 3
I'm tying to build OpenSim on a Debian 5 VPS via putty on Windows XP (hope that makes so sense to someone). I keep getting the following: Code: 09:45:18 - ...
  1. #1
    Just Joined!
    Join Date
    May 2009
    Posts
    10

    Access to port 9000

    I'm tying to build OpenSim on a Debian 5 VPS via putty on Windows XP (hope that makes so sense to someone).

    I keep getting the following:
    Code:
    09:45:18 - [REGION]: Starting HTTP server
    09:45:18 - [HTTPD]: Starting up HTTP Server
    09:45:18 - [HTTPD]: Spawned main thread OK
    09:45:18 - [HTTPD]: Error - Address already in use
    09:45:18 - [HTTPD]: Tip: Do you have permission to listen on port 9000, 0?
    09:45:18 - [APPLICATION]:
    APPLICATION EXCEPTION DETECTED: System.UnhandledExceptionEventArgs
    
    Exception: System.Net.Sockets.SocketException: Address already in use
      at System.Net.Sockets.Socket.Bind (System.Net.EndPoint local_end) [0x00000]
      at System.Net.Sockets.TcpListener.Start (Int32 backlog) [0x00000]
      at HttpServer.HttpListenerBase.Start (Int32 backlog) [0x00000]
      at OpenSim.Framework.Servers.HttpServer.BaseHttpServer.StartHTTP () [0x00000]
    Now two lines of enquiry (actually 3)

    1. Is the port blocked at the firewall (as far as I can tell no, though with Nortons Security Suite 2009, it is hard to tell what is going on - also the VPS does not block the port)

    2. I've made an error in the associated config files (don't think so, been through them several times, but I'm chasing that through on another forum specific to OpenSim.)

    3. There is a port conflict somewhere (obvious)

    Now - is there anyway to identify where the blockage or conflict is? What other application is using the port.

    I'm not highly Linux skill - skills are pretty poor actually so Mickey Mouse and 'how to suck Lemons' replies are more than welcome.:rolleyes:

    Thanks

  2. #2
    Linux Guru Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    2,096
    Another process, probably an earlier incarnation of that http server, is already bound to port 9000.

    To verify this, please do as root:
    Code:
    netstat -tunlp | grep 9000
    Use the appropiate init script to stop that daemon.
    If all else fails, find out its PID and kill it

    kill <PID NUMBER>
    and if you are really desperate:
    kill -9 <PID NUMBER>

    Then start again and the httpd server should be able to bind to port 9000

  3. #3
    Just Joined!
    Join Date
    May 2009
    Posts
    10
    Thanks for that - it is just what I needed

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •