> On Jun 12, 2017, at 14:48, lists via PacketFence-users
> <[email protected]> wrote:
>
> Hi,
>
> So, just for fun I tried a fresh install of packetfence 7.1.0 on debian 8.
>
> As far as I know, we need to configure the OS debian to start mysql.
No, you don't.
Not anymore anyway.
Systemd will automatically start the packetfence-mariadb service if you start
packetfence.
>
> However, also Packetfence tries to start something on port 3306 as well
> (haproxy) so there seems to be a conflict? Found that out, because I
> initially had forgotten to enable the mysql systemd service.
>
There is no conflict.
That is the expected behaviour.
> Manually starting mysql after install didn't work, because port 3306 was
> already taken by haproxy. Is that intentional?
>
Yes.
You are not supposed to use the mysql service.
You are expected to let systemd do the work for you.
When you run "systemctl isolate packetfence" systemd will start all the
packetfence services, and all services required by them.
For example, the packetfence-httpd.admin.service unit files defines these
dependencies:
Wants=packetfence-base.target packetfence-config.service
And in turn, the packetfence-base.target includes the
packetfence-mariadb.service.
So you don't have to do anything about mysql, and in fact you are making your
life harder by starting it.
Regards,
--
Louis Munro
[email protected] <mailto:[email protected]> :: www.inverse.ca
<http://www.inverse.ca/>
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu/>) and
PacketFence (www.packetfence.org <http://www.packetfence.org/>)
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
