Jump to content


P4 login failed in Linux partner is not a Perforce client/server

p4 login

  • Please log in to reply
6 replies to this topic

#1 yinzhenping

yinzhenping

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 17 September 2018 - 07:32 AM

All p4 command report the following error:

root@samsung-PowerEdge-R710:/opt/perforce/bin# p4
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.

root@samsung-PowerEdge-R710:/opt/perforce/bin# p4 login
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
Perforce client error:
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.
        RpcTransport: partner is not a Perforce client/server.

And my P4 set is as following:

root@samsung-PowerEdge-R710:/opt/perforce/bin# p4 set
P4CHARSET=utf8 (enviro)
P4CONFIG=.p4config (config 'noconfig')
P4PORT=165.213.180.27:1667 (enviro)
P4USER=zhenping.yin (enviro)
P4_165.213.180.27:1667_CHARSET=auto (enviro)

I already confirmed, 165.213.180.27:1667 is reachable.

#2 yinzhenping

yinzhenping

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 17 September 2018 - 10:51 AM

I just want to use the p4 client in CLI mode in the ubuntu.
I download p4 program from https://www.perforce...-line-client-p4
Does it work?
How to make it work?


best regards
zhenping.yin

#3 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 664 posts

Posted 17 September 2018 - 02:44 PM

Do you have a P4D instance listening on port 165.213.180.27:1667?  The error "not a Perforce server" is meant to indicate that you've pointed your Perforce client at something else (like a web server, etc).  For example, I can reproduce that error by pointing a p4 client at the perforce.com web server:

C:\Users\Samwise>p4 -p perforce.com:80 info
Perforce client error:
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.

If I want to try to debug what exactly my p4 client is getting, I can add the -net=5 debugging flag, which shows me that sure enough it's getting an HTTP response...

C:\Users\Samwise>p4 -v net=5 -p perforce.com:80 info
NetTcpEndPoint::GetAddrInfo(port=[perforce.com]:80, family=2, flags=0x500)
<-  NetTcpEndPoint try socket(2, 1, 0, 104.20.120.51:80)
<-  NetTcpEndpoint connect on 424
<-  NetTcpTransport: enabling TCP keepalives
<-  NetTcpTransport 192.168.86.22:54278 connected to 104.20.120.51:80
NetBuffer snd 5: <c1><c1><00><00><00>
NetBuffer snd 193: cmpfile<00><00><00><00><00><00>client<00><02><00><00><00>81<00>api<00><05><00><00><00>99999<00>enableStreams<00><00><00><00><00><00>enableGraph<00><00><00><00><00><00>expandAndmaps<00><00><00><00><00><00>host<00><08><00><00><00>COMPY386<00>port<00><0f><00><00><00>perforce.com:80<00>sndbuf<00><06><00><00><00>524288<00>rcvbuf<00><06><00><00><00>524288<00>func<00><08><00><00><00>protocol<00>
NetBuffer snd 5: <9c><9c><00><00><00>
NetBuffer snd 156: prog<00><02><00><00><00>p4<00>client<00><08><00><00><00>COMPY386<00>cwd<00><10><00><00><00>c:\Users\Samwise<00>host<00><08><00><00><00>COMPY386<00>os<00><02><00><00><00>NT<00>user<00><07><00><00><00>samwise<00>charset<00><01><00><00><00>7<00>clientCase<00><01><00><00><00>1<00>func<00><0d><00><00><00>user-discover<00>
<-  NetTcpTransport send 359 bytes
<-  NetTcpTransport recv 338 bytes
NetBuffer rcv 5: HTTP/
NetBuffer rcv 5: 1.1 4
NetBuffer rcv 5: 00 Ba
NetBuffer rcv 5: d Req
NetBuffer rcv 5: uest<0d>
NetBuffer rcv 5: <0a>Date
NetBuffer rcv 5: : Mon
NetBuffer rcv 5: , 17
NetBuffer rcv 5: Sep 2
NetBuffer rcv 5: 018 1
NetBuffer rcv 5: 4:41:
NetBuffer rcv 5: 53 GM
NetBuffer rcv 5: T<0d><0a>Co
NetBuffer rcv 5: ntent
NetBuffer rcv 5: -Type
NetBuffer rcv 5: : tex
NetBuffer rcv 5: t/htm
NetBuffer rcv 5: l<0d><0a>Co
NetBuffer rcv 5: ntent
NetBuffer rcv 5: -Leng
NetBuffer rcv 5: th: 1
NetBuffer rcv 5: 71<0d><0a>C
NetBuffer rcv 5: onnec
NetBuffer rcv 5: tion:
NetBuffer rcv 5:  clos
NetBuffer rcv 5: e<0d><0a>Se
NetBuffer rcv 5: rver:
NetBuffer rcv 5:  clou
NetBuffer rcv 5: dflar
NetBuffer rcv 5: e-ngi
NetBuffer rcv 5: nx<0d><0a>C
NetBuffer rcv 5: F-RAY
NetBuffer rcv 5: : -<0d><0a>
NetBuffer rcv 5: <0d><0a><ht
NetBuffer rcv 5: ml><0d><0a>
NetBuffer rcv 5: <head
NetBuffer rcv 5: ><tit
NetBuffer rcv 5: le>40
NetBuffer rcv 5: 0 Bad
NetBuffer rcv 5:  Requ
NetBuffer rcv 5: est</
NetBuffer rcv 5: title
NetBuffer rcv 5: ></he
NetBuffer rcv 5: ad><0d><0a>
NetBuffer rcv 5: <body
NetBuffer rcv 5:  bgco
NetBuffer rcv 5: lor="
NetBuffer rcv 5: white
NetBuffer rcv 5: "><0d><0a><
NetBuffer rcv 5: cente
NetBuffer rcv 5: r><h1
NetBuffer rcv 5: >400
NetBuffer rcv 5: Bad R
NetBuffer rcv 5: eques
NetBuffer rcv 5: t</h1
NetBuffer rcv 5: ></ce
NetBuffer rcv 5: nter>
NetBuffer rcv 5: <0d><0a><hr
NetBuffer rcv 5: ><cen
NetBuffer rcv 5: ter>c
NetBuffer rcv 5: loudf
NetBuffer rcv 5: lare<
NetBuffer rcv 5: /cent
NetBuffer rcv 5: er><0d><0a>
NetBuffer rcv 5: </bod
NetBuffer rcv 5: y><0d><0a><
NetBuffer rcv 5: /html
NetBuffer flush
<-  NetTcpTransport 192.168.86.22:54278 closing 104.20.120.51:80
<-  NetTcpTransport lastRead=1
Perforce client error:
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.
		RpcTransport: partner is not a Perforce client/server.


