Difference between revisions of "Debug"
From Berlin Harvesting and Indexing Toolkit
(Created page with "=The application is deployed but does not start= *Check the JVM used. From 1.8 there should not be any problem. *Check if the permissions (folders, database) are correct. Hav...") |
|||
| Line 13: | Line 13: | ||
*In the latest version, the sha1responses.datasetdir should only contain slashes (no backslashes anymore). If this column still contains \, please update the content. | *In the latest version, the sha1responses.datasetdir should only contain slashes (no backslashes anymore). If this column still contains \, please update the content. | ||
| − | =A | + | |
| + | =A datasource is added, the metadata are not updated= | ||
| + | *Check the accespoint you entered: on the datasource page, you can use the function "Check accesspoints validity". | ||
| + | |||
| + | =A datasource is added, the metadata are updated but no new datasource to harvest appears in the tab= | ||
*Reload the page. | *Reload the page. | ||
| − | =A | + | =A associated datasource is added, the metadata are updated but no new datasource to harvest appears in the tab= |
*Reload the Associated datasource page. | *Reload the Associated datasource page. | ||
*Check if there is a new line in the MySQL table bio_datasource. | *Check if there is a new line in the MySQL table bio_datasource. | ||
*Check if the new datasource (harvester_factory like '%Harvester%') has the correct value for "isAssociated" (should be 1). If not, edit and save the changes. For some obscure reasons, this parameter is sometimes left as false. | *Check if the new datasource (harvester_factory like '%Harvester%') has the correct value for "isAssociated" (should be 1). If not, edit and save the changes. For some obscure reasons, this parameter is sometimes left as false. | ||
| + | |||
| + | =The new jobs are listed in the tab, but disappears without anything being done= | ||
| + | It might be due to a difference between the time stamp from the database server and the server where b-hit is running. B-HIT can only handle cases where the database server is max. 5min ahead from the application server. | ||
Revision as of 09:15, 11 February 2016
Contents
- 1 The application is deployed but does not start
- 2 A new datasource can not get its metadata updated
- 3 It's complaining about some SHA file not found
- 4 A datasource is added, the metadata are not updated
- 5 A datasource is added, the metadata are updated but no new datasource to harvest appears in the tab
- 6 A associated datasource is added, the metadata are updated but no new datasource to harvest appears in the tab
- 7 The new jobs are listed in the tab, but disappears without anything being done
The application is deployed but does not start
- Check the JVM used. From 1.8 there should not be any problem.
- Check if the permissions (folders, database) are correct.
Have a look in the catalina logs and windows!
A new datasource can not get its metadata updated
- Check your MySQL schema - did you add the schemaOnly commands?
- Is it a brand new schema or protocol version, absent from the standardschema table?
It's complaining about some SHA file not found
- Check the path for the temporaryFolder - did you forget to escape the backslash on windows?
- In the latest version, the sha1responses.datasetdir should only contain slashes (no backslashes anymore). If this column still contains \, please update the content.
A datasource is added, the metadata are not updated
- Check the accespoint you entered: on the datasource page, you can use the function "Check accesspoints validity".
A datasource is added, the metadata are updated but no new datasource to harvest appears in the tab
- Reload the page.
A associated datasource is added, the metadata are updated but no new datasource to harvest appears in the tab
- Reload the Associated datasource page.
- Check if there is a new line in the MySQL table bio_datasource.
- Check if the new datasource (harvester_factory like '%Harvester%') has the correct value for "isAssociated" (should be 1). If not, edit and save the changes. For some obscure reasons, this parameter is sometimes left as false.
The new jobs are listed in the tab, but disappears without anything being done
It might be due to a difference between the time stamp from the database server and the server where b-hit is running. B-HIT can only handle cases where the database server is max. 5min ahead from the application server.
