Difference between revisions of "CWCki:Technical"

From CWCki
Jump to navigation Jump to search
Line 22: Line 22:
::*Same here.--[[User:Trombonista|trombonista]] 18:08, 5 October 2010 (PDT)
::*Same here.--[[User:Trombonista|trombonista]] 18:08, 5 October 2010 (PDT)
:::*That's actually been happening to me quite a bit, recently. --[[User:EdtheHedgehog1894|EdtheHedgehog1894]] 21:23, 5 October 2010 (EST)
:::*That's actually been happening to me quite a bit, recently. --[[User:EdtheHedgehog1894|EdtheHedgehog1894]] 21:23, 5 October 2010 (EST)
::::Extra processing and memory is used while saving a page, and since lack of memory is the likely cause of the error - it's unsurprising that you encounter it when doing the above. Implementing global caching would help alleviate server load. --[[User:Anonymax|Anonymax]] 18:30, 5 October 2010 (PDT)
::::Extra processing and memory is used while saving a page, and since lack of memory is the likely cause of the error - it's unsurprising that you encounter it when doing the above. Implementing global caching would help alleviate server load, as currently every page request from logged in users is generating server processing. Longer pages have more chance of generating the error - as they are larger, and take up more memory while being processed. --[[User:Anonymax|Anonymax]] 18:30, 5 October 2010 (PDT)

Revision as of 21:32, 5 October 2010


Community Portal
Forum News Policy
Help Technical General

For discussion of errors, extensions, and technical stuff in general(yes we know about the 500 errors).

upgraded to 1.16.0

seems like all the obvious stuff is fixed but if there are any missing extensions you need please let me know --Cogsdev 02:39, 2 August 2010 (PDT)

Audio hosting

Seeing as how some of the audio recordings that we link to on some pages have been removed from their file hosting sites, I was thinking maybe instead of having people download audio we simply host it here CWCiki side. An example of what I am talking about can be found here.[1] CrassCrab 10:14, 3 August 2010 (PDT)

This could be doable, but needs server configuration. From user's point of view, it could be a simple matter of converting the files to Ogg Vorbis and uploading them here. Currently, the upload page doesn't accept .ogg files, and files are limited to 7 MB. In order to make the in-browser support work, we'd need the OggHandler extension (which needs ffmpeg and other leet stuff installed on the server as well). --wwwwolf (wake me when you need me) 03:12, 6 August 2010 (PDT)

Apache Module versus CGI

I've been a long time lurker, but the prevalence of 500 Internal Server Errors has prompted me to register an account. I've lurked and searched the CWCki to see if this has been suggested, but I didn't see anyone bring up this potential solution. So I apologize if I'm offering a redundant suggestion. These error messages seem to suggest to me that the Wiki software is running on CGI. A lot of CGI-related performance issues can be remedied by running PHP via an Apache module, rather than as a CGI binary. The PHP CGI binary is invoked, processes a script, and then shuts down every time a page is requested. Apache modules are continuous, thread safe processes (thread safety can be build dependent). I'm not sure if this hosting provider offers such a configuration option, but it may be worth looking into one that does if this becomes an increasingly prominent issue. FastCGI may be a worthwhile alternative to the current configuration if an Apache module is not an option because of some inherent limitations with Wiki software. Sheex 10:28, 24 August 2010 (PDT)

500 internal server error poll

Please note what page you received it on and what your action was (view/edit/etc...). Clydec 14:25, 5 October 2010 (PDT)

  • Main Page/View - It happens sometimes when I try going here on a new window. --EdtheHedgehog1894 18:14, 5 October 2010 (EST)
  • I almost always get it when saving an edit, sometimes when I log in. Pfargtl9000 Spam & Eggs 17:10, 5 October 2010 (PDT)
  • That's actually been happening to me quite a bit, recently. --EdtheHedgehog1894 21:23, 5 October 2010 (EST)
Extra processing and memory is used while saving a page, and since lack of memory is the likely cause of the error - it's unsurprising that you encounter it when doing the above. Implementing global caching would help alleviate server load, as currently every page request from logged in users is generating server processing. Longer pages have more chance of generating the error - as they are larger, and take up more memory while being processed. --Anonymax 18:30, 5 October 2010 (PDT)