Ok, I have been investigating further. Packetfence 9.0 is not supported on debian 8, but packetfence 8.3.0 is not available any more in debian 9 repository.
I tried to do an upgrade of the os from debian 8 to 9 but packetfence doesn't work anymore (no mariadb). Also, I can't install a fresh debian 9, with a fresh packetfence 8.3.0, then restore my backup on it, then upgrade. _I really don't see how to upgrade from packetfence 8.3.0 on debian 8 to packetfence 9.1.0 on debian 9 in any other way than doing a fresh install and reconfigure everything from scratch._ I really would like my questions answered, or a real communication done on the webside to _tell people that the support for debian is experimental_. I only found this information: https://github.com/inverse-inc/packetfence/issues/2460 Upgrading from a version prior to 9.0.0 Support for Debian 8 dropped Debian 8 will not be supported anymore for versions 9.0.0 and above. You should instead use Debian 9 now as it is currently the only supported Debian version. Le 28/10/2019 à 09:57, Guy BLAVIN via PacketFence-users a écrit : > Hello, > > Any idea on this ? > > > Guy > > Le 22/10/2019 à 18:00, Guy BLAVIN via PacketFence-users a écrit : >> Hello Fabrice, >> >> I tried to do an update, but the inverse.ca repository doesn't give a >> newer version (8.3.0 max on debian jessie). >> >> Any idea when v9.0 or v9.1 will be available in this repository ? >> >> Thank you, >> >> Guy Blavin >> >> Le 12/10/2019 à 03:01, Durand fabrice via PacketFence-users a écrit : >>> Hello Guy, >>> >>> Le 19-10-09 à 11 h 29, Guy BLAVIN via PacketFence-users a écrit : >>>> Hello all, >>>> >>>> On a 8.3.0 packetfence cluster of three nodes on debian 8.11 I have a >>>> lot of logs about Fingerbank but I don't use it, there is no API key and >>>> I read that it means it should be disabled. >>>> >>>> On the web services pages the service "fingerbank-collector" is >>>> grayed out. >>>> >>>> The logs that pfqueue tries to connect to 127.0.0.1:4723 >>>> Oct 9 17:18:05 PBRZNETIS005 pfqueue: pfqueue(21651) ERROR: >>>> [mac:unknown] Error while communicating with the Fingerbank collector. >>>> 500 Can't connect to 127.0.0.1:4723 >>>> (pf::fingerbank::endpoint_attributes) >>>> Oct 9 17:18:05 PBRZNETIS005 pfqueue: pfqueue(21651) ERROR: >>>> [mac:unknown] Unable to fetch query arguments for Fingerbank query. >>>> Aborting. (pf::fingerbank::process) >>>> Oct 9 17:18:06 PBRZNETIS005 pfqueue: pfqueue(21355) ERROR: >>>> [mac:unknown] Error while communicating with the Fingerbank collector. >>>> 500 Can't connect to 127.0.0.1:4723 >>>> (pf::fingerbank::endpoint_attributes) >>>> Oct 9 17:18:06 PBRZNETIS005 pfqueue: pfqueue(21355) ERROR: >>>> [mac:unknown] Unable to fetch query arguments for Fingerbank query. >>>> Aborting. (pf::fingerbank::process) >>>> Oct 9 17:18:21 PBRZNETIS005 pfqueue: pfqueue(21657) ERROR: >>>> [mac:unknown] Error while communicating with the Fingerbank collector. >>>> 500 Can't connect to 127.0.0.1:4723 >>>> (pf::fingerbank::endpoint_attributes) >>>> Oct 9 17:18:21 PBRZNETIS005 pfqueue: pfqueue(21657) ERROR: >>>> [mac:unknown] Unable to fetch query arguments for Fingerbank query. >>>> Aborting. (pf::fingerbank::process) >>>> >>>> What could I do to stop pfqueue from trying or any other thing that >>>> could resolve this issue ? >>> You can't really disable that. >>>> I have read quite a lot of older answers in the list, they mostly advise >>>> to restart some specific services; I did a pfcmd pf service restart >>>> successively on each node of the cluster, to no avail... >>>> >>>> >>>> Also, I still have this problem with the dashboard showing "what's going >>>> on?" on most of the graphs, and some servers and services are displayed >>>> as failed but at the same time the cluster state page says otherwise and >>>> they are actually all available. What could I do ? Would it be advisable >>>> to upgrade to another version (even if I have tried to install the exact >>>> same versions in a lab and I don't have these issues ?). >>>> >>> I recommand you to upgrade, this is some issues that have been fixed. >>> >>> Regards >>> >>> Fabrice >>> >>>> Thx for the help. >>>> >>>> Guy >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> PacketFence-users mailing list >>>> PacketFence-users@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/packetfence-users >>> _______________________________________________ >>> PacketFence-users mailing list >>> PacketFence-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/packetfence-users >> _______________________________________________ >> PacketFence-users mailing list >> PacketFence-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/packetfence-users > > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/packetfence-users
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
