woah... the site seems to be responding very well right now....
.. (sorry to have double posted so many times... I'm just trying to keep everything very current.)
Edit:
Just noticed something... Triton, when I signed on, you were still "logged in" technically, and your session didn't expire for an hour (about). When that session finally did expire, the site slowed down and gave me a time-out error. As soon as it responded again, you were no longer listed as "Online".
Aside from that, the site seems to be responding normally now, despite my comments on the thread you linked to.
.. (sorry to have double posted so many times... I'm just trying to keep everything very current.)
Edit:
Just noticed something... Triton, when I signed on, you were still "logged in" technically, and your session didn't expire for an hour (about). When that session finally did expire, the site slowed down and gave me a time-out error. As soon as it responded again, you were no longer listed as "Online".
Aside from that, the site seems to be responding normally now, despite my comments on the thread you linked to.
no
I had again troubles with response time, and it starts with the main page as well as with other sites. and I removed all the database queries I put in the last time.
yesterday german telecom had problems with several sites to host.
i.e. google.de or fleetboard.de and they were off (not reachable) for a couple of hours.
there might be a DoS attacking issue too somewhere somehow.
there are three more things I suggest:
1. configuring the database (with the help of mud)
a. configure memory usage
b. switch on auto maintenance
c. other settings....
by doing things like that the database must be restarted
2. a full vacuuming of the database. this can take a few minutes up to a few hours and the database is locked during this action
I found out that the response time of the databases takes 40 to 600 seconds but only 1-3 seconds of cpu's time
3. after doing #2 restart the server. uptime is about 58 days now.
did someone take care of such things before giving bandamp to the community?
I had again troubles with response time, and it starts with the main page as well as with other sites. and I removed all the database queries I put in the last time.
yesterday german telecom had problems with several sites to host.
i.e. google.de or fleetboard.de and they were off (not reachable) for a couple of hours.
there might be a DoS attacking issue too somewhere somehow.
there are three more things I suggest:
1. configuring the database (with the help of mud)
a. configure memory usage
b. switch on auto maintenance
c. other settings....
by doing things like that the database must be restarted
2. a full vacuuming of the database. this can take a few minutes up to a few hours and the database is locked during this action
I found out that the response time of the databases takes 40 to 600 seconds but only 1-3 seconds of cpu's time
3. after doing #2 restart the server. uptime is about 58 days now.
did someone take care of such things before giving bandamp to the community?
probably mud did. I he was silently pulling the strings, I think. Perhaps we need to make some publicly known maintenance schedule for the system. That way, we'd all know that the site would be offline for a few hours. (A little notice could be pinned to the top of the forums within a day or two of said down-time, just to help people be aware of the status of the server.)
So, we'd probably have to resort to sending an email to the members (via the admin account here at bandamp) to let people know that in order to correct this problem, bandamp will be taken offline for several hours. I think they'd appreciate the downtime sooner rather than later. Nobody's all that thrilled about having to wait 40 to 600 seconds for every page they request
thanks for looking into this so much
(ps, this database query idea would play perfectly into what i've been noticing... playing songs through the AMP is easy; no delays, even when the site itself is on major slowdown.)
So, we'd probably have to resort to sending an email to the members (via the admin account here at bandamp) to let people know that in order to correct this problem, bandamp will be taken offline for several hours. I think they'd appreciate the downtime sooner rather than later. Nobody's all that thrilled about having to wait 40 to 600 seconds for every page they request
thanks for looking into this so much
(ps, this database query idea would play perfectly into what i've been noticing... playing songs through the AMP is easy; no delays, even when the site itself is on major slowdown.)
a couple of days ago, the site went down for a short maintenance period. i'm hoping that the issue is fixed
this message pops up if there is a database error
Even me had troubles to open bandamp
and I couldnt find out what was the reason...
the linux processes didnt tell me whats going on at that time.
I only hope that a backup job (it wasnt indicated) or whatever accessed the server
again: we need to restart the server right now it shows uptime 78+05:04:56 10:47:03
but I want some special person standby..... hope you know what I mean...
the last entries I made were really fast....
Even me had troubles to open bandamp
and I couldnt find out what was the reason...
the linux processes didnt tell me whats going on at that time.
I only hope that a backup job (it wasnt indicated) or whatever accessed the server
again: we need to restart the server right now it shows uptime 78+05:04:56 10:47:03
but I want some special person standby..... hope you know what I mean...
the last entries I made were really fast....
Sorry, you do not have access to post...
Wanna post? Join Today!