- Posts: 39
Before asking for help please read "How to request help" by clicking on that tab above here."
Solved Import family tree has been "Calculating" for 15hr
- mike@islandancestry.com
- Topic Author
- Offline
- New Member
Please Log in or Create an account to join the conversation.
- fisharebest
- Away
- Administrator
The server process almost certainly died 14 hrs 59 minutes ago.
During the "calculating" phase, it is copying the GEDCOM data into a temporary buffer (wt_gedcom_chunk table) and also deleting the old data.
If you have a slow database, deleting the data can take longer than your time limit.
It often helps to repeat the import.
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- mike@islandancestry.com
- Topic Author
- Offline
- New Member
- Posts: 39
The option to import is not available? Even after rebooting, signing out etc.
Please Log in or Create an account to join the conversation.
- fisharebest
- Away
- Administrator
From the wt_gedcom table, find the numeric ID of this tree.
Then delete rows for this tree in the individuals/families/sources/other/dates/links table.
Then visit the admin page again.
Another possibility is that there is a problem with the database that prevents a row being deleted. (Record lock, corruption, etc.).
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- mike@islandancestry.com
- Topic Author
- Offline
- New Member
- Posts: 39
SQL query:
DELETE FROM `<DB>`.`wt_gedcom` WHERE `wt_gedcom`.`gedcom_id` =6
MySQL said: Documentation
#1451 - Cannot delete or update a parent row: a foreign key constraint fails (`<DB>`.`wt_gedcom_setting`, CONSTRAINT `wt_gedcom_setting_ibfk_1` FOREIGN KEY (`gedcom_id`) REFERENCES `wt_gedcom` (`gedcom_id`))
Please Log in or Create an account to join the conversation.
- bertkoor
- Offline
- Platinum Member
- Greetings from Utrecht, Holland
mike@islandancestry.com wrote: I had a family tree, i exported it, i deleted it and then tried to import it.
What type of export / import did you choose?
On import there are two options:
- A file on your computer - takes more resources, is less efficient
- A file on the server - takes less resources, is more efficient
NB: there usually is no need to delete the tree and create it again. Importing into an existing tree should take care of the deletion of data first.
But in case of your server limitations, I can totally understand you performed the deletion manually.
stamboom.BertKoor.nl runs on webtrees v1.7.13
Please Log in or Create an account to join the conversation.
- mike@islandancestry.com
- Topic Author
- Offline
- New Member
- Posts: 39
Please Log in or Create an account to join the conversation.
- fisharebest
- Away
- Administrator
Do not delete from this table. I listed all the (large) tables that you should delete. There are others (much smaller) which shouldn't be a problem.
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- fisharebest
- Away
- Administrator
bertkoor wrote:
mike@islandancestry.com wrote: On import there are two options:
- A file on your computer - takes more resources, is less efficient
- A file on the server - takes less resources, is more efficient
It is only export that has this difference. Download to computer applies privacy filters, etc. Save on server does a simple database dump.
On import, the difference is that many servers have a maximum upload size. The "file on server" option exists to get around this limitation.
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- mike@islandancestry.com
- Topic Author
- Offline
- New Member
- Posts: 39
I dont know how to re-import now. I get the screen when it says "calculating" then i get this
/<path>/islandancestry.com/webtrees/app/Statement.php:82 SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction #0 /app/Statement.php:82 PDOException("SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction") #1 /import.php:48 execute([array])
then it goes back to calculating. It does not show the menu with all the options for the family tree.
Please Log in or Create an account to join the conversation.
- fisharebest
- Away
- Administrator
mike@islandancestry.com wrote: I know this is painful, sorry about the questions.
I dont know how to re-import now. I get the screen when it says "calculating" then i get this
/<path>/islandancestry.com/webtrees/app/Statement.php:82 SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction #0 /app/Statement.php:82 PDOException("SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction") #1 /import.php:48 execute([array])
then it goes back to calculating. It does not show the menu with all the options for the family tree.
MySQL maintains "locks" so that two people cannot update the same data at the same time.
There are timeouts, so that if one transaction takes out a lock, and then quits, the lock won't be there forever.
On a webserver, you want to keep these locks quite short, as nothing should take more than 30-60 seconds.
You probably can't change your timeouts (or reset them by restarting the database), but you can find out what they are by looking at the "variables" section in phpMyAdmin.
As the error message says, wait and try again. A common default setting in MySQL is 28800 seconds (about 40 minutes).
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- mike@islandancestry.com
- Topic Author
- Offline
- New Member
- Posts: 39
It goes from calculating, to the error above, back to calculating. It doesnt even give me the option to re-import.
Please Log in or Create an account to join the conversation.
- mike@islandancestry.com
- Topic Author
- Offline
- New Member
- Posts: 39
Please Log in or Create an account to join the conversation.
- fisharebest
- Away
- Administrator
wt_gedcom_chunk. Delete all rows.
If this doesn't help, you'll need to look at any locks/processes in your database - using phpMyAdmin.
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- mike@islandancestry.com
- Topic Author
- Offline
- New Member
- Posts: 39
Please Log in or Create an account to join the conversation.