Scalix Forums

Hi,

I have the following output from omscan -Aavfx - names changed to protect the inocent:

Missing children ....

Owner Info : John Smith / allpay/CN=John Smith
Parent Container : ~/data/00000ip/00e2j3l:1, RecNum : 0
Missing Child : ~/data/00000ip/00e2j1r:1
Child Type : Transaction file.
Child Creator : Joe Bloggs /allpay/CN=Joe Bloggs
Child Subject : FW: PLEASE PASS ON ~ EVEN TO ME!

Owner Info : John Smith / allpay/CN=John Smith
Parent Container : ~/data/00000ip/00e2j3l:1, RecNum : 0
Missing Child : ~/data/00000ip/00e2j1r:4
Child Type : Data Item.
Child Creator : Joe Bloggs /allpay/CN=Joe Bloggs
Child Subject : FW: PLEASE PASS ON ~ EVEN TO ME!

Owner Info : John Smith / allpay/CN=John Smith
Parent Container : ~/data/00000ip/00e2j3l:1, RecNum : 1
Missing Child : ~/data/00000ip/00e2j1r:3
Child Type : Transaction file.
Child Creator : Joe Bloggs /allpay/CN=Joe Bloggs
Child Subject : MAPI-1 Distribution List

Bad extensions ....

Owner Info : David Archer / allpay/CN=David Archer
Parent Container : ~/user/g000078/0000003:1, RecNum : 1527
Child Affected : ~/data/0000041/00gunno:1
Child Subject : FW: FW:

Everything else is fine. I have ran this a few times now and these are still there bugging me. It takes around 2 hours to run a full omscan on this busy server.

Any suggestions?
Thanks.
Andrew.

Hi,

It is possible that some of these missing children come from scanning messages sitting on queues where the fix mode may not have the desired effect. Try 'omscan -Avxq' to see if that is the case. Failing that, check log for any relevant error (omshowlog) and/or run omscan against just the user that has the problem which should be faster to see if the problem can be isolated further.

Regards,
Danny

Hi.

I have ran the command to check the queues and there was no error. All the queues are empty. Is there anything I need to look for in the log - do I look for this after running the specific omscan?

Thanks.
Andrew.

Yes do the omshowlog after the usual omscan run to see if anything is reported by Omscan to see if it might have tried, but failed, to fix the problem - hence the problem does not go away. Note you could narrow the scope to just the user in question to reduce run time.

Danny

Hi,

Further to this, I have just completed a scan of the users listed in those errors, and all have come back with no issues.

Andrew.

Hi,

I ran the omscan again last night and now get the following output:

Checking/Scanning message lists .... done.
Scanning name directories .... done.
Scanning temp domain .... done.
Checking/Scanning message queues .... done.

Missing children ....

Owner Info :
Parent Container : ~/user/g00009o, RecNum : 0
Missing Child : ~/user/g00009o/00000v8
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00009o, RecNum : 1
Missing Child : ~/user/g00009o/0000001
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00009o, RecNum : 2
Missing Child : ~/user/g00009o/0000002
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00009o, RecNum : 3
Missing Child : ~/user/g00009o/0000003
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00009o, RecNum : 4
Missing Child : ~/user/g00009o/0000004
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00009o, RecNum : 5
Missing Child : ~/user/g00009o/0000005
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00008n, RecNum : 0
Missing Child : ~/user/g00008n/00000v8
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00008n, RecNum : 1
Missing Child : ~/user/g00008n/0000001
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00008n, RecNum : 2
Missing Child : ~/user/g00008n/0000002
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00008n, RecNum : 3
Missing Child : ~/user/g00008n/0000003
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00008n, RecNum : 4
Missing Child : ~/user/g00008n/0000004
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00008n, RecNum : 5
Missing Child : ~/user/g00008n/0000005
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00009n, RecNum : 0
Missing Child : ~/user/g00009n/00000v8
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00009n, RecNum : 1
Missing Child : ~/user/g00009n/0000001
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00009n, RecNum : 2
Missing Child : ~/user/g00009n/0000002
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00009n, RecNum : 3
Missing Child : ~/user/g00009n/0000003
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00009n, RecNum : 4
Missing Child : ~/user/g00009n/0000004
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Owner Info :
Parent Container : ~/user/g00009n, RecNum : 5
Missing Child : ~/user/g00009n/0000005
Child Type : Container.
Child Creator : ********
Child Subject : User Folder.

Disk usage ....

Those directories in the user directory don't exist, and running the command for example:

omshowu -O $((32#90))

Brings back no such user. I am running omscan again in the same mode to see if it fixes the issue.

On another tack, does anyone know a way of getting the omscan server to do a scan on a Saturday instead of a tuesday? In the omscan configuration file, it is set to do a scan everyy 7 days,, but this happens currently on a Tuesday.

Thanks.
Andrew.

Hi,

The latest missing children errors may have been caused by some aborted attempts to create users in the past. There may be some error logged (omshowlog) or in the fatal.log to confirm that. Clearing out these errors may require manual steps to remove files in the ~/user directory.

As for the omscan scheduling, the next release will support more flexibility. In the mean time the way to impose a Saturday start time is as follows:
-stop omscan server (omoff -d0 omscan) and keep it off until Saturday
-clear out the current scan result (omscan -Z)
-on Saturday at the required time start omscan server (omon omscan)
-when finished it should pause until next Saturday and repeat the cycle

Regards,
Danny

Hi,

Thanks for your continued help. I have now actually found the relevant directories in /user/g0009o and /user/u0009o and 00009n respectively. In the U directory there is nothing, and in the G directory there is an ACL file. Can these be safely archived?

Thanks.
Andrew.

Yes - archive them off and run omscan again to double check.

Hi,

We now have a clear message store! Thanks for your help in this.

Andrew.