#Unknown error: database or disk is full

1 messages · Page 1 of 1 (latest)

sinful zealot
#

Log

spring mangoBOT
#

Welcome @sinful zealot!

Someone from <@&938443185347244033> will assist when they're available.

Including the meta.log from the beginning is a huge help, type !logs for more information.

#

You can press the "Close Post" button above or type /close at any time to close this post.

spring mangoBOT
sinful zealot
spring mangoBOT
#

📝 If you want to review this again, mrdynamo:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

silver forgeBOT
#
Providing Log Files

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ¯\(ツ)/¯

Log file too big? USE PASTEBIN or ZIP THE FILE

Thanks for using Plex Meta Manager!
spring mangoBOT
#
**User Info**

Author of Linked Message: MrDynamo
Person who Invoked the Command: MrDynamo
File Name: meta.log

Table of Contents:
Page 01: User Info
Page 02: PMM Info
Page 03: PMM Summary Info
Page 04: PMM Config.yml YAML Validation ✅
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Plex Configuration - Section 3
Page 08: Plex Configuration - Section 4
Page 09: Rec 01 - ❌ [ERROR]
Page 10: Rec 02 - ❌🛠️ INCOMPLETE LOGS
Page 11: Rec 03 - ❌⏰ PMM SCHEDULED TIME CONFLICT
Page 12: Rec 04 - ⚠️ [WARNING]
Page 13: Rec 05 - ⚠️ PLEX REGEX ERROR
Page 14: Rec 06 - 💬 CONVERT ERROR

Page 1/14
sinful zealot
#

!logscan #1187065499981447198 message

spring mangoBOT
#

📝 If you want to review this again, mrdynamo:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

#
**Rec 01** - ❌ **[ERROR]**

❌ [ERROR]
Error messages found in your attached log.
There is a very strong likelihood that PMM did not complete all of what you wanted. Some [ERROR] lines can be ignored.
For more information on handling these, [https://www.metamanager.wiki/en/latest/home/kb.html#error]
30 line(s) with [ERROR] messages. Line number(s): 5123, 5396-5397, 30237, 30323, 30409, 30495, 30581, 30667, 30753, 30839, 30925, 31011, 34411, 34494, 34577, 34660, 34743, 34826, 34909, 34992, 35075, 35158, 41062-41063, 41088-41089, 41262, 41353-41354

Page 9/14
small narwhal
# 
| sqlite3.OperationalError: database or disk is full                                                 |

Seems pretty clear. PMM is trying to save overlay status for a thing to its cache database but can't because the disk is full.

sinful zealot
#

Yeah I just wanted to see what log parser said also

#

Gonna increase my PVC size

small narwhal
#

Can't write the temp file before that:

[ERROR]    |     Overlay Error: [Errno 28] No space left on device                                              |
sinful zealot
#

Though it should already be allowed to grow dynamically…

small narwhal
#

I don't think there's anything PMM can do about this.

sinful zealot
#

No, it’s a Kubernetes sizing issue

#

I’ve increased the volume to 4gb and running now

#

Just weird that all my other pvcs could grow past requested size

sinful zealot
#

Oh there’s a bot channel I could’ve used, oops