With the latest version of ProTop, there is now only one download for Windows and one for Linux. R-code libraries are included for all the supported versions.
You can run $PROTOP/bin/pt3upd to get the latest version (or pt3upd.sh on older versions of ProTop) or download at https://wss.com/download.
Hey everyone,
ProTop 319 is ready to go! You can find all the details in the release notes.
Of note:
ProTop RT now adjusts to smaller terminal sizes. The smaller Core UI includes some interesting features like the "Of Interest" panel.
The beginning of the end of the use of WMIC on Windows
Some really cool new colour options, especially for people with visual difficulties
More and more updates to the PASOE data collector.
Try it out and please share your feedback!
@nickw regardless of which blocks are actually backed up, the probkup utility must load them all into the buffer pool to check the backup counter.
Quick correction for anyone else landing here: -Bp 10, not -bp 10. This is the private buffer pool count.
@nickw still getting the dbanalys msg too? Or just the "cannot find drive" msg?
Can you email to me log\dbmonitor.log and tmp\dbmonitor.debug and err please?
@nickw I have seen this "System cannot find the drive" message before. May be a bug - need to look in our ticketing system.
There is a new protop 319 that was released this week. I suggest you try that first. Simply run %PROTOP%\bin\pt3upd from ProEnv.
The DBAnalysis file has to be in %PROTOP\dbanalys and named nick.dba. But if you did it from ProTop RT then it should be fine. That msg may be from before you run DB Analysis.
The "Creating new flag" is normal. All ProTop processes use a file named %PROTOP%\tmp<something>.flg to signal their existance. The easiest way to stop a ProTop process is to simply remove the associated flg file.
OMG Rob don't give him ideas. pt3.14159265359...
Hi all,
The latest version of killprosession is available as part of the pt3.14 download from https://wss.com/progress-openedge-monitoring-with-protop/.
New features:
CAVEATS:
a) On AIX, you need to specify DBFILESYSTEM=/<DB file system> in $PROTOP/bin/localenv. This is because lsof on AIX only returns the file system name and not the full file name. If you have multiple DBs on multiple FS then this won't work as expected.
b) killprosession only checks shared memory segments of DBs in $PROTOP/etc/dblist.cfg.
c) Only lightly tested on HPUX as that operating system is becoming mighty scarce
$ /usr/local/protop/bin/killprosession.sh 48365686
pk4939 48365686 pts/27 _progres -pf /usr/local/etc/params.m.pf
ECHO ONLY MODE is on. Comment ECHO=echo in script.
USE AT YOUR OWN RISK. THERE IS NO 100% SAFE WAY TO KILL A SHARED MEMORY PROCESS
Please confirm the kill of this session (y/n):
and same in the usage:
Usage: /usr/local/protop/bin/killprosession.sh [ -q ] [ -f ] [ -v ] pid1 [pid2 pid3 ...]
-q quiet. No prompts
-f force. Will execute a kill -SIGFPE if lsof and svmon/pmap seem clear. DANGEROUS !!
-v verbose. Generate verbose output
ECHO ONLY MODE is on. Comment ECHO=echo in script.
Are you using killprosession? Have questions? Suggestions? This is the place.
You can get the latest version of killprosession by downloading ProTop at demo.wss.com. In Europe you can use protop-europe.com and in APAC dashboard.protop.com.au.
Paul
Rob is correct, and ProTop already has the equivalent alarm: it's called the heartbeat. If monitoring is NOT running OK for any given monitored resource, the web portal generates an alert saying "HEY! I haven't heard anything from the ProTop agent for siteName.ResourceName for the past x minutes!!". This is much more interesting than getting an hourly or daily "Everything is OK!" email as you may not notice if you miss one or two or five.
The default heartbeat check interval is 1200 seconds. After that, a heartbeat alert is generated. Note however that you must configure in ProTop where your heartbeat alerts are sent. They can stay in the web portal, they can be sent to an email list, or they can be sent to an emergency "pager" list (typically to your mobile phone).
The various web portals around the world also ping each other via email to make sure that outbound alerting is always working. if one of the portals fails to send emails for more than a few minutes, one of the other portals alerts our devOps team so that we can investigate.
Understood. Enhancement added to our TODO list.
YES. Or maybe right-click - copy the whole thing to clipboard.
Can you give me some more info on this Pieter? You want to open a new page that only contains the alert feed for that ressource and nothing else?
I'm always curious how others are using ProTop. What's the use-case here? Why is this preferable to filtering by clicking on the main alert dashboard (you call it resrc dashboard, I call it alert dashboard).
In case you didn't see them, installation instructions for UNIX and Windows can be found here: http://demo.wss.com/help/.
Usually when people get tripped up, it's because of a proxy server or permissions issues. The first thing to try, always, is to run ProTop from the command line:
$PROTOP/bin/protop <full path DB or friendlyName>
If that doesn't work, then nothing else will either.
Still having trouble? Post your questions here.
Paul