Ticket #637 (closed bug: fixed)

Opened 5 years ago

Last modified 5 years ago

smolder: server error on submission

Reported by: rg Owned by: jkeenan
Priority: normal Milestone:
Component: testing Version:
Severity: medium Keywords: smolder
Cc: mpeters@… Language:
Patch status: Platform:

Description

For about two weeks now (follwing an outage), smolder reports a 500 server error when submitting a new report. In most cases, the report still shows up on the project page.

I've now noticed, that those reports are missing their tags and if you try to display a report that does have tags, you also get a 500 server error. My guess is that those problems are related.

It has been suggested on #parrot to cc mpeters, so I'm doing that ;)

Help, please?

Change History

in reply to: ↑ description   Changed 5 years ago by jkeenan

Replying to rg:

For about two weeks now (follwing an outage), smolder reports a 500 server error when submitting a new report. In most cases, the report still shows up on the project page.

I've experienced that, too. I've also experienced simply being unable to reach the server or a Smolder web page.

But I heard from mpeters this morning and he is working on it.

  Changed 5 years ago by jkeenan

  • status changed from new to closed
  • resolution set to fixed

Michael Peters has been on the case. This evening I submitted two reports. Both concluded cleanly and both were uploaded.

So I'm closing the ticket. New smolder problems? New ticket.

Thank you very much.
kid51

  Changed 5 years ago by coke

On Tue, May 5, 2009 at 9:37 AM, Michael Peters <mpeters@plusthree.com> wrote:
> Parrot wrote:
>
>>  For about two weeks now (follwing an outage), smolder reports a 500
>> server
>>  error when submitting a new report. In most cases, the report still shows
>>  up on the project page.
>
> This was a problem with some of the cleanup code that was running.
> Apparently most of the information about the reports were committed before
> the cleanup but not all.
>
>>  I've now noticed, that those reports are missing their tags and if you
>> try
>>  to display a report that does have tags, you also get a 500 server error.
>>  My guess is that those problems are related.
>
> Apparently most of the information about the reports were committed before
> the cleanup but not all. So the report appears but the extra tags
> information is not there. This has been fixed on the server and in the git
> repository as well. Thanks for the report!
>
> --
> Michael Peters
> Plus Three, LP
>
> _______________________________________________
> parrot-tickets mailing list
> parrot-tickets@lists.parrot.org
> http://lists.parrot.org/mailman/listinfo/parrot-tickets
>

  Changed 5 years ago by coke

  • status changed from closed to reopened
  • resolution fixed deleted

This same problem is occurring again, so re-opening this ticket, instead of opening a new one as mentioned previously (and already done in #699)

I had another failure myself at midnight.

Michael; Can we investigate what would be required for parrot.org to host a copy of the server just for parrot-related projects?

  Changed 5 years ago by coke

Daily test run (and then codetest run) both failed just now.

TAP Archive created at /private/tmp/DQHweBQcWt/parrot_test_run.tar.gz
Could not upload report to Smolder at http://smolder.plusthree.com
HTTP CODE: 500 (EOF)
TAP Archive created at /private/tmp/DQHweBQcWt/parrot_test_run.tar.gz
Could not upload report to Smolder at http://smolder.plusthree.com
HTTP CODE: 500 (read timeout)

  Changed 5 years ago by coke

occurred again today:

TAP Archive created at /private/tmp/5GXtLe5YLi/parrot_test_run.tar.gz Could not upload report to Smolder at  http://smolder.plusthree.com HTTP CODE: 500 (read timeout)

About 12:17AM eastern.

follow-up: ↓ 8   Changed 5 years ago by whiteknight

  • status changed from reopened to new
  • owner set to whiteknight

This seems to me like it's not a Parrot problem, at least not directly. It's a lousy waste of time for us to be closing this ticket when smolder works, and reopening it everytime smolder goes down. It's not productive and serves no purpose. If we want to alert users that smolder is down, an automatically-generated warning message somewhere on the website would suffice. If we want to avoid the issue entirely, maybe we need to consider hosting our own smolder server on Parrot.org (the idea has been mentioned before, I don't know what came of it).

In any case, this ticket here is useless and not the right way to be tracking the status of the smolder server. Plus, so long as smolder has the possibility of any downtime ever, this ticket is unclosable, and unclosable tickets are bad.

