 Posted: Sat Jun 28, 2008 7:23 am Post subject: Re: GIXEN front-end downtime this evening |
|||
tannah225, can you please give me item numbers? I want to check this. |
|||
| Posted: Sat Jun 28, 2008 4:27 am Post subject: |
|
| Still down as of 8:26am EST | |
| Posted: Sat Jun 28, 2008 4:22 am Post subject: I can't log in either. |
|
| I can't log in either... same problem:
Warning: pg_connect().... |
|
| Posted: Sat Jun 28, 2008 2:39 am Post subject: Still happening |
|
| I just tried to log in, got the "Warning: pg_connect() ..." message. Thanks for looking into this Mario! | |
| Posted: Sat Jun 28, 2008 1:22 am Post subject: i can't get in!! |
|
| still getting the following and unable to log in, what does it all mean?
Warning: pg_connect() [function.pg-connect]: Unable to connect to PostgreSQL server: FATAL: too many connections for role "web" in /usr/local/apache2/htdocs/gixen/home_main.php on line 94 Warning: pg_freeresult(): supplied argument is not a valid PostgreSQL result resource in /usr/local/apache2/htdocs/gixen/home_main.php on line 99 Warning: pg_close(): supplied argument is not a valid PostgreSQL link resource in /usr/local/apache2/htdocs/gixen/home_main.php on line 102 |
|
| Posted: Sat Jun 28, 2008 1:04 am Post subject: Re: GIXEN front-end downtime this evening |
|||
Sorry, but the back end was down as well - four of my snipes did NOT bid last night (27/6/2008 WST Australia) and all four closed without another bid. :cry: |
|||
| Posted: Fri Jun 27, 2008 11:30 pm Post subject: first day using gixen and i get this response when i log in. |
|
| Warning: pg_connect() [function.pg-connect]: Unable to connect to PostgreSQL server: FATAL: too many connections for role "web" in /usr/local/apache2/htdocs/gixen/home_main.php on line 94
Warning: pg_freeresult(): supplied argument is not a valid PostgreSQL result resource in /usr/local/apache2/htdocs/gixen/home_main.php on line 99 Warning: pg_close(): supplied argument is not a valid PostgreSQL link resource in /usr/local/apache2/htdocs/gixen/home_main.php on line 102 The main server is not available at the moment. Please try again later. |
|
| Posted: Fri Jun 27, 2008 8:55 pm Post subject: |
|
| I will second the failing of autosnipe :(. | |
| Posted: Fri Jun 27, 2008 8:42 pm Post subject: Autosnipe still failing |
|
| Email sent. Autosnipe is still failing. But adding manually works fine.
Even with these glitches, I still won 5 out of 9 auctions today. Love Gixen! |
|
| Posted: Fri Jun 27, 2008 5:45 pm Post subject: |
|
| Sorry about that, the front-end server is recovered now, so I was moving things back from the backup server. This may have slowed down things a bit. If these problems persist, please email me with details (especially regarding api and/or autosnipe, I may have neglected this). | |
| Posted: Fri Jun 27, 2008 5:23 pm Post subject: Intermittent |
|
| Hey! Sorry to report, but I am still having intermittent problems trying to login, update or add items, and so on. Slightly different error messages, but similar.
Also, The Grease Monkey add a snipe extension failed today as well, said bad password, but that's wrong I can still login to GIXEN and eBay with the same password. Not sure, but it just started doing this a little while ago, was working finre before then. So then I went to adding times manually and now having problems there. I'll continue to struggle on and hope this gets resolved, but I am patient. I know these things can be hard to nail down. Good luck with it. I love Gixen! Bron |
|
| Posted: Fri Jun 27, 2008 2:33 pm Post subject: |
|
| I call that "upgrade", but in fact it means renting a new, more powerful server, often from a different hosting facility. This time, however, there will be no need to do that, as this problem was caused by failing hdd that was replaced in the meantime. | |
| Posted: Fri Jun 27, 2008 1:49 pm Post subject: |
|
| If you just upgrade your server, why IP changes? | |
| Posted: Thu Jun 26, 2008 8:43 pm Post subject: |
|
| I will keep looking at what happens with the front-end over the next few days. One reason I am hesitant in upgrading the front-end server is because IP address change results in drop on Google ratings, and it takes quite a bit for the rating to recover. I will have no choice however if this problem persists. | |
| Posted: Thu Jun 26, 2008 6:47 pm Post subject: |
|
| Probably, now I removed those two from the restricted list. I used to have a lot of problems with spammers so I got carried away with restrictions. | |
| Posted: Thu Jun 26, 2008 6:40 pm Post subject: SP AM Filter |
|
| Can't post messages containing the word F A T or even F A T A L???
Or even SP AM??? Hmmmm...a bit much, maybe? ;) |
|
| Posted: Thu Jun 26, 2008 6:33 pm Post subject: Still having problems. Here's errors from main login page.. |
|
| Warning: pg_connect() [function.pg-connect]: Unable to connect to PostgreSQL server: FA TAL: too many connections for role "web" in /usr/local/apache2/htdocs/gixen/home_main.php on line 94
Warning: pg_freeresult(): supplied argument is not a valid PostgreSQL result resource in /usr/local/apache2/htdocs/gixen/home_main.php on line 99 Warning: pg_close(): supplied argument is not a valid PostgreSQL link resource in /usr/local/apache2/htdocs/gixen/home_main.php on line 102 Gixen is still the best thing going! Has changed the way I eBay for sure. Bron Information The word fa t is on our list of sp am related words. Please refrain from posting this word. Your message: Warning: pg_connect() [function.pg-connect]: Unable to connect to PostgreSQL server: FA TAL: too many connections for role \"web\" in /usr/local/apache2/htdocs/gixen/home_main.php on line 94 Warning: pg_freeresult(): supplied argument is not a valid PostgreSQL result resource in /usr/local/apache2/htdocs/gixen/home_main.php on line 99 Warning: pg_close(): supplied argument is not a valid PostgreSQL link resource in /usr/local/apache2/htdocs/gixen/home_main.php on line 102 Gixen is still the best thing going! Has changed the way I eBay for sure. Bron |
|
| Posted: Thu Jun 26, 2008 4:49 pm Post subject: GIXEN front-end downtime this evening |
|
| Gixen front-end was down this evening between 5.30 pm and 5.45 pm PDT. No scheduled snipes failed because of this, as back-end was not affected. I am analyzing why this happened and may increase capacities soon.
I apologize for the inconvenience. |
|