You must reduce the time limit specified on the Import page. This limit MUST be less than the time limit your server allows for PHP scripts.
Reduce the limit by 10 seconds each time you are notified about the server's time limit having expired.
When you're successful, PGV will be able to pause the Import in such a way that it can be resumed. You will see a "continue" button on the page. You can click this button to resume the Import from where it was paused. You can also have PGV click this button automatically.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My main-GEDCOM has a size of 30MB. Last I made the import in pgv 4.2.3 with 30 seconds without problems. In the last days I installed on a subdomain (own directory) a second pgv 4.2.3. I did use for import two GEDCOM-files (19,5 MB and 3MB). Both pgv versions did work fine.
Today I tried to make an update of the first database with a new 30MB GEDCOM-file. I was not able to import this file with settings of 30, 20 or 10 seconds. I don't know why I got this problem. I deleted then the second database and tried again the import at the first database. Now I was able to make the import (with 30 seconds).
On the server I've a max-memory of 512MB and a execution-time of 300 seconds. Can anybody say, why the GEDCOM-import works only with use of one database?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It looks as if PGV is timing out while it's attempting to empty the existing database tables before actually starting the Import of the replacement GEDCOM.
Your server time limit and memory settings are more than adequate. How about the PHP time limit you have configured in the GEDCOM configuration settings?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The import starts normal and stopps then after a while. With the first attemp the file gedcom.new had a size of 15 MB - it is 50% of the complete file. I tried then a much smaller GEDCOM (3MB), but it hanging too. The problem must be in context with the second database.
I forgot to say, in the first database I've also two GECOM-files (30MB and the second with only 170kb). Please let me know, if I understand not right. I think, if PGV starts with the import, the deleting procedure is finish.
In the GEDCOM-configuration I use 300 seconds as execution time. This is important for search and for getting results with large lists. Before the import I reduce execution time to 30 seconds. That works fine.
I think it should not be a problem, the useage of two databases with four or more GEDCOM's. But how I can reach it, that the import works too?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Otmar:
The Import doesn't start until the existing database tables have been emptied and any changes to the fields (columns) in each table have been made. You shouldn't need to reduce the PHP time limit in the GEDCOM configuration - a limit of 300 seconds here should not change the way the Import behaves.
If I understand you correctly, you see the Import start and the progress bar updating, until it quits somewhere around the 50% mark. If you don't see the progress bar at all, PGV is timing out before anything has been copied to the database.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The behavior during the gedcom import is unpredictable. I started some new test. First with only one database. For the import of my main gedcom file with 30MB I did use 300 seconds of time limit. After a while import stopps (gedcom.new had a size of 5,33MB). After I tried with 200 seconds, the import works.
Then I made the import on the second database with two gedcom files (562kb and 5kb) - without problems. Then I started an new import on the first database (30MB file, 200 seconds), but it end after two minutes. New test with 100 seconds runs 38 minutes - short before ending the import stopps again (gedcom.new had a size of 29MB). With 60 seconds I couldn't start, because the progress bar was not to see. With 50 seconds works the import (Duration: 48 minutes).
I cannot find out why the import have so different behaviors.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are reaching internal memory and timing errors. ALWAYS choose a shorter time. The progress bar on PGV is buggy and it was probably fine at 60 seconds if 50 worked, but didn't show in a reasonable time. My 45mb gedcom, even with 32gb of ram, uses a 10 second time for import and takes 48 minutes on a really, really fast machine. Don't get exercised about the times, it's not worth the frustration - just use autocontinue and a short time.
BTW, webtrees is solving these import issues by premeasuring the system parameters and reconfiguring the methodology of import. Not yet ready, it has a classy 'real' progress bar to keep you informed and can be interrupted and restarted in the same place.
Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can not import gedcom of any size, or with any time limit. I always get the error that the time exceeded. Help please
You must reduce the time limit specified on the Import page. This limit MUST be less than the time limit your server allows for PHP scripts.
Reduce the limit by 10 seconds each time you are notified about the server's time limit having expired.
When you're successful, PGV will be able to pause the Import in such a way that it can be resumed. You will see a "continue" button on the page. You can click this button to resume the Import from where it was paused. You can also have PGV click this button automatically.
My main-GEDCOM has a size of 30MB. Last I made the import in pgv 4.2.3 with 30 seconds without problems. In the last days I installed on a subdomain (own directory) a second pgv 4.2.3. I did use for import two GEDCOM-files (19,5 MB and 3MB). Both pgv versions did work fine.
Today I tried to make an update of the first database with a new 30MB GEDCOM-file. I was not able to import this file with settings of 30, 20 or 10 seconds. I don't know why I got this problem. I deleted then the second database and tried again the import at the first database. Now I was able to make the import (with 30 seconds).
On the server I've a max-memory of 512MB and a execution-time of 300 seconds. Can anybody say, why the GEDCOM-import works only with use of one database?
It looks as if PGV is timing out while it's attempting to empty the existing database tables before actually starting the Import of the replacement GEDCOM.
Your server time limit and memory settings are more than adequate. How about the PHP time limit you have configured in the GEDCOM configuration settings?
The import starts normal and stopps then after a while. With the first attemp the file gedcom.new had a size of 15 MB - it is 50% of the complete file. I tried then a much smaller GEDCOM (3MB), but it hanging too. The problem must be in context with the second database.
I forgot to say, in the first database I've also two GECOM-files (30MB and the second with only 170kb). Please let me know, if I understand not right. I think, if PGV starts with the import, the deleting procedure is finish.
In the GEDCOM-configuration I use 300 seconds as execution time. This is important for search and for getting results with large lists. Before the import I reduce execution time to 30 seconds. That works fine.
I think it should not be a problem, the useage of two databases with four or more GEDCOM's. But how I can reach it, that the import works too?
Otmar:
The Import doesn't start until the existing database tables have been emptied and any changes to the fields (columns) in each table have been made. You shouldn't need to reduce the PHP time limit in the GEDCOM configuration - a limit of 300 seconds here should not change the way the Import behaves.
If I understand you correctly, you see the Import start and the progress bar updating, until it quits somewhere around the 50% mark. If you don't see the progress bar at all, PGV is timing out before anything has been copied to the database.
The behavior during the gedcom import is unpredictable. I started some new test. First with only one database. For the import of my main gedcom file with 30MB I did use 300 seconds of time limit. After a while import stopps (gedcom.new had a size of 5,33MB). After I tried with 200 seconds, the import works.
Then I made the import on the second database with two gedcom files (562kb and 5kb) - without problems. Then I started an new import on the first database (30MB file, 200 seconds), but it end after two minutes. New test with 100 seconds runs 38 minutes - short before ending the import stopps again (gedcom.new had a size of 29MB). With 60 seconds I couldn't start, because the progress bar was not to see. With 50 seconds works the import (Duration: 48 minutes).
I cannot find out why the import have so different behaviors.
You are reaching internal memory and timing errors. ALWAYS choose a shorter time. The progress bar on PGV is buggy and it was probably fine at 60 seconds if 50 worked, but didn't show in a reasonable time. My 45mb gedcom, even with 32gb of ram, uses a 10 second time for import and takes 48 minutes on a really, really fast machine. Don't get exercised about the times, it's not worth the frustration - just use autocontinue and a short time.
BTW, webtrees is solving these import issues by premeasuring the system parameters and reconfiguring the methodology of import. Not yet ready, it has a classy 'real' progress bar to keep you informed and can be interrupted and restarted in the same place.
Stephen