Helpful ReplyHot!FortiOS 6.0.4 is out!

Page: < 123 > Showing page 2 of 3
Author
ghorchem
New Member
  • Total Posts : 18
  • Scores: 0
  • Reward points: 0
  • Joined: 2012/07/07 09:09:21
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/15 14:30:13 (permalink)
0
Yes they said it would be fixed in 6.0.4. It hasn’t been fixed though.
#21
SMabille
Silver Member
  • Total Posts : 71
  • Scores: 18
  • Reward points: 0
  • Joined: 2013/03/31 15:39:51
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/16 03:54:01 (permalink)
0
New issue:
 
FortiView > All Sessions (now) : Unable to right click and filter (chrome 71)
#22
Jeroen Nieuwenbroek
New Member
  • Total Posts : 5
  • Scores: 2
  • Reward points: 0
  • Joined: 2017/11/09 01:17:54
  • Location: s Heerenhoek
  • Status: offline
Re: FortiOS 6.0.4 is out! (slowing down computers more than the previous version) 2019/01/16 05:43:14 (permalink)
0
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
 
#23
mracpa
New Member
  • Total Posts : 5
  • Scores: 0
  • Reward points: 0
  • Status: offline
Re: FortiOS 6.0.4 is out! (slowing down computers more than the previous version) 2019/01/16 06:29:09 (permalink)
0
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.
#24
ricardoduarte
New Member
  • Total Posts : 5
  • Scores: 0
  • Reward points: 0
  • Joined: 2018/12/25 03:03:39
  • Status: offline
Re: FortiOS 6.0.4 is out! (slowing down computers more than the previous version) 2019/01/16 08:33:06 (permalink)
0
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.
#25
goroga
New Member
  • Total Posts : 1
  • Scores: 0
  • Reward points: 0
  • Joined: 2019/01/17 15:55:00
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/17 16:09:43 (permalink)
0
One issue in this version:
On FortiGate 101E "Log & reports > Forward Traffic" filters are ineffective. 

Attached Image(s)

#26
James_G
Silver Member
  • Total Posts : 85
  • Scores: 4
  • Reward points: 0
  • Joined: 2016/02/28 02:55:47
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/21 06:34:38 (permalink)
0
I have LDAP working for an explicit proxy on 6.0.4
 
But as you mention, could be a site specific issue for you
#27
PeterK
New Member
  • Total Posts : 13
  • Scores: 2
  • Reward points: 0
  • Joined: 2018/01/24 08:55:45
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/21 07:28:27 (permalink)
0
I have noticed it has fixed the issue of not being able to creates routes in the GUI.  I need to test on another Firewall to see if it has restored the icons in the SSL-Web portal.  I have tested the traffic filter issue someone has mentioned, but I tend to do this through the Analyzer which is on 6.0.4 and the filters are working on this.
#28
neonbit
Expert Member
  • Total Posts : 517
  • Scores: 67
  • Reward points: 0
  • Joined: 2013/07/02 21:39:52
  • Location: Dark side of the moon
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/21 14:37:42 (permalink)
0
I'm loving this release. The SSLVPN web portal bookmark problem is solved for me and HTTP bookmarks that were pointing to HTML5 servers that never used to work are all now working!
 
