Doesnt seem to be the problem, ;logger_message is as it should be in my config.ini.php and global.ini.php.
And I dont get any data for yesterday anymore: only the Message
“SQLSTATE[HY000]: General error: 2013 Lost connection to MySQL server during query”
I just installed Piwik completely from the scratch, with a new DB. It worked for about one minute, then the same messages as above…
More precisely: The first archive-update worked, then the same errors as above.
One more detail: on the dashboard I can look at the data before the update without any problems, and piwik is still collecting data (the DB is growing).
It’s very strange, that your dashboard loads and then widgets say that they couldn’t find the config file?? that is not supposed to be technically possible (unless you delete/rename the config file between the dashboard generation the time the widgets execute)
As nothing seems to help, I reverted to a backup of my entire Website I made two days ago (with Piwik v.0.5). Now everythings works fine again, but the data of the last two days is of course gone…
[quote=vipsoft @ May 7 2010, 07:58 PM]McHunter: we made changes to config/global.ini.php in 0.6; please make sure this file is up-to-date; the log section should contain:
[log]
;possible values for log: screen, database, file
; by default, standard logging/debug messages are hidden from screen
;logger_message[] = screen
logger_error[] = screen
logger_exception[] = screen
[/quote]
Hi vipsoft
Thank you very much for your quick support.
The “;” in front of the following line in the global.ini:
;logger_message[] = screen
fixed my problem.
In version 0.5.5:
[log]
;possible values for log: screen, database, file
; normal messages
logger_message[] = screen
and in/for vers. 0.6.1:
[log]
;possible values for log: screen, database, file
; by default, standard logging/debug messages are hidden from screen
;logger_message[] = screen
Why ist this not getting fixed automatically bei automatic update? style_emoticons/<#EMO_DIR#>/dry.gif
I don’t know for certain without seeing your database.
Please see the image attachment.
QUOTE (vipsoft @ May 8 2010, 12:03 AM) [<{POST_SNAPBACK}>](index.php?act=findpost&pid=35851)
At minimum, you'll have to go to the Settings | Web Sites manager, and set the timezone for your site(s).
Done
QUOTE (vipsoft @ May 8 2010, 12:03 AM]Then you may have to delete the archives generated today.[/quote]
Where do i find these archives (files or db entries?)?
Meanwhile I made a new piwik installation with the exitisting database and everything runs perfectly.
The problems (in my case) are thus created by the piwik Auto Update. That happend already with the last three Auto Update releases. So, the next piwik update(s) i will do manually. style_emoticons/<#EMO_DIR#>/wink.gif
brand new Piwik-Installation, brand-new DB:
same problems like before:
General error: 2013 Lost connection to MySQL server during query | The Piwik configuration file couldn’t be found and you are trying to access a Piwik page etc…
The funny thing about this is, that with a brand new installation the very first archive processing works fine, all further attempts to process the archive produce the errors listed above.
And why does 0.5.5 work on the same server without any problems?
Here are the php-settings:
Directive Local Value
allow_call_time_pass_reference Off
allow_url_fopen On
allow_url_include Off
always_populate_raw_post_data Off
arg_separator.input &
arg_separator.output &
asp_tags Off
auto_append_file no value
auto_globals_jit On
auto_prepend_file no value
browscap no value
default_charset no value
default_mimetype text/html
define_syslog_variables Off
disable_classes no value
disable_functions no value
display_errors Off
display_startup_errors Off
doc_root no value
docref_ext no value
docref_root no value
enable_dl Off
error_append_string no value
error_log no value
error_prepend_string no value
error_reporting 6143
expose_php On
extension_dir /usr/lib64/php5/extensions
file_uploads On
highlight.bg #FFFFFF
highlight.comment #FF8000
highlight.default #0000BB
highlight.html #000000
highlight.keyword #007700
highlight.string #DD0000
html_errors Off
ignore_repeated_errors Off
ignore_repeated_source Off
ignore_user_abort Off
implicit_flush Off
include_path .:.:/usr/share/php5:/usr/share/php5/PEAR
log_errors On
log_errors_max_len 1024
magic_quotes_gpc Off
magic_quotes_runtime Off
magic_quotes_sybase Off
mail.force_extra_parameters no value
max_execution_time 600
max_input_nesting_level 64
max_input_time 60
memory_limit 512M
open_basedir /srv/xyz/httpdocs:/tmp
output_buffering 4096
output_handler no value
post_max_size 50M
precision 14
realpath_cache_size 16K
realpath_cache_ttl 120
register_argc_argv Off
register_globals Off
register_long_arrays Off
report_memleaks On
report_zend_debug On
safe_mode Off
safe_mode_exec_dir no value
safe_mode_gid Off
safe_mode_include_dir no value
sendmail_from no value
sendmail_path /usr/sbin/sendmail -t -i
serialize_precision 100
short_open_tag On
SMTP localhost
smtp_port 25
sql.safe_mode Off
suhosin.log.phpscript 0
suhosin.log.phpscript.is_safe Off
suhosin.log.phpscript.name no value
suhosin.log.sapi no value
suhosin.log.script no value
suhosin.log.script.name no value
suhosin.log.syslog no value
suhosin.log.syslog.facility no value
suhosin.log.syslog.priority no value
suhosin.log.use-x-forwarded-for Off
track_errors Off
unserialize_callback_func no value
upload_max_filesize 50M
upload_tmp_dir /tmp
user_dir no value
variables_order GPCS
xmlrpc_error_number 0
xmlrpc_errors Off
y2k_compliance On
zend.ze1_compatibility_mode Off
.
.
.
mysql
MySQL Support enabled
Active Persistent Links 0
Active Links 0
Client API version 5.0.45
MYSQL_MODULE_TYPE external
MYSQL_SOCKET /var/lib/mysql/mysql.sock
MYSQL_INCLUDE #NAME?
MYSQL_LIBS #NAME?
Directive Local Value
mysql.allow_persistent Off
mysql.connect_timeout 60
mysql.default_host no value
mysql.default_password no value
mysql.default_port no value
mysql.default_socket no value
mysql.default_user no value
mysql.max_links Unlimited
mysql.max_persistent Unlimited
mysql.trace_mode Off
thd=0x11c5f00
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x422e0fe0, backtrace may not be correct.
Bogus stack limit or frame pointer, fp=0x422e0fe0, stack_bottom=0x422e0000, thread_stack=262144, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x1207040 = SELECT idarchive, value, name, date1 as startDate
FROM piwik_archive_numeric_2010_05
WHERE idsite = '1'
AND date1 = '2010-05-29'
AND date2 = '2010-05-29'
AND period = '1'
AND ( (name = 'done' AND value = 1)
OR (name = 'done' AND value = 3)
OR name = 'nb_visits')
AND ts_archived >= '2010-05-29 10:31:22'
ORDER BY ts_archived DESC
thd->thread_id=1
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.