• User Newbie

    Errore Server Apache!

    Salve, ho sviluppato un componente Joomla da installare sul un sito. Dopo averlo sviluppato in locale e testato numerossissime volte, ho installato il componente sul sito. Ho effettuato numerose prove e non mi ha dato nessun problema. Dopo 2-3 ore dall'istallazione però il sito crasha.
    Questi sono i file di log di apache e mysql. Non riesco a capire cosa causa l'errore.

    error_log:

    [Sat Apr 13 17:16:53 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:16:55 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:17:28 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:17:29 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:17:29 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:17:29 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:17:30 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:17:33 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:17:35 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:17:37 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:17:37 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:17:40 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:17:46 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored
    [Sat Apr 13 17:17:47 2013] [error] Exception KeyError: KeyError(140625816418272,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored

    [Sat Apr 13 18:30:46 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
    [Sat Apr 13 18:30:46 2013] [notice] Digest: generating secret for digest authentication ...
    [Sat Apr 13 18:30:46 2013] [notice] Digest: done
    [Sat Apr 13 18:30:50 2013] [warn] mod_wsgi: Compiled for Python/2.6.2.
    [Sat Apr 13 18:30:50 2013] [warn] mod_wsgi: Runtime using Python/2.6.6.
    [Sat Apr 13 18:30:50 2013] [notice] Apache/2.2.15 (Unix) DAV/2 mod_fcgid/2.3.7 PHP/5.3.3 mod_ssl/2.2.15 OpenSSL/1.0.0-fips mod_wsgi/3.2 Python/2.6.6 configured -- resuming normal operations

    mysqld.log:

    121229 17:23:06 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    121229 17:23:06 InnoDB: Initializing buffer pool, size = 8.0M
    121229 17:23:06 InnoDB: Completed initialization of buffer pool
    121229 17:23:07 InnoDB: Started; log sequence number 0 3687006
    121229 17:23:07 [Note] Event Scheduler: Loaded 0 events
    121229 17:23:07 [Note] /usr/libexec/mysqld: ready for connections.
    Version: '5.1.61' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
    121229 17:25:10 [Note] /usr/libexec/mysqld: Normal shutdown

    121229 17:25:10 [Note] Event Scheduler: Purging the queue. 0 events
    121229 17:25:10 InnoDB: Starting shutdown...
    121229 17:25:12 InnoDB: Shutdown completed; log sequence number 0 3687006
    121229 17:25:12 [Note] /usr/libexec/mysqld: Shutdown complete

    121229 17:25:12 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
    121229 17:27:03 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    121229 17:27:04 InnoDB: Initializing buffer pool, size = 8.0M
    121229 17:27:04 InnoDB: Completed initialization of buffer pool
    121229 17:27:04 InnoDB: Started; log sequence number 0 3687006
    121229 17:27:04 [Note] Event Scheduler: Loaded 0 events
    121229 17:27:04 [Note] /usr/libexec/mysqld: ready for connections.
    Version: '5.1.61' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
    121229 17:40:12 [Note] /usr/libexec/mysqld: Normal shutdown

    121229 17:40:12 [Note] Event Scheduler: Purging the queue. 0 events
    121229 17:40:12 InnoDB: Starting shutdown...
    121229 17:40:15 InnoDB: Shutdown completed; log sequence number 0 3687016
    121229 17:40:15 [Note] /usr/libexec/mysqld: Shutdown complete

    121229 17:40:15 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
    121229 17:43:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    121229 17:43:09 InnoDB: Initializing buffer pool, size = 8.0M
    121229 17:43:09 InnoDB: Completed initialization of buffer pool
    121229 17:43:09 InnoDB: Started; log sequence number 0 3687016
    121229 17:43:10 [Note] Event Scheduler: Loaded 0 events
    121229 17:43:10 [Note] /usr/libexec/mysqld: ready for connections.
    Version: '5.1.61' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution


  • Moderatore

    C'è scritto lì e cioè il modulo threading.pyc genera un'eccezione che non viene gestita.

    Imposta LogLevel debug in httpd.conf in modo da saperne di più sull'errore.


  • User Newbie

    Prima di tutto grazie della risposta. Domani mattina proverò a fare come mi hai suggerito. L'errore relativo al modulo threading.pyc è presente anche in altre righe del file di log relativi ad altre ore e non causa il crash del sito, come mai?


  • Moderatore

    Potrebbe benissimo essere che quell'errore porta a memory leak che, accumulandosi, portano al crash dopo tot ore.


  • User Newbie

    Grazie ancora per le informazioni! Ma le impostazione del LogLevel come mi hai indicato ovviamente mi daranno informazioni sui prossimi eventuali crash non su quelli passati, vero?


  • Moderatore

    Si sui prossimi