Offline database maintenence - Compact, fixup, updall,..

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Subject: Offline database maintenence - Compact, fixup, updall,..

Feedback Type: Problem

Product Area: Domino Server

Technical Area: Administration

Platform: Linux server

Release: 8.5.3

Reproducible: Unknown

Hello.
After migrating and upgrading Domino server from one machine to another we use a linux script that does maintenence on all LND databases.

What the script does is call Domino processes for compact, fixup and updall.

In all cases we had unitl now there were no errors until now.

Now these processes keep crashing with Panic: LookupHandle: null handle error appx. every 16 minutes. It doesn't make a difference what process is working. Panics on compact, fixup and updall.

19.01.2013 09:40:12 Compacting mail/xxx.nsf (xxx xxx), -D

Thread=[04772:00008-5725040]
Stack base=0x0057544C, Stack size = 2748 bytes
PANIC: LookupHandle: null handle
Stack base = 0x0057544c, Stack size = 4572 bytes
Fatal Error signal = 0x0000000b PID/TID = 4772/5725040

19.01.2013 09:56:12 Compacting mail/yyy.nsf (yyy yyy), -D

Thread=[10911:00008-9382768]
Stack base=0x008F244C, Stack size = 2748 bytes
PANIC: LookupHandle: null handle
Stack base = 0x008f244c, Stack size = 4572 bytes
Fatal Error signal = 0x0000000b PID/TID = 10911/9382768

19.01.2013 10:12:18 Compacting , -D

Thread=[15180:00008-2411376]
Stack base=0x0024C44C, Stack size = 2748 bytes
PANIC: LookupHandle: null handle
Stack base = 0x0024c44c, Stack size = 4572 bytes
Fatal Error signal = 0x0000000b PID/TID = 15180/2411376

19.01.2013 10:28:08 Compacting , -D

Thread=[21222:00008-4897648]
Stack base=0x004AB44C, Stack size = 2748 bytes
PANIC: LookupHandle: null handle
Stack base = 0x004ab44c, Stack size = 4572 bytes
Fatal Error signal = 0x0000000b PID/TID = 21222/4897648

19.01.2013 10:43:54 Compacting , -D

Thread=[25426:00008-3160944]
Stack base=0x0030344C, Stack size = 2748 bytes
PANIC: LookupHandle: null handle
Stack base = 0x0030344c, Stack size = 4572 bytes
Fatal Error signal = 0x0000000b PID/TID = 25426/3160944

Linux administrators say that there are no errors on OS level, no scheduled processes that could interfere with Domino processes.

Os: Red Hat Enterprise Linux Server release 6.1 (Santiago) (2.6.32-131.0.15.el6.x86_64 #1 SMP Tue May 10 15:42:40 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux)

HW: IBM System x3650 M4 -[7915E3G]
4x Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
24 GB RAM

ulimit
notes soft nofile 20000
notes hard nofile 49152
notes soft nproc 12500
notes hard nproc 12500

Lotus Domino (r) Server (Release 8.5.3HF636 for UNIX) 22.01.2013 12:49:37
Server name: xxx
Domain name: xxx
Server directory: /local/notesdata
Partition: .local.notesdata
Elapsed time: 2 days 16:59:04
Transactions/minute: Last minute: 821; Last hour: 37; Peak: 17755
Peak # of sessions: 116 at 22.01.2013 08:53:53
Transactions: 1269109 Max. concurrent: 120
ThreadPool Threads: 100 (TCPIP Port)
Availability Index: 100 (state: AVAILABLE)
Mail Tracking: Not Enabled
Mail Journalling: Not Enabled
Number of Mailboxes: 1
Pending mail: 0 Dead mail: 0
Waiting Tasks: 0
DAOS: Enabled
Transactional Logging: Enabled
Fault Recovery: Enabled

Any ideas what could be causing the problem? We have suggested our customer checks RAM modules.
We will try upgrading server to FP3 first, because we have implemented a special hotfix 636 which I doubt could be the reason, but will still try FP3 first.

Feedback number AJUG947FM6 created by ~Dexter Minponeskiynds on 01/22/2013

Status: Open
Comments: