All
Accepted answers
Erik Hemdal · Feb 4, 2021 go to post

Paul, v2017.1 is supported on 8.4-1H1, documentation is here.  For the rest, reach out to your account team so they can consider your complete circumstances.

Erik

Erik Hemdal · Nov 29, 2020 go to post

Paras, On OpenVMS, versioning is handled by RMS services; the versioning is supported by the filesystem.  That versioning doesn't exist on Linux.  In %Library.File these might help (or might help Hans-Peter, too):

GetFileDateCreated() -> gives creation date to the second in $H format, given the filename.

GetFileDateModified() -> last-modified time in $H format, again given the name.

And the FileSet query might help browsing the directory, too:

query FileSet(directory As %String(MAXLEN=""), wildcards As %String, sortby As %String = "", includedirs As %Boolean = 0, delimiter As %String = ";")
 

Erik Hemdal · Nov 18, 2020 go to post

Paras, I think understanding more about the specific conditions you are working with would help.  Is the encryption supported by the printer itself, or are there intermediary agents that would receive text from IRIS, encrypt, send, decrypt, and feed the printer?  How does printing to this printer work now outside of IRIS?  And knowing details like OS, and printer model helps too.  The choice of page-description language and printer driver can be important too.

Erik

Erik Hemdal · Oct 12, 2020 go to post

Steve, Vic is correct that there is a webgateway container.  It's primarily used with ICM, which handles configuration for you.  If you are not using ICM, it may be best to contact the WRC if you need assistance.

Erik

Erik Hemdal · Sep 17, 2020 go to post

Hansel, you may want to reach out to the InterSystems WRC for help if you have not found the cause on your own. 

Erik

Erik Hemdal · Aug 6, 2020 go to post

Muni,

This can be difficult and the details of what the data is and how it was killed are very important.

You may be able to accomplish what you need via ^ZJRNFILT as Dmitry mentioned.  But that requires you to find where the KILL is in the journal files, and determine how to filter out the KILL without filtering other updates that are required.  Commonly this requires replaying ALL journals from the time of the event forward, to avoid stale data replacing current data. So the longer you wait, the more journals you have to replay.

If the global contains information that has not changed in a long time, then that stable data is probably not in the journal files anymore.  You would need to restore from a backup in that case.

Erik

Erik Hemdal · Jul 16, 2020 go to post

Vivek, if you have not been able to resolve this, consider contacting the WRC for assistance.

Erik

Erik Hemdal · Jul 8, 2020 go to post

You can get good performance on any platform.  The real keys to performance are how you specify and configure the hardware and software for the kind of workload you will run.  I share Robert Cemper's preference for Linux or UNIX, but a good Windows administrator can make a Windows server run very well.

Have you been in contact with your InterSystems account team?  They can be a good source of information in the context of what your application needs are.

Erik

Erik Hemdal · May 27, 2020 go to post

Eric, your best bet is to investigate at operating-system level; a dead job means it's no longer around as far as can be detected within Ensemble.  As to what to check, this depends very much on the specific OS platform you're running; different ones have different tools.

For Linux, try looking in /var/log/messages.  For Windows, the Event Viewer is where to go.  And there may be useful information in the Caché cconsole.log.  

The WRC can help you with getting to the bottom of problems like these because there are many reasons why a job might die unexpectedly.

Erik

Erik Hemdal · May 25, 2020 go to post

I would start by confirming your current Caché locale and the configured NLS defaults for differences (In the management portal: Home > System Administration > Configuration > National Language Settings > Configured Defaults).

If you are stuck, consider reaching out to the WRC for assistance.

Erik Hemdal · May 7, 2020 go to post

Ken, 

Are you using Docker for Windows?  I don't recommend it if you have access to a Linux system or Linux VM.  There are many frustrating limitations with it.

You can try to start your container without the --detach flag to see more about what is happening at container startup.  If everything seems right, but you still have a problem, try reaching out to the WRC for help.

Erik

Erik Hemdal · May 6, 2020 go to post

That behavior is intended, as only the emergency user is able to start and stop the instance in emergency mode.  The prompt for the EmergencyId and password confirms this.

Since the original poster mentions journal restore, I too wonder about the use case.  If this is related to an emergency situation, reaching out to the WRC may be appropriate.

Erik

Erik Hemdal · Mar 26, 2020 go to post

Daniel, if you try the audit log, turn on

%System/%Login/%LoginFailure

%System/%Security/%Protect

events and try to login again.  If these don't give you the path forward, reach out to the WRC for help.  Remember to turn off these events when you're done, especially if you are on a busy system.

Erik

Erik Hemdal · Mar 26, 2020 go to post

Sylvie, you didn't specify the exact version you are using; in v2016.1.1 and later, the limit of 999 journal files per day was removed.

If you are creating a lot of journal activity, and the 999 limit applies to you, you can also increase the size of each journal file so fewer are created each day.  As Eduard posted, testing your workload is the way to determine the journal space you need.

Erik Hemdal · Mar 19, 2020 go to post

Depending on your version of Windows, there might be a Windows Telnet service, which you would want to disable using Windows tools.

Erik Hemdal · Jan 23, 2019 go to post

Hi Alexi,

Look at invoking $System.Mirror.GetMemberStatus().  This returns a $List, so you might prefer to craft a routine to run this method and examine the results of the method.

From the Caché bin directory, running 'ccontrol help' will give you assistance for invoking this from a batch script.

If you get stuck, consider the WRC for help.

Erik

Erik Hemdal · Jan 8, 2019 go to post

Good catch.  SES credentials are not the same as IAM credentials and have to be set up separately.  But once you get SES set up and properly authorized, I've found it very capable and, well, simple!

Erik Hemdal · Dec 28, 2018 go to post

Eric, consider contacting the InterSystems WRC if you have not found and resolved the issue so a support advisor can help you.

Erik Hemdal · Oct 10, 2018 go to post

Farhan,

It's certainly possible to create a user-defined audit event and add audit events from your application code.  What's the purpose of tracking patient IDs?

Audit events are stored in the CACHEAUDIT database and by default are purged after a set number of days. So using the audit log to track patient IDs might not be the right solution.  It all depends on what your ultimate goal for tracking is.  

You might want to contact the WRC or your account team for more-specific help.

Erik

Erik Hemdal · Sep 24, 2018 go to post

Joyce, can you confirm the Docker version and the OS you are running on?

Is the user issuing the docker run command a member of the docker group at operating system level?

Thanks!  Erik

Erik Hemdal · Dec 27, 2017 go to post

Robert's suggestion is the answer nearly all the time, but it's interesting that the messages seem to show an SSH server responding on the port you are using. If you want to use SSH, Robert is right: use an external SSH client and open port 22 on the remote server.

If you definitely need to use Telnet, you need to have a Telnet server (something like telnetd) running on the remote Ubuntu server and open TCP port 23.

If you are stuck, contact the WRC (support@intersystems.com) and an advisor can help you.

Erik

Erik Hemdal · Oct 23, 2017 go to post

HP-UX uses initscripts to start processes. So you need an initscript which includes commands to start, stop, and check status of processes.

Let's take the Arbiter; it's a standalone process at OS level and is easier:

The Arbiter is an instance of ISCAgent, whose initscript is likely at /sbin/init.d/ISCAgent on your HP-UX system.

Symlink to that script in the runlevel directory for the runlevels you need this to run; this should be /sbin/rc3.d for runlevel 3 or /sbin/rc4.d for runlevel 4. You can review the HP-UX runlevels by reading the manpage for init (1M) (the command man init should get you there).

In those directories, you'll see names starting with S##name and K##name (digits for the #). This signals which services are (S)tarted or (K)illed when the system switches to this runlevel. On my test machine here, in /sbin/rc3.d I see S900ISCAgent, and I can see that it would start after

S870hpsmhd.

You would need a similar initscript which would start Cache'. I would expect that the Arbiter would be run on a host distinct from its mirror members. You can review the ISCAgent initscript to get a sense of how these are organized.

Erik Hemdal · Jan 24, 2017 go to post

Hello Thomas,

 

Since you are having an issue with a field test, please open a WRC case so we can get you the kit and investigate the trouble.

 

Kind regards, Erik

Erik Hemdal · May 27, 2016 go to post

Bear in mind that a container is not exactly the same as a full OS installation, unless you make it so. This can lead to surprising problems.

One issue that I have seen is that installations fail when using a CentOS 7 container with an error that gzip is not found -- even though gzip is installed.

If you encounter this, make sure that the 'which' command is installed in the container. The installation tool uses which to locate gzip.

yum install -y which

This may prevent an annoying issue when you are commissioning a new container.