[pete]

This error is a common problem on overloaded servers running mysql. If the server has enough memory and is not overloaded you can try to increase the number of available connection in /etc/my.cnf. At CFD Online we use "max_connections=256". The default is 100 or 151 depending on what mysql version you run.

[gschaider]

Originally Posted by pete

This error is a common problem on overloaded servers running mysql. If the server has enough memory and is not overloaded you can try to increase the number of available connection in /etc/my.cnf. At CFD Online we use "max_connections=256". The default is 100 or 151 depending on what mysql version you run.

OK. I'll extend that. The reason why I didn't do it yet was that according to my logs the Wiki has nowhere near the number of users CFD Online has (current setting is something above 100)

[pete]

If the server needs more connections due to non-intermittent memory or overload problems then increasing the max number of connections will just increase the risk of a complete server crash.

[gschaider]

Originally Posted by wyldckat

But I even got the page about the technical difficulties... the one with:

Hi Bruno!

Is it possible that this always happened around midnight. I think I stumbled upon the problem when updating the Wiki: as a coward I usually run the usual backup-script before I start updating the Wiki-software. During the running of that script I got the same error message you got and the server started to slow down.

Turns out that mysqldump does two things per default:
- lock all tables of the database (that's why you're seeing this error)
- assume that you have 1Gig of memory to buffer the output (that MAY be the cause of the memory problems I've been seeing)

The script is rather old and it never occurred to me that this might be the problem (in the good old days when the database was smaller it didn't block long enough for anyone to notice)

Now I've modified the database engine so that the dump can be done without blocking and reduced the buffer size. Script is already running faster (the large buffer size seems to have forced the machine into swapping)

Let me know if you see the problem again (the reason why I asked about midnight is that the script runs at that time)

Bernhard

[ngj]

Hi

I happened to go through this list on the Wiki:

http://openfoamwiki.net/index.php/Ca...eaturedArticle

and I wondered, if it would be better to remove "Contrib groovyBC" and "Contrib funkySetFields" and replace them by one article on swak4Foam?

Maybe this will remove some of the questions concerning the individual and obsolete development lines for these two tools.

Kind regards

Niels

[gschaider]

Originally Posted by ngj

Hi

I happened to go through this list on the Wiki:

http://openfoamwiki.net/index.php/Ca...eaturedArticle

and I wondered, if it would be better to remove "Contrib groovyBC" and "Contrib funkySetFields" and replace them by one article on swak4Foam?

Maybe this will remove some of the questions concerning the individual and obsolete development lines for these two tools.

That's a good point. I think in the beginning I didn't make swak a "featured article" because I wasn't confident enough that it is really a worthy replacement for the two, but as both haven't been developed on their own for a long time this is right. I changed that according to your suggestion

I think that the list of featured articles could stand an extension. So if anyone has a suggestion for addition raise your arm (or even better: make it a featured article by editing it according to http://openfoamwiki.net/index.php/Wi...the_front_page The worst that can happen is that I modify the edit)

For instance, Niels: if you feel that wave2foam is sufficiently stable to be featured modify your article according to the instructions (just make sure that only an abstract is NOT in <noinclude>-tags as it would otherwise mess up the front-page

[ngj]

Hi Bernhard,

Well, that is a good idea, besides the fact that I might not be the right person to ask, if my own work is stable and useful)

/ Niels

[wyldckat]

Hi Bernhard,

Originally Posted by gschaider

Let me know if you see the problem again (the reason why I asked about midnight is that the script runs at that time)

After almost a month later, I managed to accidentally hit the preview button on a page I was editing at around 23h00 WEST.
It took about a minute to recover and be back to full speed. There was no message about SQL nor did Firefox complain about a busy website or something like that
So, at least for now, so far so good!

Best regards,
Bruno

[gschaider]

Originally Posted by wyldckat

Hi Bernhard,


After almost a month later, I managed to accidentally hit the preview button on a page I was editing at around 23h00 WEST.
It took about a minute to recover and be back to full speed. There was no message about SQL nor did Firefox complain about a busy website or something like that
So, at least for now, so far so good!

Best regards,
Bruno

Great. Your signature tune from now on will be "The Midnight Poster" (sing to the melody of "The midnight rambler" of the Rolling Stones)

The unresponsiveness for one minute is unfortunate but as it "only" affects posters I'd go with this chart: http://xkcd.com/1205/ (Shave of 1minute. Assume it happens once a week ... which is much. Then I'll look into spending the 4h)

[wyldckat]

Just a quick rant: is there any plug-in/add-on for mediawiki for "Neon signs"?

Because (some) people seem to keep getting lost around groovyBC and swak4Foam's wiki pages

[gschaider]

Originally Posted by wyldckat

Just a quick rant: is there any plug-in/add-on for mediawiki for "Neon signs"?

Because (some) people seem to keep getting lost around groovyBC and swak4Foam's wiki pages

I feel your pain

Well yeah. As the front-page shows you can do HTML inside the Wiki-pages. But I rarely do that. A Wiki should be about writing and reading not designing and looking

[gschaider]

The software on the Wiki has been updated and I did some minor changes:
- possibility to have threaded discussions on the talk pages
- because of the amount of dummy users that were created by spam-bots now users have to be approved by a human (sorry)

For details see:
http://openfoamwiki.net/index.php/Ne...ed_19July_2013

[ngj]

Good morning Bernhard and Bruno,

I have a small request, namely whether it would be possible to get the

Template:Version2.2.1

producing an image as the other templates?

Thanks a lot for your time,

Niels

[wyldckat]

Hi Niels,

Done! The template is up, as well as the respective category and update to the main 2.2 category.

For reference, the image generation kit is available here: http://openfoamwiki.net/index.php/Help_talk:Editing

Best regards,
Bruno

[ngj]

Thank you very much. It looks a lot better now (http://openfoamwiki.net/index.php/Co...Versions_of_OF).

Have a nice Sunday,

Niels

[ngj]

Good morning,

This morning I noticed that I am not requested to give an answer to a control question, when I am updating a wiki-page. Is this a deliberate change after the approval of the users was made manual?

Kind regards

Niels

[wyldckat]

Hi Niels,

Quoting from the OpenFOAMWiki.net official twitter account: https://twitter.com/ofwiki/status/377800064842080256

Disabled the question ("What is the name of ..") during editing. Prepared to switch it on again if the Spambots strike #lessAnnoying

It's also shown on section 11, on the main page

As for the sentence "if the Spambots strike", I'm guessing that is because Bernhard as no way to be 100% certain of which users were created by bots and which weren't.

Best regards,
Bruno

[gschaider]

Originally Posted by wyldckat

Hi Niels,

Quoting from the OpenFOAMWiki.net official twitter account: https://twitter.com/ofwiki/status/377800064842080256
It's also shown on section 11, on the main page

As for the sentence "if the Spambots strike", I'm guessing that is because Bernhard as no way to be 100% certain of which users were created by bots and which weren't.

The thing is: For a long time I resisted the idea to verify the new accounts by a human (==me) before enabling them because I felt that this puts too high a threshold on new users because if I'm not near a computer for a couple of days (happens) then people might loose motivation if they can't edit immediately. A couple of months ago I enabled this nevertheless. People now have to provide a short description of what they do with OpenFOAM and if it makes sense and is not copy/pasted I enable them. Since then I had no new spam users. I was toying with removing the question but said "Naaah. Let's be sure". This week I tried to revise the system with which people can add news and events with forms. The thing is that the system that asks the verification question messes up the forms (data gets lost etc) so I decided to disable it for now. But as Bruno says: I'm not 100% sure if there are still "sleeping" spam users or if some security hole in the Wiki-software allows new creations of some. If that problem resurfaces I'll reenable that question.

@Niels: if you're missing that question than I can try to reenable it just for you

[ngj]

Dear Bernhard and Bruno,

Thanks for the explanation. No, I do not miss it per say, but I will not complain, if you had to re-activate it on my account, if you are in doubt that I am actually a human being

Have a nice Sunday,

Niels

[gschaider]

Originally Posted by ngj

Dear Bernhard and Bruno,

Thanks for the explanation. No, I do not miss it per say, but I will not complain, if you had to re-activate it on my account, if you are in doubt that I am actually a human being

You're a friendly bot. So no verification for you

I'm just waiting for people to say "You young people don't know how good you have it. In the good old days we had to answer questions - difficult questions - to edit on the Wiki. The standard on the MessageBoard was much higher then and we did DNS with 10 cells ... in our head ... in the snow ... and we edited our sources with one hand tied behind our back ... on the good days ... on the others we did it with our nose and no hands ... and real men only used blockMesh ... the women too ...."