Bug 179939 - www/gatling does not work with TLS in default installation
Summary: www/gatling does not work with TLS in default installation
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: tmseck
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-24 21:50 UTC by Lothar Braun
Modified: 2015-03-12 04:18 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lothar Braun 2013-06-24 21:50:00 UTC 
The gatling webserver does not work in its default configuration if TLS is enabled, throwing messages like:

Jun 24 22:26:51 horst-root gatling[57153]: accept 7 XXX.XXX.XXX.XXX 50018 1 https
Jun 24 22:26:51 horst-root gatling[57153]: ssl_protocol_error 7
Jun 24 22:26:51 horst-root gatling[57153]: close/readerr 7

This is due to the fact that /usr/local/etc/rc.d/gatling starting gating with the option -c (chroot). TLS support requires access to /dev/urandom to work properly

Fix: 

Mount the devfs in the chroot in the init script

mkdir -p $gatling_root/dev
mount -t devfs devfs $gatling_root/dev

before starting tlsgating
How-To-Repeat: Install gatling. Create a server.pem certificate by running "make cert" from the source (or generate a pem file by hand). Install the pem file at $gatling_root/server.pem. Start gatling and connect to the HTTPs port.
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2013-06-24 21:50:15 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->tmseck

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Carlo Strub freebsd_committer freebsd_triage 2014-09-14 10:33:02 UTC 
Is this PR still relevant?
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2015-03-12 04:18:04 UTC 
Feedback timeout (> 3 months).