Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 30 replies
  • Subscribers 3 subscribers
  • Views 20032 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Forced to restart UTM

AdamTyler
Hi all.  First time posting to the forum, hoping someone has an idea for me.  I've been running an old DELL computer for quite a while now with the home license of the UTM 9.  Current firmware version: 9.204-20

2 GB RAM
Log Disk: 34 GB
DATA Disk: 26GB

Anyhow, it seems like since the last firmware update I've had to restart the firewall every 3 to 5 days because the internet will die.  Anyone else out there have this problem? Any way to schedule the restarts?


This thread was automatically locked due to age.
Parents
  • 0
    quick update as i don't see it mentioned and upgrading to any version will probably NOT solve it:
    Are your "problem" NIC Intel based ones?(check in interfaces->hardware).
    if so then it's an old bug that hasn't been fixed in forever(it gets apparently fixed in 9.1, then comes back again in 9.2, etc etc) and the issue is exactly as you say.

    To confirm if it IS the bug i mention also check the kernel log AFTER the issue appears: go to logging -> view log files and search for the "kernel messages", do not use livelog, but click on view and paste here the last 40 or so lines, SPECIALLY if they mention "e1000", example of a problem machine:

    2014:06:26-15:17:31 utm kernel: [94499.808337] e1000e 0000:00:19.0 eth2: Detected Hardware Unit Hang:
    2014:06:26-15:17:31 utm kernel: [94499.808337]   TDH                  
    2014:06:26-15:17:31 utm kernel: [94499.808337]   TDT                  
    2014:06:26-15:17:31 utm kernel: [94499.808337]   next_to_use          
    2014:06:26-15:17:31 utm kernel: [94499.808337]   next_to_clean        
    2014:06:26-15:17:31 utm kernel: [94499.808337] buffer_info[next_to_clean]:
    2014:06:26-15:17:31 utm kernel: [94499.808337]   time_stamp           
    2014:06:26-15:17:31 utm kernel: [94499.808337]   next_to_watch        
    2014:06:26-15:17:31 utm kernel: [94499.808337]   jiffies              
    2014:06:26-15:17:31 utm kernel: [94499.808337]   next_to_watch.status 
    2014:06:26-15:17:31 utm kernel: [94499.808337] MAC Status             
    2014:06:26-15:17:31 utm kernel: [94499.808337] PHY Status             
    2014:06:26-15:17:31 utm kernel: [94499.808337] PHY 1000BASE-T Status  
    2014:06:26-15:17:31 utm kernel: [94499.808337] PHY Extended Status    
    2014:06:26-15:17:31 utm kernel: [94499.808337] PCI Status             

    (moe info https://community.sophos.com/products/unified-threat-management/astaroorg/f/52/t/29490 ).

    the workaround is kind of annoying to implement
Reply
  • 0
    quick update as i don't see it mentioned and upgrading to any version will probably NOT solve it:
    Are your "problem" NIC Intel based ones?(check in interfaces->hardware).
    if so then it's an old bug that hasn't been fixed in forever(it gets apparently fixed in 9.1, then comes back again in 9.2, etc etc) and the issue is exactly as you say.

    To confirm if it IS the bug i mention also check the kernel log AFTER the issue appears: go to logging -> view log files and search for the "kernel messages", do not use livelog, but click on view and paste here the last 40 or so lines, SPECIALLY if they mention "e1000", example of a problem machine:

    2014:06:26-15:17:31 utm kernel: [94499.808337] e1000e 0000:00:19.0 eth2: Detected Hardware Unit Hang:
    2014:06:26-15:17:31 utm kernel: [94499.808337]   TDH                  
    2014:06:26-15:17:31 utm kernel: [94499.808337]   TDT                  
    2014:06:26-15:17:31 utm kernel: [94499.808337]   next_to_use          
    2014:06:26-15:17:31 utm kernel: [94499.808337]   next_to_clean        
    2014:06:26-15:17:31 utm kernel: [94499.808337] buffer_info[next_to_clean]:
    2014:06:26-15:17:31 utm kernel: [94499.808337]   time_stamp           
    2014:06:26-15:17:31 utm kernel: [94499.808337]   next_to_watch        
    2014:06:26-15:17:31 utm kernel: [94499.808337]   jiffies              
    2014:06:26-15:17:31 utm kernel: [94499.808337]   next_to_watch.status 
    2014:06:26-15:17:31 utm kernel: [94499.808337] MAC Status             
    2014:06:26-15:17:31 utm kernel: [94499.808337] PHY Status             
    2014:06:26-15:17:31 utm kernel: [94499.808337] PHY 1000BASE-T Status  
    2014:06:26-15:17:31 utm kernel: [94499.808337] PHY Extended Status    
    2014:06:26-15:17:31 utm kernel: [94499.808337] PCI Status             

    (moe info https://community.sophos.com/products/unified-threat-management/astaroorg/f/52/t/29490 ).

    the workaround is kind of annoying to implement
Children
No Data