Error [C01B], updating index

Hi,

for a few users there are permanently messages like these in the POA's log:

Error [C01B], updating index: userp48.db, 59107


I wonder if I can ignore them, or if there is a problem to be addressed?

I tried to rebuild the index (7012997), but while the index is rebuild the message appears again. The numbers at the end of the error message are always the same, so I guess they indicate a position within the user database. I found that C01B has to do with invalid characters - so probably there is a character in the user database, that quickfinder does not like? Then this does not mean that the user database itself has a problem? There is just one item missing in the index?

Is this reasoning correct or just wishful thinking?

Thanks,
Mirko

Tags:

  • In article <mguldner.8xkopb@no-mx.forums.microfocus.com>, Mguldner wrote:
    > > Error [C01B], updating index: userp48.db, 59107

    >
    > I wonder if I can ignore them, or if there is a problem to be
    > addressed?
    >
    > I tried to rebuild the index (7012997), but while the index is rebuild
    > the message appears again. The numbers at the end of the error message
    > are always the same, so I guess they indicate a position within the user
    > database. I found that C01B has to do with invalid characters - so
    > probably there is a character in the user database, that quickfinder
    > does not like? Then this does not mean that the user database itself has
    > a problem? There is just one item missing in the index?


    I wouldn't ignore it as it could be a part of or hiding a bigger issue.
    It could also be preventing that user's mail from being indexed any
    further.
    I would look closely at the structurally and then content GWChecks for
    this user to make sure they are running clear or give better clues as to
    what is going on.
    I'm assuming you already have a full preventative maintenance set of
    GWChecks running similar to
    http://KonecnyConsulting.ca/gw/gwmnt.html
    If not that is a place to start.

    The POA logs in verbose mode, you can see how many messages to be indexed
    in the lines like
    Updating QuickFinder index: userp48.db (###)
    where the number in the brackets tells you how messages let to deal with
    and that should generally be less than the number of messages received in
    a day.


    Andy of
    http://KonecnyConsulting.ca/gw in Toronto
    Knowledge Partner
    https://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

  • Hi Mirko,

    You might have to manually delete the index files associated with the user account and then rebuild the index.

    https://support.microfocus.com/kb/doc.php?id=7022175

    Cheers,
  • Yes, thanks to your help in an earlier thread I have set up the maintenance tasks. Unfortunately I don't find the time to check and compare the logs regularly...

    I have checked the logs again... currently there are 4 accounts that are permanently throwing C01Bs into ther log.

    For all of them the value in brackets goes down to 1 or 2.

    Structure, Content checks:

    user1: no error in structure, all content errors corrected in second run
    user2: only error 39 in structure, no error in content
    user3: no error in structure, all content errors corrected in second run
    user4: no error in structure, all content errors corrected in second run

    Thanks,
    Mirko
  • In article <mguldner.8xvn8n@no-mx.forums.microfocus.com>, Mguldner
    wrote:
    > Yes, thanks to your help in an earlier thread I have set up the
    > maintenance tasks. Unfortunately I don't find the time to check and
    > compare the logs regularly...


    Your welcome, always glad to help that way. Checking the results is
    always a challenge, but having them run without checking is better than
    not having them run. This way you have the results ready to look at
    when you do find a problem.

    So this error is still just in the POA logs. Have you been able totally
    recreate the indexes as per the TID Laura posted? And if so is the
    error still happening?

    A thought, what languages are both the server and your GroupWise
    running at? Matching I hope, otherwise that might be a part of the
    issue.

    Next steps might be a structural rebuild of the users (NOT a recreate)
    with another rebuild of their indexes.


    If it is still happening after that, then an SR might be needed to get
    to root of this.


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    https://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

  • Hi Laura,

    laurabuckley;2497538 wrote:


    You might have to manually delete the index files associated with the user account and then rebuild the index.

    https://support.microfocus.com/kb/doc.php?id=7022175


    I re-checked this: it makes not difference if I delete the files before doing a "Structural Rebuild" and then "Update and Compress Indexes" in HTTP Console: during this first indexing run the same "C01B"-messages are in the log file. The messages are exactly the same - same number of messages and same numbers within the messages - as in every days quickfinder run:

    Daily Quickfinder:

    0402poa.003:01:02:03 48C1 Updating QuickFinder index: usercn4.db (3)
    0402poa.003:01:02:03 48C1 Error [C01B], updating index: usercn4.db, 25583
    0402poa.003:01:02:03 48C1 Error [C01B], updating index: usercn4.db, 25655
    0402poa.003:01:02:03 48C1 Updating QuickFinder index: usercn4.db (3)
    0402poa.003:01:02:03 48C1 Error [C01B], updating index: usercn4.db, 25583
    0402poa.003:01:02:03 48C1 Error [C01B], updating index: usercn4.db, 25655


    Reindexing:

    gw2a:/media/nss/PO2/groupwise/agents/log/gw_po-og.poa # grep -i c01b 0415poa.02*
    0415poa.027:15:35:34 E70E Error [C01B], updating index: usercn4.db, 25583
    0415poa.027:15:35:36 E70E Error [C01B], updating index: usercn4.db, 25655
    0415poa.028:15:49:26 E70E Error [C01B], updating index: usercn4.db, 25583
    0415poa.028:15:49:26 E70E Error [C01B], updating index: usercn4.db, 25655

    Thanks,
    Mirko
  • konecnya;2498235 wrote:
    In article <mguldner.8xvn8n@no-mx.forums.microfocus.com>, Mguldner
    wrote:
    So this error is still just in the POA logs. Have you been able totally
    recreate the indexes as per the TID Laura posted?


    I re-checked this today (please see my answer to Laura): same messages when doing the first indexing after deleting the files.


    And if so is the error still happening?


    Currently I only see the error for one user; I don't see the error any more for the four other users, where it had been in the logs until recently. I don't know why it has disappeared - the simplest explanation might be, that the users have deleted the problematic messages from their mailboxes.


    A thought, what languages are both the server and your GroupWise
    running at? Matching I hope, otherwise that might be a part of the
    issue.


    Hm, simple question - but I struggle to answer it. What language setting do you have in mind? These are the ones I can come up with:

    - GroupWise Post Offices: all "German - German"
    - POA: --language EN
    - SLES: yast languages: Primary Language: "English (US)"


    Next steps might be a structural rebuild of the users (NOT a recreate)
    with another rebuild of their indexes.


    Structural Rebuild was already part of the recreation of the index...

    Thanks,
    Mirko
  • In article <mguldner.8yjtlz@no-mx.forums.microfocus.com>, Mguldner
    wrote:
    > - GroupWise Post Offices: all "German - German"
    > - POA: --language EN
    > - SLES: yast languages: Primary Language: "English (US)"


    I guess worried that umlauts could be tripping things up give that
    English doesn't have them (just like English doesn't have the proper
    characters for my family name in it's original Czech)

    normally we don't bother telling the POA what language to run as and
    let it take its guidance from the Post Office definition. This might
    be worth opening an SR on focused on the original error and include
    this difference in language setting in the details with the question of
    if that can cause problems.
    I'm not sure about changing that setting part way through the use of a
    system. At the very least it is a POA stop/start to make the edit of
    that config file active.


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    https://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

  • Hi Mirko,

    You are "grepping" only on the error thus eliminating other information. On the lines after the error is there reference to a specific email?

    Cheers,
  • laurabuckley;2498401 wrote:

    You are "grepping" only on the error thus eliminating other information. On the lines after the error is there reference to a specific email?


    There a two lines after the error which refer to the mail:

    0415poa.036:21:00:42 F644 Error [C01B], updating index: usercn4.db, 25583
    0415poa.036-21:00:42 F644 From: <Name edited>
    0415poa.036-21:00:42 F644 Date: 04/16/2015 10:24:38
    0415poa.036:21:00:42 F644 Error [C01B], updating index: usercn4.db, 25655
    0415poa.036-21:00:42 F644 From: <Name edited>
    0415poa.036-21:00:42 F644 Date: 04/21/2015 08:16:18

    I asked user 'cn4' if there is anything special about that mail, or if there are any problems - nothing, no problems. I think for now I will not spent more time on this topic, just monitor from time to time if the number of errors increases.

    Thanks,
    Mirko
  • Hi Mirko,

    Probably find the sender of the email has some contacts in their Frequent Contacts where there are unnecessary spaces after the email address. If you go to user 'cn4' and look at the properties of the email it should be evident there.

    Cheers,