The easiest way here will be to recreate your database.
Connect as root in mysql and do:
drop database pf;
drop database pf_graphite;
You also need to remove a file with:
rm conf/currently-at
After that restart PacketFence, and when you try to reach the admin you
will be redirected to the configurator, you will need to re-do it.
Thanks,
On 01/08/2016 01:07 PM, Jason Maher wrote:
Looks like the user isn’t present. How do I go about creating one?
mysql> use mysql;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> select * from user where User="pf" \G
Empty set (0.00 sec)
*Jason A. Maher*
*Network Engineer*
*Multi-State Lottery*
*P: 515-453-1408*
*F: 515-453-1420*
*From:*Antoine Amacher [mailto:[email protected]]
*Sent:* Friday, January 08, 2016 11:50 AM
*To:* [email protected]
*Subject:* Re: [PacketFence-users] Packetfence Dependencies trouble
Is the user pf existing in the database, while logged as root, do:
use mysql;
select * from user where User="pf" \G
If the user is present and is still doesn't work you could try to
change the password of the user pf.
On 01/08/2016 12:38 PM, Jason Maher wrote:
Looks like root worked but pf did not.
musl@PacketFence:/usr/local/pf/conf$ mysql -u pf -p
Enter password:
ERROR 1045 (28000): Access denied for user 'pf'@'localhost' (using
password: YES)
musl@PacketFence:/usr/local/pf/conf$ mysql -u root -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 473
Server version: 5.5.46-0ubuntu0.12.04.2 (Ubuntu)
Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights
reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current
input statement.
mysql>
*Jason A. Maher*
*Network Engineer*
*Multi-State Lottery*
*P: 515-453-1408*
*F: 515-453-1420*
*From:*Antoine Amacher [mailto:[email protected]]
*Sent:* Friday, January 08, 2016 11:33 AM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [PacketFence-users] Packetfence Dependencies trouble
Are you able to connect to the database?
with for instance:
mysql -u pf -p
or
mysql -u root -p
Thanks,
On 01/08/2016 12:12 PM, Jason Maher wrote:
I updated this file with the correct password… now I only have
these errors left.
^Cmusl@PacketFence:/usr/local/pf/conf$ sudo
/etc/init.d/packetfence start
[sudo] password for musl:
* Starting packetfence service|command
httpd.admin|already started
redis_queue|already started
Checking configuration sanity...
Could not write namespace config::PfDefault to L2 cache ! This
is bad.
Could not write namespace config::Documentation to L2 cache !
This is bad.
Could not write namespace config::Cluster to L2 cache ! This
is bad.
Could not write namespace config::PfDefault to L2 cache ! This
is bad.
Could not write namespace config::Documentation to L2 cache !
This is bad.
Could not write namespace config::Cluster to L2 cache ! This
is bad.
unable to connect to database: Access denied for user
'pf'@'localhost' (using password: YES) at
/usr/local/pf/lib/pf/version.pm line 42.
*Jason A. Maher*
*Network Engineer*
*Multi-State Lottery*
*P: 515-453-1408*
*F: 515-453-1420*
*From:*Antoine Amacher [mailto:[email protected]]
*Sent:* Friday, January 08, 2016 10:40 AM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [PacketFence-users] Packetfence Dependencies
trouble
Can you verify that the password in conf/pfconfig.conf for the
user pf is the one you setup during the configurator?
Thank you
On 01/08/2016 11:12 AM, Jason Maher wrote:
Yes it is and yes I have.
Uptime: 68221 Threads: 1 Questions: 106 Slow queries: 0
Opens: 48 Flush tables: 1 Open tables: 41 Queries per
second avg: 0.001
*Jason A. Maher*
*Network Engineer*
*Multi-State Lottery*
*P: 515-453-1408*
*F: 515-453-1420*
*From:*Antoine Amacher [mailto:[email protected]]
*Sent:* Friday, January 08, 2016 8:10 AM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [PacketFence-users] Packetfence
Dependencies trouble
Jason,
Is mysql running?
Did you went through the configurator already?
Thanks,
On 01/07/2016 05:57 PM, Jason Maher wrote:
Next problem…. Im receiving these errors.
musl@PacketFence:/usr/local/pf/conf$ sudo
/etc/init.d/packetfence restart
* Stopping packetfence service|command
carbon-cache|already stopped
carbon-relay|already stopped
collectd|already stopped
dhcpd|already stopped
haproxy|already stopped
httpd.aaa|already stopped
httpd.admin|stop
httpd.graphite|already stopped
httpd.portal|already stopped
httpd.proxy|already stopped
httpd.webservices|already stopped
iptables|already stopped
p0f|already stopped
pfbandwidthd|already stopped
pfdetect|already stopped
pfdns|already stopped
pfmon|already stopped
pfqueue|already stopped
pfsetvlan|already stopped
radiusd-acct|already stopped
radiusd|already stopped
radsniff3|already stopped
redis_queue|stop
snmptrapd|already stopped
snort|already stopped
statsd|already stopped
suricata|already stopped
keepalived|already stopped
* Starting packetfence service|command
Could not write namespace config::PfDefault to L2
cache ! This is bad.
Could not write namespace config::Documentation to L2
cache ! This is bad.
Could not write namespace config::Cluster to L2 cache
! This is bad.
Could not write namespace config::Pf to L2 cache !
This is bad.
Could not write namespace interfaces to L2 cache !
This is bad.
Could not write namespace config::Network to L2 cache
! This is bad.
Could not write namespace config::Authentication to L2
cache ! This is bad.
Could not write namespace config::Switch to L2 cache !
This is bad.
Could not write namespace config::Domain to L2 cache !
This is bad.
Could not write namespace resource::fqdn to L2 cache !
This is bad.
Could not write namespace config::AdminRoles to L2
cache ! This is bad.
Could not write namespace config::ApacheFilters to L2
cache ! This is bad.
Could not write namespace config::Authentication to L2
cache ! This is bad.
Could not write namespace
resource::authentication_config_hash to L2 cache !
This is bad.
Could not write namespace
resource::authentication_lookup to L2 cache ! This is bad.
Could not write namespace
resource::authentication_sources to L2 cache ! This is
bad.
Could not write namespace config::Profiles to L2 cache
! This is bad.
Could not write namespace
resource::guest_self_registration to L2 cache ! This
is bad.
Could not write namespace config::BillingTiers to L2
cache ! This is bad.
Could not write namespace config::Cluster to L2 cache
! This is bad.
Could not write namespace config::Pf to L2 cache !
This is bad.
Could not write namespace resource::CaptivePortal to
L2 cache ! This is bad.
Could not write namespace resource::Database to L2
cache ! This is bad.
Could not write namespace resource::fqdn to L2 cache !
This is bad.
Could not write namespace config::Pfdetect to L2 cache
! This is bad.
Could not write namespace interfaces to L2 cache !
This is bad.
Could not write namespace interfaces::listen_ints to
L2 cache ! This is bad.
Could not write namespace
interfaces::dhcplistener_ints to L2 cache ! This is bad.
Could not write namespace interfaces::ha_ints to L2
cache ! This is bad.
Could not write namespace interfaces::internal_nets to
L2 cache ! This is bad.
Could not write namespace
interfaces::inline_enforcement_nets to L2 cache ! This
is bad.
Could not write namespace
interfaces::vlan_enforcement_nets to L2 cache ! This
is bad.
Could not write namespace interfaces::monitor_int to
L2 cache ! This is bad.
Could not write namespace
interfaces::management_network to L2 cache ! This is bad.
Could not write namespace interfaces::portal_ints to
L2 cache ! This is bad.
Could not write namespace interfaces::inline_nets to
L2 cache ! This is bad.
Could not write namespace
interfaces::routed_isolation_nets to L2 cache ! This
is bad.
Could not write namespace
interfaces::routed_registration_nets to L2 cache !
This is bad.
Could not write namespace resource::cluster_servers to
L2 cache ! This is bad.
Could not write namespace resource::cluster_hosts to
L2 cache ! This is bad.
Could not write namespace config::Documentation to L2
cache ! This is bad.
Could not write namespace config::Domain to L2 cache !
This is bad.
Could not write namespace resource::domain_dns_servers
to L2 cache ! This is bad.
Could not write namespace config::Firewall_SSO to L2
cache ! This is bad.
Could not write namespace config::FloatingDevices to
L2 cache ! This is bad.
Could not write namespace config::Network to L2 cache
! This is bad.
Could not write namespace interfaces to L2 cache !
This is bad.
Could not write namespace interfaces::listen_ints to
L2 cache ! This is bad.
Could not write namespace
interfaces::dhcplistener_ints to L2 cache ! This is bad.
Could not write namespace interfaces::ha_ints to L2
cache ! This is bad.
Could not write namespace interfaces::internal_nets to
L2 cache ! This is bad.
Could not write namespace
interfaces::inline_enforcement_nets to L2 cache ! This
is bad.
Could not write namespace
interfaces::vlan_enforcement_nets to L2 cache ! This
is bad.
Could not write namespace interfaces::monitor_int to
L2 cache ! This is bad.
Could not write namespace
interfaces::management_network to L2 cache ! This is bad.
Could not write namespace interfaces::portal_ints to
L2 cache ! This is bad.
Could not write namespace interfaces::inline_nets to
L2 cache ! This is bad.
Could not write namespace
interfaces::routed_isolation_nets to L2 cache ! This
is bad.
Could not write namespace
interfaces::routed_registration_nets to L2 cache !
This is bad.
Could not write namespace config::PKI_Provider to L2
cache ! This is bad.
Could not write namespace config::PfDefault to L2
cache ! This is bad.
Could not write namespace config::Pf to L2 cache !
This is bad.
Could not write namespace resource::CaptivePortal to
L2 cache ! This is bad.
Could not write namespace resource::Database to L2
cache ! This is bad.
Could not write namespace resource::fqdn to L2 cache !
This is bad.
Could not write namespace config::Pfdetect to L2 cache
! This is bad.
Could not write namespace interfaces to L2 cache !
This is bad.
Could not write namespace interfaces::listen_ints to
L2 cache ! This is bad.
Could not write namespace
interfaces::dhcplistener_ints to L2 cache ! This is bad.
Could not write namespace interfaces::ha_ints to L2
cache ! This is bad.
Could not write namespace interfaces::internal_nets to
L2 cache ! This is bad.
Could not write namespace
interfaces::inline_enforcement_nets to L2 cache ! This
is bad.
Could not write namespace
interfaces::vlan_enforcement_nets to L2 cache ! This
is bad.
Could not write namespace interfaces::monitor_int to
L2 cache ! This is bad.
Could not write namespace
interfaces::management_network to L2 cache ! This is bad.
Could not write namespace interfaces::portal_ints to
L2 cache ! This is bad.
Could not write namespace interfaces::inline_nets to
L2 cache ! This is bad.
Could not write namespace
interfaces::routed_isolation_nets to L2 cache ! This
is bad.
Could not write namespace
interfaces::routed_registration_nets to L2 cache !
This is bad.
Could not write namespace config::Profiles to L2 cache
! This is bad.
Could not write namespace FilterEngine::Profile to L2
cache ! This is bad.
Could not write namespace resource::URI_Filters to L2
cache ! This is bad.
Could not write namespace config::Provisioning to L2
cache ! This is bad.
Could not write namespace config::RadiusFilters to L2
cache ! This is bad.
Could not write namespace FilterEngine::RadiusScopes
to L2 cache ! This is bad.
Could not write namespace config::Realm to L2 cache !
This is bad.
Could not write namespace config::Scan to L2 cache !
This is bad.
Could not write namespace config::Switch to L2 cache !
This is bad.
Could not write namespace resource::default_switch to
L2 cache ! This is bad.
Could not write namespace resource::switches_ranges to
L2 cache ! This is bad.
Could not write namespace config::Violations to L2
cache ! This is bad.
Could not write namespace FilterEngine::Violation to
L2 cache ! This is bad.
Could not write namespace
resource::accounting_triggers to L2 cache ! This is bad.
Could not write namespace
resource::bandwidth_expired_violations to L2 cache !
This is bad.
Could not write namespace config::VlanFilters to L2
cache ! This is bad.
Could not write namespace FilterEngine::VlanScopes to
L2 cache ! This is bad.
Could not write namespace config::Wmi to L2 cache !
This is bad.
Could not write namespace resource::array_test to L2
cache ! This is bad.
Could not write namespace resource::reverse_fqdn to L2
cache ! This is bad.
apache2: Could not reliably determine the server's
fully qualified domain name, using 127.0.1.1 for
ServerName
httpd.admin|start
redis_queue|start
Checking configuration sanity...
Could not write namespace config::PfDefault to L2
cache ! This is bad.
Could not write namespace config::Documentation to L2
cache ! This is bad.
Could not write namespace config::Cluster to L2 cache
! This is bad.
Could not write namespace config::PfDefault to L2
cache ! This is bad.
Could not write namespace config::Documentation to L2
cache ! This is bad.
Could not write namespace config::Cluster to L2 cache
! This is bad.
unable to connect to database: Access denied for user
'pf'@'localhost' (using password: YES) at
/usr/local/pf/lib/pf/version.pm line 42.
*Jason A. Maher*
*Network Engineer*
*Multi-State Lottery*
*P: 515-453-1408*
*F: 515-453-1420*
*From:*Jason Maher
*Sent:* Thursday, January 07, 2016 11:07 AM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* RE: [PacketFence-users] Packetfence
Dependencies trouble
Your right guys! I ended up resolving this by using
the command:
Sudo rm –rf /var/lib/apt/lists/*
sudo apt-get update
*Jason A. Maher*
*Network Engineer*
*Multi-State Lottery*
*P: 515-453-1408*
*F: 515-453-1420*
*From:*Louis Munro [mailto:[email protected]]
*Sent:* Thursday, January 07, 2016 9:46 AM
*To:* [email protected]
<mailto:[email protected]>
*Subject:* Re: [PacketFence-users] Packetfence
Dependencies trouble
On Jan 6, 2016, at 17:51 , Jason Maher
<[email protected] <mailto:[email protected]>> wrote:
Still the same trouble with Ubuntu 12.04 any thoughts?
Works just fine for me on a brand new install of 12.04.
It looks like a misconfiguration in your apt sources
(possibly).
Please show us your /etc/apt/sources.list and
/etc/apt/sources.list.d/*
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>)
CONFIDENTIAL INFORMATION DO NOT DISTRIBUTE - The
information in this email and any attachments is
confidential, privileged and intended only for the
recipient listed above. If you have received this
message in error, please notify the sender immediately
by email or telephone and delete the original message.
Do not distribute the contents of this email or any
attachments without specific authorization of the sender.
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/packetfence-users
--
Antoine Amacher
[email protected] <mailto:[email protected]> :: +1.514.447.4918
*130 ::www.inverse.ca <http://www.inverse.ca>
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu>)
and PacketFence (www.packetfence.org <http://www.packetfence.org>)
CONFIDENTIAL INFORMATION DO NOT DISTRIBUTE - The
information in this email and any attachments is
confidential, privileged and intended only for the
recipient listed above. If you have received this message
in error, please notify the sender immediately by email or
telephone and delete the original message. Do not
distribute the contents of this email or any attachments
without specific authorization of the sender.
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/packetfence-users
--
Antoine Amacher
[email protected] <mailto:[email protected]> :: +1.514.447.4918 *130
::www.inverse.ca <http://www.inverse.ca>
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu>) and
PacketFence (www.packetfence.org <http://www.packetfence.org>)
CONFIDENTIAL INFORMATION DO NOT DISTRIBUTE - The information
in this email and any attachments is confidential, privileged
and intended only for the recipient listed above. If you have
received this message in error, please notify the sender
immediately by email or telephone and delete the original
message. Do not distribute the contents of this email or any
attachments without specific authorization of the sender.
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/packetfence-users
--
Antoine Amacher
[email protected] <mailto:[email protected]> :: +1.514.447.4918 *130
::www.inverse.ca <http://www.inverse.ca>
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu>) and
PacketFence (www.packetfence.org <http://www.packetfence.org>)
CONFIDENTIAL INFORMATION DO NOT DISTRIBUTE - The information in
this email and any attachments is confidential, privileged and
intended only for the recipient listed above. If you have received
this message in error, please notify the sender immediately by
email or telephone and delete the original message. Do not
distribute the contents of this email or any attachments without
specific authorization of the sender.
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/packetfence-users
--
Antoine Amacher
[email protected] <mailto:[email protected]> :: +1.514.447.4918 *130
::www.inverse.ca <http://www.inverse.ca>
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu>) and
PacketFence (www.packetfence.org <http://www.packetfence.org>)
CONFIDENTIAL INFORMATION DO NOT DISTRIBUTE - The information in this
email and any attachments is confidential, privileged and intended
only for the recipient listed above. If you have received this message
in error, please notify the sender immediately by email or telephone
and delete the original message. Do not distribute the contents of
this email or any attachments without specific authorization of the
sender.
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
--
Antoine Amacher
[email protected] :: +1.514.447.4918 *130 :: www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
