List Info

Thread: admin checkpoint aborted?




admin checkpoint aborted?
user name
2006-07-19 16:13:05
I'm new to p4 and am taking over the backups for an
existing p4
depot. What does it mean:

/usr/local/bin/p4 -u USER -p HOST:1666 admin checkpoint
script.sh: line 22: 31219 Aborted                 $P4 admin
checkpoint

The command is on line 22 of script.sh and the PID is 31219.
Why
would a checkpoint abort?

I ran the command again and the unix return code is 134.
Does that
number mean anything?

Mike
_______________________________________________
p4perl mailing list
p4perlperforce.com

http://maillist.perforce.com/mailman/listinfo/p4perl
admin checkpoint aborted?
user name
2006-07-20 07:46:25
On Wednesday 19 July 2006 17:13, Mike wrote:
> I'm new to p4 and am taking over the backups for an
existing p4
> depot. What does it mean:
>
> /usr/local/bin/p4 -u USER -p HOST:1666 admin checkpoint
> script.sh: line 22: 31219 Aborted                 $P4
admin checkpoint
>
> The command is on line 22 of script.sh and the PID is
31219. Why
> would a checkpoint abort?

I don't know, but it looks like the p4 process exited with
a SIGABRT, and 
that's not good. Try running the command manually (not
through a script) and 
see if it still fails. If so, you should log a call with
Perforce technical 
support on this one, it may take some digging to resolve.

> I ran the command again and the unix return code is
134. Does that
> number mean anything?

Yes. 134 = 0x86. On my Linux box, the macro
WIFSIGNALED(status) is defined 
thus  ((status) & 0x7f). 

	0x86 & 0x7f = 0x06

'kill -l' says signal number 6 is SIGABRT. So, it just
means that the command 
aborted (which we already knew because the shell told us
so).

Tony
_______________________________________________
p4perl mailing list
p4perlperforce.com

http://maillist.perforce.com/mailman/listinfo/p4perl
[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )