I've just recently implemented TSM's new journaling service for AIX TSM clients (new with 5.3.3). We're running AIX 5.1 ML9 and TSM client 5.3.4.0. Following the instructions in the 5.3.4.0 readme, we set it up on one box, and immediately got the following in the nohup.out file:
11/13/06 13:56:49 Starting Tivoli Journal Based Daemon Kernel extension /opt/filepath/filepath was succesfully loaded, kmid=704df00 major no:36 devno:0x240000 kmid = 117759744 (0x704df00) successfully added device 0x240000 (36,0) success loaded mid[704df00] devno[2359296] mknod succeeded for /dev/filepath ...and crash! (The file /opt/filepath/filepath is a real file, but isn't referenced anywhere in our setup.) The other box we set up journaling on has an identical OS and TSM setup, and it crashed after a few minutes with the message: 11/13/06 13:22:47 Version 5, Release 3, Level 4.0 Last Update: Apr 11 2006 /usr/tivoli/tsm/client/ba/bin/tsmjbbd, /usr/tivoli/tsm/client/ba/bin, Prefs file: /usr/tivoli/tsm/client/ba/bin/tsmjbbd.ini, Journal dir: /journaldbs Journaled filespaces: /usr/grok/images 11/13/06 13:22:50 Bringing Journaled File System '/usr/grok/images' online: Journal Database : '/journaldbs/tsm_usr_grok_images.jdb' Notification Buffer Size : 0X020000 Preserve Journal On Exit : No Allow Deferred Start : No Defer Retry Interval : NA Log File System Errors : Yes 11/13/06 13:46:33 waitForClientToConnect(): Error Accepting Client connection on pipe '/tmp/tsmjbbd.pipe.jnlSessionMgr', NpConnect(:) rc=-190. 11/13/06 13:46:33 JnlSessionManager(): Error Accepting Client connection on pipe, NpConnect() rc=-190. 11/13/06 13:46:34 psMonitorThread(): exiting RC=0 . 11/13/06 13:46:52 Version 5, Release 3, Level 4.0 Last Update: Apr 11 2006 /usr/tivoli/tsm/client/ba/bin/tsmjbbd, /usr/tivoli/tsm/client/ba/bin, Prefs file: /usr/tivoli/tsm/client/ba/bin/tsmjbbd.ini, Journal dir: /usr/tivoli/dakserv1-jfs Journaled filespaces: /usr/grok/images 11/13/06 13:46:55 Bringing Journaled File System '/usr/grok/images' online: Journal Database : '/usr/tivoli/dakserv1-jfs/tsm_usr_grok_images.jdb' Notification Buffer Size : 0X020000 Preserve Journal On Exit : No Allow Deferred Start : No Defer Retry Interval : NA Log File System Errors : Yes 11/13/06 14:47:10 Version 5, Release 3, Level 4.0 Last Update: Apr 11 2006 /usr/tivoli/tsm/client/ba/bin/tsmjbbd, /usr/tivoli/tsm/client/ba/bin, Prefs file: /usr/tivoli/tsm/client/ba/bin/tsmjbbd.ini, Journal dir: /usr/tivoli/dakserv1-jfs Journaled filespaces: /usr/grok/images 11/13/06 14:47:13 Bringing Journaled File System '/usr/grok/images' online: Journal Database : '/usr/tivoli/dakserv1-jfs/tsm_usr_grok_images.jdb' Notification Buffer Size : 0X020000 Preserve Journal On Exit : No Allow Deferred Start : No Defer Retry Interval : NA Log File System Errors : Yes Anyone seen anything like this? -- Mark Stapleton ([EMAIL PROTECTED]) Senior TSM consultant
