Hi Tomer,

Thanks for the fast reply.

control@pia /usr/local/src/rpyc-3.2.2 $ sudo netstat -nap | grep 18812
tcp 0 0 0.0.0.0:18812 0.0.0.0:* LISTEN 6274/python
control@pia /usr/local/src/rpyc-3.2.2 $

Sorry but I am not too sure what that means. How do I change the port number?

As far as I know there is no firewall on the Pi.

Cheers
Mick

On 30/07/12 23:50, Tomer Filiba wrote:
interesting. either it's already in use, which would be strange (TCP 18812) or the kernel has a more limited TCP port space (on this limited device) -- but that would be very strange.
try running
sudo netstat -nap | grep 18812
to see who's taking it

if that won't help, try changing the port to a lower number, say, 8812.

btw, the pi doesn't have any firewalls on it, right?



-----------------------------------------------------------------

        *Tomer Filiba*
tomerfiliba.com <http://tomerfiliba.com/> <http://www.facebook.com/tomerfiliba> <http://il.linkedin.com/in/tomerfiliba>




On Tue, Jul 31, 2012 at 1:44 AM, Mick Sulley <[email protected] <mailto:[email protected]>> wrote:

    Hi,
    I am trying to use rpyc on my Raspberry Pi running Raspian.  When
    I try to run rpyc_classic.py I get an error

    control@pia /usr/local/src/rpyc-3.2.2 $ sudo rpyc_classic.py
    Traceback (most recent call last):
      File "/usr/local/bin/rpyc_classic.py", line 171, in <module>
        main()
      File "/usr/local/bin/rpyc_classic.py", line 167, in main
        handler(options)
      File "/usr/local/bin/rpyc_classic.py", line 122, in serve_threaded
        auto_register = options.auto_register)
      File
    "/usr/local/lib/python2.7/dist-packages/rpyc/utils/server.py",
    line 76, in __init__
        self.listener.bind((hostname, port))
      File "/usr/lib/python2.7/socket.py", line 224, in meth
        return getattr(self._sock,name)(*args)
    socket.error: [Errno 98] Address already in use
    control@pia /usr/local/src/rpyc-3.2.2 $

    Have I done something wrong here?  I am far from an expert so it
    is quite possible I have made a stupid mistake.  I did try
    installing 3.2.0, which I have running on an Ubuntu server, but
    that gave the same problem.

    Any ideas?
    Thanks
    Mick



Reply via email to