Skip Menu |

This queue is for tickets about the metabase-relayd CPAN distribution.

Report information
The Basics
Id: 59436
Status: open
Priority: 0/
Queue: metabase-relayd

People
Owner: Nobody in particular
Requestors: njh [...] bandsman.co.uk
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.18
Fixed in: (no value)



Subject: Failed to send
I have seen this message: "Client '16' failed to send parsable data!" 1) What's this mean? 2) How do I fix it? 3) Will it retry the send? 4) If not and I retry will the client inform me (incorrectly, since it was never sent) that it's a duplicate report and fail to send?
Subject: Re: [rt.cpan.org #59436] Failed to send
Date: Fri, 16 Jul 2010 15:50:00 +0100
To: "njh [...] bandsman.co.uk via RT" <bug-metabase-relayd [...] rt.cpan.org>
From: "Chris 'BinGOs' Williams" <chris [...] bingosnet.co.uk>
On Fri, Jul 16, 2010 at 05:53:44AM -0400, njh@bandsman.co.uk via RT wrote: Show quoted text
> Fri Jul 16 05:53:44 2010: Request 59436 was acted upon. > > I have seen this message: "Client '16' failed to send parsable data!" > > 1) What's this mean?
It is generated by POE::Component::Metabase::Relay::Server when a client disconnects and hasn't sent any valid data to the server. We use Storable::thaw unfreeze the data and then check that it a). exists; b). is a reference; c). it is a hash reference; Show quoted text
> 2) How do I fix it?
It could well be an incompatibility between the Storable on the relay versus the Storable on the smoker. I tend to update Storable on my smokers to the latest version ( I was doing this before metabase anyways ). Check the Storable versions. Show quoted text
> 3) Will it retry the send?
No. It received nothing valid that it could send to metabase. Test::Reporter::Transport::Socket has no retransmission mechanism. Show quoted text
> 4) If not and I retry will the client inform me (incorrectly, since it > was never sent) that it's a duplicate report and fail to send? >
Nothing was received by the relay to convert to a Metabase::Fact and then submitted to the metabase so there won't be an duplicate reports. --- Thanks for ticket. -- Chris Williams aka BinGOs PGP ID 0x4658671F http://www.gumbynet.org.uk ==========================
Download (untitled)
application/pgp-signature 189b

Message body not shown because it is not plain text.

Subject: Re: [rt.cpan.org #59436] Failed to send
Date: Fri, 16 Jul 2010 18:13:27 +0100
To: bug-metabase-relayd [...] rt.cpan.org
From: Nigel Horne <njh [...] bandsman.co.uk>
Show quoted text
>> 2) How do I fix it? >>
> It could well be an incompatibility between the Storable on the relay > versus the Storable on the smoker. I tend to update Storable on my > smokers to the latest version ( I was doing this before metabase anyways ). > > Check the Storable versions. >
I am using 2.21 on both machines. -Nigel
From: njh [...] bandsman.co.uk
It just happened again. Rather annoying this because it was after a 90 minute build on a slow emulated machine. Anyway, that's beside the point, I got an extra message: Client '577' failed to send parsable data! The error from Storable::thaw was ''
From: njh [...] bandsman.co.uk
It seems to happen more often when the client is not an Intel type CPU. Perhaps there is an endianism problem in the network data transfer? Client '10' failed to send parsable data! The error from Storable::thaw was '' Submit '3jHoCXmy3xGp3cEIWN5c/w==' (1.30392909049988s) success Client '14' failed to send parsable data! The error from Storable::thaw was '
From: njh [...] bandsman.co.uk
On Sat Aug 28 05:58:24 2010, njh@bandsman.co.uk wrote: Show quoted text
> It seems to happen more often when the client is not an Intel type CPU. > Perhaps there is an endianism problem in the network data transfer?
Yes - I can add more to back this up. It happens mostly (perhaps exclusively) when the client is a MIPS machine running NetBSD. (MIPS on Linux is OK, as is NetBSD on other architectures). Client '1262' failed to send parsable data! The error from Storable::thaw was ''
From: njh [...] bandsman.co.uk
I just did a "make test" on Storable 2.21 on a MIPS NetBSD machine and got this error: # Failed test (t/downgrade.t at line 225) # got: 4.4501477170144e-308 # expected: 0 # Failed test (t/downgrade.t at line 234) # got: 4.4501477170144e-308 # expected: 0 # Looks like you failed 2 tests of 169. t/downgrade.t ......... Dubious, test returned 2 (wstat 512, 0x200) Failed 2/169 subtests Now that shouldn't matter (something isn't rounding floating point numbers correctly), but I do wonder about knock on effects if the code isn't correctly checking floating point numbers.
From: njh [...] bandsman.co.uk
Do you use Storable's nstore feature?
Subject: Re: [rt.cpan.org #59436] Failed to send
Date: Tue, 14 Sep 2010 19:47:39 +0100
To: "njh [...] bandsman.co.uk via RT" <bug-metabase-relayd [...] rt.cpan.org>
From: "Chris 'BinGOs' Williams" <chris [...] bingosnet.co.uk>
On Tue, Sep 14, 2010 at 06:09:07AM -0400, njh@bandsman.co.uk via RT wrote: Show quoted text
> Queue: metabase-relayd > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=59436 > > > Do you use Storable's nstore feature? >
Yes I do. -- Chris Williams aka BinGOs PGP ID 0x4658671F http://www.gumbynet.org.uk ==========================
Download (untitled)
application/pgp-signature 189b

Message body not shown because it is not plain text.

From: njh [...] bandsman.co.uk
Client '4' failed to send parsable data! The error from Storable::thaw was 'Storable binary image v40.85 more recent than I am (v2.7) at blib/lib/Storable.pm (autosplit into blib/lib/auto/Storable/thaw.al) line 415, at /usr/local/share/perl/5.10.1/POE/Component/Metabase/Relay/Server.pm line 254 '
From: njh [...] bandsman.co.uk
The latest update seems to have fixed it. Please close.
From: njh [...] bandsman.co.uk
I may have spoken too early. I've not tried a machine recently which showed the symptoms. I've just tried it and it's still failing: Client '662' failed to send parsable data! The error from Storable::thaw was ''