- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Re: MDS log search failing on primary, works on st...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
MDS log search failing on primary, works on standby MDS/CMAs R80.20 T161
Has anyone else had any issues with SmartLog on MDS, it basically times out with "This session has expired. Please try to refresh the view" error. If I log onto standby CMA, it works perfectly. Started out of blue, so not entirely sure what triggers it. Active MDS reboot fixes it for short time and then it comes back.
CPU and memory usage looks OK and there are no hanging proceses
Strange that it works from standby MDS
Inserting pictures does not seem to work right now so adding screenshot as a file
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
See: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We're are on the latest and greatest take GA take for R80.20, that was one of the first things I did but it didn't help I'm afraid. Looks like TAC case..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
just try: "evstop;mdstart"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@kaspars i would update to R80.30 it works better then the R80.20 versions did. we did have bugs from time to time within R80.20 and it did go away in R80.30.
Upgrade for MDS from R80.20 to R80.30 was no issues what so ever.
took us 3hours to upgrade 4 boxes with 30 CMA each. (we did upgrade all boxes at the same time in paralell 😄 )
Regards,
magnus
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cool! I was trying to skip R80.30 and go directly to R80.40 🙂 but maturity of R80.40 is still not there if you ask me. We have long process publishing apps in Citrix for our admins so getting new console version published is the biggest problem, not actual server upgrade :)... typical big corporate issue..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thats why you use jumpgates 😄
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
jumpgates??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just a quick update - worked seamlessly for 2 weeks after upgrade to R80.30 T215 but crashed yesterday again.
Found this SK published two days ago that matches our symptoms even though it's published only for R80.40
[Expert@mdms01:0]# cat /opt/CPrt-R80.30/log_indexes/firewallandvpn_2020-08-25T00-00-00/core.properties
#Written by CorePropertiesLocator
#Tue Aug 25 00:00:00 CEST 2020
tag=PAGING
name=firewallandvpn_2020-08-25T00-00-00
properties=${server.settings.properties.file}
configSet=firewallandvpn
