[Pvfs2-developers] protocol fomat mismatch causes server segfault

Kyle Schochenmaier kschoche at scl.ameslab.gov
Wed May 9 15:59:55 EDT 2007


Backtrace:

[S 05/09 15:00] PVFS2 Server version 2.7.0pre1-2007-04-21-220052 starting...
[New Thread 1082132832 (LWP 11300)]
[New Thread 1090525536 (LWP 11301)]
[New Thread 1098918240 (LWP 11302)]
[S 05/09 15:00] PVFS2 Server ready.
[E 15:00:24.742773] Error: poorly formatted protocol message received.
[E 15:00:24.742819]    Protocol version mismatch: received major version 
3 when expecting 4.
[E 15:00:24.742829]    Please verify your PVFS2 installation and make 
sure that the version is
   consistent.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47207450763200 (LWP 11297)]
0x00000000004112c9 in server_state_machine_start ()
(gdb) bt
#0  0x00000000004112c9 in server_state_machine_start ()
#1  0x0000000000462148 in unexpected_map ()
#2  0x000000000044ca5c in PINT_state_machine_invoke ()
#3  0x000000000044c70f in PINT_state_machine_next ()
#4  0x000000000044cdae in PINT_state_machine_continue ()
#5  0x0000000000410feb in main ()

And I believe the state/op from my debug file is '28', if thats at all 
helpful.


Kyle

Sam Lang wrote:
>
> On Apr 24, 2007, at 1:41 PM, Kyle Schochenmaier wrote:
>
>> Is there a reason why this is a 'fatal' error?  I forgot to add the 
>> new install to my path, and was therefore using an old version of 
>> pvfs2-ls, which also caused my MD server to segfault.
>
> Hi Kyle,
>
> Sorry for the delayed response.  Do you know where the segfault is in 
> the server?  A backtrace would be helpful.
>
>>
>> I think we could do a workaround on this to make it still error, but 
>> not segfault.
>>
>> The text is also goofy on this last message..
>> (if someone wants to fix it:  line 203: 
>> src/proto/PINT-reqproto-encode.c, it has an extra \n in there)
>
> Ok.  Committed a fix for this.
>
> -sam
>>
>> [D 12:17:27.501391] PVFS2 Server version 2.7.0pre1-2007-04-21-220052 
>> starting.
>> [E 12:33:58.987667] Error: poorly formatted protocol message received.
>> [E 12:33:58.987707]    Protocol version mismatch: received major 
>> version 3 when
>> expecting 4.
>> [E 12:33:58.987716]    Please verify your PVFS2 installation and make 
>> sure that
>> the version is
>>   consistent.
>>
>> _______________________________________________
>> Pvfs2-developers mailing list
>> Pvfs2-developers at beowulf-underground.org
>> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
>>
>
>
> !DSPAM:46409810259569439013359!
>


-- 
Kyle Schochenmaier
kschoche at scl.ameslab.gov
Research Assistant, Dr. Brett Bode
AmesLab - US Dept.Energy
Scalable Computing Laboratory 



More information about the Pvfs2-developers mailing list