FAILURE: Exception occured Traceback (most recent call last): File "/home/svnuser/Projects/Etsy/trunk/emid/emid/MethodCaller.py", line 79, in __call__ data = method(*args) File "/home/svnuser/Projects/Etsy/trunk/emid/emid/SQLInterface.py", line 142, in wrapped return SQLInterfaceFunc(tmpl, a) File "/home/svnuser/Projects/Etsy/trunk/emid/emid/SQLInterface.py", line 305, in getOneThing desc, results = procSQL_return_one_record(sql, args) File "/home/svnuser/Projects/Etsy/trunk/emid/emid/Resources.py", line 146, in procSQL_return_one_record conn = Pool.getconn() File "/home/svnuser/Projects/Etsy/trunk/emid/emid/thirdparty/pool.py", line 149, in getconn return self._getconn(key) File "/home/svnuser/Projects/Etsy/trunk/emid/emid/thirdparty/pool.py", line 89, in _getconn return self._connect(key) File "/home/svnuser/Projects/Etsy/trunk/emid/emid/thirdparty/pool.py", line 60, in _connect conn = psycopg2.connect(*self._args, **self._kwargs) OperationalError: could not connect to server: Connection refused Is the server running on host "10.110.10.151" and accepting TCP/IP connections on port 6666? >
You are on webserver web2
Time January 15, 2007, 12:36 pm
The above is an example of a database cursing. This is the response I got at 7:36 this morning when I clicked a link to an etsy.com shop from one of my lists: "Line this - FU, line that - FU. Go look it up yourself moron! Then when I get sick, you tell me I should have backed myself up! Go to the Devil!!!"
Yikes. Maybe I should just read a book.