Discussions
Compare notes among each other.

Your shopping cart

There are no items in your cart.

ViMP Admin Guide

Download the ViMP 2.6 Admin Documentation!

Download now!

ViMP Hosting

All from one source! Host your ViMP portal in our cloud-based SaaS solution!
 
ViMP Hosting

ViMP Servers

Dedicated power for your ViMP portal with full control and exclusive usage!
 
ViMP Servers

Support Forum

 
Avatar
eru
Posts: 48
Hallo,
beim studieren der Logs bin ich auf folgende fehler (aller 1 Minute) gestossen, die ich mir nicht erklären kann.

aus frontend_dev.log:

iconCode:
Dec 02 22:51:02 symfony [info] <4ED948467D75E> {stDatabaseSessionStorage} session started with id "d10ukp4ra44qnbm3asrq1s3an3"
Dec 02 22:51:02 symfony [info] <4ED948467D75E> {sfFilterChain} Executing filter "stConfigFilter"
Dec 02 22:51:02 symfony [info] <4ED948467D75E> {sfFilterChain} Executing filter "stDatabaseConfigFilter"
Dec 02 22:51:02 symfony [info] <4ED948467D75E> {stDatabaseConfigFilter} upload_max_size was greater than php setting upload_max_filesize
Dec 02 22:51:02 symfony [info] <4ED948467D75E> {stDatabaseSessionStorage} session with id "d10ukp4ra44qnbm3asrq1s3an3" inserted.
Dec 02 22:51:02 symfony [info] <4ED948467D75E> {stDatabaseSessionStorage} data (260): c3ltZm9ueS91c2VyL3NmVXNlci9sYXN0UmVxdWVzdHxpOjEzMjI4NjI2NjI7c3ltZm9ueS91c2VyL3NmVXNlci9hdXRoZW50aWNhdGVkfGI6MDtzeW1mb255L3VzZXIvc2ZVc2VyL2NyZWRlbnRpYWxzfGE6MDp7fXN5bWZvbnkvdXNlci9zZlVzZXIvYXR0cmlidXRlc3xhOjA6e31zeW1mb255L3VzZXIvc2ZVc2VyL2N1bHR1cmV8czoyOiJkZSI7
Dec 02 22:51:02 symfony [info] <4ED948467D75E> {stDatabaseSessionStorage} session closed
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Clear all current routes
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "template_images" (/images/*)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "template_css" (/css/*)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "template_js" (/js/*)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "media_list" (/medias)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "youtube" (/youtube/:title/:key)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "youtube_list" (/youtubes)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "homepage" (/)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "signup" (/signup)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "login" (/login)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "logout" (/logout)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "password" (/password)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "language" (/language/:lang)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "video" (/video/:title/:key)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "video_list" (/videos)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "picture" (/picture/:title/:key)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "picture_list" (/pictures)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "audio" (/audio/:title/:key)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "audio_list" (/audios)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "document" (/document/:title/:key)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "document_list" (/documents)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "category" (/category/:category/:category_id)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "group" (/group/:title/:key)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "blog" (/blog/:title/:blogid)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "webcontent_default" (/pages/:action/*)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "leanbackPlayer_null" (/null)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "default_index" (/:module)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRoute "default" (/:module/:action/*)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Connect sfRequestRoute "captchagd" (/captcha)
Dec 02 22:52:02 symfony [info] <4ED94882D2C22> {sfPatternRouting} Match route "homepage" (/) for / with parameters array (  'module' => 'start',  'action' => 'index',)
Dec 02 22:52:02 symfony [err] <4ED94882D2C22> {stDatabaseSessionStorage} cannot read session data with id "f9pharle40j4oijb2rfpd6ejr2".
Dec 02 22:52:02 symfony [err] <4ED94882D2C22> {stDatabaseSessionStorage} MySQL ERROR 0: 
Dec 02 22:52:02 symfony [err] <4ED94882D2C22> {stDatabaseSessionStorage} SQL Statement: "SQL: [71] SELECT session FROM session WHERE sessid = :id ORDER BY created_at DESC
Params:  1
Key: Name: [3] :id
paramno=-1
name=[3] ":id"
is_param=1
param_type=2
"


Innerhalb 24 Stunden sind das mal 6MB-Logfile. Upload_max_size istdefinitiv gleich zu den php-settings, habe ich per phpinfo überprüft.

Im frontend_prod.log um etwa die gleiche Zeit:
iconCode:
Dec 02 22:50:30 symfony [err] <4ED94826D0E5E> {stDatabaseSessionStorage} SQL Statement: "SQL: [71] SELECT session FROM session WHERE sessid = :id ORDER BY created_at DESC
Params:  1
Key: Name: [3] :id
paramno=-1
name=[3] ":id"
is_param=1
param_type=2
"
Dec 02 22:50:40 symfony [err] <4ED948307FE96> {stDatabaseSessionStorage} cannot read session data with id "jas0qu34lbahlb84j678sgv7t1".
Dec 02 22:50:40 symfony [err] <4ED948307FE96> {stDatabaseSessionStorage} cannot read session data with id "jas0qu34lbahlb84j678sgv7t1".
Dec 02 22:50:40 symfony [err] <4ED948307FE96> {stDatabaseSessionStorage} MySQL ERROR 0: 
Dec 02 22:50:40 symfony [err] <4ED948307FE96> {stDatabaseSessionStorage} MySQL ERROR 0: 
Dec 02 22:50:40 symfony [err] <4ED948307FE96> {stDatabaseSessionStorage} SQL Statement: "SQL: [71] SELECT session FROM session WHERE sessid = :id ORDER BY created_at DESC
Params:  1
Key: Name: [3] :id
paramno=-1
name=[3] ":id"
is_param=1
param_type=2
"
Dec 02 22:50:40 symfony [err] <4ED948307FE96> {stDatabaseSessionStorage} SQL Statement: "SQL: [71] SELECT session FROM session WHERE sessid = :id ORDER BY created_at DESC
Params:  1
Key: Name: [3] :id
paramno=-1
name=[3] ":id"
is_param=1
param_type=2
"
Dec 02 22:53:07 symfony [err] <4ED948C3C9BBA> {stDatabaseSessionStorage} cannot read session data with id "qo9f9qs08tvdj37ignn78h9596".
Dec 02 22:53:07 symfony [err] <4ED948C3C9BBA> {stDatabaseSessionStorage} cannot read session data with id "qo9f9qs08tvdj37ignn78h9596".
Dec 02 22:53:07 symfony [err] <4ED948C3C9BBA> {stDatabaseSessionStorage} MySQL ERROR 0: 
Dec 02 22:53:07 symfony [err] <4ED948C3C9BBA> {stDatabaseSessionStorage} MySQL ERROR 0: 
Dec 02 22:53:07 symfony [err] <4ED948C3C9BBA> {stDatabaseSessionStorage} SQL Statement: "SQL: [71] SELECT session FROM session WHERE sessid = :id ORDER BY created_at DESC
Params:  1
Key: Name: [3] :id
paramno=-1
name=[3] ":id"
is_param=1
param_type=2
"


Irgendwelche Ideen? Ist doch nicht gut für die performance, denke ich...

Beste Grüße,
Eru
02.12.2011 23:08
Avatar
support
ViMP Support
Posts: 3650
Hallo eru,

vorneweg, es ist richtig, dass das frontend_dev.log sehr groß werden kann. Das kannst Du einfach zwischendurch mal löschen oder per logrotate rotieren lassen (bitte googlen).

Da die Daten einfach an das file angehängt werden, ist das keine performance-Bremse.

Hast Du die ViMP-interne maximale Dateigröße (im backend: administration -> Basis -> Datei-upload-limit).
Wenn Du den Wert bearbeitest, kannst Du auch z.B. einfach 1024MB o.ä. dort eintragen. Nach dem Speichern wird der Wert in Byte angezeigt.
Dieser Wert muss kleiner sein, als upload_max_filesize in der php.ini

Die Meldungen "cannot read session data...." sind völlig normal. Auch bei einer neuen Session wird immer geprüft, ob diese bereits in der Datenbank vorhanden ist. Wenn nicht, wird sie erstellt (und auch in die db geschrieben).

Was mich allerdings etwas verwundert ist, dass diese Einträge immer doppelt bei Dir geschrieben werden.
Ist das immer und immer noch der Fall? Hast Du da irgendeine besondere Konfiguration?

Viele Grüße
ViMP Support Team
07.12.2011 22:23
Avatar
eru
Posts: 48
Hallo Kai,

Danke füpr die Erläuterung.
Ich habe die Größe nun nicht gleich 1024MB sondern kleiner gewählt und nun geht es!


was die Doppelten Einträge angeht, habe ich keine Ahnung, was dies verursachen könnte. Ich habe eine Standard Ubuntu-installation mit Plesk und habe nichts weiter "getweakt" Wenn ich wüsste wo ich schauen soll, könnte ich mal die Logs durchforsten...

Viele Grüße und Danke!

eru
08.12.2011 00:34
 
Log in or register in order to write forum posts.