One thing I did notice is that some of the pages (FortiView > Applications and Log & Report > Forward Traffic) are taking a little time to load.
#29
sashag
New Member
  • Total Posts : 2
  • Scores: 0
  • Reward points: 0
  • Joined: 2018/09/27 06:24:03
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/22 00:43:52 (permalink)
0
Upgraded yesterday from 5.6.6 to 6.0.4 600D cluster. System - Settings page not loading, cannot configure central management. Anybody else experiencing this GUI issue?
#30
PeterK
New Member
  • Total Posts : 13
  • Scores: 2
  • Reward points: 0
  • Joined: 2018/01/24 08:55:45
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/23 01:43:55 (permalink)
0
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.
#31
tgold
New Member
  • Total Posts : 1
  • Scores: 0
  • Reward points: 0
  • Joined: 2019/01/24 09:11:07
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/24 09:19:56 (permalink)
0
Does anyone know when Forticloud will support 6.0.4 for management? It currently won't allow me to enable management.
#32
seadave
Expert Member
  • Total Posts : 318
  • Scores: 48
  • Reward points: 0
  • Joined: 2004/11/03 18:02:09
  • Location: Seattle, WA
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/27 13:02:26 (permalink)
0
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.
#33
SMabille
Silver Member
  • Total Posts : 71
  • Scores: 18
  • Reward points: 0
  • Joined: 2013/03/31 15:39:51
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/28 01:23:56 (permalink) ☄ Helpfulby seadave 2019/01/29 00:34:14
5 (1)
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.
(https://aws.amazon.com/marketplace/pp/B06Y1K63ZH?qid=1548667167351&sr=0-1&ref_=srh_res_product_title#pdp-overview)
 
dfollis
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.




#34
seadave
Expert Member
  • Total Posts : 318
  • Scores: 48
  • Reward points: 0
  • Joined: 2004/11/03 18:02:09
  • Location: Seattle, WA
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/29 00:48:06 (permalink)
0
@SMaBille you changed my life.  It is funny how you can be so advanced at somethings, and be aware of other solutions that you at the time do not use, until someone says "hey dummy, try this!"  I stood up a FAZ in AWS today.  My first AWS VM by the way, and it works great.  I went with the $1, t2.tiny instance, already had IAM configured for Glacier, created my ssh keys, applied a firewall policy, and I was able to sync my FWF-60E to it on the first try.  Awesome.  Amazon suggests it will cost $17/month which is fine by me considering what I paid previously for a FAZ VM license on my home network.  So now that it is running, I am seeing a ton of messages similar to what was reported above:
 
Destination IP127.0.0.1
Source IP127.0.0.1
Device IDFWF60E4Q1#######
Device NameGATE
Useradmin
User Interfacehttps(127.0.0.1)
Methodhttps
Sub Typesystem
Typeevent
Actionlogin
Levelalert
Reasonpasswd_invalid
Log DescriptionAdmin login failed
Log ID0100032002
MessageAdministrator admin login failed from https(127.0.0.1) because of invalid password
SN0
Statusfailed
Virtual Domainroot
Date/Time00:29:50
Destination End User ID0
Destination Endpoint ID3
Device Time2019-01-29 00:29:50
End User ID3
Endpoint ID3
Event Time1548750590
Time Stamp2019-01-29 00:29:50
bid1365
dvid1026
idseq205745199928836098
logver60
 
This makes no sense to me as I am not logging into a local host address?  I also do not have the HTML5 console open for extended periods.  This is repeated every 60 seconds, whether I am logged into the UI or not.
 
My FWF-60E has been crashing after ~12 hours it seems.  Hard reset brings it back.  Now that it is talking to FAZ I should be able to get better telemetry if it happens again.  Before I setup the FAZ I was logging to memory and a syslog device.  I have both of those options disabled now.  Will see if that helps.
#35
SMabille
Silver Member
  • Total Posts : 71
  • Scores: 18
  • Reward points: 0
  • Joined: 2013/03/31 15:39:51
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/29 01:04:17 (permalink)
0
Hi,
 
You are welcome, I came across it by chance, not something published / promoted enough. Might have been mentioned on fndn.
 
For the error below, download the FortiAnalyzer 6.0.4 image "FAZ_VM64_AWSOnDemand-v6-build0292-FORTINET.out" from support site and apply it to your AWS. Had the same issue.
 
 
dfollis
@SMaBille you changed my life.  It is funny how you can be so advanced at somethings, and be aware of other solutions that you at the time do not use, until someone says "hey dummy, try this!"  I stood up a FAZ in AWS today.  My first AWS VM by the way, and it works great.  I went with the $1, t2.tiny instance, already had IAM configured for Glacier, created my ssh keys, applied a firewall policy, and I was able to sync my FWF-60E to it on the first try.  Awesome.  Amazon suggests it will cost $17/month which is fine by me considering what I paid previously for a FAZ VM license on my home network.  So now that it is running, I am seeing a ton of messages similar to what was reported above:
 
Destination IP127.0.0.1
Source IP127.0.0.1
Device IDFWF60E4Q1#######
Device NameGATE
Useradmin
User Interfacehttps(127.0.0.1)
Methodhttps
Sub Typesystem
Typeevent
Actionlogin
Levelalert
Reasonpasswd_invalid
Log DescriptionAdmin login failed
Log ID0100032002
MessageAdministrator admin login failed from https(127.0.0.1) because of invalid password
SN0
Statusfailed
Virtual Domainroot
Date/Time00:29:50
Destination End User ID0
Destination Endpoint ID3
Device Time2019-01-29 00:29:50
End User ID3
Endpoint ID3
Event Time1548750590
Time Stamp2019-01-29 00:29:50
bid1365
dvid1026
idseq205745199928836098
logver60
 
This makes no sense to me as I am not logging into a local host address?  I also do not have the HTML5 console open for extended periods.  This is repeated every 60 seconds, whether I am logged into the UI or not.
 
My FWF-60E has been crashing after ~12 hours it seems.  Hard reset brings it back.  Now that it is talking to FAZ I should be able to get better telemetry if it happens again.  Before I setup the FAZ I was logging to memory and a syslog device.  I have both of those options disabled now.  Will see if that helps.


#36
seadave
Expert Member
  • Total Posts : 318
  • Scores: 48
  • Reward points: 0
  • Joined: 2004/11/03 18:02:09
  • Location: Seattle, WA
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/29 07:27:07 (permalink)
0
@SMabille, are you saying the 6.0.4 FAZ update fixes the localhost failed login events or Gate crashing?  I can see now with my FAZ that my Gate stopped passing traffic at 2:20AM last night until I hard rebooted it this AM.  I can't find any events coinciding with the drop.  In fact it looks like system CPU and memory usage were nominal at the time.  So I guess my next step is to connect a machine with Putty on it to the console to see if I can log a crash event.  Very frustrating.  I have to trouble shoot stuff at work all day, would be nice if I didn't have to do so at home also.  As another test I attempted to reset my FS108DPOE, but that didn't bring things up so the issue is definitely with the FWF60E.
#37
SMabille
Silver Member
  • Total Posts : 71
  • Scores: 18
  • Reward points: 0
  • Joined: 2013/03/31 15:39:51
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/29 07:38:25 (permalink)
0
The 6.0.4 FAZ update will fix the multiple 127.0.0.1 login errors, since then I also haven't noticed further complete crash. I suspect reaching maximum logging sessions (and keeping trying) might impact resource and possibly cause crash.
 
Everything not fantastic either, I have performance issues that are difficult to pin point to anything particular. I suspect DNS server and/or DNS helper to be involved but very difficult to troubleshoot/pinpoint the root cause (I already noticed the issue on 6.0.3). No failed session but increased latency and what looks like reduced bandwidth.
 
dfollis
@SMabille, are you saying the 6.0.4 FAZ update fixes the localhost failed login events or Gate crashing?  I can see now with my FAZ that my Gate stopped passing traffic at 2:20AM last night until I hard rebooted it this AM.  I can't find any events coinciding with the drop.  In fact it looks like system CPU and memory usage were nominal at the time.  So I guess my next step is to connect a machine with Putty on it to the console to see if I can log a crash event.  Very frustrating.  I have to trouble shoot stuff at work all day, would be nice if I didn't have to do so at home also.  As another test I attempted to reset my FS108DPOE, but that didn't bring things up so the issue is definitely with the FWF60E.




#38
seadave
Expert Member
  • Total Posts : 318
  • Scores: 48
  • Reward points: 0
  • Joined: 2004/11/03 18:02:09
  • Location: Seattle, WA
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/29 07:57:50 (permalink)
0
I updated my FAZ to 6.0.4 but unfortunately the localhost Admin failed logins are still occurring every 60s.  See image, I updated FAZ at 07:38:45, after reboot failed logins started right back up.
 
 
post edited by seadave - 2019/01/29 08:01:23

Attached Image(s)

#39
SMabille
Silver Member
  • Total Posts : 71
  • Scores: 18
  • Reward points: 0
  • Joined: 2013/03/31 15:39:51
  • Status: offline
Re: FortiOS 6.0.4 is out! 2019/01/29 08:03:07 (permalink)
0
Hi,
 
Mine was returning "admin login failed due to max session" not for invalid password.
Maybe try to remove connection to FAZ in security fabric. Also delete/check status of device in FAZ (I remember having an issue there, device not visible until I reset the FAZ in Security Fabric after upgrading FAZ).
 
If still don't work, could you post a new threat so we keep this seperate and not polutting this general thread too much?
 
Thanks,
Stephane
 
dfollis
I updated my FAZ to 6.0.4 but unfortunately the localhost Admin failed logins are still occurring every 60s.  See below, I updated FAZ at 07:38:45, after reboot failed logins started right back up.
 
itime=1548777151date=2019-01-29time=07:52:30vd=roottype=eventsubtype=systemaction=loginbid=50062dstepid=3dsteuid=0dstip=127.0.0.1dvid=1026epid=3euid=3eventtime=1548777150idseq=205745199928836096level=alertlogdesc="Admin login failed"logid=0100032002logver=60method=httpsmsg="Administrator admin login failed from https(127.0.0.1) because of invalid password"reason=passwd_invalidsn=0srcip=127.0.0.1status=failedui=https(127.0.0.1)user=admin
 
 




#40
Page: < 123 > Showing page 2 of 3
Jump to:
© 2019 APG vNext Commercial Version 5.5