Error Launching: EOFException: Unexpected end of ZLIB input stream

Ignition
1

Using v8.0.16.

We have an Ignition Gateway at a remote site that we VPN to using a cellular modem. When trying to use the client launcher it gets stuck for a couple minutes on the “Downloading Project” screen. It will eventually get up to about 60% downloaded and then we get the following error:
Error launching application:
EOFException: Unexpected end of ZLIB input stream

Any thoughts?

image
image

2

Hi, mate. How do you manage to solve the error?
Today it’s showing me the same error.
Thank you.

3

We are also having this issue. The Ignition Gateway is on a remote site and a computer with the client launcher connects to the Ignition Gateway via Radio communication. Did you find a solution to this? Thanks.

4

I honestly don’t recall what I did to get past this, but it was probably purging the Java cache. That seems to be the solution to a bunch of weird launching issues.

5

I've the same error, any solution found? I didn´t understand how to delete the Java cache. Can someone provide where is located the Java library cache.

6

Anyone ever figure this out? I'm getting the same error on a gateway running 8.1.36.

7

I just ran into this when restoring an edge backup (8.1.35, Ubuntu 22). I fixed it by stopping the gateway, deleting folder <installDirectory>/data/jar-cache, and restarting the gateway.

8

Bumping this.

I have some edge devices that are remote and I don't have the best support onsite to delete folders on the device. Any other workaround besides deleting the cache? How to prevent in the future?

9

Use Linux. I can't remember the last time I had to delete any client machine caches.

1 Like
10

They are on Opto 22 PLCs which are using Linux. :sweat_smile:

11

The pictured errors are client failures to launch, not gateway failures. Is the Opto 22 in question a panel PC?

12

It is not. Trying to load a designer on a local PC connected to it.

13

Then you could try deleting the .ignition/cache/ directory under your local user profile folder - this is one of the rare occasions where that might actually help. If that really doesn't work, but you've got access to the gateway web interface, you could do something pretty hacky:

  1. Use a separate, working Ignition install to create a gateway startup script that deletes the jar-cache folder in question (I'm not convinced that's related to this issue, but it's the only breadcrumb you have to go on).
  2. Export the project from that gateway.
  3. Import it into the affected gateway.

Et voila, you've run code on the machine that you don't otherwise have access to.