Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After upgrading to Helm Chart 9.0.3: "ERROR: #<Errno::EROFS: Read-only file system @ dir_s_mkdir - /opt/zammad/storage>" #194

Closed
rmuehlbauer opened this issue Jun 27, 2023 · 1 comment

Comments

@rmuehlbauer
Copy link

Used Zammad Version

6.0.0

Environment

Zammad Helm Chart Version 9.0.3 (upgraded from 8.3.1) running latest Zammad version 6.0.0-36

Actual behaviour

After upgraded a working zammad installation using Helm from zammad-8.3.1 to zammad-9.0.3 the system can not process any incoming emails containing attachment.

I use "Filesystem" to store my Attachments (Settings -> System -> Storage)

To me the explanation for this issue seems to be quite simple - due to the changes introduced to the filesystems with version 9.0.0 there is no writeable filesystem /opt/zammad/storage anymore

Here is the complete error message

"ERROR:` Can't process email, you will find it for bug reporting under /opt/zammad/var/spool/unprocessable_mail/93ee041d58e64e5b3e218110d5ec0a36.eml, please create an issue at https://github.com/zammad/zammad/issues" "ERROR: #<Errno::EROFS: Read-only file system @ dir_s_mkdir - /opt/zammad/storage>" E, [2023-06-27T14:58:46.466406#1-112260] ERROR -- : Can't process email, you will find it for bug reporting under /opt/zammad/var/spool/unprocessable_mail/93ee041d58e64e5b3e218110d5ec0a36.eml, please create an issue at https://github.com/zammad/zammad/issues E, [2023-06-27T14:58:46.466488#1-112260] ERROR -- : Read-only file system @ dir_s_mkdir - /opt/zammad/storage (Errno::EROFS)

How to deal with this?
I think either there must be a writeable filesystem under /opt/zammad/storage again or the storage path zammad uses to store attachements (at least in "filesystem mode") has to be adjusted.

Another issues seems to be data migration - as for now, not only new emails cant be processed but also all the attachment for the existing tickets are gone ... of course again, because the filesystem isnt there anymore.
I suppose to get the attachments back again, either bring back to filesystem zammad used to storage attachments or bring up a new filesystem and update all the attachment locations in the database.

Expected behaviour

emails should be processed correctly and previously stored attachment should be still accessable after upgrading.

Steps to reproduce the behaviour

upgrade zammad helm chart <9 to >= 9

Support Ticket

No response

I'm sure this is a bug and no feature request or a general question.

yes

@fliebe92 fliebe92 transferred this issue from zammad/zammad Jun 28, 2023
@monotek
Copy link
Member

monotek commented Jun 30, 2023

duplicate of: #191

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants