After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 702791 - HTTP 500 error when uploading PO files
HTTP 500 error when uploading PO files
Status: RESOLVED FIXED
Product: sysadmin
Classification: Infrastructure
Component: Other
unspecified
Other All
: Normal blocker
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
: 702829 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-06-21 07:19 UTC by Christian Kirbach
Modified: 2013-06-23 13:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screen-shot (99.98 KB, image/png)
2013-06-21 09:37 UTC, Christian Kirbach
Details

Description Christian Kirbach 2013-06-21 07:19:56 UTC
Hi

vertimus is currently nearly unusable. I get an HTTP500 error when trying to

* upload PO files
* change a translation status along with a comment

reserving modules without a comment does work, tough.
Comment 1 Andrea Veri 2013-06-21 09:12:46 UTC
Can you verify it is working again? there was a temporary mysqld shutdown during software upgrades yesterday, so that might be the reason of the 500 errors.
Comment 2 Christian Kirbach 2013-06-21 09:34:52 UTC
hmm it is still not working for me :(

i cannot add a comment to e.g.
https://l10n.gnome.org/vertimus/grilo/master/po/de

And I tried uploading my PO file to 
https://l10n.gnome.org/vertimus/91101/18

The error page I receive seems to be missing style sheets.
The title says "Server error (500)" which looks like an HTTP 500 error.


I have already logged out and in again.
Comment 3 Christian Kirbach 2013-06-21 09:37:14 UTC
Created attachment 247414 [details]
screen-shot
Comment 4 Christian Kirbach 2013-06-22 23:39:42 UTC
It is still not working for me, nor for people in my team.

E.g. we cannot add a comment to https://l10n.gnome.org/vertimus/grilo/master/po/de
Comment 5 Claude Paroz 2013-06-23 09:29:29 UTC
At last, I was able to reproduce the error.

It is due to an SMTP connection error ([Errno 111] Connection refused). Reassigning the issue.
Comment 6 Claude Paroz 2013-06-23 10:10:08 UTC
Now, all actions should not result in a server error, but with a warning on the top of the page that something went wrong during mail send operation.

Hopefully, the SMTP issue can be solved soon by sysadmins.
Comment 7 Andrea Veri 2013-06-23 10:12:04 UTC
Should be fixed by now, please confirm.
Comment 8 Claude Paroz 2013-06-23 10:12:18 UTC
*** Bug 702829 has been marked as a duplicate of this bug. ***
Comment 9 Christian Kirbach 2013-06-23 13:18:17 UTC
I can confirm the issue has been fixed. Thanks.