Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Random reboots
My Fortigate WIFI 60B, latest build (v4.0,build0291,100824 (MR2 Patch 2)) is randomly rebooting. I can' t see a cause for it other than this little blurb in the Event Log.
317 2010-10-30 17:49:00 information dhcp 26001 Client requests IP address/configuration parameters
318 2010-10-30 17:49:00 information system 20001 authentication Client 00:23:12:0b:2d:6b does WPA
319 2010-10-30 17:49:00 information system 20001 associate Accepted association from 00:23:12:0b:2d:6b
320 2010-10-30 17:48:55 information admin 32006 Fortigate started
321 2010-10-30 17:48:55 notice admin 32401 init add Administrator daemon_admin added an application control list WoW-Choke from init
322 2010-10-30 17:48:55 notice admin 32401 init add Administrator daemon_admin added an application control list monitor-p2p-and-media from init
323 2010-10-30 17:48:55 notice admin 32401 init add Administrator daemon_admin added an application control list block-p2p from init
324 2010-10-30 17:48:55 notice admin 32401 init add Administrator daemon_admin added an application control list monitor-all from init
325 2010-10-30 17:48:55 notice admin 32120 init add Administrator daemon_admin added an address all from init
20 REPLIES 20
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, here is Fortinet' s reply to my ticket.
Hello Joseph,
Your issue may be part of a bug that we are currently working on. Going back to the older firmware should fix the issue. You can then upgrade again to 4.0 MR2 Patch2 or wait for a new release.
Thank you,
Hassan Harb
Fortinet TAC Americas
1-866-648-4638
https://support.fortinet.com
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have been seeing this on our FWF60B as well the last couple of weeks. We are also at v4 MR2 P2.
Did they give any indication on when the fix would be released?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Coldfirex - No, they have not indicated. I would recommend down one patch level.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks jtfinley. Unfortunately downgrading makes me pretty nervous.
Would scheduling a reboot in the middle of the night, daily, get around this for the time being? If so, how could that be accomplished?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks jtfinley. Unfortunately downgrading makes me pretty nervous. Would scheduling a reboot in the middle of the night, daily, get around this for the time being? If so, how could that be accomplished?I downgraded just fine. It only becomes a major issue if you downgrade a complete REVISION. All my settings were maintained after downgrading to the lesser Patch Level (1).
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
jtfinley: I plan to attempt the downgrade. Has it been working well for you since? We are seeing a random reboot almost everyday currently.
Is the downgrade process the same as upgrading where you simply upload the firmware version and apply it?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, it is.
Depending on the FG model you could load the older revision into the backup location on flash and reboot at a specified time.
conf sys global
set daily-restart enable
set restart 00:00
...
You' ll have to look up the details in the CLI Guide and Admin Reference.
Don' t forget to disable daily-restart the next morning :)
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ede_pfau,
Thank you for that info! I use this for a specific customer. Was unaware of a daily reboot. A certain cable provider we have will just stop talking to our Fortigate - a daily reboot resolves it. Work-around yes, but has not had an issue since.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Im supposing this is probably still an issue in v4 MR2 P3?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Well, I upgraded our FWF60B from 4.2.2 to 4.2.3 and we have not had the random reboot since (its been about 10 days now). FYI.