#4 yinzhenping

yinzhenping

    Newbie

  • Members
  • Pip
  • 3 posts

Posted 18 September 2018 - 12:59 AM

Thanks for your reply.
165.213.180.27:1667 is really running  p4d.  This server is in Korea.
When I access from Korea Linux PC, it successed.  The log is as following.

yinzp@tilde-PMASB09A-Samsung-DeskTop:~$ p4 -v net=5 -p 165.213.180.27:1667 info
NetTcpEndPoint::GetAddrInfo(port=[165.213.180.27]:1667, family=2, flags=0x30)
<- NetTcpEndPoint try socket(2, 1, 6, 165.213.180.27:1667)
<- NetTcpEndpoint connect on 3
<- NetTcpTransport: enabling TCP keepalives
<- NetTcpTransport 10.251.131.102:55456 connected to 165.213.180.27:1667
NetBuffer snd 5: <00><00><00>
NetBuffer snd 193: cmpfile<00><00><00><00><00><00>client<00><02><00><00><00>84<00>api<00><05><00><00><00>99999<00>enableStreams<00><00><00><00><00><00>enableGraph<00><00><00><00><00><00>expandAndmaps<00><00><00><00><00><00>host<00><04><00><00><00>home<00>port<00><13><00><00><00>165.213.180.27:1667<00>sndbuf<00><06><00><00><00>319487<00>rcvbuf<00><06><00><00><00>319488<00>func<00><08><00><00><00>protocol<00>
NetBuffer snd 5:			 			<00><00><00>
		NetBuffer snd 221: version<00><1c><00><00><00>2018.1/LINUX26X86_64/1660568<00>autoLogin<00><00><00><00><00><00>prog<00><02><00><00><00>p4<00>client<00><0a><00><00><00>yinzp_view<00>cwd<00><0b><00><00><00>/home/yinzp<00>host<00><04><00><00><00>home<00>os<00><04><00><00><00>UNIX<00>user<00><0c><00><00><00>zhenping.yin<00>unicode<00><00><00><00><00><00>charset<00><01><00><00><00>1<00>clientCase<00><01><00><00><00>0<00>func<00><09><00><00><00>user-info<00>
		<- NetTcpTransport send 424 bytes
		<- NetTcpTransport recv 2264 bytes
		NetBuffer rcv 5: <00><00><00>
		NetBuffer rcv 180: xfiles<00><01><00><00><00>7<00>server<00><01><00><00><00>3<00>server2<00><02><00><00><00>42<00>serverID<00><06><00><00><00>nwp4d1<00>revver<00><01><00><00><00>9<00>unicode<00><01><00><00><00>1<00>tzoffset<00><05><00><00><00>32400<00>security<00><01><00><00><00>3<00>sndbuf<00><08><00><00><00>12582911<00>rcvbuf<00><08><00><00><00>12582912<00>func<00><08><00><00><00>protocol<00>
		NetBuffer rcv 5: ]]<00><00><00>
		NetBuffer rcv 93: code0<00><09><00><00><00>285219949<00>fmt0<00><11><00><00><00>User name: %user%<00>user<00><0c><00><00><00>zhenping.yin<00>func<00><0e><00><00><00>client-Message<00>
		User name: zhenping.yin
		NetBuffer rcv 5: aa<00><00><00>
		NetBuffer rcv 97: code0<00><09><00><00><00>285219951<00>fmt0<00><15><00><00><00>Client name: %client%<00>client<00><0a><00><00><00>yinzp_view<00>func<00><0e><00><00><00>client-Message<00>
		Client name: yinzp_view
		NetBuffer rcv 5: WW<00><00><00>
		NetBuffer rcv 87: code0<00><09><00><00><00>285219953<00>fmt0<00><13><00><00><00>Client host: %host%<00>host<00><04><00><00><00>home<00>func<00><0e><00><00><00>client-Message<00>
		Client host: home
		NetBuffer rcv 5: ll<00><00><00>
		NetBuffer rcv 108: code0<00><09><00><00><00>285219978<00>fmt0<00><13><00><00><00>Client root: %root%<00>root<00><19><00><00><00>/home/yinzp/workspace8400<00>func<00><0e><00><00><00>client-Message<00>
		Client root: /home/yinzp/workspace8400
		NetBuffer rcv 5: jj<00><00><00>
		NetBuffer rcv 106: code0<00><09><00><00><00>285219954<00>fmt0<00><1c><00><00><00>Current directory: %dirName%<00>dirName<00><0b><00><00><00>/home/yinzp<00>func<00><0e><00><00><00>client-Message<00>
		Current directory: /home/yinzp
		NetBuffer rcv 5: pp<00><00><00>
		NetBuffer rcv 112: code0<00><09><00><00><00>285220424<00>fmt0<00><18><00><00><00>Peer address: %peerAddr%<00>peerAddr<00><14><00><00><00>10.251.131.102:55456<00>func<00><0e><00><00><00>client-Message<00>
		Peer address: 10.251.131.102:55456
		NetBuffer rcv 5: pp<00><00><00>
		NetBuffer rcv 112: code0<00><09><00><00><00>285219955<00>fmt0<00><1c><00><00><00>Client address: %clientAddr%<00>clientAddr<00><0e><00><00><00>10.251.131.102<00>func<00><0e><00><00><00>client-Message<00>
		Client address: 10.251.131.102
		NetBuffer rcv 5: uu<00><00><00>
		NetBuffer rcv 117: code0<00><09><00><00><00>285219956<00>fmt0<00><1c><00><00><00>Server address: %serverAddr%<00>serverAddr<00><13><00><00><00>165.213.180.27:1667<00>func<00><0e><00><00><00>client-Message<00>
		Server address: 165.213.180.27:1667
		NetBuffer rcv 5: kk<00><00><00>
		NetBuffer rcv 107: code0<00><09><00><00><00>285219957<00>fmt0<00><19><00><00><00>Server root: %serverRoot%<00>serverRoot<00><0c><00><00><00>/p4/metadata<00>func<00><0e><00><00><00>client-Message<00>
		Server root: /p4/metadata
		NetBuffer rcv 5: <00><00><00>
		NetBuffer rcv 160: code0<00><09><00><00><00>301997174<00>fmt0<00>*<00><00><00>Server date: %serverDate% %serverTimeZone%<00>serverDate<00><13><00><00><00>2018/09/18 09:51:18<00>serverTimeZone<00><09><00><00><00>+0900 KST<00>func<00><0e><00><00><00>client-Message<00>
		Server date: 2018/09/18 09:51:18 +0900 KST
		NetBuffer rcv 5: aa<00><00><00>
		NetBuffer rcv 97: code0<00><09><00><00><00>285220207<00>fmt0<00><17><00><00><00>Server uptime: %uptime%<00>uptime<00><08><00><00><00>55:00:39<00>func<00><0e><00><00><00>client-Message<00>
		Server uptime: 55:00:39
		NetBuffer rcv 5: <93><93><00><00><00>
		NetBuffer rcv 147: code0<00><09><00><00><00>301997175<00>fmt0<00><1f><00><00><00>Server version: %id% (%idDate%)<00>id<00> <00><00><00>P4D/LINUX26X86_64/2016.2/1648692<00>idDate<00><0a><00><00><00>2018/04/16<00>func<00><0e><00><00><00>client-Message<00>
		Server version: P4D/LINUX26X86_64/2016.2/1648692 (2018/04/16)
		NetBuffer rcv 5: ^^<00><00><00>
		NetBuffer rcv 94: code0<00><09><00><00><00>285220438<00>fmt0<00><14><00><00><00>ServerID: %ServerID%<00>ServerID<00><06><00><00><00>nwp4d1<00>func<00><0e><00><00><00>client-Message<00>
		ServerID: nwp4d1
		NetBuffer rcv 5: xx<00><00><00>
		NetBuffer rcv 120: code0<00><09><00><00><00>285220663<00>fmt0<00>!<00><00><00>Server services: %ServerServices%<00>ServerServices<00><0d><00><00><00>commit-server<00>func<00><0e><00><00><00>client-Message<00>
		Server services: commit-server
		NetBuffer rcv 5: <00><00><00>
		NetBuffer rcv 187: code0<00><09><00><00><00>285219960<00>fmt0<00><19><00><00><00>Server license: %license%<00>license<00>_<00><00><00>Samsung Electronics Network Division 2100 users (support ends 2019/09/15) (expires 2019/06/01) <00>func<00><0e><00><00><00>client-Message<00>
		Server license: Samsung Electronics Network Division 2100 users (support ends 2019/09/15) (expires 2019/06/01)
		NetBuffer rcv 5: vv<00><00><00>
		NetBuffer rcv 118: code0<00><09><00><00><00>285220222<00>fmt0<00><1e><00><00><00>Server license-ip: %licenseIp%<00>licenseIp<00><13><00><00><00>165.213.180.27:1667<00>func<00><0e><00><00><00>client-Message<00>
		Server license-ip: 165.213.180.27:1667
		NetBuffer rcv 5: nn<00><00><00>
		NetBuffer rcv 110: code0<00><09><00><00><00>285220266<00>fmt0<00><1d><00><00><00>Case Handling: %caseHandling%<00>caseHandling<00><09><00><00><00>sensitive<00>func<00><0e><00><00><00>client-Message<00>
		Case Handling: sensitive
		NetBuffer rcv 5: <11><11><00><00><00>
		NetBuffer rcv 17: func<00><07><00><00><00>release<00>
		NetBuffer snd 5: <12><12><00><00><00>
		NetBuffer snd 18: func<00><08><00><00><00>release2<00>
		NetBuffer flush
		<- NetTcpTransport send 23 bytes
		<- NetTcpTransport 10.251.131.102:55456 closing 165.213.180.27:1667
		<- NetTcpTransport lastRead=0
		tcp info: retransmits 0 probes 0 backoff 0
		options timestamps sack wscale
		sscale 11 rscale 2
		rto 204000 ato 40000 snd_mss 1448 rcv_mss 1448
		unacked 1 sacked 0 lost 0 retrans 0 fackets 0
		last_data_sent 0 last_data_recv 8 last_ack_recv 16
		pmtu 1500 rcv_ssthresh 33728 rtt 293 rttvar 120
		snd_ssthresh 2147483647 snd_cwnd 10 advmss 1448 reordering 3
		yinzp@tilde-PMASB09A-Samsung-DeskTop:~$ 

