How much space do you think I am going to need to dump? It said 57, but I ran
out of space at 85GB, so was it shooting for 114GB or so?
I have a feeling that when I imported my data from the IMAP server it was on,
some of the existing users had many layers and folders within the inbox
>Would a migrate deal with potential DB issues? If I did a migrate to the
new
>server platform, would it clear up the little DB issues? I have something
Honestly, it sounds like if you *don't* dump and load your db soon (either
using the migrate commands or whatever) you're going to have
Also, I am getting this many times in my logs as users log in:
>
>
>Aug 12 23:01:07 smcit citserver[599]: msgbase: CtdlFetchMessage(15796750, 1)
>Failed!
>
>Aug 12 23:01:07 smcit citserver[599]: msgbase: CtdlFetchMessage(15796750, 1)
>Failed!
>
>
>
>Aug 12 23:01:07 smcit citserver[599]:
Would a migrate deal with potential DB issues? If I did a migrate to the new
server platform, would it clear up the little DB issues? I have something
funny going on for a while about the BASEROOM being changed somehow by one of
my IMAP users and how they named the folder. I think I am still
Checking my logs, I get a lot of entries like this (emphasis added):
>
>
>Aug 12 17:21:14 smcit webcit[1200]: SSL started
>
>Aug 12 17:21:14 smcit webcit[1200]: GET /dotgoto?room=_MAIL_ HTTP/1.1
>
>*Aug 12 17:21:15 smcit webcit[1200]: ConditionalWholistExpanded() returns 0*
>
>
I tried the export, as it only said I needed 57GB to run it, and it ended up
filling my drive at 85 GB. Does it actually need 114GB to export a DB of
57GB?
> Sat Aug 12 2017 07:34:04 PM EDT from IGnatius T Foobar @ Uncensored
>Subject: Re: DB corruption
>
>I'm so sorry about the timing on
I'm so sorry about the timing on this, I only seem to have a couple of short
bursts of energy each day and I don't know when I will get them. If you can
get db_recover et al to run clean, you should be good, but if you have the
ability to do a full export, do the export.
Not sure if it was the right thing to do, but I just moved those log files
which were not current and were causing issues to a different directory, and
then ran db_recover etc again. Seemed fine. We will see.
> Fri Aug 11 2017 07:35:12 PM EDT from bennabiy @ Uncensored Subject: DB
>corruption