Bug#744944: repro: Dies without explanation when finding startup problems

[Martín Ferrari]

Package: repro
Version: 1.9.6-1
Severity: normal

Repro has a tendency to be unbearably verbose in its logging, but when it
encounters a problem during start-up, it just dies without a trace.

It even logs to syslog if you pass a wrong command line argument, which is
silly, but you will need to manually start it, with special parameters, to see
it could not bind to a port (and it does not even tell me which one!):

# su -s /bin/bash -c "/usr/sbin/repro /etc/repro/repro.config --Daemonize=false -l=cout" repro
Likely a port is already in use
Failed to start repro, exiting...


This is *very* unfriendly to debug issues.

-- System Information:
Debian Release: 7.4
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages repro depends on:
ii  adduser                3.113+nmu3
ii  libc-ares2             1.9.1-3
ii  libc6                  2.18-4
ii  libdb5.3++             5.3.28-3
ii  libfreeradius-client2  1.1.6-7
ii  libgcc1                1:4.7.2-5
ii  libmysqlclient18       5.5.35+dfsg-0+wheezy1
ii  libpython2.7           2.7.3-6+deb7u2
ii  libresiprocate-1.9     1.9.6-1
ii  libssl1.0.0            1.0.1e-2+deb7u6
ii  libstdc++6             4.7.2-5
ii  multiarch-support      2.13-38+deb7u1

Versions of packages repro recommends:
ii  apache2-utils              2.2.22-13+deb7u1
ii  openssl                    1.0.1e-2+deb7u6
pn  stun-server | turn-server  <none>

Versions of packages repro suggests:
pn  jscommunicator-web-phone  <none>

-- Configuration Files:
/etc/repro/repro.config changed [not included]
/etc/repro/users.txt changed [not included]

-- no debconf information