Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fatal error on Importing from Pocket #833

Closed
fujianto opened this issue Sep 9, 2014 · 10 comments
Closed

Fatal error on Importing from Pocket #833

fujianto opened this issue Sep 9, 2014 · 10 comments
Labels
Bug
Milestone
1.9.2

Comments

@fujianto
Copy link

fujianto commented Sep 9, 2014

I've got this Fatal error when trying to import from Pocket.

Fatal error: Call to a member function fetch() on a non-object in /home/u634230043/public_html/inc/poche/Database.class.php on line 389

Here's my host configuration.
Wallabag version 1.7.2
MySQL

Result from compatibility check.
PHP 5.3.3 or higher 5.4.32
XML Enabled Enabled, and sane
PCRE Enabled Enabled
Data filtering Enabled Enabled
Tidy Enabled Disabled
cURL Enabled Enabled
Parse ini file Enabled Enabled
Parallel URL fetching Enabled Enabled
allow_url_fopen Enabled Enabled
gettext Enabled Enabled

I don't have access to php.ini file and php error log. I've tried to keep importing, after several batches the Fatal error persist, sometimes causing 500 internal server error.
Is it because the host just bad? Since I'm using free hosting.
@tcitworld
Copy link
Member

It's the display of the articles after they are imported which throws this error. You may have other errors before, but they didn't display.

Can you activate debug mode in the inc/poche/config.inc.php file and set DEBUG_POCHE from FALSE to TRUE and then retry ? You may get more information.
Also, check out the cache/log.txt file.

@tcitworld tcitworld added the Bug label Sep 9, 2014
@fujianto
Copy link
Author

fujianto commented Sep 9, 2014

Here's the log file. Maybe some kind mysql connection error caused the bug?

2014/09/09_18:56:44 - 180.245.72.255 - Fetching article 694
2014/09/09_18:56:49 - 180.245.72.255 - Article 694 updated.
2014/09/09_18:56:49 - 180.245.72.255 - Fetching article 695
2014/09/09_18:56:49 - 180.245.72.255 - Article 695 updated.
2014/09/09_18:56:49 - 180.245.72.255 - Fetching article 696
2014/09/09_18:56:49 - 180.245.72.255 - Article 696 updated.
2014/09/09_18:56:49 - 180.245.72.255 - Fetching article 697
2014/09/09_18:57:04 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2013 Lost connection to MySQL server during query
2014/09/09_18:57:04 - 180.245.72.255 - Article 697 updated.
2014/09/09_18:57:04 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:57:13 - 180.245.72.255 - storage type mysql
2014/09/09_18:57:13 - 180.245.72.255 - Fetching next batch of articles...
2014/09/09_18:57:13 - 180.245.72.255 - Fetching article 697
2014/09/09_18:57:28 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2013 Lost connection to MySQL server during query
2014/09/09_18:57:28 - 180.245.72.255 - Article 697 updated.
2014/09/09_18:57:28 - 180.245.72.255 - Fetching article 698
2014/09/09_18:57:29 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:57:29 - 180.245.72.255 - Article 698 updated.
2014/09/09_18:57:29 - 180.245.72.255 - Fetching article 699
2014/09/09_18:57:29 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:57:29 - 180.245.72.255 - Article 699 updated.
2014/09/09_18:57:29 - 180.245.72.255 - Fetching article 700
2014/09/09_18:57:30 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:57:30 - 180.245.72.255 - Article 700 updated.
2014/09/09_18:57:30 - 180.245.72.255 - Fetching article 701
2014/09/09_18:57:32 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:57:32 - 180.245.72.255 - Article 701 updated.
2014/09/09_18:57:32 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:57:41 - 180.245.72.255 - storage type mysql
2014/09/09_18:57:41 - 180.245.72.255 - Fetching next batch of articles...
2014/09/09_18:57:41 - 180.245.72.255 - Fetching article 697
2014/09/09_18:57:56 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2013 Lost connection to MySQL server during query
2014/09/09_18:57:56 - 180.245.72.255 - Article 697 updated.
2014/09/09_18:57:56 - 180.245.72.255 - Fetching article 698
2014/09/09_18:57:56 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:57:56 - 180.245.72.255 - Article 698 updated.
2014/09/09_18:57:56 - 180.245.72.255 - Fetching article 699
2014/09/09_18:57:56 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:57:56 - 180.245.72.255 - Article 699 updated.
2014/09/09_18:57:56 - 180.245.72.255 - Fetching article 700
2014/09/09_18:57:58 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:57:58 - 180.245.72.255 - Article 700 updated.
2014/09/09_18:57:58 - 180.245.72.255 - Fetching article 701
2014/09/09_18:58:00 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:58:00 - 180.245.72.255 - Article 701 updated.
2014/09/09_18:58:00 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:58:22 - 180.245.72.255 - storage type mysql
2014/09/09_18:58:22 - 180.245.72.255 - Fetching next batch of articles...
2014/09/09_18:58:22 - 180.245.72.255 - Fetching article 697
2014/09/09_18:58:38 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2013 Lost connection to MySQL server during query
2014/09/09_18:58:38 - 180.245.72.255 - Article 697 updated.
2014/09/09_18:58:38 - 180.245.72.255 - Fetching article 698
2014/09/09_18:58:38 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:58:38 - 180.245.72.255 - Article 698 updated.
2014/09/09_18:58:38 - 180.245.72.255 - Fetching article 699
2014/09/09_18:58:38 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:58:38 - 180.245.72.255 - Article 699 updated.
2014/09/09_18:58:38 - 180.245.72.255 - Fetching article 700
2014/09/09_18:58:40 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:58:40 - 180.245.72.255 - Article 700 updated.
2014/09/09_18:58:40 - 180.245.72.255 - Fetching article 701
2014/09/09_18:58:42 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away
2014/09/09_18:58:42 - 180.245.72.255 - Article 701 updated.
2014/09/09_18:58:42 - 180.245.72.255 - execute query error : SQLSTATE[HY000]: General error: 2006 MySQL server has gone away

