Package: rt4-fcgi
Version: 4.4.1-3+deb9u3
Severity: important

Dear Maintainer,

The daemon is enabled in /etc/default/rt4-fcgi.
Without any fix, when I launch the daemon, this one restarts constantly:

root@vm-rt:~# tail -n 20 /var/log/daemon.log
Feb  2 10:07:23 vm-rt systemd[1]: rt4-fcgi.service: Unit entered failed state.
Feb  2 10:07:23 vm-rt systemd[1]: rt4-fcgi.service: Failed with result 
'exit-code'.
Feb  2 10:07:28 vm-rt systemd[1]: rt4-fcgi.service: Service hold-off time over, 
scheduling restart.
Feb  2 10:07:28 vm-rt systemd[1]: Stopped request-tracker4 FastCGI daemon.
Feb  2 10:07:28 vm-rt systemd[1]: Starting request-tracker4 FastCGI daemon...
Feb  2 10:07:29 vm-rt rt4-fcgi[4227]: spawn-fcgi: child spawned successfully: 
PID: 4228
Feb  2 10:07:29 vm-rt rt4-fcgi[4227]: spawn-fcgi: child spawned successfully: 
PID: 4229
Feb  2 10:07:29 vm-rt systemd[1]: Started request-tracker4 FastCGI daemon.
Feb  2 10:07:30 vm-rt systemd[1]: rt4-fcgi.service: Main process exited, 
code=exited, status=1/FAILURE
Feb  2 10:07:30 vm-rt systemd[1]: rt4-fcgi.service: Unit entered failed state.
Feb  2 10:07:30 vm-rt systemd[1]: rt4-fcgi.service: Failed with result 
'exit-code'.
Feb  2 10:07:35 vm-rt systemd[1]: rt4-fcgi.service: Service hold-off time over, 
scheduling restart.
Feb  2 10:07:35 vm-rt systemd[1]: Stopped request-tracker4 FastCGI daemon.
Feb  2 10:07:35 vm-rt systemd[1]: Starting request-tracker4 FastCGI daemon...
Feb  2 10:07:36 vm-rt rt4-fcgi[4235]: spawn-fcgi: child spawned successfully: 
PID: 4236
Feb  2 10:07:36 vm-rt rt4-fcgi[4235]: spawn-fcgi: child spawned successfully: 
PID: 4237
Feb  2 10:07:36 vm-rt systemd[1]: Started request-tracker4 FastCGI daemon.
Feb  2 10:07:37 vm-rt systemd[1]: rt4-fcgi.service: Main process exited, 
code=exited, status=1/FAILURE
Feb  2 10:07:37 vm-rt systemd[1]: rt4-fcgi.service: Unit entered failed state.
Feb  2 10:07:37 vm-rt systemd[1]: rt4-fcgi.service: Failed with result 
'exit-code'.

To find where it came from, I launch rt-server directly :

root@vm-rt:~# /usr/share/request-tracker4/libexec/rt-server.fcgi --socket 
/var/run/rt4-fcgi.sock
[3501] [Fri Feb  2 08:57:31 2018] [critical]: Something went wrong while trying 
to run RT's standalone web server:
        Can't locate FCGI/ProcManager.pm in @INC (you may need to install the 
FCGI::ProcManager 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 
/usr/share/perl5/Plack/Util.pm line 26. 
(/usr/share/request-tracker4/lib/RT.pm:394)
Something went wrong while trying to run RT's standalone web server:
        Can't locate FCGI/ProcManager.pm in @INC (you may need to install the 
FCGI::ProcManager 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 
/usr/share/perl5/Plack/Util.pm line 26.

To fix this error, installation of the following package is required:  
libfcgi-procmanager-perl
So, I think is a good things to add the package in dep or at least rec.

Thanks a lot for your work.

Best regards,
A. LE GALL.

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rt4-fcgi depends on:
ii  libfcgi-perl  0.78-2
ii  lsb-base      9.20161125
ii  procps        2:3.3.12-3
ii  spawn-fcgi    1.6.4-1+b1

Versions of packages rt4-fcgi recommends:
ii  nginx-full  1.10.3-1+deb9u1

rt4-fcgi suggests no packages.

-- Configuration Files:
/etc/default/rt4-fcgi changed:
enabled=1
workers=2


-- no debconf information

Reply via email to