Fathom Startup Failed

[dlangschied]

I installed OE 11.6 a couple of months ago. Now Fathom is failing to startup. I am including the failure from admserv.log. It seems to be having and issue with database.ocf. I do not know what happened, but I need to know what to do to fix it.

Regards,
David

[2015/12/14@20:30:46.776-0500] [3] [Fathom-GRAPH] Opening OpenEdge Management activity database: plocal:C:\OpenEdge\wrk_oemgmt\cachedata\cachedb (17889)

[2015/12/14@20:30:46.782-0500] [3] [STDERR] Dec 14, 2015 8:30:46 PM com.orientechnologies.common.log.OLogManager log
[2015/12/14@20:30:46.782-0500] [3] [STDERR] WARNING: segment file 'database.ocf' was not closed correctly last time

[2015/12/14@20:30:46.787-0500] [0] [Fathom] * Error starting Fathom probe: "Error loading the activity database: Error opening OpenEdge Management activity database: C:\OpenEdge\wrk_oemgmt\cachedata\cachedb, Reason: Cannot open local storage ''C:/OpenEdge/wrk_oemgmt/cachedata/cachedb'' with mode=rw" (10148)
[2015/12/14@20:30:46.791-0500] [0] [*UnexpectedError*] * recorded as exception #1 in file ads0.exp.
[2015/12/14@20:30:46.791-0500] [3] [Fathom] Stopping Fathom probe. (10149)
[2015/12/14@20:30:46.791-0500] [3] [Fathom] Stopping Fathom project. (10152)
[2015/12/14@20:30:46.791-0500] [3] [Fathom] Waiting for active work threads to complete. (11218)
[2015/12/14@20:30:46.791-0500] [3] [Fathom] Fathom project stopped. (10153)
[2015/12/14@20:30:46.791-0500] [3] [Fathom] Stopping Fathom WebServer. (10154)
[2015/12/14@20:30:46.792-0500] [3] [Fathom] Fathom WebServer stopped. (10155)
[2015/12/14@20:30:46.792-0500] [3] [Fathom] Fathom probe stopped. (10156)
[2015/12/14@20:30:46.792-0500] [0] [Fathom] * Fathom startup failed. (9661)

 

[Rob Fitzpatrick]

Have you tried this?
Fathom probe fails to start errors 10148 9661.
Knowledge Article

 

[dlangschied]

I tried it, but it did not work. I get the same error.

 

[Rob Fitzpatrick]

Could be a new 11.6 issue. I'd open a case with TS.

 

[Chris Hughes]

Just a thought - you only have 11.6 installed on the machine with the problem?

Multiple OE versions on same box has always caused issues with fathom.

 

[dlangschied]

No, there is only one version.

This file that it says was not close properly, database.ocf; can that be restored from backup without issue?

Regards,
David

 

[zerovian]

Post the exception from the ads0.exp file.

[2015/12/14@20:30:46.791-0500] [0] [*UnexpectedError*] * recorded as exception #1 in file ads0.exp.

 

[zerovian]

Or just delete the activity database. Its a cache for graphing, and you won't lose anything important beyond some graphing data.

 

[dlangschied]

I found the problem. It seems as though it is behaving badly when the service is launched as the system account. Generally, I do not like using user logins for such things, because some Windows environments that I encounter do not allow for a non-expiring password. In this case, I am okay. However, does this ring a bell for anybody as to how to get OE service to start as system account? Or, what I can do on my machine as far as folder permissions to allow the system account to access cache folders?

 

[Cringer]

Have a look in services, at the actual adminservice service. On our production server we have this set to log on as a specific user rather than the default.
Gyazo - dd58f9f1715252b00c64e02ede9c46bf.png
No idea if it will help, but no harm trying. Stop and start the service after making changes.

 

[Chris Hughes]

Unless you have changed the default permissions the standard "Local System" account will have access to all of your folders.