Re: Pyro4 Flame SSH Reverse Tunneling

On 2-10-2014 15:15, Martin Lapointe wrote:
> I Have try to disable my firewall and change port for a port well know
> working because i use it on Pyro STD object but i stil have this error,
> 
> 
> Anyone have idea why not working ?
> 
> Traceback (most recent call last):
>   File "c_access.py", line 10, in <module>
>     print("remote host name=", socketmodule.gethostname())
>   File "/usr/local/lib/python2.7/dist-packages/Pyro4/core.py", line 168, in
> __call__

[snip rest of traceback]

socketmodule is a Flame remote module object, right?
It tries to connect to something that doesn't allow it (errno 111=ECONNREFUSED) so
unlike your other Pyro code that you say does work, this one uses a different location
than you think.

Find out what the difference in location is, and fix it.
You could do this by adding in your code:
  print socketmodule.flameserver
It will output something like :
<Pyro4.core.Proxy at 0x36ad230, not connected, for PYRO:Pyro.Flame@localhost:49247>
Check if the location in the URI is what it should be.

Perhaps enabling the pyro log would give you some clues as well.

Irmen


------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk