topic Re: Montoring Blades in General Topics

Montoring Blades

Railx — Mon, 17 Apr 2023 10:26:40 GMT

Hello.

We have a gateway and management server version R80.40 with jumbo hotfix take 180 installed.

We have "Monitoring Blade" enabled, but "Gateway has stopped transmitting data" error appears in "Top Interfaces" tab.
I have checked the output of the cpwd_admin list and enabled_blades commands and all necessary processes are running.
Tried restarting the security gateway and management server, tried shutting down the blade, tried restarting the RTMD and CPSM processes, but nothing helped.

Has anyone encountered the same problem?
Thanks in advance.

Re: Montoring Blades

Timothy_Hall — Mon, 17 Apr 2023 12:33:25 GMT

A few things:

1) Make sure you are running the latest version of the R80.40 SmartConsole software as it doesn't notify you of available updates in that version

2) Anything interesting logged to $FWDIR/log/rtmd.elg or $FWDIR/log/cpstat_monitor.elg on the gateway when you try to run that report?

3) Wonky behavior by the SmartConsole can sometimes be fixed by clearing its local settings/cache: sk177134: SmartConsole shows "Unable to load page" when attempting to view a policy package

4) That report data is sent on TCP/18202 I believe, make sure that port is not being blocked somewhere (ACL, local firewall software).

Re: Montoring Blades

Railx — Tue, 18 Apr 2023 07:16:56 GMT

Yes, when examining $FWDIR/log/rtmd.elg we found this error:
Warning:cp_timed_blocker_handler: A handler [0xf6767d80] blocked for 3 seconds.
Warning:cp_timed_blocker_handler: Handler info: Library [/opt/CPshrd-R80.40/lib/libkiss_apps.so], Function offset [0x10dd80].
Do you know what this could be related to

Re: Montoring Blades

_Val_ — Tue, 18 Apr 2023 07:20:29 GMT

Hi, this is normal behavior, please look into sk173443 for more details.

Re: Montoring Blades

Railx — Tue, 18 Apr 2023 07:25:50 GMT

Thank you for your reply.
However, I still do not understand why we have this error.
Has anyone encountered a similar problem?

Re: Montoring Blades

Tal_Paz-Fridman — Tue, 18 Apr 2023 07:32:50 GMT

I think additional debug is needed and opening a ticket for TAC.

Increase the RTMD debug level:

# rtm debug on TDERROR_ALL_ALL=5
# tail -f #$FWDIR/log/rtmd.elg

Then reproduce the issue again

Re: Montoring Blades

Railx — Tue, 18 Apr 2023 07:33:03 GMT

We also found the following errors in $FWDIR/log/fwd.elg:
CBinaryFile::Open: exit status false
CMappedBinaryFile::error opening file /opt/CPsuite-R80.40/fw1/log//ip_block.log
CLogFile::Open2: error: open (/opt/CPsuite-R80.40/fw1/log//ip_block.log) for reading failed
log_initfile: error - unable to open and read file: /opt/CPsuite-R80.40/fw1/log//ip_block.log
CBinaryFile::Open: exit status false
CMappedBinaryFile::error opening file /opt/CPsuite-R80.40/fw1/log//archive_tool.log
CLogFile::Open2: error: open (/opt/CPsuite-R80.40/fw1/log//archive_tool.log) for reading failed
log_initfile: error - unable to open and read file: /opt/CPsuite-R80.40/fw1/log//archive_tool.log
CBinaryFile::Open: exit status false
CMappedBinaryFile::error opening file /opt/CPsuite-R80.40/fw1/log/password_manager.log
CLogFile::Open2: error: open (/opt/CPsuite-R80.40/fw1/log/password_manager.log) for reading failed
log_initfile: error - unable to open and read file: /opt/CPsuite-R80.40/fw1/log/password_manager.log