On 24.09.12 16.09, Karl Wright wrote:
Maybe our routines for upgrading MCF need to be changed. We want to be sure
that these connectors do not need new fields in the database tables due to
changed/new functions.
This should happen automatically if you simply reregister the
connector. You do not need to unregister it, I am pretty sure.
Thanks. This makes our upgrading routines far more easier. I will update
our routine document right away.
Still I cannot delete my jobs since their statuses are "cleaning up". And
the reason is because I didn't delete my jobs prior to executing
"crawler.UnRegisterAll"?
Once you register the missing connectors again, and have the agents
process running, the job should delete. If this is not happening it
may just take a few minutes for things to wake up, but it should pick
up where it left off.
If it doesn't seem to recover, it may be time to look in the database
to see what the status is of all the connectors. When you unregister
and reregister a connector, it goes through the jobs that depend on
the connector and changes their state. If there is something wrong
with that logic then the connector will be registered but the job will
still be in the "unregistered" state.
Great. The Agent process is always running on our test server with a
cron job checking its status every day. I can check again tomorrow in
case the jobs have been deleted.
I will install RC1 and vote later this week.
Erlend
--
Erlend Garåsen
Center for Information Technology Services
University of Oslo
P.O. Box 1086 Blindern, N-0317 OSLO, Norway
Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
