Skip to main content
MitchK
MitchK
New Member
October 21, 2008
Question

System Connection Limit Reached

  • October 21, 2008
  • 7 replies
  • 6176 views
I just noticed the following message on my dashboard' s Alert Message Console: " Fortigate has reached system connection limit for 31 seconds" . It occurred four times, each time with different numbers of seconds, the most was 66 seconds. What does this mean, and is there a way to increase the limit? Thanks very much.

    7 replies

    abelio
    SuperUser
    abelio
    SuperUser
    October 21, 2008
    Hi, Check this: http://kc.forticare.com/default.asp?id=1076 The way to ' increase' the limit is optimize your configuration; follow the links in the above article.
    MitchK
    MitchKAuthor
    New Member
    October 21, 2008
    Memory usage at this moment is about 26%. I checked the memory graph under system resources for the past 24 hours and although the graph shows no numbers (!) it shows almost a straight line. That means the memory usage could not have been much higher than 30%, including the time that I got the alert.
    laf
    laf
    New Member
    October 22, 2008
    If I check Log allowed traffic on each firewall policy, is of any help if I m not using a FA or a Syslog server? Is there a CLI command to clear the FG' s memory?
    abelio
    SuperUser
    abelio
    SuperUser
    October 22, 2008
    If I check Log allowed traffic on each firewall policy, is of any help if I m not using a FA or a Syslog server?
    if you don' t use memory or webtrends logging either, no.
    Is there a CLI command to clear the FG' s memory?
    execute reboot (just a joke) regards,
    rwpatterson
    rwpatterson
    New Member
    October 22, 2008
    ORIGINAL: abelio
    Is there a CLI command to clear the FG' s memory?
    execute reboot (just a joke) regards,
    I was going to write the same thing, but declined. Too funny!
    laf
    laf
    New Member
    October 22, 2008
    :), 10x for the answers. Still where can I see the Log allowed traffic result ? Log Access --> Memory and from here ... ?
    abelio
    SuperUser
    abelio
    SuperUser
    October 22, 2008
    Still where can I see the Log allowed traffic result ? Log Access --> Memory and from here ... ?
    exactly, and take care about logconfig->eventlog settings
    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    February 2, 2011
    When going from the old Knowledgebase " kc.forticare.com" to the new " kb.forticare.com" add 10.000 to the old article number. Like here 1.076 + 10.000 = 11.076. You' ll find the article about memory conservation here: http://kb.fortinet.com/kb/documentLink.do?externalID=11076
    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    February 2, 2011
    Still where can I see the Log allowed traffic result ? Log Access --> Memory and from here ... ?
    surprisingly, nobody answered your question. You see traffic logged in the Traffic log, not in the Event Log. To add to an old discussion, I guess this alert condition can not only be raised if ALL of the memory is exhausted but also when certain buffers only are consumed. Like heaps, address object space, queues and such. There might be " free" memory left but the maximum number of allocated buffers reached. So in practice it' s not easy to pinpoint which setting eventually caused the alert.
    laf
    laf
    New Member
    February 3, 2011
    Thanks mate! By any chance do you know: if I tick Log allowed traffic, but no external logging appliance/service is connected will it increase the equipment CPU/Memory load?
    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    February 3, 2011
    If you log into memory then a certain fixed amount of memory is allocated for the log. This is of limited usefulness if you see heavy traffic. With just 20 users I only get to see a few minutes of traffic log on a FG-80C with 1 GB total memory. For anything past that time window I' m out of luck then. So yes it does add to the memory consumption but this will not increase over time. Whether it uses ressources if you do NOT check any one of " remote syslog" or " memory" log destinations but check " Log allowed traffic" in each policy I' d have to guess that it' ll use CPU cycles and perhaps some memory for buffers. In practice I always enable logging on policies routinely; more often than not I have to use it. And I haven' t run into memory troubles because of this yet.
    Terms & ConditionsAccessibility statement