Re: RL service crashing on Win2k3 when edir is stopped
(8.7.3 on

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Are you really on 8.7.3.0?  What version of IDM?  Can you reproduce
this?  Anything else about your driver that you can share like how long
it has been up, how the connection was broken, if heartbeat is involved,
if other drivers do the same thing in the RL on the same box, etc.?

There is a known issue in some rare cases where this can happen for
which a patch will be released any day now, but it's fairly difficult to
reproduce so the more details the merrier.

Good luck.





Lothar Haeger wrote:
| Have seen and posted this before but no solution so far:
|
| When stopping edir (or when ndsd crashes on my SLES9 IDM server)
sometimes the RL service on Win2k3 that runs the AD driver also stops.
Restarting edir of course does not restart the Windows service, so that
driver does not continue working automatically. Here's how the RL trace
looks like in that case:
|
| DirXML: [05/15/08 14:40:01.14]: ADDriver: object changes complete
| DirXML: [05/15/08 14:41:01.14]: ADDriver: Publisher Poll
| DirXML: [05/15/08 14:41:01.14]: ADDriver: get object changes - 0x0000
| DirXML: [05/15/08 14:41:01.14]: ADDriver: object changes complete
| DirXML: [05/15/08 14:42:01.14]: ADDriver: Publisher Poll
| DirXML: [05/15/08 14:42:01.14]: ADDriver: get object changes - 0x0000
| DirXML: [05/15/08 14:42:01.14]: ADDriver: object changes complete
| DirXML: [05/15/08 14:43:01.14]: ADDriver: Publisher Poll
| DirXML: [05/15/08 14:43:01.14]: ADDriver: get object changes - 0x0000
| DirXML: [05/15/08 14:43:01.14]: ADDriver: object changes complete
| DirXML: [05/15/08 14:43:58.07]:
| DirXML Log Event -------------------
|     Driver  =
\MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
|     Thread  = Connection Receiver
|     Level   = warning
|     Message = SSL protocol-violating EOF found or I/O error:
| DirXML: [05/15/08 14:43:58.07]:
| DirXML Log Event -------------------
|     Driver  =
\MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
|     Thread  = Subscriber Channel
|     Level   = error
|     Message = Connection was broken
| DirXML: [05/15/08 14:43:58.07]:
| DirXML Log Event -------------------
|     Driver  =
\MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
|     Thread  = Subscriber Channel
|     Level   = fatal
|     Message = Connection was broken
| DirXML: [05/15/08 14:43:58.16]:
| DirXML Log Event -------------------
|     Driver  =
\MUMMERT-META\de\mummert\hamburg\DIRXML_DRVSET01\DRV_DOM-ADMIN
|     Thread  = Subscriber Channel
|     Level   = error
|     Message = SSL protocol failure: error:140D00CF:SSL
routines:SSL_write:protocol is shutdown
| DirXML: [05/15/08 14:43:58.18]: Loader: Stopping driver
| DirXML: [05/15/08 14:43:58.19]: ADDriver: Driver::destroy
| DirXML: [05/15/08 14:43:58.19]: ADDriver: driver destroy without
publisher start
| DirXML: [05/15/08 14:43:58.24]: ADDriver: Driver::~Driver()
| DirXML: [05/15/08 14:43:58.39]: Loader: Waiting for DirXML to connect
on 'TCP server socket, port 8090, address localhost, using SSL'...
|
| From the trace it looks like the RL service would be waiting for a
reconnect now, but in fact it stopped a few seconds later. Windows event
log has the following:
|
|
| Event Type:	Error
| Event Source:	Service Control Manager
| Event Category:	None
| Event ID:	7034
| Date:		15.05.2008
| Time:		14:44:03
| User:		N/A
| Computer:	HAMBURGAD03
| Description:
| The DirXML Loader: C:\Program Files\Novell\RemoteLoader\ADDriver.dll
command: 8000 service terminated unexpectedly.  It has done this 1 time(s).
|
|
| Anyone else seeing this? Any known workaround or solution to the issue?
|
| Many Thanks, Lothar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFILELS3s42bA80+9kRAlX3AJ9r5R+Of6g0WDfGMXCAL1nr3ez3iACdHARS
4tof8Ugd+EAl5mPNSS6zCW4=
=JiSV

ab@novell.com wrote:

> Are you really on 8.7.3.0?  What version of IDM?  

8.7.3.10 (without the "a" so far), but I've seen it with 8739 as well,
IDM is 351, as is the RL. 

> Can you reproduce this?  

not on demand, but it happens every now and then, not only with the AD driver,
but with a custom developed DLL as well. Never seen it with a java based driver,
which makes me believe that it's a bug in the RL code specific to Windows native
driver shims.

> Anything else about your driver that you can share like how long
> it has been up, how the connection was broken, if heartbeat is involved,
> if other drivers do the same thing in the RL on the same box, etc.?

nothing too specific, this time it happened to an AD driver that is the only
instance on that box, but the custom driver I mentioned above runs on the same
machine beside about 10 other drivers (Notes, SAP UM, DelText, jdbc etc...). I
sometimes see that "SSL-violation EOF" stuff even when restarting a
driver that connects via SSL to a RL (in fact most of my drivers run remotely,
and all remote drivers use SSL)

> There is a known issue in some rare cases where this can happen for
> which a patch will be released any day now, but it's fairly difficult to
> reproduce so the more details the merrier.

what kind of known issue is that? Some more details might give me a hint on what
to look for on my machines...