Is there an ETA as to when 5.4.1 is going to drop? I have a brand new 300D that I am waiting to put into production as soon as 5.4.1 is ready.
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
by end of next week (April 15)
That amount of clashes is nothing to worry about I'd say. On the LB-vdom I mentioned earlier the log shows 6-digit amounts of clashes. The clash counter is reset at reboot btw, and is not related to the current amount of sessions. It is just an ongoing counter.
To my knowledge, all restarts of applications with restart option 11 (segmentation fault) in FortiOS is seen as a crash. It doesn't have to mean anything bad per se. The OS recycles processes all the time using option 15 (graceful restart). When that doesn't work, it moves on to try to restart with option 11 wich will generate a log entry in the syslog. The recycle process continues all the time, buffers needs to be cleared etc etc. However, a constant restarting of the same application can also mean various problems - Memory leaks, buffer overflows etc.
I checked your log, but I can't see anything else then the PID and some weird ASCII-signs as application name. It does look kinda odd.
Check your logs and keep track of if the application crash log entries correlates with odd behaviour in the firewall, we're talking sudden reboots, functions and features stopping/not working.
What does "diagnose debug crashlog read" say?
Also, do a "diagnose sys top", a few times during the day. Do you have processes in Z or D state?
Richie
NSE7
I don't care for 1 or two week if this release works fine
but I don't have theses new boxes only running 5.4...
2 FGT 100D + FTK200
3 FGT 60E FAZ VM some FAP 210B/221C/223C/321C/421E
We have a ton of open tickets for 5.4 bugs. Got an update this morning on one of them (grammar and all) "This issue will fix on 5.4.1 which should be release in next 2 weeks."
I'm completely ok with them releasing it "when it's done" the last thing I want is rushed code that makes my production and test environments crash
Mike Pruett
It is a big joke: I got answer from fortinet support in our ticket: There is not workaround in 5.2.x. But it is fixed only in the release in 5.4.!
But release 5.4 has a lot of another bugs!
It has not solution. :-))))
Hello
We have a bug in 5.2.3 regarding explicit proxy function
support answered that the fix will only be released in 5.4.1
After keeping pressure on fortinet ( as gold partner ) we will receive fix in 5.2.8
It is not possible to work with 5.4.0 ( maybe 5.4.1 ) at this instant as bugs present in 5.2.x disappear in 5.4.0 but some others come ...
NSE6
WAITING, WAITING, WAITING,.... AND WAITING............
FWF60D x2 FWF60C x3 FGT80C rev.2 FGT200B-POE FAP220B x3 FAP221B x2
FSW224B x1
Yes, yes, yes, ... and yes.....
I am waiting already 2 months. :-)))
And my customer is waiting with me.
And I must to soothe him.
rcarreras wrote:
Nice one, rcarreras! :)
You almost bought me a new keyboard. I was able to divert the water elsewhere!
rcarreras wrote:
Mike Pruett
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1633 | |
1063 | |
751 | |
443 | |
210 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.