[request-tracker-maintainers] Rt 4.4.1

[TheSin]

Sorry that last one had the errors if /etc/request-tracker4/RT_SiteConfig.pm wasn’t writable by www-data, I’ve done a chgrp www-data and chmod g+w on it and this is the error now

RT couldn't connect to the database where tickets are stored.
If this is a new installation of RT, you should visit the URL below
to configure RT and initialize your database.

If this is an existing RT installation, this may indicate a database
connectivity problem.

The error RT got back when trying to connect to your database was:

install_driver(Pg) failed: Can't locate DBD/Pg.pm in @INC (you may need to install the DBD::Pg module) (@INC contains: /usr/local/share/request-tracker4/lib /usr/share/request-tracker4/lib /etc/perl /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 66) line 3.
Perhaps the DBD::Pg perl module hasn't been fully installed,
or perhaps the capitalisation of 'Pg' isn't right.
Available drivers: DBM, ExampleP, File, Gofer, Proxy, Sponge, mysql.
 at /usr/share/perl5/DBIx/SearchBuilder/Handle.pm line 106.


WARNING: RT couldn't start up a web server on port 80.
This is often the case if the port is already in use or you're running /usr/share/request-tracker4/libexec/rt-server.fcgi
as someone other than your system's "root" user.  You may also specify a
temporary port with: /usr/share/request-tracker4/libexec/rt-server.fcgi --port <port>
[Mon Feb 06 12:54:26.296804 2017] [:warn] [pid 5045] FastCGI: server "/usr/share/request-tracker4/libexec/rt-server.fcgi" (pid 5046) terminated by calling exit with status '1'

---
TS
http://www.southofheaven.org/
Life begins and ends with chaos, live between the chaos!

> On Feb 6, 2017, at 12:30 PM, Dominic Hargreaves <dom at earth.li> wrote:
> 
> On Mon, Feb 06, 2017 at 12:15:19PM -0700, TheSin wrote:
>> I did the update this morning which clears out /etc/request-tracker4/RT_SiteConfig.pm to prefer the .d style, sadly this make every version of apache2 configure no longer work since they are trying to load the .pm.  I’ve tried changing it to use .d/*.pm but still doesn’t work, I really need to get it back up with apache2, I don’t care if it’s perl2, rigid or fastcgi (what I was using till now).  What went wrong in the update, how can I fix this issue?  I’d make a bug report but I’m not sure if it’s a package bug of just on my end, all I know if I can’t get it to start at all and it won’t read any config and tries to use the Pg.pm no matter what I do and I”m not using Pg, I’m using mysql.
> 
> Hi there,
> 
> Sorry to hear that you had trouble. Please could you poste the exact
> error messages you received so that we can help diagnose the problem?
> 
> Relevant parts of your Apache configuration would also be useful.
> 
> Thanks,
> Dominic.