Re: [PacketFence-users] packetfence-pki on Debian Jessie

[David H. <da...@th...>]

I feel like there are clues here which almost have me there:

[wsgi:warn] [pid 31927] mod_wsgi: Compiled for Python/2.7.8.
[Thu Jun 22 16:32:35.008061 2017] [wsgi:warn] [pid 31927] mod_wsgi: Runtime
using Python/2.7.9.
[Thu Jun 22 16:32:35.008275 2017] [wsgi:alert] [pid 31927] (2)No such file
or directory: mod_wsgi (pid=31927): Couldn't bind unix domain socket
'/var/run/apache2/wsgi.31927.0.1.sock'.
[Thu Jun 22 16:32:35.009096 2017] [mpm_prefork:notice] [pid 31927] AH00163:
Apache/2.4.10 (Debian) OpenSSL/1.0.2k mod_wsgi/4.3.0 Python/2.7.9
configured -- resuming normal operations
[Thu Jun 22 16:32:35.009109 2017] [core:notice] [pid 31927] AH00094:
Command line: '/usr/sbin/apache2 -f
/usr/local/packetfence-pki/conf/httpd.conf'

And indeed there is no /var/run/apache2/wsgi.31927.0.1.sock

On Thu, Jun 22, 2017 at 4:17 PM, David Harvey <da...@th...>
wrote:

> FWIW, I also get the same bad request error after forcing apt with:
> dpkg -i --ignore-depends=python-django-bootstrap3
> packetfence-pki_1.0.4_all.deb
>
> On Thu, Jun 22, 2017 at 4:06 PM, David Harvey <da...@th...>
> wrote:
>
>> Hi packetfence users,
>>
>> I've been attmepting to experiment with packetfence-pki, but have fallen
>> at the first hurdle. Namely there doesn't seem to be a Debian Jessie
>> package avialable as advertised at https://packetfence.org/doc
>> /PacketFence_PKI_Quick_Install_Guide.html (section 3.1)
>> http://inverse.ca/downloads/PacketFence/debian/pool/jessie/p/
>>
>> I attempted to install the generic deb, but predictably it wouldn't
>> accept the pip installed version of django-bootstrap3 as apt doesn't know
>> about "python-django-bootstrap3".
>>
>> Attempted to install from source
>> <https://github.com/inverse-inc/packetfence-pki> which looked promising
>> until there was no service file that came with make install, so using an
>> init.d script (/etc/init.d/packetfence-pki.dpkg-new) admittedly origin
>> unknown I managed to get to complaints over
>> /usr/local/packetfence-pki/conf/server.crt and /usr/local/packetfence-pki/conf/server.key.
>> I dutifully copied the packetfence ones, and although the service starts, I
>> get a bad request 400 error when visiting https://server:9393.
>>
>> Now I understand I've mangled the instructions massively, so is there
>> a) A correct way to do this on Jessie any more?
>> b) A way of breathing life into my Frankenstein's monster?
>>
>> Thanks in advance,
>>
>> David
>>
>
>