Blob Storage Issues in Enonic XP: Missing Files and Failed Directory Creation

Enonic version: YourEnonicVersion
OS: YourOS

We got some issues with our Enonic:

  • Broken images in front end, some images still showing
  • Seems that all images are Broken images in Enonic XP
  • Not able to take a dump issues with finding or creating dumps in dump directory

When checking logs we got this issues:

Blob error message when creating dump:
com.enonic.xp.blob.BlobStoreException: Failed to create directory [/var/enonic/www/sandnes/home/data/dump/sandnes-2501150000] at com.enonic.xp.repo.impl.dump.DumpBlobStore.mkdirs(DumpBlobStore.java:127) at com.enonic.xp.repo.impl.dump.DumpBlobStore.<init>(DumpBlobStore.java:29)

Blob other error message:
Caused by: java.io.FileNotFoundException: /var/enonic/www/sandnes/home/repo/blob/node/bc/bc/63/bcbc631c3ab156a2d3c0435532860a279fe092c8 (No such file or directory) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(FileOutputStream.java:270) at java.io.FileOutputStream.<init>(FileOutputStream.java:213) at com.google.common.io.Files$FileByteSink.openStream(Files.java:200) at com.google.common.io.Files$FileByteSink.openStream(Files.java:188) at com.google.common.io.ByteSource.copyTo(ByteSource.java:240) at com.enonic.xp.internal.blobstore.file.FileBlobStore.addRecord(FileBlobStore.java:123) at com.enonic.xp.internal.blobstore.file.FileBlobStore.addRecord(FileBlobStore.java:59) ... 121 common frames omitted12:47:53.705 ERROR c.e.x.p.i.e.ExceptionRendererImpl - /var/enonic/www/sandnes/home/work/cache/img/76/23/a4/7623a43e1859cf6e0a968af666e7619c37c4a5b6 (No such file or directory)com.enonic.xp.web.WebException: /var/enonic/www/sandnes/home/work/cache/img/76/23/a4/7623a43e1859cf6e0a968af666e7619c37c4a5b6 (No such file or directory)

We are running: Enonic XP 6.15.12, updating version is not a solution at this moment.

Any suggestions on what this could be?

To focus on one thing, a referenced blob is missing. You may try installing and running XP doctor on your repos to see it that helps.

From stacktrace it seems like your disk is full: no space left of run out of inodes

In that case, assuming that “YourOS” is in fact a Unix-like OS (my guess based on the path style /var/enonic/…), you should be able to check if your disk has run out of space by running these two commands:

Check byte space: df
Example result:

Filesystem      1K-blocks      Used Available Use% Mounted on
overlay          51290592  21895312  26757456  46% /
tmpfs               65536         0     65536   0% /dev
tmpfs             8190648         0   8190648   0% /sys/fs/cgroup
shm                 65536         0     65536   0% /dev/shm
/dev/sdb         51290592  21895312  26757456  46% /etc/hosts
/dev/sda1        20134592   8273404  11844804  42% /var/enonic/home
tmpfs             8190648         0   8190648   0% /proc/acpi
tmpfs             8190648         0   8190648   0% /proc/scsi
tmpfs             8190648         0   8190648   0% /sys/firmware

Check inode space: df -i
Example result:

Filesystem       Inodes    IUsed    IFree IUse% Mounted on
overlay         3276800   164530  3112270    6% /
tmpfs           2047662       16  2047646    1% /dev
tmpfs           2047662       17  2047645    1% /sys/fs/cgroup
shm             2047662        1  2047661    1% /dev/shm
/dev/sdb        3276800   164530  3112270    6% /etc/hosts
/dev/sda1       2580480   114434  2466046    5% /var/enonic/home
tmpfs           2047662        1  2047661    1% /proc/acpi
tmpfs           2047662        1  2047661    1% /proc/scsi
tmpfs           2047662        1  2047661    1% /sys/firmware