Broker Connection Error
Contents |
ls -lrt script.sh -rwxr-xr-x 1 user01 group001 1358 Apr 13 13:56 script.sh The section I am having trouble with is below. === script.sh === /usr/local/bin/ssh -B winuser@windowsServer001 icam login E:\mybatchfile.bat === script.sh === When I run the script as user01 it
Icam Source Connection Error
runs fine. However if as user02 I Run: sudo -H -u user01 /home/user01/script.sh I get the following SSH error: No
Icam Login Failed
such file or directory Connection error: Unable to connect to Broker Any Ideas on what is wrong? sudo broker asked Apr 13 '11 at 16:00 grahambo 1●1●1●1 edited Apr 13 '11 at
Icam Proxy
22:34 Roman ♦♦ 773●5●8●17 Hi, Does it work for user02 if you run it without sudo? Also what Tectia and OS versions are you using? (Apr 13 '11 at 22:33) Roman ♦♦ Hi, If you run the script as user02, i.e: ssh -B winuser@windowsServer001 E:mybatchfile.bat What results do you get? Thanks, James (Jun 21 '11 at 15:32) jamesw ♦♦ Be the first one to answer icam troubleshooting this question! toggle preview community wiki Follow this questionBy Email:Once you sign in you will be able to subscribe for any updates hereBy RSS: Answers Answers and Comments Markdown Basics *italic* or __italic__ **bold** or __bold__ link:[text](http://url.com/ "title") image?![alt text](/path/img.jpg "title") numbered list: 1. Foo 2. Bar to add a line break simply add two spaces to where you would like the new line to be. basic HTML tags are also supported learn more about Markdown Remember to accept the best answer by clicking on the check-mark to the left of the answer! Tags: broker ×27 sudo ×2 Asked: Apr 13 '11 at 16:00 Seen: 3,606 times Last updated: Jun 21 '11 at 15:32 All user contributed content licensed under the cc-by-sa license. Related questions Unable to connect to Broker Broker Error Pop Up SSH Tectia - Error - Failed to open a secure terminal session: What is the ssh-broker-cli process that gets started when using sshg3/sftpg3/scpg3? Public Key via ssh-keygen no ssh-broker Error running ssh-broker-ctl command Hung Broker on Z/OS broker stopping Broker error while opening subsystem Failed to open a secure terminal session: broker failure All user contributed content license
→ Administration Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. 0 Error running Perforce command! Broker connection error: failed to connect to myserver:1666 WSAEADDRINUSE Started by GeoffPate, Nov 15 http://forums.perforce.com/index.php?/topic/2165-error-running-perforce-command-broker-connection-error-failed-to-connect-to-myserver1666-wsaeaddrinuse/ 2012 11:21 AM Please log in to reply 1 reply to this topic #1 GeoffPate GeoffPate Member Members 10 posts Posted 15 November 2012 - 11:21 AM Error running Perforce command! Broker connection error: failed to connect to myserver:1666. TCP connect to myserver:1666 failed. connect: myserver:1666: WSAEADDRINUSE Has anyone ever seen this before? It looks like the broker can't create any more connections to the server? Is there a limit on the number connection error of broker connections? I can't see anything in the config file. Any idea how I can dump the current list of broker connections? Back to top #2 P4Lester P4Lester Advanced Member Members 143 posts Posted 20 November 2012 - 06:56 AM Hi Geoff, This is a general socket error code in Windows. From this MSDN article: QuoteAddress already in use. Typically, only one usage of each socket address (protocol/IP address/port) is permitted. This error broker connection error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that was not closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt (SO_REUSEADDR). Client applications usually need not call bind at all—connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf. Please contact support@perforce.com should you need more information. I work for Perforce. Workshop | Twitter | LinkedIn | about.me Back to top Back to Administration 0 user(s) are reading this topic 0 members, 0 guests, 0 anonymous users Reply to quoted postsClear Perforce Forums → Usage → Administration Privacy Policy Change Theme IP.Board Mobile Default Helix Rebrand Mark Community Read Forums Members Mark all as read Help Sign In Use Facebook Use Twitter Need an account? Register now! Username Forum Password I've forgotten my password Remember me This is not recommended for shared computers Sign in anonymously Don't add me to the active users list Privacy Policy