Scalix Forums

Hi

Scalix seems to be running fine, and I'm not getting any complaints from users, but the error logs are full of two types of warning.

The first is:


This seems to be the result of 'check names' on SWA attempting to access a folder called 'My Contacts' which doesn't exist. Of course, the contacts folder on Scalix is called 'Contacts', not 'My Contacts'. I get this error for a number of different users.

The second most common warning is:


This looks like SWA is sending a null date. How do I stop this?

In both cases the clients are running SWA and don't complain about errors. However, I like to see nice clean logs and am keen to fix these two Warnings.

Any ideas??

peteb wrote:Hi

Scalix seems to be running fine, and I'm not getting any complaints from users, but the error logs are full of two types of warning.

The first is:

Code: Select all

WARNING                        LDAP Daemon   (LDAP Engine   ) 01.13.06 11:39:47
[OM 16065] The requested Directory does not exist.

        -> deng_doSearch
        -> dr_ACIModContextFlags
        <- dr_ACIModContextFlags
        -> dr_ACICheckReadPerm
        <- dr_ACICheckReadPerm
        -> dr_ACIModContextFlags
        <- dr_ACIModContextFlags
        <- deng_doSearch
        -> im_CrNewTempItem
        -> im_GetNewTempItemNum
        <- im_GetNewTempItemNum
        <- im_CrNewTempItem
        -> im_ItemRef2FName
        <- im_ItemRef2FName
        <- /build/9.4.0.9/src/lib/ombase/dr/dr_opendir.c:399[3,16065]
        <- /build/9.4.0.9/src/lib/ombase/dr/dr_opendir.c:542[3,16065]


This seems to be the result of 'check names' on SWA attempting to access a folder called 'My Contacts' which doesn't exist. Of course, the contacts folder on Scalix is called 'Contacts', not 'My Contacts'. I get this error for a number of different users.

The second most common warning is:

Code: Select all

WARNING                        IMAP Server Da(IMAP Server Pr) 01.03.06 11:58:17
[OM 10024] Date and time value "" in the XML for an application/scalix-properties
body part is not of a recognised format.
Time set to start of 1st January 1970.
User Name: xxx xxx / renoir, aramoko/CN=xxx, xxx
  Last Msg Subject: xxx
  Last Msg Sender: xxx/xxx///renoir/aramoko//////////////////%xxx, xxx%%%//"
  Last Msg Id: 8648283.11362894969
  Last Ct RecNo: 0


This looks like SWA is sending a null date. How do I stop this?

In both cases the clients are running SWA and don't complain about errors. However, I like to see nice clean logs and am keen to fix these two Warnings.

Any ideas??

Hello,

when you say your log is full of those, do you mean that every time a SWA user checks the directory an entry is logged? If so, what is the content of your partner.xml ?

The directory is called MyContacts, that is definately correct.

Please post the content of partner.xml here.

Thanks,

Sascha.

The reason I thought the problem was MyContacts, was from the Jakarta logs.

See below



However on re-reading this message could be saying that MyContacts is the only available directory. If so, how do I find out what it is looking for?

Which is correct?

Can you check /var/opt/scalix/sys/slapd.conf. It should contain the following:

Cheers

Dave

Yep it's all there.

Quite alot of my users use subfolders below 'Contacts'. These were set up using exchange. Could these be causing the SWA probs?

Oops

When I say Exchange, I mean Outlook...

Hi,

o=MyContacts is a fixed name - the Scalix LDAP server is actually mapping this special name to the primary Contacts folder of the authenticated user. The folder should have been created first time you logged into Scalix with that user using either Outlook or SWA.

Now, one question to ask is if this also happens with a new user account and SWA. If not, we might be looking at a folder data problem here - you want to make sure that the Contacts folder was properly initialized before you import any data - again, to make sure this is the case, I believe you should be logging in with either Outlook or SWA before making any imports through outlook express or so.

If it also happens with fresh and new users, either your partner.xml setting is broken or your server config is wrong.

To reset partner.xml, i would suggest uninstallating SWA using the Scalix installer, removing partner.xml, then reinstalling just this component. If you use the custom mode of the installer, no data will be affected.

One relatively common thing is that another LDAP server listens on port 389 on your machine and prevents the Scalix ldap server from starting properly.

The way to check this is to do an
netstat -anp | grep 389
and checking the process name at the end of the LISTEN line for port 389 - it should read omldapd. If anything else listens on the port, you will see a error state on the Scalix ldap server when you check it with omstat -a and also should see some error message on Scalix startup in omshowlog.

You would need to reconfigure your other LDAP server as Scalix LDAP must currently run on port 389 or SAC will not function correctly. This will change in a future release.

Cheers,
Florian.