Errors and other log messages

MailServer

Please send me more! I need explainations for all the errors that confuse customers.
Error log: Messages appearing in the error.log
[19/Aug/2005 08:26:48] php_utils.cpp: webmail forceDelete: Folder error (~spiff@kerio.com/INBOX: invalid uid: 218)

IMPACT: HARMLESS: Only reporting is done, nothing is wrong.

Steps to reproduce this log message:

  1. Open 2 webmail sessions
  2. Delete a message in one webmail session
  3. Try to delete it in the other webmail session
[22/Aug/2005 11:33:31] php_utils.cpp: webmail createFolder: Unable to create folder (~spiff@kerio.com/INBOX/test; reason: 1)

IMPACT: HARMLESS: Only reporting is done, nothing is wrong.

Steps to reproduce this log message:

  1. In webmail, create a folder that already exists.
[22/Aug/2005 11:36:06] php_utils.cpp: webmail openFolder: Cannot open folder (~spiff@kerio.com/INBOX/test of type 0)

IMPACT: HARMLESS: Only reporting is done, nothing is wrong.

Steps to reproduce this log message:

  1. Delete a folder from one webmail session
  2. Click on the folder in the other webmail session
[22/Aug/2005 11:50:44] php_utils.cpp: webmail deleteFolder: Unable to delete folder (~kwhittaker@us.kerio.com/INBOX/test; reason: 1)

IMPACT: HARMLESS: Only reporting is done, nothing is wrong.

Steps to reproduce this log message:

  1. In 2 webmail sessions, choose delete, but do not choose "OK" when it prompts you.
  2. Now, go to each one and select "OK" and the error will occur

[27/Jan/2006 11:25:53] php_utils.cpp: webmail openFolder: Cannot open folder (~joeuser@usershack.com/Tasks of type 3)

IMPACT: BROKEN: A folder type is wrong.

This error is reported because the folder type specified in the status.fld is wrong. Tasks is supposed to be type 3, but if you open the status.fld for that folder, it is T0.

Here is the status.fld file:

See, the T0 should be a T3

This can happen to any special folder. The correct types are as follows:

T0 Normal email
T1 Contacts
T2 Calendar
T3 Tasks
T4 Journal
T5 Notes

[29/Aug/2005 15:56:22] mail_folder.cpp: Cannot open synchronization file C:\Program Files\Kerio\MailServer\store/mail/emua.local/spiff/untitled folder/sync.fld: File not found!

IMPACT: ANNOYANCE: No symptoms seem to occur. Users do not notice anything broken.

Simply create a folder in Entourage and it will soon log a message like this for the folder.

Sometimes customers report that the error repeats forever. The cause of this is unknown. Please tell kwhittaker if you find the cause of repeated sync.fld messages for one folder.

[23/Aug/2005 16:52:34] spamassassin.cpp: SpamAssassin check of message file C:\Program Files\Kerio\MailServer\store/queue/27/430b8c90-0000001d.eml failed: NULL result returned

IMPACT: BROKEN: Spamassassin is completely broken and needs to be re-installed as per the instructions below.

This error echoes on the console from which KMS was started. Usually it can only be seen from OSX or Linux if KMS was started from a terminal.

This error appears when using incorrect spamassassin.dll library in KMS. It seems that there is still an old library from previous version. Repair option during the installation would solve it.

Cannot open bayes databases /Volumes/XRaid_Mail/keriodata/spamassassin/bayes/bayes_* R/W: lock failed: File exists

IMPACT: BROKEN: It is possible BAYES will not work correctly.

This error echoes on the console from which KMS was started. Usually it can only be seen from OSX or Linux if KMS was started from a terminal.

The error means that the SpamAssassin engine is trying to create a lock for read/write access to the bayes database. The lock is a regular file stored in /store/spamassassin/bayes/<computername>.lock. It shouldn’t happen under normal conditions but the lock may remain locked after some bad KMS crash.

The solution is to stop KMS and delete the lock file.

[12/Jan/2006 07:14:04] mail_folder.cpp: Index error in folder ~jdoe@somecompany.com/INBOX: The database disk image is malformed
[12/Jan/2006 07:14:05] mail_folder.cpp: Index error in folder ~jdoe@somecompany.com/INBOX: Insertion failed because database is full

Impact: BROKEN: It is possible searching doesn't work correctly for this user.

This error is reported by search indexing engine (sqlite database). Deleting of the search.fld file should fix this.

Deleting status.fld fixes this, but can break other things. This should only be done as a last resort. Try deleting search.fld first.

[08/Mar/2006 07:36:47] httpserver.cpp: PHP Fatal error: Call to a member function on a non-object in d:\kerio\mailserver\webmail\default\mail.inc on line 246
[08/Mar/2006 07:36:57] httpserver.cpp: PHP Fatal error: Call to a member function on a non-object in d:\kerio\mailserver\webmail\default\mail.inc on line 246

Impact: HARMLESS: DSN might not be received, but most people don't use these emails anyways.

See bug 15599, comment 6 (duplicate to bug 9464)

This error message appears in the log if some user receives an error message from Mail Delivery Subsystem (DSN report) with message/rfc822-headers attachment. This message cannot be viewed in WebMail and is displayed as a blank. As you can see, this error is almost harmless.

PHP Fatal error: Call to a member function on a non-object in c:\program files\kerio\mailserver\webmail\default\calendar.inc on line 48

IMPACT: HARMLESS: Something is wrong in the code, but nothing serious happens to the user or mailserver.

How to create this log message (see bug 15781):

  1. switch to list view in any calendar folder
  2. create two calendar events
  3. select both events
  4. press "Delete" key

It is also possible to produce this log message from mail and contact folders. Steps are not provided here.

[09/Mar/2006 12:57:46] dav_fldMsgHandler.cpp: SEARCH: User jschmoe@example.com is trying to access an event message without VEvent structure: /usr/local/kerio/mailserver/store/mail/example.com/jschmoe/Calendar/00000af1.eml

IMPACT: BROKEN: The message is not really a Calendar item or is corrupted.

This message appears when KMS fails parsing the calendar event. The file may be corrupted or more probably it’s another kind of message (email, contact, etc.)

Winroute

Error log: Messages appearing in the error.log
Unable to sync SIC to DB.
OrangeWeb filter has expired. OrangeWeb filter comes with a 60 day trial. Sometimes customers are alarmed when it expires. Inform them that it requires an additional license and is not included with the base Winroute license. If you look in Content Filtering->HTTP Policy->ISS OrangeWeb Filter, you should see a line of text that says "ISS OrangeWeb Filter subscription ticket is not valid, categorization is disabled."