error_log - cache sqlite errors

Hello,



just found these errors (see below) in error_log file. Any advise about these errors? Thanks.



[size=3][14-Nov-2012 06:01:20 UTC] PHP Warning: SQLite3Result::fetchArray() [sqlite3result.fetcharray]: Unable to execute statement: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 134

[14-Nov-2012 06:01:26 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: Unable to prepare statement: 5, database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 130

[14-Nov-2012 06:01:26 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: Unable to prepare statement: 5, database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 130

[14-Nov-2012 06:01:26 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 40

[14-Nov-2012 06:01:26 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php:130) in /home/mysite/public_html/core/fn.init.php on line 413

[14-Nov-2012 06:01:26 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: Unable to prepare statement: 5, database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 130

[14-Nov-2012 06:01:26 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: Unable to prepare statement: 5, database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 130

[14-Nov-2012 06:01:26 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: Unable to prepare statement: 5, database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 130

[14-Nov-2012 06:01:26 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 40

[14-Nov-2012 06:01:26 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: Unable to prepare statement: 5, database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 130

[14-Nov-2012 06:01:30 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 40

[14-Nov-2012 06:01:30 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php:130) in /home/mysite/public_html/core/fn.control.php on line 503

[14-Nov-2012 06:01:30 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 40

[14-Nov-2012 06:01:30 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 93

[14-Nov-2012 06:01:30 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 85

[14-Nov-2012 06:01:32 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: Unable to prepare statement: 5, database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 130

[14-Nov-2012 06:01:32 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: Unable to prepare statement: 5, database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 130

[14-Nov-2012 06:01:32 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 40

[14-Nov-2012 06:01:32 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php:130) in /home/mysite/public_html/core/fn.init.php on line 413

[14-Nov-2012 06:01:32 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: Unable to prepare statement: 5, database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 130

[14-Nov-2012 06:01:32 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: Unable to prepare statement: 5, database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 130

[14-Nov-2012 06:01:32 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: Unable to prepare statement: 5, database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 130

[14-Nov-2012 06:01:32 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 40

[14-Nov-2012 06:01:32 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: Unable to prepare statement: 5, database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 130

[14-Nov-2012 06:01:32 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 40

[14-Nov-2012 06:01:32 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php:130) in /home/mysite/public_html/core/fn.control.php on line 503

[14-Nov-2012 06:01:32 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 40

[14-Nov-2012 06:01:32 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 93

[14-Nov-2012 06:01:32 UTC] PHP Warning: SQLite3::query() [sqlite3.query]: database is locked in /home/mysite/public_html/core/cache/class.cache_backend_sqlite.php on line 85[/size]



CS-Cart 2.2.5

Are you using backend cache = sqlite

Is this a new install?

Has php been configured with SQLite3 support?

Are you using backend cache = sqlite

Yes.

Is this a new install?

No.

Has php been configured with SQLite3 support?

Not sure. Where/how to check it?

phpinfo will indicate goto administration->database click PHP Information

[quote name='Adrian8' timestamp='1352919318' post='149175']

phpinfo will indicate goto administration->database click PHP Information

[/quote]

Sorry… Here is the info:



PHP 5.3.13



SQLite3 support / enabled

SQLite3 module version / 0.7-dev

SQLite Library / 3.7.7.1

sqlite3.extension_dir / no value / no value

It looks like php support is enabled. These errors only refer to backend cache (not sure of the cause), you could either switch backend cache to file or contact cs-cart, unless someone else may have the answer.

It’s a timeout issue. They added this to the default install package but I do not know if it was before or after 2.2.5. Check the file for the code in the post. If it’s not there then add it.

Adrian8 & The Tool, thanks for paying attention on this issue.

I'm using v. 2.2.5 and the file class.cache_backend_sqlite.php is correctly updated in this version.

The code values are:

self::_set_timeout(60000);

and

$result = self::$db->setAttribute(PDO::ATTR_TIMEOUT, ($msec / 1000));

The funny thing is that I'm getting these errors on ocassional basis. e.g. It started on Oct 7, than appears again on Oct 8-9, Oct 15-16, Oct 22-25, Nov 3, Nov 8, Nov 14-15, Nov 18…

The site is hosted on the WT VPS and their's technician conclusion is: “it would appear that something in the code is crashing and locking up the sqlite database located at /home/…/public_html/var/cache/cache.db”

I'll contact CS-Cart support in order to look further into this.

I had exactly the same problem when I moved from VPS to dedicated. The problem was still there after the fixes suggested in the thread mentioned by the tool. I had at least 5 guys from hosting-support look at it, but nobody was able to fix it. In the end Jesse Lee Stringer completely re-configured my server and fixed it.



On yet another vps I have (different host), I had the same problem. But after numerous tries by their support they did fix it.