NuSphere Forums Forum Index
NuSphere Forums
Reply to topic
how to use dbg via ssh?


Joined: 13 Jun 2004
Posts: 4
Reply with quote
Hi, all:

I am sorry that I have to ask this question since I could not figure it out even though I have found there are some posts related to my question, such as http://forum.nusphere.com/tip-troubleshooting-debugger-communications-t579.html and http://forum.nusphere.com/tip-troubleshooting-debugger-communications-ssh-t581.html

Let's give you the detailed information.

I have dbg 2.11.23 installed on a redhat 9 server by loading dbg.so-4.2.2 since my php version is 4.2.2.

The [Debugger] section in php.ini is the following:
[Debugger]
debugger.enabled = on
debugger.profiler_enabled = on
debugger.hosts_allow = localhost
debugger.hosts_deny = all
debugger.ports = 7869

I have added port 7869 in /etc/ssh/sshd_config and restart sshd.
$ netstat -na | grep 7869
tcp 0 0 0.0.0.0:7869 0.0.0.0:* LISTEN

I have dbg 2.11.23 client installed on a windows XP Pro machine.

When I tried to create a ssh tunnal I got:
c:\ssh -R 7869:localhost:7869 myname@myhost
Warning: remote port forwarding failed for listen port 7869
$

When I tried to :
$ telnet localhost 7869
Trying 127.0.0.1...
Connected to mywebserver (127.0.0.1).
Escape character is '^]'.
SSH-1.99-OpenSSH_3.5p1

The dbg listener running on my XP did not receive any signal.

When I tried to:
$telnet myxphostname 7869
The dbg listener got the signal (the dbg listener icon was changed ) but failed to complete the connection after a long time.


Please note, I only masked my username, hostname, and domain name.
I didn't mask something by "localhost", which means the key work "localhost" was used exactly above. Honestly, I am confused by the "localhost" keyword presented in the posts I found.

Please help me to fix my problem. I really want to let dbg work via ssh in my work environment.

If you think providing more information would be helpful, please just let me know and I will be very happy to do that.

Many thanks in advance and look forward to hearing from you soon.


JX
View user's profileFind all posts by athinkerSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 7881
Reply with quote
Warning: remote port forwarding failed for listen port 7869 means that port is probably in use on the server or is bound and therefore can't be forwarded.
View user's profileFind all posts by dmitriSend private messageVisit poster's website


Joined: 13 Jun 2004
Posts: 4
Reply with quote
Thank you. I guess so.

Could you please help me to fix it?

Many thanks again.

JX
View user's profileFind all posts by athinkerSend private message
Site Admin

Joined: 13 Jul 2003
Posts: 7881
Reply with quote
run netstat -nao from the server console and make sure that port 7869 is not in use.
View user's profileFind all posts by dmitriSend private messageVisit poster's website


Joined: 04 Dec 2003
Posts: 27
Location: Portland, OR
Reply with quote
athinker wrote:
Thank you. I guess so.

Could you please help me to fix it?

Many thanks again.

JX


You don't want to add 7869 to sshd_config .. that just means that sshd will listen for ssh connections on that port. Pull that out and *then* initiate the tunnel. The tunnel exists on its own, unrelated to sshd_config or listen ports.
View user's profileFind all posts by SigneSend private messageVisit poster's websiteAIM AddressYahoo MessengerMSN MessengerICQ Number
Site Admin

Joined: 13 Jul 2003
Posts: 7881
Reply with quote
oh, clear.
I overlooked these words:
Quote:
...I have added port 7869 in /etc/ssh/sshd_config and restart sshd

sure, 7869 should not be added to sshd_config...
View user's profileFind all posts by dmitriSend private messageVisit poster's website
how to use dbg via ssh?
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT - 5 Hours  
Page 1 of 1  

  
  
 Reply to topic