Bug Tracking System

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001785PacketFencecorepublic2014-04-04 08:042014-04-04 08:04
Assigned To 
PlatformLinuxOSRHEL / CentOSOS Version6
Product Version4.1.0 
Target VersionFixed in Version 
Summary0001785: When database is stoped, pfmon ends in an inconsistent state
DescriptionTo perform backup, we stop the database of PacketFence every night.
If pfmon tries to access the DB during the backup, it logs:
Apr 02 18:00:23 pfmon(0) INFO: running expire check (main::cleanup)
Apr 02 18:00:23 pfmon(0) INFO: checking registered nodes for expiration (main::cleanup)
Apr 02 18:00:23 pfmon(0) WARN: database query failed with: MySQL server has gone away. (errno: 2006), will try again (pf::db::db_query_execute)
Apr 02 18:00:23 pfmon(0) FATAL: unable to connect to database: Can't connect to MySQL server on '' (111) at /usr/local/pf/lib/pf/ line 888.
Apr 02 18:00:23 pfmon(0) ERROR: Error restarting pfmon: unable to connect to database: Can't connect to MySQL server on '' (111) at /usr/local/pf/lib/pf/ line 888.

Also, pfmon results running with "ps", but "pfcmd service pfmon status" doesn't agree:
/usr/local/pf # ./bin/pfcmd service pfmon status

so it's not possible to restart it without doing kill to the running process.

Nodes expired after this happening are not requested login again (they are registered forever), and so they do not expire
Steps To Reproduce1) start PacketFence
2) stop database
3) wait a minute
TagsNo tags attached.
fixed in git revision
fixed in mtn revision
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2014-04-04 08:04 canepan New Issue

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker