Discussion:
[PacketFence-devel] requesting diagnostic help
Boris Epstein
2015-07-02 20:54:18 UTC
Permalink
Hello all,

Any help with diagnosing the source of these messages will be appreciated.

[***@pf1 pf]# service packetfence start
Starting PacketFence...Set name-type for VLAN subsystem. Should be visible
in /p
roc/net/vlan/config
service|command
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_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 i s 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::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 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 ba d.
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 i s 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 b ad.
Could not write namespace interfaces::portal_ints 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 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 ba d.
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 i s 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 b ad.
Could not write namespace interfaces::portal_ints to L2 cache ! This is bad.
Could not write namespace config::PKI_Provider 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 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 ba d.
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 i s 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 b ad.
Could not write namespace interfaces::portal_ints 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 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 ba d.
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 i s 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 b ad.
Could not write namespace interfaces::portal_ints to L2 cache ! This is bad.
Could not write namespace config::Profiles to L2 cache ! This is bad.
Could not write namespace resource::Profile_Filters to L2 cache ! This is
bad.
Could not write namespace config::Provisioning 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 config::VlanFilters to L2 cache ! This is bad.
Could not write namespace config::Wmi 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 ba d.
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 i s 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 b ad.
Could not write namespace interfaces::portal_ints to L2 cache ! This is bad.
Could not write namespace interfaces::dhcplistener_ints to L2 cache ! This
is ba d.
Could not write namespace interfaces::ha_ints 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::inline_nets to L2 cache ! This is bad.
Could not write namespace interfaces::internal_nets to L2 cache ! This is
bad.
Could not write namespace interfaces::listen_ints to L2 cache ! This is bad.
Could not write namespace interfaces::management_network to L2 cache ! This
is b ad.
Could not write namespace interfaces::monitor_int to L2 cache ! This is bad.
Could not write namespace interfaces::portal_ints to L2 cache ! This is bad.
Could not write namespace interfaces::routed_isolation_nets to L2 cache !
This i s bad.
Could not write namespace interfaces::routed_registration_nets to L2 cache
! Thi s is bad.
Could not write namespace interfaces::vlan_enforcement_nets to L2 cache !
This i s 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::Profile_Filters to L2 cache ! This is
bad.
Could not write namespace resource::array_test 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 resource::cluster_hosts to L2 cache ! This is bad.
Could not write namespace resource::cluster_servers to L2 cache ! This is
bad.
Could not write namespace resource::default_switch to L2 cache ! This is
bad.
Could not write namespace resource::fqdn to L2 cache ! This is bad.
Could not write namespace resource::guest_self_registration to L2 cache !
This i s bad.
Could not write namespace resource::reverse_fqdn to L2 cache ! This is bad.
Could not write namespace resource::switches_ranges to L2 cache ! This is
bad.
memcached|start
httpd: Could not reliably determine the server's fully qualified domain
name, us ing
127.0.0.1 for ServerName
httpd.admin|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: Unknown database 'pf_dev' at
/usr/local/pf/lib/pf
/version.pm line 42

[***@pf1 pf]#

Cheers,

Boris.
Louis Munro
2015-07-02 20:56:21 UTC
Permalink
Is the database properly defined in both pf.conf and pfconfig.conf?

--
Louis Munro
***@inverse.ca :: www.inverse.ca
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org)
Post by Boris Epstein
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: Unknown database 'pf_dev' at /usr/local/pf/lib/pf
Boris Epstein
2015-07-02 21:13:08 UTC
Permalink
Louis,

Thanks!

Looks like it is.

Boris.
Post by Louis Munro
Is the database properly defined in both pf.conf and pfconfig.conf?
--
Louis Munro
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (
www.packetfence.org)
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: Unknown database 'pf_dev' at
/usr/local/pf/lib/pf
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
PacketFence-devel mailing list
https://lists.sourceforge.net/lists/listinfo/packetfence-devel
Louis Munro
2015-07-02 21:18:03 UTC
Permalink
I am sorry, do you mean it is defined and the issue must be something else, or that that was the source of the problem?

