Problem with RT/Debian

1

Hi everyone.

I currently is in the process to migrate a RT 5.0.5 on FreeBSD to RT 5.0.7 on Debian.

The problem I got under Debian is to got randomly this kind of error

Sep 22 11:14:48 support-test mariadbd[29271]: 2025-09-22 11:14:48 34 [Warning] Aborted connection 34 to db: ‘rt’ user: ‘rt’ host: ‘support-test’ (Got an error reading communication packets) Sep 22 11:14:48 support-test mariadbd[29271]: 2025-09-22 11:14:48 35 [Warning] Aborted connection 35 to db: ‘rt’ user: ‘rt’ host: ‘support-test’ (Got an error reading communication packets) Sep 22 11:14:57 support-test mariadbd[29271]: 2025-09-22 11:14:57 36 [Warning] Aborted connection 36 to db: ‘rt’ user: ‘rt’ host: ‘support-test’ (Got an error reading communication packets) Sep 22 11:14:57 support-test mariadbd[29271]: 2025-09-22 11:14:57 37 [Warning] Aborted connection 37 to db: ‘rt’ user: ‘rt’ host: ‘support-test’ (Got an error reading communication packets) Sep 22 11:20:23 support-test mariadbd[29271]: 2025-09-22 11:20:23 39 [Warning] Aborted connection 39 to db: ‘rt’ user: ‘rt’ host: ‘support-test’ (Got an error reading communication packets) Sep 22 11:20:23 support-test mariadbd[29271]: 2025-09-22 11:20:23 38 [Warning] Aborted connection 38 to db: ‘rt’ user: ‘rt’ host: ‘support-test’ (Got an error reading communication packets)

I try everything I can think of in the tunning of mariadb. But no luck. (Note the RT/apache are on the same server as the database so no network issue.

It seem it’s work a better with fcgi instead of mod_perl (even I’m not sure to see why).

I also try to use postgresql instead of mariadb, and It seem also work better (no connection problem) but postgresql is slower than mariadb in the render of one ticket.

Any one have a idea why those pb of connection ? It’s more obvious in the render of the dashboard. Less with one ticket.

2

Can you ping that host - ‘support-test’ from within Debian?
Perhaps you need to add an entry in /etc/hosts for it?
Migrating RT shouldn’t be that difficult.

3

Yes no problem. And I didn’t say it’s not working at all. I way It’s stop working randomly. For example if you load the «dashboard» 5 times, you end up with 2 time with blank page and the error message in the apache log. The other 3 times you get the correct page.

I end up with fcgi and it’s working. I don’t understand why with mod_perl it’s not working.

It’s not the first time I upgrade RT…using RT since 2008 :wink: :wink:

First time I got this super weird issue.

4

Is this using the Debian packages for RT?

5

Yes. Everything is install through apt

6

Okay, interesting. I’m using request-tracker5 from Trixie (so 5.0.7) with modperl2 and that works okay with PostgreSQL.