how to take daemon debug log:R81.20

[saitoh]

Hi all,

I would like to know whether or not there is the way to take daemon debug log, in order to check if alertmail functions as expected or not.

I am more like fortinet guy, guite beginner at CP, so it would be lovely if CP had the counterpart to "diagnose debug application alertmail -1..."

I surmise CP has one, but not sure which log file is which.

Your help would be more than appreciated!

Saitoh

[PhoneBoy · Accepted solution]

I'm assume your question is related to this thread: https://community.checkpoint.com/t5/Management/Track-Log-Mail-would-not-work-R81-20/m-p/232420#M4039... 

In general, there are two types of debugs:

• Firewall kernel, for which there's an extensively documented process
• Userland processes, which each have different debug steps

In this case, it's a userland process, specifically fwd, that requires debugging.
See: https://support.checkpoint.com/results/sk/sk86321 

[saitoh]

Dear @PhoneBoy ,

I am sorry for the late reply, took a week of holidays, and thanks for the detailed documents.

Your assumption is correct. I had a hard time getting along with alertmail, which was done successfully the other day.

Saitoh

[the_rock]

What exact process you wish to debug? What @PhoneBoy gave looks correct.

Andy

[saitoh]

Dear @the_rock ,

Thanks for your comment.

My aim is to confirm if the CP fires alert mail or not, and I surmised I could safely say it was functioning when I saw a debug log of the certain daemon.

This is what I always do in the case of FortiGate troubleshooting, so I tried following the same way this time.

What @PhoneBoy  gave me, and another post associated with this helped me solve the issue, and now it is working as expected.

Saitoh