Skip to main content
billflu
New Member
November 3, 2015
Question

100D Locks Up Every Few Days

  • November 3, 2015
  • 2 replies
  • 23972 views

Every three days or so we have an issue where our 100D stops handing out DHCP addresses, so users are not able to get online. The only way to fix this is to hard power cycle. During the time of the issue, when trying to log into the web interface you can get through the authentication and the next page shows an error 500:

 

The command line interface reacts very minimally, but I was able to get the process list while this is occurring. Some of the processes are labeled "D". I wasn't able to find documentation for this, but it may refer to dead?

 

2U, 0N, 0S, 98I; 3954T, 1458F, 323KF
       ipsengine 120 S < 3.5 2.6
       ipsengine 118 S < 3.3 2.6
       ipsengine 117 S < 2.1 2.5
       ipsengine 119 S < 1.1 2.6
       scanunitd 8779 S < 0.7 0.3
         src-vis 92 S 0.3 1.1
       scanunitd 8731 S < 0.3 0.3
         updated 86 S 0.1 1.5
     proxyworker 88 S 0.1 1.1
     proxyworker 89 S 0.1 1.1
          newcli 8780 R 0.1 0.4
         reportd 82 D 0.0 2.0
             dsd 113 D 0.0 1.0
         pyfcgid 8629 D 0.0 0.8
          httpsd 8688 D 0.0 0.8
         pyfcgid 8716 D 0.0 0.8
         pyfcgid 8723 D 0.0 0.8
         pyfcgid 8730 D 0.0 0.8
         pyfcgid 8717 D 0.0 0.8
         pyfcgid 8737 D 0.0 0.7

 

Any input on this issue is appreciated. I've been restarting the firewall nightly, and that seems to keep the issue at bay. We've already done a format and re-install of the OS and also a complete hardware replacement.

 

Thank you

 

2 replies

mscheiber
New Member
November 10, 2015

Hi

 

are you using vdoms? 

 

We have a similar problem with our 100D's. We are using vdoms and i cant go into the vdom over cli nor even can access some parts over the gui.

And the only fix is to do a hard reboot, because when i do a soft reboot the device will hang. Which FortiOS version do you use? I saw that kind of problem with 5.0.9 and 5.0.12. 

 

I also opened a ticket at Fortinet support and they recommend to upgrade to 5.2.3 or 5.2.4.

 

This is my post https://forum.fortinet.com/tm.aspx?m=130647

 

billflu
billfluAuthor
New Member
November 11, 2015

mscheiber, thanks for the response. It does sound similar, but I'm not using vdoms. The firmware is the latest v5.2.4,build688 (GA). Support is recommending I factory default and restore the configuration again, but it seems they may just be grasping at straws.

gzarini
New Member
November 11, 2015

billflu, i had an issue like that with a 100d unit.

It worked fine, but one night it didn't renew dhcp leases, and the next morning dhcp server didn't lease any ip.

I tried that day to enter gui and fg gave that same error, i couldn't even restarted from console so i rebbot the device from the on/off switch. Then it didn't boot.

Since day the unit is on RMA. my recommendation in to make a hardware check with fortigate technical support to check if hardware is working fine.

In my case it was the hard disk that broke up.

 

Regards.

dpaul
New Member
January 21, 2019

msg="EXT2-fs (sdb1): previous I/O error to superblock detected" error showing on Fortigate 100D 

jphoeke
New Member
December 11, 2019

I had a similar problem with my 60D running 6.2.0 and resolved it by upgrading to 6.2.2