Hi,

I am using Atrium Discovery and Dependency Mapping 8.1.1

Following a space issue we had to shutdown the server and increase a space. Once done we tried to boot the server and start the services. Unfortunately service don’t start after that and we get the below error.
==========================================================================
[tideway@SEANEA-Tideway log]$ sudo /sbin/service tideway start
Starting Tideway application services
  Starting Free Space Monitor service:            [ SKIP ]
  Rebuilding CSS extensions:                    [  OK ]
  Starting Security service:                    [ SKIP ]
  Starting Options service:                    [ SKIP ]
  Starting Discovery service:                  [ SKIP ]
  Starting Model service:                      [FAILED]
Fri Jan 21 04:38:56 2011 : tw_svc_model started.
Failed to open names database.
Fri Jan 21 04:38:57 2011 : Watchdog : Service failed in 1.5 seconds (signal 0). Exiting.

The Tideway service ‘40model’ failed to start. Check logs.
==========================================================================

I guess this type of error occurs if the clock is skewed.

Can you help me with a solution to resolve this issue.

What did the log (/usr/tideway/log/tw_svc_model.log) say?

Note that the model uses time for determining attempted concurrent modification of values so if the clock has gone backwards the model will not start.

yes, i am aware of that. Can you help me to find out on which part of the model log this information is available?

hi andrew,

below is the log from tw_svc_model.log

=========================
47813013678528: 2011-01-21 08:18:32,698: model.datastore.store: INFO: Open environment in directory ‘/usr/tideway/var/tideway.db/data/datadir’...
47813013678528: 2011-01-21 08:18:34,532: model.datastore.store: INFO: Environment opened.
47813013678528: 2011-01-21 08:18:34,533: model.datastore.store: INFO: Database is data model version 8.
47813013678528: 2011-01-21 08:18:34,534: model.datastore.store: INFO: Data store last run at Tue Jan 18 11:26:42 2011.
1131063616: 2011-01-21 08:18:34,535: model.datastore.dsthreads: INFO: DB checkpoint thread started.
1141553472: 2011-01-21 08:18:34,536: model.datastore.dsthreads: INFO: DB update thread started.
47813013678528: 2011-01-21 08:18:34,536: model.datastore.store: INFO: Store initialised.
47813013678528: 2011-01-21 08:18:34,537: model.datastore.main: INFO: DataStore low-level Main created.
47813013678528: 2011-01-21 08:18:34,543: model.datastore.store: CRITICAL: Failed to open names database.
Traceback (most recent call last):
  File “./store.py”, line 613, in __init__
DBInvalidArgError: (22, ‘Invalid argument—/usr/tideway/var/tideway.db/data/datadir/names: unexpected file type or format’)
===================================

it says the last run was on Jan 18 11:26:42 2011.

Have you done a DB compaction? If so, have you moved the resultant datastore back to the original location as per the instructions? Trying to start the original datastore after the pre-compact preparation steps can give errors like this.

It may also be more appropriate to open a support case for this.
Nick