Slide 1
Most trusted JOB oriented professional program
DevOps Certified Professional (DCP)

Take your first step into the world of DevOps with this course, which will help you to learn about the methodologies and tools used to develop, deploy, and operate high-quality software.

Slide 2
DevOps to DevSecOps – Learn the evolution
DevSecOps Certified Professional (DSOCP)

Learn to automate security into a fast-paced DevOps environment using various open-source tools and scripts.

Slide 2
Get certified in the new tech skill to rule the industry
Site Reliability Engineering (SRE) Certified Professional

A method of measuring and achieving reliability through engineering and operations work – developed by Google to manage services.

Slide 2
Master the art of DevOps
Master in DevOps Engineering (MDE)

Get enrolled for the most advanced and only course in the WORLD which can make you an expert and proficient Architect in DevOps, DevSecOps and Site Reliability Engineering (SRE) principles together.

Slide 2
Gain expertise and certified yourself
Azure DevOps Solutions Expert

Learn about the DevOps services available on Azure and how you can use them to make your workflow more efficient.

Slide 3
Learn and get certified
AWS Certified DevOps Professional

Learn about the DevOps services offered by AWS and how you can use them to make your workflow more efficient.

previous arrow
next arrow

Some Common Perforce Error

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 perforce server is not able to receive or sent data packets to each other. This can be due to various reason.
Check following…

1. Fix this file ownership problem of the repository. It should be same user by which p4d services has been re-started.
2. Please check network issues.

Problem

Perforce client error:
RpcTransport: partial message read
TCP receive failed.
read: socket: Connection reset by peer”

Solutions:
Connection 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).

More Info can be found in
kb.perforce.com/article/410/wsaeconnreset-error-description

Perforce client error:

TO BE WRITTEN

RpcTransport: partial message read

TO BE WRITTEN

TCP receive failed.

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.

read: socket: WSAECONNABORTED

TO BE WRITTEN

error: read: socket: Connection reset by peer

TO BE WRITTEN

Perforce command exited abnormally with error code 1!

TO BE WRITTEN

Partner exited unexpectedly.

TO BE WRITTEN

WSAECONNABORTED or WSAECONNREFUSED or WSAETIMEDOUT Error

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

Unicode server permits only unicode enabled clients.

TO BE WRITTEN

Problem
RpcTransport: partial message read
TCP receive failed.
read: socket: WSAECONNABORTED
Perforce::executePerforceCommand – Perforce command exited abnormally with error code 1!
error: RpcTransport: partial message read

Solution
1. Check if you have DOt extention files. Windows does not support “DOT” extension files so it could be releated to this.
2. Network drop out for few second may also cause issues.

Problem:
An issue with older Perforce Windows clients with an artificially low send window size would appear as:
rpc send receive errors, duplexing F/R 1249/0 in perforce.log

Solution: Clients need to be upgdraded

Problem: protected namespace – access denied

This means user is not assigned with access to the perforce or specific depot path

Error –
Large files integration using p4v somtime givs following error.
Error in change specification.
Can’t include file(s) not already opened.
Open new files with p4 add, p4 edit, etc.

Solution:
Post integration, you just fetch the changelist number and run over the command line.
p4 submit -c #changelost

or

try integrating using new clientspec

Error –
RpcTransport: partial message read
TCP receive exceeded maximum configured duration of 300 seconds.\

Solution:
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

rajeshkumar replied the topic: Some Common Perforce Error
Journal record replay failed!
perforce@perforce:~/1/logs$ more checkpoint.log
Fri Jul 4 03:00:02 PDT 2014 : Start p4_1 Checkpoint
Fri Jul 4 03:00:02 PDT 2014 : Truncating journal…
Rotating /p4/1/logs/journal to /p4/1/checkpoints/p4_1.jnl.5453…

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

real 77m30.886s
user 0m0.828s
sys 0m19.789s
Fri Jul 4 04:17:33 PDT 2014 : Journal replay failed. Abort!

Answer
You’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.

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).

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:

p4d -r offline_P4ROOT -xx

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.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Rajesh Kumar
0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x