@tcitworld
Copy link
Member

Yup, too much connections to your MySQL database. Any ideas someone ?

@fujianto
Copy link
Author

I've reinstall and use Sqlite instead, it's working but with time out problem. adding @set_time_limit(600); on makefulltextfeed.php solve it. So far, I've tried everything on MySQL but no luck.

@tcitworld tcitworld added this to the 1.8.1 milestone Oct 4, 2014
@tcitworld
Copy link
Member

Note for myself : Was looking an article describing a similar problem, look if MySQL connexion is closed each time or not.

@rros
Copy link

rros commented Oct 14, 2014

If you send a large query to MySQL it can close the connection. Maybe one of the imported articles has a very large body?

Also see the MySQL documentation about "MySQL server has gone away": http://dev.mysql.com/doc/refman/5.5/en/gone-away.html

You can also get these errors if you send a query to the server that is incorrect or too large. If mysqld receives a packet that is too large or out of order, it assumes that something has gone wrong with the client and closes the connection. If you need big queries (for example, if you are working with big BLOB columns), you can increase the query limit by setting the server's max_allowed_packet variable, which has a default value of 1MB. You may also need to increase the maximum packet size on the client end. More information on setting the packet size is given in Section B.5.2.10, “Packet Too Large”.

@tcitworld
Copy link
Member

I think it can be fixed with $this->handle->setAttribute(PDO::ATTR_TIMEOUT, DB_TIMEOUT)
What default value should the DB_TIMEOUT constant have ?

@tcitworld
Copy link
Member

max_allowed_packet can't be changed in the case of shared hosting, unfortunately.

@nicosomb
Copy link
Member

(Wow, I read max_allowed_pocket ...)

@nicosomb nicosomb modified the milestones: 1.8.1, 1.8.2 Oct 29, 2014
@tcitworld tcitworld modified the milestones: 1.8.3, 1.8.2 Dec 22, 2014
@tcitworld tcitworld modified the milestones: 1.8.3, 1.9.1 Feb 10, 2015
@tcitworld tcitworld mentioned this issue May 5, 2015
Closed
@nicosomb nicosomb modified the milestones: 1.9.2, 1.9.1 Aug 3, 2015
@nicosomb
Copy link
Member

This issue affects wallabag v1. This version won't move anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug
Projects
None yet
Milestone
1.9.2
Development

No branches or pull requests
4 participants
@nicosomb @rros @tcitworld @fujianto