I'm running phpgedview 7312 on a Mac which has solved a lot of problems
with the display tabs and the Tree not expanding that I reported some
time ago.
An intermittent problem that I now have is that on the 'Welcome Page'
and 'MyGedView Portal' I sometimes get
ERROR 2: PDO::__construct(): MySQL server has gone away
but the rest of the site works fine. If I understand correctly these
later version run from the database rather than the GEDCOM file, so the
database hasn't gone away. Also, on the host using command line I can
open a connection to the database and see the data.
It's only those two pages, and sometimes some of the panes work and some
don't, those that don't giving that same errors.
Two sample stack traces:
ERROR 2: PDO::__construct(): MySQL server has gone away
0 Error occurred on in function __construct
1 called from line 119 of file class_pgv_db.php in function createInstance
2 called from line 402 of file session.php in function require_once
3 called from line 83 of file config.php in function require
4 called from line 35 of file index.php
and
Fatal error: DB connection error in PGV_DB::createInstance():
SQLSTATE[HY000][2006] MySQL server has gone away in
/Library/WebServer/Documents/phpgedview7312/includes/classes/class_pgv_db.php
on line 405
Regards,
David
David Ledger
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Odd though that the main gedview stuff access the database with no
problem. Must use a different calling technique. Be nice to know why,
but it may be a difference between different programmers' styles.
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nope, the code in PhpGedView is consistent in the way it uses the database. It could be the number of concurrent connections.
One thing that I noticed, 'way back when, was that if the database tables use the innodb engine, PhpGedView is EXTREMELY slow when importing a GEDCOM file. I haven't bothered to track this down; I think it has something to do with the program not releasing record locks properly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm running phpgedview 7312 on a Mac which has solved a lot of problems
with the display tabs and the Tree not expanding that I reported some
time ago.
An intermittent problem that I now have is that on the 'Welcome Page'
and 'MyGedView Portal' I sometimes get
ERROR 2: PDO::__construct(): MySQL server has gone away
but the rest of the site works fine. If I understand correctly these
later version run from the database rather than the GEDCOM file, so the
database hasn't gone away. Also, on the host using command line I can
open a connection to the database and see the data.
It's only those two pages, and sometimes some of the panes work and some
don't, those that don't giving that same errors.
Two sample stack traces:
ERROR 2: PDO::__construct(): MySQL server has gone away
0 Error occurred on in function __construct
1 called from line 119 of file class_pgv_db.php in function createInstance
2 called from line 402 of file session.php in function require_once
3 called from line 83 of file config.php in function require
4 called from line 35 of file index.php
and
Fatal error: DB connection error in PGV_DB::createInstance():
SQLSTATE[HY000] [2006] MySQL server has gone away in
/Library/WebServer/Documents/phpgedview7312/includes/classes/class_pgv_db.php
on line 405
Regards,
David
David Ledger
This appears to be a server misconfiguration.
A Google search for MySQL server has gone away gives this result, among others:
https://haydenjames.io/mysql-server-has-gone-away-error-solutions/
On 9/10/21 8:50 PM, Gerry Kroll wrote:
Thanks for that Gerry. I'll check into it.
Odd though that the main gedview stuff access the database with no
problem. Must use a different calling technique. Be nice to know why,
but it may be a difference between different programmers' styles.
David
Nope, the code in PhpGedView is consistent in the way it uses the database. It could be the number of concurrent connections.
One thing that I noticed, 'way back when, was that if the database tables use the innodb engine, PhpGedView is EXTREMELY slow when importing a GEDCOM file. I haven't bothered to track this down; I think it has something to do with the program not releasing record locks properly.