Internal Server ErrorThe server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application. Is there a different site to search ProFox archives?I keep getting this error. Philip B.Vicksburg, MI ____________________________________________________________ Sponsored by https://www.newser.com/?utm_source=part&utm_medium=uol&utm_campaign=...
In This State, the Party's Over http://thirdpartyoffers.netzero.net/TGL3241/5efd0fab5712ffab2dbcst02duc1 Fox Anchor Out Amid Sexual Misconduct Accusations http://thirdpartyoffers.netzero.net/TGL3241/5efd0fab73108fab2dbcst02duc2 Doomed Groom May Have Infected 100 at His Wedding http://thirdpartyoffers.netzero.net/TGL3241/5efd0fab8e3c9fab2dbcst02duc3
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
On Jul 1, 2020, at 17:34, Philip Borkholder plborker@netzero.net wrote:
Internal Server ErrorThe server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application. Is there a different site to search ProFox archives?I keep getting this error.
Looks like an update to the Elasticsearch backend. Let me investigate.
-- Ed Leafe
On Jul 1, 2020, at 17:48, Ed Leafe ed@leafe.com wrote:
Looks like an update to the Elasticsearch backend. Let me investigate.
Turned out to be a bit of corruption in the index. Should be working fine now!
And thanks for letting me know!
-- Ed Leafe
On 7/2/2020 7:44 AM, Ed Leafe wrote:
On Jul 1, 2020, at 17:48, Ed Leafe ed@leafe.com wrote:
Looks like an update to the Elasticsearch backend. Let me investigate.
Turned out to be a bit of corruption in the index. Should be working fine now!
And thanks for letting me know!
-- Ed Leafe
What's the database managing all of this, Ed?
On Jul 2, 2020, at 7:25 AM, MB Software Solutions, LLC mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
On Jul 1, 2020, at 17:48, Ed Leafe ed@leafe.com wrote:
Looks like an update to the Elasticsearch backend. Let me investigate.
Turned out to be a bit of corruption in the index. Should be working fine now!
And thanks for letting me know!
-- Ed Leafe
What's the database managing all of this, Ed?
I mentioned it above: Elasticsearch
-- Ed Leafe
-
Ed Leafe -
MB Software Solutions, LLC -
Philip Borkholder