[ic] Verisign PFProAPI causes segment faults

Dave nelson dave at indyweb.net
Thu Mar 2 15:48:49 EST 2006


>> >>> I'm having problems with Verisign PFProAPI. It causes Segment
>>> >>> faults. This
>> >>> happens even when I run their test.pm. I don't get any errors
>> >>> during the
>> >>> compile. Having searched the lists, I don't see any messages that
>> >>> pertain.
>> >>> Anyone has this problem? I E-mailed Verisign and they couldn't
>> >>> explain, but
>> >>> they do have a new Beta that uses an SSL connection and doe's HTTP
>> >>> POSTS.
>> >>> Sounds like it may be similar to Authorize.net or others. Anyone
>> >>> looked
>> >>> into this? I hate to have to re-invent the wheel if someone else
>> >>> has been
>> >>> down this road.
>> >>>
>> >>> I'm running 5.2.0 on Redhat 9.0 and have a few stores on this
>> >>> server. This
>> >>> store is the first with PayFlow Pro.
>> >
>> >> Have you tried placing a test order through Interchange? Just make
>> >> sure you use 'test-payflowpro.verisign.com'. I run PayflowPro, but
I
>> >> don't think I ever ran their test.pm.
>> >
>> > I have tried to run it through Interchange and it locks up
>> > Interchange.
>> > I have to restart it. That's a Major thing since I have a few stores
>> > running.
>> 
>> Maybe you should try their Java version.
>> 
>> --
>> Josh Lavin
>> Kingdom Design   http://www.kingdomdesign.com/
>> 

>I don't recommend going down that path, it was very frustrating to setup
>the java version on an alpha box.  Give the pfpro executable a try, it
>seems to work well.

Well, I tryed the Binary (pfpro) and it worked with Verisigns "test.sh" but
although
it doesn't crash IC, it doe's return an error with blank data.

errror.log entry:
"Real-time charge failed. Reason: Charge error:  Reason: . Please call in
your order or try again."

I used the same CC number and authorization as that used in Verisigns
"test.sh".

I did an strace of PFProAPI and found stuff I don't understand:

strace:
stat64("../certs/f73e89fd.0", {st_mode=S_IFREG|0755, st_size=993, ...}) = 0
open("../certs/f73e89fd.0", O_RDONLY)   = 4
fstat64(4, {st_mode=S_IFREG|0755, st_size=993, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x4001f000
read(4, "subject=/C=US/O=RSA Data Securit"..., 4096) = 993
read(4, "", 4096)                       = 0
close(4)                                = 0
munmap(0x4001f000, 4096)                = 0
stat64("../certs/f73e89fd.1", 0xbfffd2fc) = -1 ENOENT (No such file or
directory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

It seems to be trying to stat a cert file that is no-existant after it used
the the real cert file.

Thanks, for all the help on this

Dave


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 268.1.1/272 - Release Date: 3/1/2006
 



More information about the interchange-users mailing list