Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Railx
Explorer

Montoring Blades

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.

 

 

0 Kudos
6 Replies
Timothy_Hall
Champion
Champion

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).

Updated 2023 IPS/AV/ABOT R81.20 Course now
available at maxpowerfirewalls.com
Railx
Explorer

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

0 Kudos
_Val_
Admin
Admin

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

0 Kudos
Railx
Explorer

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

0 Kudos
Tal_Paz-Fridman
Employee
Employee

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

0 Kudos
Railx
Explorer

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

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events