I'll close this ticket in a few days if nobody objects too strongly, and we can look for a better way (or open a ticket for finding a better way) to track the status of the smolder server.

in reply to: ↑ 7   Changed 5 years ago by coke

Replying to whiteknight:

This seems to me like it's not a Parrot problem, at least not directly. It's a lousy waste of time for us to be closing this ticket when smolder works, and reopening it everytime smolder goes down. It's not productive and serves no purpose. If we want to alert users that smolder is down, an automatically-generated warning message somewhere on the website would suffice. If we want to avoid the issue entirely, maybe we need to consider hosting our own smolder server on Parrot.org (the idea has been mentioned before, I don't know what came of it).

It's a problem with the smolder tech stack; moving the tech stack to another host is unlikely to resolve the underlying problem.

In any case, this ticket here is useless and not the right way to be tracking the status of the smolder server. Plus, so long as smolder has the possibility of any downtime ever, this ticket is unclosable, and unclosable tickets are bad. I'll close this ticket in a few days if nobody objects too strongly, and we can look for a better way (or open a ticket for finding a better way) to track the status of the smolder server.

It is possible to re-submit a smolder test at a later time; I recommend someone create a wiki page noting how to do that, and link to it from here.

  Changed 5 years ago by coke

Parrot wrote:

 For about two weeks now (follwing an outage), smolder reports a 500 server
 error when submitting a new report. In most cases, the report still shows
 up on the project page.

This was a problem with some of the cleanup code that was running. Apparently most of the information about the reports were committed before the cleanup but not all.


 I've now noticed, that those reports are missing their tags and if you try
 to display a report that does have tags, you also get a 500 server error.
 My guess is that those problems are related.

Apparently most of the information about the reports were committed before the cleanup but not all. So the report appears but the extra tags information is not there. This has been fixed on the server and in the git repository as well. Thanks for the report!

-- 
Michael Peters
Plus Three, LP

follow-up: ↓ 12   Changed 5 years ago by coke

Parrot wrote:

 Michael; Can we investigate what would be required for parrot.org to host
 a copy of the server just for parrot-related projects?

Yes, it's pretty easy to do.

 cpan> install Smolder

When it and all it's prereqs are installed then I'll help you set up a smolder.conf and get a copy of the sqlite db that parrot currently uses.

But I have to warn you that I'm not sure it will be more reliable. In my effort to make Smolder a CPAN install I switched from using Apache/mod_perl to HTTP::Server::Simple and it works great for a while. But after it's run for a day or so it just locks up and I have to restart it. I've been meaning to find some time to investigate other Perl HTTP servers (like Mojo) but I just haven't had the time.

-- 
Michael Peters
Plus Three, LP

  Changed 5 years ago by jkeenan

  • component changed from none to testing

in reply to: ↑ 10   Changed 5 years ago by jkeenan

  • owner changed from whiteknight to jkeenan
  • status changed from new to assigned

Replying to coke:

>  Michael; Can we investigate what would be required for parrot.org to host
>  a copy of the server just for parrot-related projects?
> 
> Yes, it's pretty easy to do.
> 
>  cpan> install Smolder
> 
> When it and all it's prereqs are installed then I'll help you set up a smolder.conf and get a copy of the sqlite db that parrot currently uses.
> 
> But I have to warn you that I'm not sure it will be more reliable. 
> In my effort to make Smolder a CPAN install I switched from using 
> Apache/mod_perl to HTTP::Server::Simple and it works great for a while. 
> But after it's run for a day or so it just locks up and I have to 
> restart it. I've been meaning to find some time to investigate other 
> Perl HTTP servers (like Mojo) but I just haven't had the time.
> 
> -- 
> Michael Peters
> Plus Three, LP

No one has added this ticket in 6 months, which suggests to me that, while the Smolder site at plusthree might not always work well, our devs know how to submit delayed reports.

So I'd like to (a) close this ticket and drive a stake through its heart; and (b) encourage our admins to file a separate infrastructure ticket if we really want to run our own Smolder server.

Comments? (If none, I will close in 2-3 days.)

Thank you very much.
kid51

  Changed 5 years ago by jkeenan

  • status changed from assigned to closed
  • resolution set to fixed

No comments; closing ticket.

Note: See TracTickets for help on using tickets.