Can you try bin/pfcmd configreload hard and restart pfmon


Le 2017-03-17 à 10:29, Mike Campanaro a écrit :
>
> Hey Fabrice,
>
>  
>
> The following is the output you asked for:
>
>  
>
> 'maintenance' => {
>                              'person_cleanup' => 'disabled',
>                              'iplog_rotation' => 'disabled',
>                              'iplog_cleanup_batch' => '100',
>                              'iplog_rotation_batch' => '100',
>                              'violation_maintenance_timeout' => '10',
>                              'auth_log_cleanup_timeout' => '10',
>                              'iplog_rotation_timeout' => '10',
>                              'option82_query_interval' => 82800,
>                              'acct_maintenance_interval' => '60',
>                              'inline_accounting_maintenance_interval'
> => '60',
>                              'node_cleanup_window' => 0,
>                              'radius_audit_log_cleanup_batch' => '100',
>                              'auth_log_cleanup_interval' => '60',
>                              'auth_log_cleanup_batch' => '100',
>                              'iplog_rotation_window' => 604800,
>                              'locationlog_cleanup_window' => 604800,
>                              'radius_audit_log_cleanup_window' => 604800,
>                              'iplog_cleanup_window' => 2592000,
>                              'iplog_cleanup_timeout' => '10',
>                              'radius_audit_log_cleanup_interval' => '60',
>                              'auth_log_cleanup_window' => 604800,
>                              'iplog_rotation_interval' => '60',
>                              'locationlog_cleanup_interval' => '60',
>                              'violation_maintenance_batch' => '1000',
>                              'cluster_check_interval' => 60,
>                              'violation_maintenance_interval' => '60',
>                              'populate_ntlm_redis_cache_interval' => '0',
>                              'iplog_cleanup_interval' => '60',
>                              'fingerbank_data_update_interval' => 86400,
>                              'radius_audit_log_cleanup_timeout' => '10',
>                              'online_node_count_interval' => 900,
>                              'nodes_maintenance_interval' => '60',
>                              'provisioning_compliance_poll_interval'
> => '300',
>                              'person_cleanup_interval' => '60',
>                              'locationlog_cleanup_batch' => '100',
>                              'locationlog_cleanup_timeout' => '10',
>                              'node_cleanup_interval' => '60'
>
>  
>
> Please let me know what I can do from here.
>
> Thanks,
>
> *Mike Campanaro
> **Network Administrator I
> Dumac Business Systems*
>
>  
>
>  
>
>  
>
> *From:*Fabrice Durand [mailto:[email protected]]
> *Sent:* Friday, March 17, 2017 10:14 AM
> *To:* [email protected]
> *Subject:* Re: [PacketFence-users] Pfmon problem, log file eating away
> at my server storage
>
>  
>
> Hello Mike,
>
> can you paste the maintenance section of the result of this command:
>
> bin/pfcmd pfconfig show config::Pf
>
> Regards
>
> Fabrice
>
>  
>
>  
>
> Le 2017-03-17 à 09:40, Mike Campanaro a écrit :
>
>     Hello all,
>
>      
>
>     I’m having a bit of an odd issue. Two days ago I was getting
>     errors on my PF server (PF 6.5 on a CentOS 7vm) stating that I
>     only had 20kb of storage left. I investigated the issue and
>     noticed that the logs folder for PF was taking up over 40gb alone.
>     I went in and cleared all the old logs and freed up nearly 40gb of
>     space and then thought nothing more of it. Today, however, I’m
>     having the same issue. I’m getting low space warnings.
>
>      
>
>     I decided to investigate further and I see that the pfmon.log file
>     is the culprit. The active log file is taking 22gb of space and
>     the rotated compressed file is taking 18gb.. Keep in mind that I
>     just cleared these out two days ago. I opened the log file to see
>     what was going on and it’s the same error being repeated over and
>     over again. The error is as follows:
>
>      
>
>     Pfmon(15790) ERROR: Argument “0s” isn’t numeric in subtraction (-)
>     at /usr/local/pf/sbin/pfmon line 466.
>
>     (main::_runtask)
>
>      
>
>     That’s it. That same error comes in at what seems to be over 100
>     times a second and goes on for hundreds of thousands of lines and
>     is eating away at my storage, making it so PF is completely
>     non-functional because when I’m low on storage I get “Cannot write
>     to log” errors and then nothing will seem to work.
>
>      
>
>     Any guidance would be greatly appreciated.
>
>      
>
>      
>
>      
>
>     Thanks,
>
>     *Mike Campanaro
>     **Network Administrator I*
>
>     * *
>
>     *cid:[email protected]*
>
>       
>
>     19 Corporate Circle
>     East Syracuse, NY  13057
>     For more information, visit us at www.dumac.com
>     <http://www.dumac.com/>
>
>     *
>     **/Notice: This E-mail (including attachments) is covered by the
>     Electronic Communications Privacy Act, 18 U.S.C. §§2510-2521, is
>     confidential and may be legally privileged. If you are not the
>     intended recipient, you are hereby notified that any retention,
>     dissemination, distribution, or copying of this communication is
>     strictly prohibited. Please reply to the sender that you have
>     received the message in error, then delete it. Thank you./*
>
>     This message (and any associated files) is intended only for the
>     use of the individual or entity to which it is addressed and may
>     contain information that is confidential, subject to copyright or
>     constitutes a trade secret.  Messages sent to and from us may be
>     monitored.
>
>     Internet communications cannot be guaranteed to be secure or
>     error-free as information could be intercepted, corrupted, lost,
>     destroyed, arrive late or incomplete, or contain viruses.
>     Therefore, we do not accept responsibility for any errors or
>     omissions that are present in this message, or any attachment,
>     that have arisen as a result of e-mail transmission. If
>     verification is required, please request a hard-copy version. Any
>     views or opinions presented are solely those of the author and do
>     not necessarily represent those of DUMAC Business Systems, Inc.
>
>      
>
>
>
>
>     
> ------------------------------------------------------------------------------
>
>     Check out the vibrant tech community on one of the world's most
>
>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
>
>     _______________________________________________
>
>     PacketFence-users mailing list
>
>     [email protected]
>     <mailto:[email protected]>
>
>     https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
>
>
> -- 
> Fabrice Durand
> [email protected] <mailto:[email protected]> ::  +1.514.447.4918 (x135) ::  
> www.inverse.ca <http://www.inverse.ca>
> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence 
> (http://packetfence.org) 
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> PacketFence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users

-- 
Fabrice Durand
[email protected] ::  +1.514.447.4918 (x135) ::  www.inverse.ca
Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence 
(http://packetfence.org) 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to