Dads_Vinyl wrote:

I am curious, I have seen more error problems in the last several days than the total amount I have seen sense I joined.

I have had about 15 errors today alone, and 7 times I could not even get to the web-site!

What is going on?

Dads_Vinyl wrote:

No reply's.

It's just a question! I am not making judgement.. Why are there so many error's lately? As I said just curious.

Myriad wrote:

I've been having lots of screens telling me the page could not be retreived or something like that...

teo wrote:

Yes, our database server has gotten bogged down over the past few weeks. We're working on improvements which should be completed in a few days.

Dads_Vinyl wrote:

Nice, Thanks for the info. Hope it goes smoooooooooothly.

;)

MR_E wrote:

Performance has been pretty bad lately. I use discogs just about every day and lately I'm getting a blank page, internal server error or other error message more often than not. Any updates on the unspecified improvements?

makbo wrote:

I too have been having intermittent service problems, mostly just today (Sunday Jul 5).

Maybe management is rebuilding some database indexes, it would explain slow response and also the fact that since yesterday, newly added releases are not showing up in queries via the API (at least, that's my major problem at the moment).

makbo wrote:

Heh, well I went to read a book, and now it's working again. Other screens responding normally now also.

DougBear wrote:

Hi

I added a new listing: http://www.discogs.com/Beatles...les/release/1837607. I then went to sell this item, processed it & it shows up in my inventory. However, it is not showing on Shopping icon for sale. When I go to label: Mun-Hwa records it is not showing for sale either. When I click '1 Item for sale' button it is listed with other Item. Can anyone help me?

DougBear wrote:

Problem solved It is there Thanks Discogs

MR_E wrote:

You have to wait anywhere from a few minutes to a few hours for new listings to show up. Usually it's pretty quick, but site performance has been poor lately, as noted above.

disruptive-influence wrote:

Ive still got submissions that dont show up in the search 10 days after I subbbed them.

The site is really slow on a regular basis. Its getting quite frustrating now.

Any news on when this all might be fixed?

I keep getting loads of error messages also...heres the latest

Custom error handler had an error:Error(OperationalError): (2003, "Can't connect to MySQL server on 'dbmasta' (99)")file: /usr/lib64/python2.3/site-packages/MySQLdb/connections.py line 41apply(super(ConnectionBase, self).__init__, args, kwargs)/usr/lib64/python2.3/site-packages/MySQLdb/connections.py:41/usr/lib64/python2.3/site-packages/MySQLdb/connections.py:116/usr/lib64/python2.3/site-packages/MySQLdb/__init__.py:64/var/www/discogs/mysqlconn.py:77/var/www/discogs/PyDO.py:491/var/www/discogs/pydostatic.py:51/var/www/discogs/lib/controller.py:489/var/www/discogs/lib/controller.py:851/var/www/discogs/discogsapp.py:23/var/www/discogs/modpython-handler.py:7/usr/lib64/python2.3/site-packages/mod_python/apache.py:299---------------------------------------------Original Stack Trace:Error(OperationalError): (2003, "Can't connect to MySQL server on 'dbmasta' (99)")file: /usr/lib64/python2.3/site-packages/MySQLdb/connections.py line 41apply(super(ConnectionBase, self).__init__, args, kwargs)/usr/lib64/python2.3/site-packages/MySQLdb/connections.py:41/usr/lib64/python2.3/site-packages/MySQLdb/connections.py:116/usr/lib64/python2.3/site-packages/MySQLdb/__init__.py:64/var/www/discogs/mysqlconn.py:77/var/www/discogs/PyDO.py:491/var/www/discogs/pydostatic.py:51/var/www/discogs/lib/controller.py:489/usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/request.py:1007/usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/exception.py:61/usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/request.py:1017/usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/request.py:1054/usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/request.py:277/usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/interp.py:156/var/www/discogs/lib/controller.py:851/var/www/discogs/discogsapp.py:23/var/www/discogs/modpython-handler.py:7/usr/lib64/python2.3/site-packages/mod_python/apache.py:299Error(OperationalError): (2003, "Can't connect to MySQL server on 'dbmasta' (99)") file: /usr/lib64/python2.3/site-packages/MySQLdb/connections.py line 41 apply(super(ConnectionBase, self).__init__, args, kwargs) /usr/lib64/python2.3/site-packages/MySQLdb/connections.py:41 /usr/lib64/python2.3/site-packages/MySQLdb/connections.py:116 /usr/lib64/python2.3/site-packages/MySQLdb/__init__.py:64 /var/www/discogs/mysqlconn.py:77 /var/www/discogs/PyDO.py:337 /var/www/discogs/pydostatic.py:51 /var/www/discogs/dbobjects.py:14851 /var/www/discogs/pydostatic.py:51 /var/www/discogs/mviews/m/orders.myt:17 /var/www/discogs/mviews/autohandler:107 /var/www/discogs/lib/controller.py:851 /var/www/discogs/discogsapp.py:23 /var/www/discogs/modpython-handler.py:7 /usr/lib64/python2.3/site-packages/mod_python/apache.py:299 --------------------------------------------- Original Stack Trace: Error(OperationalError): (2003, "Can't connect to MySQL server on 'dbmasta' (99)") file: /usr/lib64/python2.3/site-packages/MySQLdb/connections.py line 41 apply(super(ConnectionBase, self).__init__, args, kwargs) /usr/lib64/python2.3/site-packages/MySQLdb/connections.py:41 /usr/lib64/python2.3/site-packages/MySQLdb/connections.py:116 /usr/lib64/python2.3/site-packages/MySQLdb/__init__.py:64 /var/www/discogs/mysqlconn.py:77 /var/www/discogs/PyDO.py:337 /var/www/discogs/pydostatic.py:51 /var/www/discogs/dbobjects.py:14851 /var/www/discogs/pydostatic.py:51 /tmp/obj/main//m/orders.myt.py:65 /usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/component.py:128 /usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/request.py:389 /usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/request.py:300 /usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/request.py:725 /tmp/obj/main//autohandler.py:293 /usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/component.py:128 /usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/request.py:389 /usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/request.py:250 /usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/exception.py:61 /usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/request.py:270 /usr/lib/python2.3/site-packages/Myghty-1.1-py2.3.egg/myghty/interp.py:156 /var/www/discogs/lib/controller.py:851 /var/www/discogs/discogsapp.py:23 /var/www/discogs/modpython-handler.py:7 /usr/lib64/python2.3/site-packages/mod_python/apache.py:299

hafler3o wrote:

the site is absolutely diabolical this morning (UK time) constant timeouts, misconfiguration, temporarily off-line, 'there was an error' is my fave, really frustrating...........

fixed in a few days says Teo 6 days ago, any further news?

PS this took a dozen go's to post! Even the marketplace doesn't work...

Curiopete wrote:

...sucks...

Jooles wrote:

12:56 CET in Brussels and just got access to the site after about an hour of trying.
Sometimes just a blank screen, other times I got a message something like: "Discogs servers are overloaded... we're working on it"

Jayfive wrote:

Its fixed now. The site was usuable for me the last few days but this morning I was getting internal server 500 errors making it impossible to check my Manage Inventory or reply in the forums. Then got the 'Servers are overloaded screen' about 45 mins ago. Went out, came back and the site back to normal.

About 2 hours worth of errors by the looks of the times of the post in here. I bet they wouldve been quicker on the fixing but as Ive mentioned already its about 3-4am where the servers are :D

peaking wrote:

discogs offline for a couple of hours here in Australia...
fees go up, reliability goes down??

Mr.Mystery wrote:

Where's the rolleyes smiley when you need it...