[Tim Jipson]

We keep 1 year of smatdb on everything. Each of our sites are on their own file systems, the largest is 600GB. Also we cycle them nightly using clControl.tcl but I have a second script that puts them into yyyy-mm named directories.

[Tim Jipson]

Since the alerts are run inside of a site process you don’t need to setsite.

You can always force an echo into a log of your choice.
exec echo “Outbound Queue Depth – $threadname \n” >> $log_path

[Tim Jipson]

Your Cloverleaf is throwing the error? Post your log.

I don’t know it this will help buy I’ve posted a couple images of our interconnect thread setup.

Attachments:

You must be logged in to view attached files.

[Tim Jipson]

Alerts are controlled by the MonitorD so check that log for errors.

I’ve attached my generic alert script and a generic alert file so you can see how I use the script. The script itself lives on the master site but each alert file needs to live on each site.

Attachments:

You must be logged in to view attached files.

[Tim Jipson]

Hi Jason, Looks like it was a firewall issue on the F5 load balancer.

[Tim Jipson]

Hi Jason, We were running 9.1 with 2022.09.03 and everything was running great. Then the server admin applied ‘patches’ that brought the engine up to RHEL 9.7. It has been an absolute living hell since then.  The server admin says 9.7 can’t be backed out so we trying to avoid a server rebuilt and hoping that 2022.09.04, being one minor version from certified, will be more stable.

The biggest issue we are seeing is hcienginestop does not work. Migrating to hcienginerestart has helped but there is still massive instability.

 

This is a rely from Infor I got a couple weeks ago:

Based on KB2282305, RHEL 9.1 is the latest authorized version for Cloverleaf 2022.09.03. For Cloverleaf 2022.09.04, the authorized version is RHEL 9.6. For more information, please refer to the attached KB article.

[Tim Jipson]

Interconnect doesn’t Need https. We have a couple standard tcp-ip connections interconnect. The big issue we had was a load balancer routing issue. The connection worked when connecting directly to one one the interconnect servers but not the load balancer.

[Tim Jipson]

Thanks, Ramachandran! I’d love an update next week if you have time.

Jason, It is far easier to install a patch than do a major version upgrade. Also, most hospitals I’ve worked at have no desire to be bleeding edge.

[Tim Jipson]

I did double check all the folders, but I’ve never seen an issue with fileset-local folders not automatically cleaning up.

Maybe memory leak is the wrong term, but we are now monitoring the server’s free memory and restarting hciss when memory gets low, about every 3-4 weeks I think.

[Tim Jipson]

Thanks Jim, unfortunetly our smatdb files are encrypted so that won’t work. I was able to use Charlie’s hcismatdb script to get my counts. Aside from the code for looping through the directories, this is all the code I needed then I just parse what is returned in msgCount.

 

msgCount=/hci-scripts/msgCount/hcismatdb.tcl -i $smatFile -orsf tempsmat -site ${site:1}

[Tim Jipson]

We have tracked this issue down to a memory leak in CloverleafHostServer. I’ve seen the host sever use over 5GB over the course of a month, restarting the host server drops memory usage to under 1GB. Since we’ve been doing weekly host server restarts, we have not had any site crashing issues.

[Tim Jipson]

Jim, All that script does is read messages out of smat and then creates a new file. I need to modify the smatdb file. I opened a ticket with Infor, hopefully I’ll get some useage info for smatdbdelete.

[Tim Jipson]

Thanks Jim, I’ll check that out

[Tim Jipson]

I actually just found “smatdbdelete”, I think this is what I need. Would anyone have the proper syntax for this command?

 

[Tim Jipson]

I’m doing something similar using a couple global variables in an xLate. If the new message matches the old GVs then the message is supressed. If the new message does not match the old GVs then the GVs are updated and the message is sent.

[Author]

Replies