But When I want to access this server from Beijing.  the following Error Occurs:
root@samsung-PowerEdge-R710:~# p4 -v net=5 -p 165.213.180.27:1667 info
NetTcpEndPoint::GetAddrInfo(port=[165.213.180.27]:1667, family=2, flags=0x30)
<- NetTcpEndPoint try socket(2, 1, 6, 165.213.180.27:1667)
<- NetTcpEndpoint connect on 3
<- NetTcpTransport: enabling TCP keepalives
<- NetTcpTransport 109.105.46.96:49586 connected to 165.213.180.27:1667
NetBuffer snd 5: <00><00><00>
NetBuffer snd 193: cmpfile<00><00><00><00><00><00>client<00><02><00><00><00>84<00>api<00><05><00><00><00>99999<00>enableStreams<00><00><00><00><00><00>enableGraph<00><00><00><00><00><00>expandAndmaps<00><00><00><00><00><00>host<00><04><00><00><00>home<00>port<00><13><00><00><00>165.213.180.27:1667<00>sndbuf<00><06><00><00><00>319487<00>rcvbuf<00><06><00><00><00>319488<00>func<00><08><00><00><00>protocol<00>
NetBuffer snd 5: <00><00><00>
NetBuffer snd 215: version<00><1c><00><00><00>2018.1/LINUX26X86_64/1660568<00>autoLogin<00><00><00><00><00><00>prog<00><02><00><00><00>p4<00>client<00><0a><00><00><00>yinzp_view<00>cwd<00><05><00><00><00>/root<00>host<00><04><00><00><00>home<00>os<00><04><00><00><00>UNIX<00>user<00><0c><00><00><00>zhenping.yin<00>unicode<00><00><00><00><00><00>charset<00><01><00><00><00>1<00>clientCase<00><01><00><00><00>0<00>func<00><09><00><00><00>user-info<00>
<- NetTcpTransport send 418 bytes
<- NetTcpTransport recv 73 bytes
NetBuffer rcv 5: Scrip
NetBuffer rcv 5: t><0d><0a>d
NetBuffer rcv 5: ocume
NetBuffer rcv 5: nt.lo
NetBuffer rcv 5: catio
NetBuffer rcv 5: n.hre
NetBuffer rcv 5: f = "
NetBuffer rcv 5: http:
NetBuffer rcv 5: //109
NetBuffer rcv 5: .10.1
NetBuffer rcv 5: .229:
NetBuffer rcv 5: 8080/
NetBuffer rcv 5: ";<0d><0a><
NetBuffer rcv 5: /Scri
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
NetBuffer flush
<- NetTcpTransport 109.105.46.96:49586 closing 165.213.180.27:1667
<- NetTcpTransport lastRead=1
tcp info: retransmits 0 probes 0 backoff 0
options timestamps sack wscale
sscale 2 rscale 2
rto 236000 ato 40000 snd_mss 1448 rcv_mss 536
unacked 0 sacked 0 lost 0 retrans 0 fackets 0
last_data_sent 0 last_data_recv 0 last_ack_recv 0
pmtu 1500 rcv_ssthresh 29200 rtt 35008 rttvar 20587
snd_ssthresh 2147483647 snd_cwnd 10 advmss 1448 reordering 3
t/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport懭Perforce client error:
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.
RpcTransport: partner is not a Perforce client/server.

I don't know why it response me with an http address http://109.10.1 .229: 8080/

Can you give me some advice ?
Thanks a lot~~
yin zhenping

#5 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 664 posts

Posted 18 September 2018 - 03:48 AM

Script><0d><0a>document.location.href = "http://109.10.1.229:8080/";<0d><0a></Scri

That's a Javascript redirect. Maybe an HTTP proxy trying to route you to a web server on that machine (which isn't working because your client isn't a web browser and the server isn't a web server)?  I recommend asking your local IT people for help.

#6 Zerner254

Zerner254

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 04 October 2018 - 07:45 AM

I am creating a p4 stream from the CLI without having to open the editor, But, none of the tricks are working for me. My goal here is to alias 'p4 stream -P <current stream> -t task <generated dev task branch name>' that doesn't require editing the stream spec file at all. How to do it? Mobdro Please help

#7 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 664 posts

Posted 04 October 2018 - 03:29 PM

p4 stream -P <current stream> -t task -o <new stream name>| p4 stream -i

should do it.





Also tagged with one or more of these keywords: p4 login

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users