500 - Internal error

Hi all!

I have this problem because I have tried to update lots of tickets.

I have resolved giving grant to the “rt3” database to the “_rt_user”
user.

But. now I can initialize session with no user :frowning: :frowning: :frowning:

Some idea??

PS. The installation is a production server that it worked fine until 18.30 :frowning:
:frowning:

Regards,

ALBERTO VILLANUEVA VAL

Consultor

Altran

ParqueEmpresarial Las Mercedes, Edificio 1
C/ Campezo, 1. 28022 Madrid
Tel : + 34 91 744 46 00
Fax: + 34 91 415 24 57

http://www.altran.es www.altran.es

What do the logs say ?-----Original Message-----
From: “Alberto Villanueva” alberto.villanueva@altran.es

Date: Thu, 19 Feb 2009 20:23:50
To: rt-users@lists.bestpractical.com
Subject: [rt-users] 500 - Internal error

http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

The rt log ("/var/log/rt.log") is empty :S :S :S

The log of apache (/var/log/httpd/error_log):

[Thu Feb 19 19:38:45 2009] [warning]: DBD::mysql::st execute failed: INSERT
command denied to user ‘vtd_rt_dbuser’@‘localhost’ for table ‘sessions’ at
/usr/lib/perl5/site_perl/5.10.0/Apache/Session/Store/DBI.pm line 44.
(/usr/lib/perl5/site_perl/5.10.0/Apache/Session/Store/DBI.pm:44)

The log of apache (/var/log/mysql_log):

090219 18:52:45 mysqld started
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090219 18:52:46 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer…
090219 18:52:51 InnoDB: Started; log sequence number 0 480031337
090219 18:52:54 [Note] /usr/sbin/mysqld-max: ready for connections.
Version: ‘5.0.51a-Max’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 SUSE
MySQL RPM
090219 19:22:37 [Note] /usr/sbin/mysqld-max: Normal shutdown

090219 19:22:37 InnoDB: Starting shutdown…
090219 19:22:39 InnoDB: Shutdown completed; log sequence number 0 482089083
090219 19:22:39 [Note] /usr/sbin/mysqld-max: Shutdown complete

090219 19:22:39 mysqld ended

090219 19:22:40 mysqld started
090219 19:22:40 InnoDB: Started; log sequence number 0 482089083
090219 19:22:40 [Note] /usr/sbin/mysqld-max: ready for connections.
Version: ‘5.0.51a-Max’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 SUSE
MySQL RPM
090219 19:39:40 [Note] /usr/sbin/mysqld-max: Normal shutdown

090219 19:39:40 InnoDB: Starting shutdown…
090219 19:39:42 InnoDB: Shutdown completed; log sequence number 0 482089083
090219 19:39:42 [Note] /usr/sbin/mysqld-max: Shutdown complete

090219 19:39:42 mysqld ended

090219 19:39:42 mysqld started
090219 19:39:42 InnoDB: Started; log sequence number 0 482089083
090219 19:39:42 [Note] /usr/sbin/mysqld-max: ready for connections.
Version: ‘5.0.51a-Max’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 SUSE
MySQL RPM
090219 19:48:36 [Note] /usr/sbin/mysqld-max: Normal shutdown

090219 19:48:38 InnoDB: Starting shutdown…
090219 19:48:39 InnoDB: Shutdown completed; log sequence number 0 482116559
090219 19:48:39 [Note] /usr/sbin/mysqld-max: Shutdown complete

090219 19:48:39 mysqld ended

090219 19:48:40 mysqld started
090219 19:48:40 InnoDB: Started; log sequence number 0 482116559
090219 19:48:40 [Note] /usr/sbin/mysqld-max: ready for connections.
Version: ‘5.0.51a-Max’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 SUSE
MySQL RPM
090219 19:50:42 [Note] /usr/sbin/mysqld-max: Normal shutdown

090219 19:50:42 InnoDB: Starting shutdown…
090219 19:50:43 InnoDB: Shutdown completed; log sequence number 0 482123150
090219 19:50:43 [Note] /usr/sbin/mysqld-max: Shutdown complete