If the latter, then make sure you really have a running database called pf_dev that you can connect to with the credentials in pfconfig.conf.


--
Louis Munro
***@inverse.ca :: www.inverse.ca
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org)
Post by Boris Epstein
Louis,
Thanks!
Looks like it is.
Boris.
Is the database properly defined in both pf.conf and pfconfig.conf?
--
Louis Munro
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org)
Post by Boris Epstein
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: Unknown database 'pf_dev' at /usr/local/pf/lib/pf
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
PacketFence-devel mailing list
https://lists.sourceforge.net/lists/listinfo/packetfence-devel
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/_______________________________________________
PacketFence-devel mailing list
https://lists.sourceforge.net/lists/listinfo/packetfence-devel
Boris Epstein
2015-07-02 21:23:33 UTC
Permalink
Louis,

Sorry about being vague.

I looked over the configurations in both pf.conf and pfconfig.conf and the
credentials for connecting to DB pf_dev are there and look correct. The
initialization of the DB seemed to have gone through smoothly as well.

Both pf_dev and pf_dev_graphite do contain tables and look OK, at least
superficially.

Boris.
Post by Louis Munro
I am sorry, do you mean it is defined and the issue must be something
else, or that that was the source of the problem?
If the latter, then make sure you really have a running database called
pf_dev that you can connect to with the credentials in pfconfig.conf.
--
Louis Munro
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (
www.packetfence.org)
Louis,
Thanks!
Looks like it is.
Boris.
Post by Louis Munro
Is the database properly defined in both pf.conf and pfconfig.conf?
--
Louis Munro
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (
www.packetfence.org)
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: Unknown database 'pf_dev' at
/usr/local/pf/lib/pf
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
PacketFence-devel mailing list
https://lists.sourceforge.net/lists/listinfo/packetfence-devel
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/_______________________________________________
PacketFence-devel mailing list
https://lists.sourceforge.net/lists/listinfo/packetfence-devel
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
PacketFence-devel mailing list
https://lists.sourceforge.net/lists/listinfo/packetfence-devel
Louis Munro
2015-07-02 21:30:32 UTC
Permalink
Post by Boris Epstein
Louis,
Sorry about being vague.
I looked over the configurations in both pf.conf and pfconfig.conf and the credentials for connecting to DB pf_dev are there and look correct. The initialization of the DB seemed to have gone through smoothly as well.
Both pf_dev and pf_dev_graphite do contain tables and look OK, at least superficially.
Ok, then test the configuration manually.
Use the mysql client to manually connect to the database, as in

# mysql -h dbhost -p -upf pf_dev

Check to see if there are any errors.

You are running a development version now.
Expect to have to do some extra work (as in reading the code…) since we cannot guarantee that the devel branch is free of bugs at all times.

I am away for three days. I’ll catch up with you on Monday.

Happy fourth of July to all our american friends.

--
Louis Munro
***@inverse.ca :: www.inverse.ca
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org)
Boris Epstein
2015-07-02 21:37:39 UTC
Permalink
Louis,

Thanks!

And Happy Canada Day!

Alright, just checked the mysql connection - looks good.

Boris.
Post by Boris Epstein
Louis,
Sorry about being vague.
I looked over the configurations in both pf.conf and pfconfig.conf and the
credentials for connecting to DB pf_dev are there and look correct. The
initialization of the DB seemed to have gone through smoothly as well.
Both pf_dev and pf_dev_graphite do contain tables and look OK, at least superficially.
Ok, then test the configuration manually.
Use the mysql client to manually connect to the database, as in
# mysql -h dbhost -p -upf pf_dev
Check to see if there are any errors.
You are running a development version now.
Expect to have to do some extra work (as in reading the code
) since we
cannot guarantee that the devel branch is free of bugs at all times.
I am away for three days. I’ll catch up with you on Monday.
Happy fourth of July to all our american friends.
--
Louis Munro
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (
www.packetfence.org)
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
PacketFence-devel mailing list
https://lists.sourceforge.net/lists/listinfo/packetfence-devel
Continue reading on narkive:
Loading...