I keep getting the error message in various places in the message center, in four configurations:

• Error message, nothing else;
• Header and left sidebar, error message, nothing else;
• Header, LSB, main thread listing, error message, no right sidebar;
• Error message and everything, except COMM, Nillytown, etc.

Does this mean the message center is using four separate connections every time it's displayed?

I keep getting the error message in various places in the message center, in four configurations:

• Error message, nothing else;
• Header and left sidebar, error message, nothing else;
• Header, LSB, main thread listing, error message, no right sidebar;
• Error message and everything, except COMM, Nillytown, etc.

Does this mean the message center is using four separate connections every time it's displayed?

ita checked. It's still 5 minutes.

ita checked. It's still 5 minutes.

ita checked. It's still 5 minutes.

Anything we can do right now? I guess the hope is that there was a change made on the server which can be fixed or reversed, right?

We really should have somewhere we can display a status message -- one like:

"We know about the max_connections message, please be aware there will be many skipped message numbers, working on it."

I've looked at the daily numbers, and we must have been hitting over our max_connections every damned moment. Here's the table for the month:

Hourly Statistics for September 2003

Hour Hits Files Pages KBytes Avg Total Avg Total Avg Total Avg Total

0549120891.21%38183871.29%388421.10%63581398851.19% 131669650.69%21146550.71%235100.67%3774830360.70% 223251040.51%16336010.55%214630.61%2860629150.53% 332671880.72%23351290.79%286320.83%4425973580.83% 4576126771.26%36981271.25%5111331.49%72341591561.35% 5778171281.71%490107981.66%7115752.07%95462100081.78% 61247274532.74%799175972.70%9921922.88%162903583743.04% 72067454844.54%1395306964.71%17338064.99%258885695334.83% 82904638926.37%1994438846.73%22148626.38%342197528176.38% 93306727527.26%2247494397.58%25656477.41%384558460207.17% 103393746577.45%2222488957.50%26558417.66%399498788887.45% 113636800027.98%2299505787.76%27660807.98%428219420717.98% 123470763537.61%2185480907.38%25856767.45%408558988107.62% 133598791747.90%2362519727.97%28562848.24%432599517008.06% 143074676366.75%1984436606.70%23752246.85%348007655956.49% 152579567455.66%1582348255.34%19342505.58%297056535065.54% 162226489834.89%1394306714.70%17237894.97%252355551764.70% 171898417584.16%1186260944.00%14732384.25%218444805764.07% 181851407284.06%1219268314.11%13630083.95%224694943174.19% 192097461354.60%1334293534.50%14030864.05%241975323334.51% 201862409784.09%1195262974.03%11826163.43%205284516083.83% 211502330503.30%986216953.33%10322692.98%171123764623.19% 221220268452.68%810178352.74%8719242.52%140533091632.62% 23859189141.89%588129411.98%5812801.68%105162313601.96%

We really should have somewhere we can display a status message -- one like:

"We know about the max_connections message, please be aware there will be many skipped message numbers, working on it."

I've looked at the daily numbers, and we must have been hitting over our max_connections every damned moment. Here's the table for the month:

Hourly Statistics for September 2003

Hour Hits Files Pages KBytes Avg Total Avg Total Avg Total Avg Total

0549120891.21%38183871.29%388421.10%63581398851.19% 131669650.69%21146550.71%235100.67%3774830360.70% 223251040.51%16336010.55%214630.61%2860629150.53% 332671880.72%23351290.79%286320.83%4425973580.83% 4576126771.26%36981271.25%5111331.49%72341591561.35% 5778171281.71%490107981.66%7115752.07%95462100081.78% 61247274532.74%799175972.70%9921922.88%162903583743.04% 72067454844.54%1395306964.71%17338064.99%258885695334.83% 82904638926.37%1994438846.73%22148626.38%342197528176.38% 93306727527.26%2247494397.58%25656477.41%384558460207.17% 103393746577.45%2222488957.50%26558417.66%399498788887.45% 113636800027.98%2299505787.76%27660807.98%428219420717.98% 123470763537.61%2185480907.38%25856767.45%408558988107.62% 133598791747.90%2362519727.97%28562848.24%432599517008.06% 143074676366.75%1984436606.70%23752246.85%348007655956.49% 152579567455.66%1582348255.34%19342505.58%297056535065.54% 162226489834.89%1394306714.70%17237894.97%252355551764.70% 171898417584.16%1186260944.00%14732384.25%218444805764.07% 181851407284.06%1219268314.11%13630083.95%224694943174.19% 192097461354.60%1334293534.50%14030864.05%241975323334.51% 201862409784.09%1195262974.03%11826163.43%205284516083.83% 211502330503.30%986216953.33%10322692.98%171123764623.19% 221220268452.68%810178352.74%8719242.52%140533091632.62% 23859189141.89%588129411.98%5812801.68%105162313601.96%

Should we go to peoplesforum for awhile and see if it still happens?

The page is displaying only posts 4994, 4999, 5002, 5006, 5007, 5008, 5009, 5011, 5014, 5015, 5018, 5019, with 5019 being the last post.

Many of us have tried to submit posts, only to have it fail during the "post message" process. The thought above, is that if it fails after the number is assigned, the post still doesn't get posted, but the board considers that number assigned.

Someone said it better upstream, Jon. I think it was Liese.