090219 19:50:43 mysqld ended

090219 19:50:43 mysqld started
090219 19:50:43 InnoDB: Started; log sequence number 0 482123150
090219 19:50:43 [Note] /usr/sbin/mysqld-max: ready for connections.
Version: ‘5.0.51a-Max’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 SUSE
MySQL RPM
090219 19:52:22 [Note] /usr/sbin/mysqld-max: Normal shutdown

090219 19:52:22 InnoDB: Starting shutdown…
090219 19:52:24 InnoDB: Shutdown completed; log sequence number 0 482123150
090219 19:52:24 [Note] /usr/sbin/mysqld-max: Shutdown complete

090219 19:52:24 mysqld ended

090219 19:52:24 mysqld started
090219 19:52:24 InnoDB: Started; log sequence number 0 482123150
090219 19:52:24 [Note] /usr/sbin/mysqld-max: ready for connections.
Version: ‘5.0.51a-Max’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 SUSE
MySQL RPM
090219 20:03:34 [Note] /usr/sbin/mysqld-max: Normal shutdown

090219 20:03:36 InnoDB: Starting shutdown…
090219 20:03:37 InnoDB: Shutdown completed; log sequence number 0 482123160
090219 20:03:37 [Note] /usr/sbin/mysqld-max: Shutdown complete

090219 20:03:37 mysqld ended

090219 20:03:37 mysqld started
090219 20:03:38 InnoDB: Started; log sequence number 0 482123160
090219 20:03:38 [Note] /usr/sbin/mysqld-max: ready for connections.
Version: ‘5.0.51a-Max’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 SUSE
MySQL RPM
090219 20:19:43 [Note] /usr/sbin/mysqld-max: Normal shutdown

090219 20:19:45 InnoDB: Starting shutdown…
090219 20:19:46 InnoDB: Shutdown completed; log sequence number 0 482123160
090219 20:19:46 [Note] /usr/sbin/mysqld-max: Shutdown complete

090219 20:19:46 mysqld ended

090219 20:19:46 mysqld started
090219 20:19:46 InnoDB: Started; log sequence number 0 482123160
090219 20:19:46 [Note] /usr/sbin/mysqld-max: ready for connections.
Version: ‘5.0.51a-Max’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 SUSE
MySQL RPM

Thanks!

Regards,

ALBERTO VILLANUEVA VAL
Consultor
Altran
ParqueEmpresarial Las Mercedes, Edificio 1
C/ Campezo, 1. 28022 Madrid
Tel : + 34 91 744 46 00
Fax: + 34 91 415 24 57
www.altran.es-----Mensaje original-----
De: chaim.rieger@gmail.com [mailto:chaim.rieger@gmail.com]
Enviado el: jueves, 19 de febrero de 2009 20:30
Para: Alberto Villanueva; rt-users-bounces@lists.bestpractical.com;
rt-users@lists.bestpractical.com
Asunto: Re: [rt-users] 500 - Internal error

What do the logs say ?

-----Original Message-----
From: “Alberto Villanueva” alberto.villanueva@altran.es

Date: Thu, 19 Feb 2009 20:23:50
To: rt-users@lists.bestpractical.com
Subject: [rt-users] 500 - Internal error

http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Alberto Villanueva wrote:

The rt log ("/var/log/rt.log") is empty :S :S :S

The log of apache (/var/log/httpd/error_log):

[Thu Feb 19 19:38:45 2009] [warning]: DBD::mysql::st execute failed: INSERT
command denied to user ‘vtd_rt_dbuser’@‘localhost’ for table ‘sessions’ at
/usr/lib/perl5/site_perl/5.10.0/Apache/Session/Store/DBI.pm line 44.
(/usr/lib/perl5/site_perl/5.10.0/Apache/Session/Store/DBI.pm:44)

Looks like vtd_rt_dbuser lacks the proper MySQL permissions write to the
sessions table.

Regards
Racke

LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team