Skip to main content
mhdganji
mhdganji
Explorer III
April 21, 2022
Solved

Logging stops and start after restarting

  • April 21, 2022
  • 5 replies
  • 12067 views

Hi,

On one of my 200E firewalls, after some time, logging to memory does not show anything but after restarting the device it comes up and working. Any way to troubleshoot and solve the problem?

 

Regards,

Best answer by Debbie_FTNT

Hey mhdganji,

what firmware version is the affected FortiGate?

As for restarting logging without restarting the whole device, this can usually be achieved by restarting the miglogd service:

#fnsysctl killall miglogd

 

If you are looking to troubleshoot the logging issue, you can also dig into the miglogd debug itself:
#dia de app miglogd -1
#dia de en

5 replies

jhussain_FTNT
Staff
jhussain_FTNT
Staff
April 22, 2022

When FortiGate is enabled with memory logging, default specific amount of memory space will be allocated for memory logging. Memory logging is not suggested in Lower/middle end firewall,you can configure either Disk or external logging like Fortianalyzer for logging.

warshad
Staff
warshad
Staff
April 22, 2022

Hi,

 

memory logging is not suggested in Lower end firewall, for troubleshooting any specific issue or for monitoring the traffic logs locally, it is possible to enable the memory logging and disable it later.

 

 

jhussain_FTNT
Staff
jhussain_FTNT
Staff
April 22, 2022

Hi Waqas,

Yes, you can enable the logging for temporarily but it will not store the logs, it will display only the most recent logs entries only.

mhdganji
mhdganjiAuthor
Explorer III
April 22, 2022

Hi,

I just need it to do some fast troubleshooting but anyway I need it. Is there any daemon or service to bring it back alive without restarting the device? And my main question still on the table: why it happens just to this device among many ones?

 

regards

Debbie_FTNT
Staff & Editor
Debbie_FTNTAnswer
Staff & Editor
April 22, 2022

Hey mhdganji,

what firmware version is the affected FortiGate?

As for restarting logging without restarting the whole device, this can usually be achieved by restarting the miglogd service:

#fnsysctl killall miglogd

 

If you are looking to troubleshoot the logging issue, you can also dig into the miglogd debug itself:
#dia de app miglogd -1
#dia de en

mhdganji
mhdganjiAuthor
Explorer III
April 22, 2022

"fnsysctl killall miglogd"   did the trick. The command is not predicted while typing and I was looking for it more than 30 minutes :)

The O.S. is 6.4.5. Maybe I should update it to resolve the problem.

mhdganji
mhdganjiAuthor
Explorer III
July 31, 2022

Hi,

Even after updating to 7.0.6 the problem still is there.

After fnsysctl killall miglogd the logs are displayed for a while but again they vanish.

 

This is the log of miglogd. Any hint from this log to find out the problem?

 

Logs.JPG

Debbie_FTNT
Staff & Editor
Debbie_FTNT
Staff & Editor
August 1, 2022

Hey mhdganji,

the output looks fine to me - a technical ticket is probably the best way to go here, to really dig into debug and figure out what may be happening.

Sorry to hear the issue is not resolved.

warshad
Staff
warshad
Staff
July 31, 2022

Hi,

 

I would suggest you open a ticket with FortiGate Technical Support for further investigation..

 

Terms & ConditionsAccessibility statement