lots of bugfixes
https://docs.fortinet.com...release-notes/download
sudo apt-get-rekt
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.
You can get a FAZ license for $1 on AWS for 500Gb and up to 2 "home" Fortigate/VDOM (up to Fortigate 90 and VM-01), still have to pay for AWS usage, I'm at around $25 a month.
dfollis wrote:I have a home setup of the following:
FWF-60E v6.0.4 build0231 (6.0.4)
FSW-108D-POE v3.6.9-build0426 (this model does not support v6)
FortiAP FP221C v6.0-build0027 (just upgraded to build0030, 6.0.4)
Fairly simple setup for home using these devices. I've experienced random outages after ~24 hours after upgrading from 6.0.3 to 6.0.4. Symptom is Wifi will be down and hard wire connection to FWF-60E will not respond without a hard power reset.
I first tried to update my FSW from 3.6.8 to .9 but crash occurred again. This AM after another hard reset was needed, I noticed that 6.0.4 for FP221C was released on 1/25 so I have just updated that. As this is a home setup, I'm not paying for FAZ (considering we spend thousands of dollars on FTNT gear at work sure would be nice for free FAZ with low daily limit for home use/testing, just saying :-)).
I do have a synology though so I'm going to enable SYSLOG and dump to that to see if I can get better system events. When I check events logged to FortiCloud I don't see anything odd. Running "diag debug crashlog read" shows the following:
1: 2019-01-26 22:27:10 scanunit=manager pid=152 str="AV database changed; restarting workers" 2: 2019-01-26 22:27:12 <00152> scanunit=manager str="Success loading anti-virus database." 3: 2019-01-26 22:37:10 scanunit=manager pid=152 str="AV database changed; restarting workers" 4: 2019-01-26 22:37:12 <00152> scanunit=manager str="Success loading anti-virus database." 5: 2019-01-26 22:40:14 the killed daemon is /bin/pyfcgid: status=0x0 6: 2019-01-26 22:59:10 scanunit=manager pid=152 str="AV database changed; restarting workers" 7: 2019-01-26 22:59:12 <00152> scanunit=manager str="Success loading anti-virus database."
8: 2019-01-27 12:33:03 <00152> scanunit=manager str="Success loading anti-virus database."
It is interesting that that last event logged is an AV update until I reset it 12 hours later, see events 7 and 8 above.
Not sure if anyone else is seeing stability issues like this. It is possible I have an odd config that is causing an issue as I have a few VLANs that are trunked over my FSW, but nothing unconventional that I'm aware of. Will update post if I see another crash.
Hello.
How we will use Citrix and Port Forwarding if all browser that support java is not supported by FortiOS now?
Internet explorer dont open nothing in WEB SSL VPN.
we have Fortigate 600D with firmware 5.4.2. we can directly upgrade to 6.0.4
I have LDAP working for an explicit proxy on 6.0.4
But as you mention, could be a site specific issue for you
I got a lot of complaints about slower computers (response time between switching programs, opening websites) since 6.0.4 was installed.
We use Windows 7 Proffesional and and use forticlient in combination with EMS
Every time when one of my colleages submits a helpdesk request i quickly login to the computer to look what is causing the slowdown of the computer. What i noticed is that fmon.exe generates a lot of hard faults. I disabled the vulnerability scan, planned scans, heuristics, and VPN with almost no effect. I even disabled searchindexer because while it was indexing the harddisk fmon was creating hard faults too.
Still my colleages notice sometimes delays.
We don't have this problems with our terminal servers Windows 2008R2 running with 6.0.4
JN
Just upgraded from 6.0.3 to 6.0.4 last night. No issues noted yet. The GUI seems to have been tweaked for better visibility. Improved font size maybe? Pages also load MUCH faster than in 6.0.3.
After 6.0.4, my 200E no longer updates from Fortiguard or manually.
It gives an error all the time.
Downgraded to 5.6.7 and it works.
Anyone else notice that sequence numbers have disappeared. We have hundreds of policies on some of our interfaces. This makes it difficult to know if one policy is above another without slowly scrolling through every policy. Not sure if this has been removed deliberately.
Does anyone know when Forticloud will support 6.0.4 for management? It currently won't allow me to enable management.
I have a home setup of the following:
FWF-60E v6.0.4 build0231 (6.0.4)
FSW-108D-POE v3.6.9-build0426 (this model does not support v6)
FortiAP FP221C v6.0-build0027 (just upgraded to build0030, 6.0.4)
Fairly simple setup for home using these devices. I've experienced random outages after ~24 hours after upgrading from 6.0.3 to 6.0.4. Symptom is Wifi will be down and hard wire connection to FWF-60E will not respond without a hard power reset.
I first tried to update my FSW from 3.6.8 to .9 but crash occurred again. This AM after another hard reset was needed, I noticed that 6.0.4 for FP221C was released on 1/25 so I have just updated that. As this is a home setup, I'm not paying for FAZ (considering we spend thousands of dollars on FTNT gear at work sure would be nice for free FAZ with low daily limit for home use/testing, just saying :-)).
I do have a synology though so I'm going to enable SYSLOG and dump to that to see if I can get better system events. When I check events logged to FortiCloud I don't see anything odd. Running "diag debug crashlog read" shows the following:
1: 2019-01-26 22:27:10 scanunit=manager pid=152 str="AV database changed; restarting workers" 2: 2019-01-26 22:27:12 <00152> scanunit=manager str="Success loading anti-virus database." 3: 2019-01-26 22:37:10 scanunit=manager pid=152 str="AV database changed; restarting workers" 4: 2019-01-26 22:37:12 <00152> scanunit=manager str="Success loading anti-virus database." 5: 2019-01-26 22:40:14 the killed daemon is /bin/pyfcgid: status=0x0 6: 2019-01-26 22:59:10 scanunit=manager pid=152 str="AV database changed; restarting workers" 7: 2019-01-26 22:59:12 <00152> scanunit=manager str="Success loading anti-virus database."
8: 2019-01-27 12:33:03 <00152> scanunit=manager str="Success loading anti-virus database."
It is interesting that that last event logged is an AV update until I reset it 12 hours later, see events 7 and 8 above.
Not sure if anyone else is seeing stability issues like this. It is possible I have an odd config that is causing an issue as I have a few VLANs that are trunked over my FSW, but nothing unconventional that I'm aware of. Will update post if I see another crash.
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 |
---|---|
1697 | |
1092 | |
752 | |
446 | |
228 |
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.