Re: [PacketFence-users] PF 10.0.0 webadmin won't start after Upgrade

2020-04-24 Thread felix13890--- via PacketFence-users 
    packetfence-pfmon.service   started   25271    packetfence-pfperl-api.service  started   19671    packetfence-pfpki.service   started   25244    packetfence-pfqueue.service started   25370    packetfence-pfsso.service   started   25235    packetfence-pfstats.service started   25273    packetfence-radiusd-acct.service    disabled  0    packetfence-radiusd-auth.service    started   26133    packetfence-radiusd-cli.service started   26037    packetfence-radiusd-eduroam.service disabled  0    packetfence-radiusd-load_balancer.service   started   26154    packetfence-radsniff.service    started   25603    packetfence-redis-cache.service started   2035 packetfence-redis_ntlm_cache.service    started   25356    packetfence-redis_queue.service started   25340    packetfence-snmptrapd.service   disabled  0    packetfence-tc.service  disabled  0    packetfence-tracking-config.service disabled  1    packetfence-winbindd.service    started   26034   When accessing the webinterface, there’s a message „come back later“ Best regardsFelix  Von: Nicolas Quiniou-Briand via PacketFence-usersGesendet: Mittwoch, 22. April 2020 16:03An: packetfence-users@lists.sourceforge.netCc: Nicolas Quiniou-BriandBetreff: Re: [PacketFence-users] PF 10.0.0 webadmin won't start after Upgrade   On 22/04/2020 12:44, felix13890--- via PacketFence-users wrote:> AH00558: httpd: Could not reliably determine the server's fully > qualified domain name, using 172.20.5.14. Set the 'ServerName' directive > globally to suppress this message This message doesn't mean that web admin is not started. Could you give us output of /usr/local/pf/bin/pfcmd service pf status ?  -- Nicolas Quiniou-Briandn...@inverse.ca  ::  +1.514.447.4918 *140  ::  https://inverse.caInverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence (https://packetfence.org) and Fingerbank (http://fingerbank.org)  ___PacketFence-users mailing listPacketFence-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/packetfence-users ___
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Re: [PacketFence-users] PF 10.0.0 webadmin won't start after Upgrade

2020-04-22 Thread Nicolas Quiniou-Briand via PacketFence-users 




On 22/04/2020 12:44, felix13890--- via PacketFence-users wrote:
AH00558: httpd: Could not reliably determine the server's fully 
qualified domain name, using 172.20.5.14. Set the 'ServerName' directive 
globally to suppress this message


This message doesn't mean that web admin is not started. Could you give 
us output of /usr/local/pf/bin/pfcmd service pf status ?



--
Nicolas Quiniou-Briand
n...@inverse.ca  ::  +1.514.447.4918 *140  ::  https://inverse.ca
Inverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence 
(https://packetfence.org) and Fingerbank (http://fingerbank.org)



___
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users

[PacketFence-users] PF 10.0.0 webadmin won't start after Upgrade

2020-04-22 Thread felix13890--- via PacketFence-users 
Hello Folks! After upgrading to 10.0.0 from 9.3.0 I’m unable to start the webadmin interface. Here the message from systemctl:AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 172.20.5.14. Set the 'ServerName' directive globally to suppress this message  I’ve already tried to set the hostname in pf.conf to the clusters Name instead of the servers name and checked the /etc/hosts so it can resolve the different servers in the cluster. Any ideas?

___
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users