[p4perl] Problem Running P4Perl Based Triggers After Linux SystemUpdate

Scott Lavender Scott.Lavender at visiprise.com
Wed May 7 09:03:52 PDT 2008


Also, in reference to the P4PASSWD error, here is the output showing my
long term(permanent) ticket:

[root at perforce test]# p4 tickets
192.168.1.61:1666 (build) B740A553FDFAAE9A3C85DFD19485DE5F
[root at perforce test]# p4 login -s
User build ticket expires in 27727 hours 42 minutes. 

-----Original Message-----
From: Tony Smith [mailto:tony at smee.org] 
Sent: Wednesday, May 07, 2008 11:18 AM
To: p4perl at perforce.com
Cc: Scott Lavender; Nate Harney
Subject: Re: [p4perl] Problem Running P4Perl Based Triggers After Linux
SystemUpdate

Hi Scott,

Seems very odd. Can you add:

  $p4->DebugLevel( 9 );

Just before the call to Connect(), and send me the output?

Thanks,

Tony


On Friday 02 May 2008 18:48:08 Scott Lavender wrote:
> Tried a test script and ran it from the command line:
>
> ##############################################
> Script: p4test.pl
> ##############################################
> require P4;
>
> my $p4 = new P4;
> $p4->ParseForms();
> $p4->Connect or die ( "Failed to connect to Perforce Server" );
>
> # Try getting list of all Jobs
> my $jobs = $p4->Jobs();
> if ( $#jobs >= 0 )
> {
>     foreach $job ( @jobs )
>     {
>         print "$job\n";
>     }
> }
> else
> {
>     print "There are no jobs...\n";
> }
>
> # Look for warnings...
> my $warnings = $p4->Warnings();
> foreach $warning ( @warnings )
> {
>     print "\nWarnings: $warning\n\n";
> }
>
> # Look for errors...
> my $errors = $p4->Errors();
> foreach $error ( @errors )
> {
>     print "\nError: $error\n\n";
> }
>
> # Get a particular job
> my $testJob = "BuildSystem_Maint";
> my $jobHash = $p4->FetchJob( $testJob );
> print "testJob = $testJob\n";
> print "jobHash = $jobHash\n";
> print "User = $jobHash->{ 'User' }\n";
> print "Tracker = $jobHash->{ 'Tracker' }\n";
> ##############################################
>
>
> ##############################################
> Output:
> ##############################################
> There are no jobs...
> testJob = BuildSystem_Maint
> jobHash =
> User =
> Tracker =
> ##############################################
>
> ________________________________
>
> From: p4perl-bounces at perforce.com [mailto:p4perl-bounces at perforce.com]
> On Behalf Of Scott Lavender
> Sent: Friday, May 02, 2008 12:33 PM
> To: p4perl at perforce.com
> Cc: Nate Harney
> Subject: [p4perl] Problem Running P4Perl Based Triggers After Linux
> SystemUpdate
> Importance: High
>
>
> To All,
>
> We recently updated out Linux installation to the latest patch level
and
> rebooted. Now my P4Perl based trigger scripts are acting up. The
> basically all return '1'. So, none of my jab validation is working....
> ;(
>
> I'm not sure if I need to rebuild P4Perl or not. Here are some
details:
>
> *	Perforce P4D 2007.2
> *	P4API: Release 2005 2, PatchLevel = 93627, SuppUpdate = 2006 02
> 14
> *	P4Perl 3.5313
>
> Here is the list of patches applied:
>
> Apr 26 19:47:57 Installed: kernel.i686 2.6.17-1.2142_FC4
> Apr 26 19:48:35 Updated: glibc-common.i386 2.3.6-3
> Apr 26 19:48:45 Updated: glibc.i686 2.3.6-3
> Apr 26 19:48:47 Updated: popt.i386 1.10.1-23
> Apr 26 19:48:57 Updated: ncurses.i386 5.4-19.fc4
> Apr 26 19:48:59 Updated: shadow-utils.i386 2:4.0.12-8.FC4
> Apr 26 19:49:01 Updated: info.i386 4.8-8.fc4.2
> Apr 26 19:49:02 Updated: sed.i386 4.1.5-4.fc4
> Apr 26 19:49:07 Updated: xorg-x11-libs.i386 6.8.2-37.FC4.49.2.1
> Apr 26 19:49:09 Updated: db4.i386 4.3.27-5.fc4
> Apr 26 19:49:20 Updated: python.i386 2.4.3-8.FC4
> Apr 26 19:49:36 Updated: perl.i386 3:5.8.6-24
> Apr 26 19:49:36 Updated: rpm-libs.i386 4.4.1-23
> Apr 26 19:49:37 Updated: cyrus-sasl.i386 2.1.20-6
> Apr 26 19:49:38 Updated: bind-libs.i386 24:9.3.1-20.FC4
> Apr 26 19:49:38 Updated: xorg-x11-Mesa-libGL.i386 6.8.2-37.FC4.49.2.1
> Apr 26 19:49:39 Updated: procps.i386 3.2.5-6.4
> Apr 26 19:49:39 Updated: device-mapper.i386 1.02.07-2.0
> Apr 26 19:49:39 Updated: xorg-x11-Mesa-libGLU.i386 6.8.2-37.FC4.49.2.1
> Apr 26 19:49:41 Installed: libidn.i386 0.5.15-1
> Apr 26 19:49:43 Updated: glibc-headers.i386 2.3.6-3
> Apr 26 19:49:46 Updated: dhclient.i386 10:3.0.2-34.FC4
> Apr 26 19:49:46 Installed: curl.i386 7.13.1-5.fc4
> Apr 26 19:49:46 Updated: libtiff.i386 3.7.1-6.fc4.3
> Apr 26 19:49:49 Updated: bind-utils.i386 24:9.3.1-20.FC4
> Apr 26 19:49:51 Updated: rpm.i386 4.4.1-23
> Apr 26 19:49:52 Updated: libuser.i386 0.53.7-1.fc4.1
> Apr 26 19:49:55 Updated: samba-common.i386 3.0.23a-1.fc4.1
> Apr 26 19:49:55 Installed: gamin.i386 0.1.1-3.FC4
> Apr 26 19:49:58 Updated: tcsh.i386 6.14-1.fc4.2
> Apr 26 19:49:59 Updated: nscd.i386 2.3.6-3
> Apr 26 19:50:03 Updated: glibc-devel.i386 2.3.6-3
> Apr 26 19:50:06 Updated: nfs-utils.i386 1.0.7-13.FC4
> Apr 26 19:50:07 Updated: anacron.i386 2.3-36.FC4
> Apr 26 19:50:07 Updated: dhcdbd.i386 1.14-1.FC4
> Apr 26 19:50:13 Updated: samba.i386 3.0.23a-1.fc4.1
> Apr 26 19:50:14 Updated: cyrus-sasl-plain.i386 2.1.20-6
> Apr 26 19:50:14 Updated: cyrus-sasl-md5.i386 2.1.20-6
> Apr 26 19:50:18 Updated: autofs.i386 1:4.1.4-26
> Apr 26 19:50:18 Updated: rpm-python.i386 4.4.1-23
> Apr 26 19:50:19 Updated: net-tools.i386 1.60-52.fc4.2
> Apr 26 19:50:23 Updated: gnupg.i386 1.4.5-1
> Apr 26 19:50:24 Updated: authconfig.i386 4.6.12-2
> Apr 26 19:50:26 Updated: mtr.i386 2:0.71-0.FC4.1
> Apr 26 19:50:27 Updated: bind.i386 24:9.3.1-20.FC4
> Apr 26 19:50:29 Updated: lvm2.i386 2.02.06-1.0.fc4
> Apr 26 19:50:42 Installed: kernel-smp.i686 2.6.17-1.2142_FC4
> Apr 26 19:50:42 Updated: jwhois.i386 3.2.3-3.3.fc4.1
> Apr 26 19:50:43 Updated: logwatch.noarch 7.2.1-1.fc4
> Apr 26 19:50:45 Updated: sendmail.i386 8.13.7-2.fc4.2
> Apr 26 19:50:46 Updated: rsync.i386 2.6.8-1.FC4.1
> Apr 26 19:50:47 Updated: selinux-policy-targeted.noarch 1.27.1-2.28
>
> Can anyone tell me how to rebuild P4Perl? Any help would be
appreciated.
>
> Thanks.....
> Scott Lavender | SCM Specialist | Visiprise | office: 770.619.4166 |
> www.visiprise.com <http://www.visiprise.com/>
>
> It is our company policy not to accept email of any data controlled by
> the International Traffic in Arms Regulations (ITAR). Please direct
> inquiries to ITAR at visiprise.com for instructions and authorization to
> transmit such data.
>
>
>
>
> !DSPAM:481b53d668493285824817!




More information about the p4perl mailing list