Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#17337 - {wiki} Confirmation email doesn't put into effect
Attached to Project:
Arch Linux
Opened by Nekmo (nekmo) - Tuesday, 01 December 2009, 17:59 GMT
Last edited by Dan McGee (toofishes) - Thursday, 17 March 2011, 16:10 GMT
Opened by Nekmo (nekmo) - Tuesday, 01 December 2009, 17:59 GMT
Last edited by Dan McGee (toofishes) - Thursday, 17 March 2011, 16:10 GMT
|
DetailsGreetings.
I've tried to register in Arch Linux's Wiki ( http://wiki.archlinux.org/ ). Unfortunately, after several unsuccessful attemps, I couldn't do it. The register works properly, and I have received the confirmation e-mail. If I click on the first link, I can clearly see "Your e-mail address has now been confirmed.", but I'm still unable to edit wiki pages. ("You must confirm your e-mail address before editing pages. Please set and validate your e-mail address through your user preferences."). I also noticed that user changes on the options panel just don't work. I've already tried with 3 nicks, 3 emails, and 3 different passwords, but I still can't get it working. Thank you for your time, and I hope you answer soon, cause I'm really excited about contributing in my fav. distribution's Wiki. ----- ESPAÑOL (España) ------ Título: "[WIKI-ARCH] Confirmación de email no pone en efecto" Muy buenas. He intentado registrarme en la Wiki de Archlinux ( http://wiki.archlinux.org/ ) pero tras varios intentos me ha sido imposible. El registro se realiza correctamente, y recibo el email de confirmación, confirmo mediante el primer enlace, y efectivamente se puede ver el mensaje "Your e-mail address has now been confirmed.", pero aún así sigo sin poder editar páginas del wiki ("You must confirm your e-mail address before editing pages. Please set and validate your e-mail address through your user preferences."). También he notado que los cambios efectuados en opciones no se realizan. He probado con 3 nicks, 3 emails y 3 contraseñas diferentes, todos los intentos han llevado a error. Muchas gracias por vuestra paciencia, y espero vuestra contestación, pues estoy realmente ansioso de poder colaborar con la Wiki de mi distribución favorita. Saludos. |
This task depends upon
Closed by Dan McGee (toofishes)
Thursday, 17 March 2011, 16:10 GMT
Reason for closing: No response
Additional comments about closing: Old bugs that aren't going anywhere.
Thursday, 17 March 2011, 16:10 GMT
Reason for closing: No response
Additional comments about closing: Old bugs that aren't going anywhere.
As a side-note, gmail marked the email as spam. Unrelated, but interesting
- nekmo
- capitanquartz
- nintux
Thanks :)
For now I switched to APC for caching. According to Dan APC had caused problems (see http://bugs.php.net/bug.php?id=46025) I don't know if this problem is still valid though. In the meantime we have updated to new major versions of PHP and APC and switched from mod_php to fcgi.
We should monitor the servers behavior at least for one week before I consider this bug as "resolved".
If you tracked this down to "the use of memcached", you did file a bug upstream with MediaWiki I assume? I'd love to help but the lack of detail here is not very good. Considering they (Wikimedia) use memcached heavily in production, I'm a bit skeptical here.
APC is per process but we only have one php-fcgi process which launches some child processes. APC works fine here and all those children share one cache.
For now I have no more detailed information than that it works with memcached disabled and doesn#t with it enabled. It will take some time to setup a similar server locally and to reproduce this problem; I don't really want to debug this directly on the server.
EDIT: I fear you are right about the php process. I just saw that apache indeed launches several independent processes. But I guess this can be configured differently. E.g. I have set "max-procs" to 1 in lighttpd.
[2009-09-13 11:28] upgraded memcached (1.2.8-1 -> 1.4.1-1)
[2009-10-26 23:45] upgraded memcached (1.4.1-1 -> 1.4.2-1)
[2009-11-26 13:24] upgraded memcached (1.4.2-1 -> 1.4.3-1)
Perhaps on bug day this weekend someone can take a peek at this? I will try to be around and may hit up #memcached or #wikipedia or whatever the relevant channels are to see if anyone has an idea of what is going on here.