Error 500: Internal Server Error in web interface

[m0j0]

I've got a couple of 60C's in HA running 5.0.4.  I tried to log in to the web interface today and it logs me in and loads the top toolbar and sits there with two empty frames for a while before it finally returns a "Error 500: Internal Server Error" in the left frame.  I've tried killing all the httpsd processes but it hasn't made a difference.  A diag debug on the web-ui shows the following when the error shows in the web interface:-

[httpsd 27319] http_config.c[573] ap_invoke_handler -- handler 'fastcgi-script' completed (result==500)

[httpsd 27319] http_request.c[1443] ap_internal_redirect -- internal redirect to '/p/pubredir/httperror/'

Trying to avoid rebooting the firewall at all costs.  I've considered a forced failover to the secondary device but want to exhaust any other possible options before going down that road, and I'm not sure it will fix it anyway.  

The web interface was working fine a day or two ago and nothing has changed since then.  Firewall uptime is 223 days and looking at my Cacti graphs, memory utilisation has been sitting around 65% since November but appears to have just nudged up to 70% very recently.  Not sure if this is the cause of the problem or not.

[ede_pfau]

@Tommy: are you aware that formatting the flash disk (as recommended) will erase the firmware as well? Usually, one has to TFTP the image back onto flash to get the unit to boot.

Doing this from remote is daring at best, impossible at worst.

[Tommy_Rogers]

I am formatting the loggingdisk, I thought it was a partition on the flash drive seprrate from the boot partition.

[NotMine]

Tommy Rogers wrote:
I am formatting the loggingdisk, I thought it was a partition on the flash drive seprrate from the boot partition.

I thought so, also. But the CLI reference (http://help.fortinet.com/...I/execute.31.024.html) says this:

CLI_Ref wrote:
In addition to deleting logs, this operation will erase all other data on the disk, including system configuration, quarantine files, and databases for antivirus and IPS.

As it is often the case, documentation is not very clear. I do not remember running this command ever. Have you managed to recover the device?

[Tommy_Rogers]

I was able to finally disable the log disk and restart. I know it was risky but it worked and it took several hours to initiate the command. This is a high risk so I am not suggesting anyone try it.

[Tommy_Rogers]

Now there is no sign of the logdisk at all in the GUI or from CLI commands. CUstomer is up and able to get to the GUI now so I have other fish to fry. I will address this at a later time.

Thanks for everyones input.

[NotMine]

Hi Tommy, thank you for the feedback. I hate to be a party breaker, but I'm sure you are aware that this device should not be trusted until thoroughly tested, maybe even with a HQIP image. :)

Cheers!

Slavko

[Nils]

I get this more often when i use Chrome then if I'm using Explorer. I always thought that the issue was my computer :)

[Tommy_Rogers]

It appears that the logdisk option has been removed from the 60x all the way up to the 100x models. I do not get any logdisk command options in the 100D CLI command structure what so ever now.

[Stefan_H]

Hi everyone,

I'm new to this forum because we've got the same issues with our new 200D's.

We already replaced the broken one with a new 200D and after ~4 days we are facing the same problems again.

At first we restarted the broken one and it wasn't able to boot again.

Luckily we've got a HA and the second one took over.

Are there any new information regarding this issues?

At other locations we are using the same 200Ds (same firmware etc.) and its just a question of time when the big bang occurs.

It's really disappointing that these problems aren't fixed since a year and we bought new fortigates last month.

Thanks in advance

Stefan

[NotMine]

Hi Stefan,

Reduce traffic and event disk logging to the minimum. If you have web caching enabled, disable it. These are the first aid tips. :)

Cheers!

Slavko