Failed to Backup Gateway 8.3.2 In Docker

Ignition
1

Hi,

Im getting a Failed to fetch error toast message when i try to backup an 8.3.2 gateway running in docker.

The folowing error appears in the logs

org.eclipse.jetty.io.EofException: null

at org.eclipse.jetty.io.SocketChannelEndPoint.flush(SocketChannelEndPoint.java:118)

at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:419)

at org.eclipse.jetty.io.WriteFlusher.completeWrite(WriteFlusher.java:374)

at org.eclipse.jetty.io.SelectableChannelEndPoint$2.run(SelectableChannelEndPoint.java:67)

at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:480)

at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:428)

at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:293)

at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.run(AdaptiveExecutionStrategy.java:201)

at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:311)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:981)

at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.doRunJob(QueuedThreadPool.java:1211)

at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1166)

at java.base/java.lang.Thread.run(Unknown Source)

Caused by: java.io.IOException: Broken pipe

at java.base/sun.nio.ch.FileDispatcherImpl.writev0(Native Method)

at java.base/sun.nio.ch.SocketDispatcher.writev(Unknown Source)

at java.base/sun.nio.ch.IOUtil.write(Unknown Source)

at java.base/sun.nio.ch.IOUtil.write(Unknown Source)

at java.base/sun.nio.ch.SocketChannelImpl.write(Unknown Source)

at java.base/java.nio.channels.SocketChannel.write(Unknown Source)

at org.eclipse.jetty.io.SocketChannelEndPoint.flush(SocketChannelEndPoint.java:112)

Any ideas what could be the root cause.

Regards

2

Broken pipe on socket write. IIRC, that is typically an abrupt TCP connection reset. Is this Docker on Windows? AV, perhaps?

3

Docker on linux,

Running on Alpine 3.17.10

4

Anything special about the deployment? or is it just a container running on a published port, accessed directly?

5

What version of Docker? V29 breaks some things. And I had an issue with the upgrade from V28 to V29 really breaking my system so that even though my compose files were using volumes, and the volumes were being used, any file writes weren't actually persisting to disk. Found that one out the ugly way.

Had to wipe docker completely, and then go straight to V29 and then things are running fine.

6

Hi @kcollins1

Sorry for the late reply.
Just a simple docker stack with an postgresql database and ignition gateway.

Since my last message, i didn’t get that error anymore.