make smoke
Gerd Pokorra
"make smolder_test" stops with:
TAP Archive created
at /home/gz016/parrot-sources/smolder.test/parrot_test_run.tar.gz
Could not upload report to Smolder at http://smolder.plusthree.com
HTTP CODE: 500 (read timeout)
make: *** [smolder_test] Fehler 255
[gz016@hilton smolder.test]$
-- Gerd
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
Michael Hind
I am getting this fairly consistently now.
The report is sent to the server and before it has completed processing the report it reaches the timeout and returns the 500 error, but continues processing the report and usually completes.
If you check the site, (a couple of minutes later), you will find that the report is then there.
http://smolder.plusthree.com/app/projects/smoke_reports/8
We had this problem a week or so ago, and I think the timeout was adjusted, but, either the site is busier, or the timeout reverted, and this has happened with most of my smoke reports in the last week.
Cheers, Michael (mikehh)
Michael H. Hind
Tel: +44 (0) 1224 631 581
Cell: +44 (0) 7877 224 745
Michael Peters
> We had this problem a week or so ago, and I think the timeout was
> adjusted, but, either the site is busier, or the timeout reverted, and
> this has happened with most of my smoke reports in the last week.
> Cheers, Michael (mikehh)
I do apologize for this. That smolder server is seeing a lot more
traffic and processing a lot more reports than it did in the beginning,
so it's starting to show.
--
Michael Peters
Plus Three, LP
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
Will Coleda
> On 02/04/2010 05:14 AM, Michael Hind wrote:
>
>> We had this problem a week or so ago, and I think the timeout was
>> adjusted, but, either the site is busier, or the timeout reverted, and
>> this has happened with most of my smoke reports in the last week.
>> Cheers, Michael (mikehh)
>
> I do apologize for this. That smolder server is seeing a lot more traffic
> and processing a lot more reports than it did in the beginning, so it's
> starting to show.
Perhaps now would be a good time to reconsider hosting it somewhere on
parrot.org?
> --
> Michael Peters
> Plus Three, LP
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>
--
Will "Coke" Coleda
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
Michael Peters
> Perhaps now would be a good time to reconsider hosting it somewhere on
> parrot.org?
That's not a bad idea. To set up a new install would be really easy.
Migrating the historical data is a little trickier, but not too bad
(smolder really needs an export/import system, but that's for another day).
Will Coleda
> On 02/04/2010 10:36 AM, Will Coleda wrote:
>
>> Perhaps now would be a good time to reconsider hosting it somewhere on
>> parrot.org?
>
> That's not a bad idea. To set up a new install would be really easy.
> Migrating the historical data is a little trickier, but not too bad (smolder
> really needs an export/import system, but that's for another day).
>
> --
> Michael Peters
> Plus Three, LP
>
The historical data has a short shelf life, IMO. If you can write up
what it would take to setup on a parrot.org server (with or without
the history copy), I can work with our hosting folks.
Michael Peters
> The historical data has a short shelf life, IMO. If you can write up
> what it would take to setup on a parrot.org server (with or without
> the history copy), I can work with our hosting folks.
cpan> install Smolder
Now create an /etc/smolder.conf (I can help if they have questions about
how to configure it). Then login with the default admin user (change
it's password after login), create the Parrot project (and any other
projects you want to move over too like Cardinal, etc), setup any users
you want, and then change the source code of Parrot to submit to the new
URL.
--
Michael Peters
Plus Three, LP
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
Will Coleda
<michael...@gmail.com> wrote:
> On 02/04/2010 10:49 AM, Michael Peters wrote:
>
>>> The historical data has a short shelf life, IMO. If you can write up
>>> what it would take to setup on a parrot.org server (with or without
>>> the history copy),
>
> sqlite database with any non-parrot stuff removed which you'll put in place
> of the one that smolder creates when installed. Then I'll need to create a
> tarball of the TAP archives, and HTML rendered reports for Parrot related
> stuff that they will need to unpack in the new smolder's data directory.
>
> --
> Michael Peters
>
Let's take a poll - Anyone think that the old smokes are worth
preserving, or can we just cut over to a new site with a clean slate?
jerry gay
> Let's take a poll - Anyone think that the old smokes are worth
> preserving, or can we just cut over to a new site with a clean slate?
>
months, right, michael?
perhaps michael can provide the current conf file to the osuosl admins
so they have a head start at configuration.
~jerry
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
Michael Peters
>> The historical data has a short shelf life, IMO. If you can write up
>> what it would take to setup on a parrot.org server (with or without
>> the history copy),
The historical data is trickier. I'd need to give your guys a copy of
the sqlite database with any non-parrot stuff removed which you'll put
in place of the one that smolder creates when installed. Then I'll need
to create a tarball of the TAP archives, and HTML rendered reports for
Parrot related stuff that they will need to unpack in the new smolder's
data directory.
--
Michael Peters
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
Michael Peters
> cut straight over--we can use the old site for history for a few
> months, right, michael?
Yes. We're still using it at Plus Three for our internal projects too.
> perhaps michael can provide the current conf file to the osuosl admins
> so they have a head start at configuration.
Here's what mine looks like (with a different Secret):
DataDir /var/lib/smolder
LogFile /var/lib/smolder/smolder.log
Port 80
HostName 70.42.42.150
Secret XXXXXXXX
SMTPHost mail.plusthree.com
PidFile /var/run/smolder.pid
James E Keenan
> On Thu, Feb 4, 2010 at 10:40 AM, Michael Peters<mpe...@plusthree.com> wrote:
>> On 02/04/2010 10:36 AM, Will Coleda wrote:
>>
> The historical data has a short shelf life, IMO.
Isn't that by design?
Ever since we've had Smolder, I've only been able to access the last
couple of dozen smoke reports in full detail (tester metadata; full
output of individual test files; etc.) Anything older than X days only
appears on the summary page.
I suppose this is because the amount of data that builds up when you
have 30,000+ submissions is just too big to store.
I don't know whether the rule is: Don't show full reports for
submissions older than N days.
... or: Show only the most recent M reports.
FWIW, I think it's time we did our own hosting.
Mi dos centavos.
kid51
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
Jonathan Leto
--
Jonathan "Duke" Leto
jona...@leto.net
http://leto.net
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
Gerd Pokorra
I suggest http://smolder.parrot.org or https://smolder.parrot.org for
it.