New Member

Solved

Error 500: Internal Server Error in web interface

46 replies
154744 views

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.

PrometheusAnswer

New Member

Hi Skippy,

So far so good. We did not experience the problem anymore since we installed 5.2.8. But we only installed the devices 10 days ago. It took the 5.2.7 devices like 14 days to come up with the problem, so I cannot confirm nor can I deny that 5.2.8 is the right solution.

Skippy wrote:
Prometheus wrote:
So last night we switched to the backup cluster using the 5.2.8 firmware. I'll keep you guys posted if it keeps on working or not. The faulty device also worked again after a reboot but this is still under investigation by Fortinet.

Is it normal to have something like 28GB of disk logging in roughly 10 days of operation?
Full logging enabled for all policies with four WAN interfaces and both static and policy routes as well as BGP.

I think this is quite normal. I see it with our network monitoring which collected over 2GB of logging in 12 hours. But once again i'm not sure.

vjoshi_FTNT

Staff

Hello,

I remember, there is a known issue for the same problem. Upgrading to the latest patch should fix this issue.

If you need a confirmation about the bug ID etc., a support ticket might help. But I am pretty sure, there was a bug on this.

Hope that helps.

Robin_Svanberg

New Member

vjoshi wrote:
Hello,

I remember, there is a known issue for the same problem. Upgrading to the latest patch should fix this issue.

If you need a confirmation about the bug ID etc., a support ticket might help. But I am pretty sure, there was a bug on this.

Hope that helps.

Probably Bug ID #239368. Web-based Manager : Fix Internal 500 Server Error after login.

Solved in 5.0 Patch 8.

BR Robin

bikash_Shaw

New Member

Hi

Can you connect your PC to fortigate firewall via console. I think it might be issue with disk.

Regards

Bikash

CorneJvV

New Member

Looks like this issue has carried over to FortiOS 5.2.3 as well.

We have a few 100D's that are now getting this issue often.

Is there another way to resolve this except for rebooting/shut down the FortiGate ?

All of these devices are in live non- HA environments.

CorneJvV

New Member

Issue Resolved Pending, format the device and re-install the image.

From the "diag sys top" output, there a lot of processes in Dead state.

Run Time: 13 days, 18 hours and 20 minutes 0U, 0N, 1S, 99I; 3954T, 1579F, 193KF proxyworker 112 S 0.4 1.2 sshd 3891 S 0.4 0.3 urlfilter 120 S 0.0 2.1 reportd 100 D 0.0 1.7 httpsd 72 S 0.0 1.6 proxyworker 108 S 0.0 1.2 httpsd 73 S 0.0 1.0 pyfcgid 3883 S 0.0 0.8 pyfcgid 3900 S 0.0 0.8 pyfcgid 3877 S 0.0 0.8 pyfcgid 3878 D 0.0 0.8 pyfcgid 3887 D 0.0 0.8 pyfcgid 3876 D 0.0 0.8

Tommy_Rogers

New Member

This is really getting to be a pain in the butt. I have a 100D with version 5.2.5 firmware. I have RMA'ed three (3) of these guys back to Fortinet. This is the fourth one they have sent me and I am still getting the error after a few days of service. The exact verbage is "Error 500: Internal Server Error". I know that it is a disk error but I don't know why. There is no way that all four 100d's can have bad flash drives unless it is a bad batch from a manufacture.

This is really embarrassing for my company to have to tell our customer that they have a defective unit. THIS IS THE FORTH ONE GUYS!!!! Come on get your engineers awake and tell me what is wrong with this thing.

The bad thing here is we recommended a Fortigate 100D over a Sonicwall, They were going to buy a Sonicwall but we talked them in to a Fortigate.

I need this fricking problem fixed ASAP!

Sign up

Login with SSO

Login to the community

Login with SSO