{"id":1566,"date":"2017-12-04T12:21:02","date_gmt":"2017-12-04T12:21:02","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/?p=1566"},"modified":"2025-02-01T22:39:40","modified_gmt":"2025-02-01T22:39:40","slug":"some-common-perforce-error","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/some-common-perforce-error\/","title":{"rendered":"Some Common Perforce Error"},"content":{"rendered":"

rajeshkumar created the topic: Some Common Perforce Error<\/strong>
\nProblem:<\/p>\n

Perforce client error:
\nTCP send failed.
\nwrite: socket: Connection reset by peer<\/p>\n

Solutions:
\nThese issues occur only when perforce client and perforce server is not able to receive or sent data packets to each other. This can be due to various reason.
\nCheck following…<\/p>\n

1. Fix this file ownership problem of the repository. It should be same user by which p4d services has been re-started.
\n2. Please check network issues.<\/p>\n

Problem<\/p>\n

Perforce client error:
\nRpcTransport: partial message read
\nTCP receive failed.
\nread: socket: Connection reset by peer”<\/p>\n

Solutions:
\nConnection reset be peer” generally suggests a network issue. this could be due to either misconfigured or faulty network hardware. OR An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket).<\/p>\n

More Info can be found in
\nkb.perforce.com\/article\/410\/wsaeconnreset-error-description <\/a><\/p>\n

Perforce client error:<\/p>\n

TO BE WRITTEN<\/p>\n

RpcTransport: partial message read<\/p>\n

TO BE WRITTEN<\/p>\n

TCP receive failed.<\/p>\n

The TCP errors indicate that of something being killed on the server( may be some triggers\/ network issues \/ process \/ jobs \/ services and hence the connection to your client drops.<\/p>\n

read: socket: WSAECONNABORTED<\/p>\n

TO BE WRITTEN<\/p>\n

error: read: socket: Connection reset by peer<\/p>\n

TO BE WRITTEN<\/p>\n

Perforce command exited abnormally with error code 1!<\/p>\n

TO BE WRITTEN<\/p>\n

Partner exited unexpectedly.<\/p>\n

TO BE WRITTEN<\/p>\n

WSAECONNABORTED or WSAECONNREFUSED or WSAETIMEDOUT Error<\/p>\n

This kind of error occur on Windows systems due to some network issues. to bebug more, please refer following url..
\nkb.perforce.com\/article\/905\/common-windo…erver-network-errors <\/a>
\nwww.scmgalaxy.com\/perforce\/perforce-netw…eshooting-hints.html <\/a>
\nkb.perforce.com\/article\/410\/wsaeconnreset-error-description <\/a><\/p>\n

Unicode server permits only unicode enabled clients.<\/p>\n

TO BE WRITTEN<\/p>\n

Problem
\nRpcTransport: partial message read
\nTCP receive failed.
\nread: socket: WSAECONNABORTED
\nPerforce::executePerforceCommand – Perforce command exited abnormally with error code 1!
\nerror: RpcTransport: partial message read<\/p>\n

Solution
\n1. Check if you have DOt extention files. Windows does not support \u201cDOT\u201d extension files so it could be releated to this.
\n2. Network drop out for few second may also cause issues.<\/p>\n

Problem:
\nAn issue with older Perforce Windows clients with an artificially low send window size would appear as:
\nrpc send receive errors, duplexing F\/R 1249\/0 in perforce.log<\/p>\n

Solution: Clients need to be upgdraded<\/p>\n

Problem: protected namespace – access denied<\/p>\n

This means user is not assigned with access to the perforce or specific depot path<\/p>\n

Error –
\nLarge files integration using p4v somtime givs following error.
\nError in change specification.
\nCan’t include file(s) not already opened.
\nOpen new files with p4 add, p4 edit, etc.<\/p>\n

Solution:
\nPost integration, you just fetch the changelist number and run over the command line.
\np4 submit -c #changelost<\/p>\n

or<\/p>\n

try integrating using new clientspec<\/p>\n

Error –
\nRpcTransport: partial message read
\nTCP receive exceeded maximum configured duration of 300 seconds.\\<\/p>\n

Solution:
\nRegards,
\nRajesh Kumar
\nTwitt me @ twitter.com\/RajeshKumarIn<\/a><\/p>\n

rajeshkumar replied the topic: Some Common Perforce Error<\/strong>
\nJournal record replay failed!
\nperforce@perforce:~\/1\/logs$ more checkpoint.log
\nFri Jul 4 03:00:02 PDT 2014 : Start p4_1 Checkpoint
\nFri Jul 4 03:00:02 PDT 2014 : Truncating journal…
\nRotating \/p4\/1\/logs\/journal to \/p4\/1\/checkpoints\/p4_1.jnl.5453…<\/p>\n

real 0m0.180s
\nuser 0m0.000s
\nsys 0m0.020s
\nFri Jul 4 03:00:03 PDT 2014 : Replay journal to offline db.
\nRecovering from \/p4\/1\/checkpoints\/p4_1.jnl.5453…
\nFri Jul 4 04:17:09 PDT 2014 : Recreate offline db files for quick recovery process.
\nPerforce db files in ‘\/p4\/1\/offline_db’ will be created if missing…
\nRecovering from \/p4\/1\/checkpoints\/p4_1.ckp.5453.gz…
\nPerforce server error:
\nJournal file ‘\/p4\/1\/checkpoints\/p4_1.jnl.5453’ replay failed at line 216307!
\nJournal record replay failed!
\nIn table db.desc, the following row was not present or could not be deleted. It may be possible to use the
\n‘-f’ flag to proceed beyond this point. Row data: “1253455 @@ ”<\/p>\n

real 77m30.886s
\nuser 0m0.828s
\nsys 0m19.789s
\nFri Jul 4 04:17:33 PDT 2014 : Journal replay failed. Abort!<\/p>\n

Answer
\nYou’re getting this error because Perforce is trying to replay a @dv@ line (a database record to delete) when the expected database record is not present in the current state of the database that has been replayed so far.<\/p>\n

Usually this is not necessary an issue as the end result is for this record not to be present in your database and as mentioned in the error, you can replay the journal using the -f flag (e,g, p4d -r offline_P4ROOT -jr -f \/p4\/1\/checkpoints\/p4_1.jnl.5453).<\/p>\n

Although this error is not serious, it is not expected and I would like to check the integrity of your database from a logical database point of view. Could you run the following command:<\/p>\n

p4d -r offline_P4ROOT -xx<\/p>\n

Send the command output and the jnl.fix it will produce. Also send me line 216307 (a db.desc record) of \/p4\/1\/checkpoints\/p4_1.jnl.5453 for review.
\nRegards,
\nRajesh Kumar
\nTwitt me @ twitter.com\/RajeshKumarIn<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

rajeshkumar created the topic: Some Common Perforce Error Problem: Perforce client error: TCP send failed. write: socket: Connection reset by peer Solutions: These issues occur only when perforce client and… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[370],"tags":[373],"class_list":["post-1566","post","type-post","status-publish","format-standard","hentry","category-perforce","tag-perforce"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/1566","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=1566"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/1566\/revisions"}],"predecessor-version":[{"id":1567,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/1566\/revisions\/1567"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=1566"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=1566"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=1566"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}