I might suggest you get the server running and verify that it is happy before trying to get in with Studio. It might be easiest to do it all from the cube - ie you can start iris from there. I mention that because I don't believe you're expected to call irisstart directly. You can call "iris start <instancename>" (distinction is using the iris command to call start).

If the cube fails to start IRIS it should throw an error (likely in the messages.log that the error will tell you to check).

Once you've started IRIS perhaps you can try accessing terminal and the management portal, then Studio. That could narrow down the communication error which may be generic.

Hopefully you've figured this out by now but I'd suggest looking at the Filezilla logs to see if anythings stands out compared to the ssh log you get from IRIS.

My best guess is that the FTP server may not support specifically "key-pair" authentication or might require multiple forms of authentication and the other sftp methods you tried (Filezilla, sftp) may be succeeding with other auth methods. This is somewhat documented here:


You could reach out to the WRC with this.

As Alexander said, I would not recommend deleting journals from the OS. Worst case you make mirror syncing or transactions fail, or less bad but annoying you can orphan journals from the instance's record.

Journals are an important part of backup recovery as well (though a mirror covers some of that recovery role). How many days of journals are you keeping such that you fill your disk?

What kind of processes? Most user processes will need to be restarted on the other member. The mirror has some mechanisms to allow for, for example, productions to start automatically on failover, but for any given random process you probably need to handle that manually. You can use ZMIRROR.


Hi Roger,

The latest InterSystems product is IRIS, but in the Caché documentation you can find various chapters on converting from MSM > Caché.


I'd suggest reaching out to the InterSystems sales department as they may be able to assist you or point you in a direction for moving off MSM onto something more modern.


Hello Ephraim,

This seems like a better question for InterSystems Support / WRC who can look at the full log and system to try and determine what's happening.

From a file system disk space perspective, the database is almost filling the disk, but there is free space WITHIN the database from the IRIS perspective.

Regarding the performance side of things, what did you check such that it looks fine? CPU / memory / disk? When did the warnings start and are they ongoing? What's being done on the system, anything abnormal?

Hello Mark,

That's a HealthShare Information Exchange / Unified Care Record specific task. The "standard" mirroring docs don't cover it for that reason. As you gleaned from its code, it makes sure the HealthShare mirror agent is running. To be honest, I don't know all the details of what that agent does.

I'd suggest reaching out to the WRC to investigate what happened to cause the task to fail, and they can probably give more details on what the task does. While you're at it, you could also ask why it isn't documented, and poke on why it's listed as a user type task - though I see that many of the HealthShare-specific tasks are "user"-typed, so perhaps that is intended.

It's tough to say without knowing your config and what exactly was done. For the second error at least it seems reasonably clear what could be causing it, maybe that will help to resolve the first error as well? I'm not an Apache expert so take my personal advice with a grain of salt, I just know that many people have found Mark's article to be helpful.


Hi Scott,

Did you look at Web Servers for UNIX, Linux, and macOS? That page explains how to configure Apache to serve CSP files.

I'm not sure what you mean by calls to the management portal. If you have the standalone Apache / gateway set up appropriately, you can serve the portal through (presumably default) port 80, ex. go to http://<hostname>:80/csp/sys/UtilHome.csp, rather than attempting to use your private web server port.

Really the independent Apache is the main piece, you can consider the standalone web gateway to be a module on that Apache web server.

Hope that helps.