Page 1 of 2

New Concert Hall server problems?

PostPosted: Sat Dec 12, 2015 4:39 am
by OAM
Don't get access to the website anymore:

"Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request."

Re: New Concert Hall server problems?

PostPosted: Sat Dec 12, 2015 6:18 am
by EdoL
Same here.

After you upgraded it worked for about three hours.

Then I got the databe error message.

After that the message of the internal server error 500.

Edo

Re: New Concert Hall server problems?

PostPosted: Sat Dec 12, 2015 6:38 am
by pointyflute
Me, too. It's heartbreaking! :(

Re: New Concert Hall server problems?

PostPosted: Sat Dec 12, 2015 9:06 am
by telemanr
Works for me. No problems.

Re: New Concert Hall server problems?

PostPosted: Sat Dec 12, 2015 11:22 am
by EdoL
No access yet.

The error message now is: Database Error1141

Re: New Concert Hall server problems?

PostPosted: Sat Dec 12, 2015 2:12 pm
by dhm
I got the "Internal server error" message earlier today, but the website is accessible now.

Re: New Concert Hall server problems?

PostPosted: Sat Dec 12, 2015 6:32 pm
by pointyflute
Back in business now. :D

Re: New Concert Hall server problems?

PostPosted: Sun Dec 13, 2015 9:33 am
by OAM
Unfortunately a new database error occurs, when trying to open
http://www.contrebombarde.com/concerthall/music/18811

What happened with our wonderful Concert Hall ? ....


"A Database Error Occurred
Error Number: 1064
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's sing with a proud an loud voice)' AND music_id != '18811' ORDER BY RA' at line 14

SELECT * FROM music LEFT JOIN organs ON fk_organ_id = organ_id LEFT JOIN composers ON music.fk_composer_id = composers.composer_id LEFT JOIN fa_user ON fa_user.id = fk_user_id WHERE music_title = 'Noel "Chantons de voix hautaine" (Let's sing with a proud an loud voice)' AND music_id != '18811' ORDER BY RAND() Limit 0,5"

Re: New Concert Hall server problems?

PostPosted: Sun Dec 13, 2015 10:14 am
by OAM
Now it's working correctly again.

What's going on there?

Re: New Concert Hall server problems?

PostPosted: Sun Dec 13, 2015 1:58 pm
by sesquialtera
Hello to every conctrebombarde users.

I'm a amateur and modest contrebombarde listener/uploader,
This site is a unique source of musical pleasure, where we can discover rarities, discuss and argue about organ history, and compare sound quality of virtual organs.

But listening and/or uploading has become quite difficult yet : It's often impossible to access to the page, or the player randomly stops, and needs a very long time for buffering ...

Do we realy need "the barde" ?, do we need streaming, charts, stats and playlists ??
I don't know, but the "browse" page is all that I need, I don't ask anything more.

So, please, Mr Dwood, keep it simple and efficient.
and thank you very much again for your work !

Kind regards,
Sesq.

Re: New Concert Hall server problems?

PostPosted: Sun Dec 13, 2015 3:12 pm
by Hoofdwerk
OAM wrote:Now it's working correctly again.

What's going on there?


That particular SQL error was being caused by the apostrophe in Let's, which was being interpreted as terminating the WHERE clause that contains it. The server thinks all the text after Let' is extra characters.

My guess is that they are still fine-tuning the SQL server and its configuration settings so that things like embedded delimiters are not such a problem. With the move to a totally different server backend, some of this is (sadly) hard to avoid.

Re: New Concert Hall server problems?

PostPosted: Sun Dec 13, 2015 4:48 pm
by johnh
A skilled hacker could exploit that. Probably best not to publicize it.

Re: New Concert Hall server problems?

PostPosted: Mon Dec 14, 2015 9:22 am
by dwood
Thanks all for your patience.

This weekend, we had to change servers again. We had a few database issues during the changeover. Hopefully, those are over with. It's been a long haul of a month since our original hosting package. Each package had strange fine print exclusions that uniquely affected what we do at CB.

The original hosting had great specs with unlimited storage. However, they had an unpublished limit to the number of files that it would allow. (unlimited size but limited number...)

The next had unlimited bandwidth and a great amount of storage for us. However, once we took the package, it became apparent that they limited the number of connections to the site (again an unpublished limitation). So, when too many people were on the site, it would deny service and give you the database connection error.

This weekend's festivities were just the result of us tweaking the database calls.

The challenge lies in that each successive hosting has cost multiples of the previous. The current hosting is 9 times the cost of the original hosting. We were trying to keep the costs down. Next stop is 16 times... We hope we don't have to go there.

Anyway, by all means, let us know if you receive other issues. We hope that we have a new server home that will last us for a good long time. We're hoping to rest from site development for a while.

Re: New Concert Hall server problems?

PostPosted: Mon Dec 14, 2015 10:25 am
by engrssc
So maybe you should go into the hosting business? :roll:

Rgds,
Ed

Re: New Concert Hall server problems?

PostPosted: Mon Dec 14, 2015 10:36 am
by dwood
Booooo. No. Absolutely not! :shock:

LOL.

The serendipity is that Raymond just got a massive, while painful, education in server admin and I learned about it from the 5000 ft overview level.

BTW. Hoofdwerk was right about the comma issue. When we moved the database over, the new backend stripped out all the "/'" from the database that makes commas safe in amongst the text. So, that messed up the database. A simple search and replace fixed it.