We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda NextGen Firewall X

boxfw crash with 'Request handler got signal 25'

  • Type: Knowledgebase
  • Date changed: 6 months ago
Solution #00005092 
 
Scope:
This solution replies to:
- NG Firewall firmware versions 4.2.x
- netfence firmware versions 4.2.x

 
Symptoms:

The firewall stops forwarding traffic. Following entries are displayed in the in the "Log" > "Box" > "fatal.log".

Fatal +0100 [box_Control_daemon] Box service boxfw is NOT active
Fatal +0100 [box_Firewall] [Main] Process: Request handler got signal 25 lastPos=1
  

 

 
Solution:

This problem occurs if the firewall handles high traffic load and thus generates huge log files. When the log file size reaches 2 GB the firewall crashes.

 

To solve this problem cycle the logwrap in short intervals. Insert the following cronjob on the box and run it every 2 hours:

    /opt/phion/modules/box/boxsrv/logwrap/bin/logwrapd -w & &>/dev/null

 

 

Note:
Do not run the cronjob between 01:00 and 02:00 am. This would invoke a conflict between logstor and logwrap, as logstor as well runs at this time. 

 

 

Link to This Page:
https://campus.barracuda.com/solution/50160000000IKY9AAO