THX, works!
But, the dialog window on the command line did not find/display the tar file.
I had to enter the file name manually.
Best regards,
Stefan
···
-----Ursprüngliche Nachricht-----
Von:Martijn Brinkers via Users <users(a)lists.djigzo.com>
Gesendet: Sam 6 Mai 2017 19:53
An: users(a)lists.djigzo.com
Betreff: Re: Restoring a backup from an old system fails: backup file to large
On 05/06/2017 07:49 PM, Stefan Günther via Users wrote:
> Hello,
>
> one of our clients is running a six year old Djigzo 2.3.1-7 (tar installation)
>
> The backup creates a nice 58 MB tar backup file.
>
> But when we try to import the backup on a 3.2.7-5, (virtual appliance) we get the error message "Restore failed. Message: Socket Exception: Connection reset."
>
> /var/log/djigzo.log contains the following error:
>
> 06 May 2017 21:39:49 | ERROR Unexpected exception from downstream in Netty servlet handler, due to: {0}. (org.apache.cxf.transport.http.netty.server.NettyHttpServletHandler) [defaultEventExecutorGroup-4-3]
> io.netty.handler.codec.TooLongFrameException: HTTP content length exceeded 52428800 bytes.
> at io.netty.handler.codec.http.HttpObjectAggregator.decode(HttpObjectAggregator.java:218)
> at io.netty.handler.codec.http.HttpObjectAggregator.decode(HttpObjectAggregator.java:57)
> at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:89)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:278)
> at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:277)
> at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:372)
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:245)
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292)
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:278)
> at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:962)
> at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
> at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:528)
> at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:485)
> at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:399)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:371)
> at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
> at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
> at java.lang.Thread.run(Thread.java:745)
>
> How can I raise the limit of 52428800 bytes or is there something in the backup file that may savely be removed?
What happens if you try to restore the backup from the console
application? (i.e., login with ssh, then select backup -> restore
Hmm yes. Old versions created a .tar file. Newer version create .tar.gz
files (i.e., the backup is gzipped). The file filter only shows .tar.gz.
Since there is a workaround to support very old backups (multiple years
old), I'll leave it as is 
Kind regards,
Martijn Brinkers
···
On 05/06/2017 08:21 PM, Stefan Michael Guenther via Users wrote:
-----Ursprüngliche Nachricht-----
Von:Martijn Brinkers via Users <users(a)lists.djigzo.com>
Gesendet: Sam 6 Mai 2017 19:53
An: users(a)lists.djigzo.com
Betreff: Re: Restoring a backup from an old system fails: backup file to large
On 05/06/2017 07:49 PM, Stefan Günther via Users wrote:
Hello,
one of our clients is running a six year old Djigzo 2.3.1-7 (tar installation)
The backup creates a nice 58 MB tar backup file.
But when we try to import the backup on a 3.2.7-5, (virtual appliance) we get the error message "Restore failed. Message: Socket Exception: Connection reset."
/var/log/djigzo.log contains the following error:
06 May 2017 21:39:49 | ERROR Unexpected exception from downstream in Netty servlet handler, due to: {0}. (org.apache.cxf.transport.http.netty.server.NettyHttpServletHandler) [defaultEventExecutorGroup-4-3]
io.netty.handler.codec.TooLongFrameException: HTTP content length exceeded 52428800 bytes.
at io.netty.handler.codec.http.HttpObjectAggregator.decode(HttpObjectAggregator.java:218)
at io.netty.handler.codec.http.HttpObjectAggregator.decode(HttpObjectAggregator.java:57)
at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:89)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:278)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:277)
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:372)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:245)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:278)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:962)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:528)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:485)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:399)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:371)
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
at java.lang.Thread.run(Thread.java:745)
How can I raise the limit of 52428800 bytes or is there something in the backup file that may savely be removed?
What happens if you try to restore the backup from the console
application? (i.e., login with ssh, then select backup -> restore
THX, works!
But, the dialog window on the command line did not find/display the tar file.
I had to enter the file name manually.
--
CipherMail email encryption
Email encryption with support for S/MIME, OpenPGP, PDF encryption and
secure webmail pull.
Twitter: http://twitter.com/CipherMail