daemian

Members
  • Posts

    50
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

daemian's Achievements

Rookie

Rookie (2/14)

4

Reputation

  1. Thanks for the assistance. I ran unraid in safe mode for several days without issues, so i rebooted into "regular" mode and on a hunch started everything but my Frigate docker. Low and behold it ran for a week without issue. Yesterday i started Frigate back up and it crashed in a few hours. So clearly its that docker causing the issue and I can try to get assistance with that specific application for root cause. Thinking about it though and I have a followup questions - is there anything i can do to prevent that docker from crashing the entire system? For instance, can I throttle its access to resources so it cannot choke everything out (at least thats what I assume is happening)? Or are there are prevention/protection measures i can put in place?
  2. i did also switch from macvlan to ipvlan a while back (last time i had stability issues) and found it made a massive difference. I did double check that i am still set to ipvlan. Syslog is attached from the latest crash. Thanks, syslog
  3. Hello, I have been running unraid for many years. I have had issues at times, but for the last 1-2 years its been extremely stable. Then, seemingly out of nowhere, I stated having stability issues. I cannot think of any notable changes. The server will run fine for a few hours, but then the dockers crash and the GUI goes unreachable. I am not able to connect via SSH either. If i hit the local console it responds initially, and I am able to enter a username, but then i never get to enter the password (it times out after 60 sec and goes back to the username prompt. After it started happening, I did try upgrading to 6.12.3, but that did not help, so i went back down to 16.12.1 Attached is a diagnostics taken after the most recent crash. Hoping someone can take a look and help me figure out what is causing this. Its driving me crazy! TIA! ur01.marx.local-diagnostics-20230812-2205.zip
  4. Just wanted to chime in to say I am running into the same issue w/ my Raven scanner and unraid (which had been working for quite some time). Hoping you get a resolution from their support - let us know!
  5. just to provide an update. I made the suggested change and so far its been almost 7 days without issue. I will post back if it occurs again - otherwise future readers can assume that did it. Thanks for your help Jorge!
  6. ok so the server has crashed a few times since the last post. I did try downgrading back to 6.9.2 - but the problem persisted. Attached is the syslog file from the latest crash time frame (Aug 2 around 11:30am). TIA! syslog-192.168.166.2 (2).log
  7. ok I have enabled the syslog server. Thanks for coaching me along here. I will report back when i have data after a crash.
  8. Hi all, Hoping someone smarter than I can help me figure out whats going on. I have been running unraid for many years. I have been on the current hardware for over a year and its been very stable. Recently, I began experiencing crashes pretty regularly (uptime always less than 24 hours). This started after 2 changes: 1. I began to really use Frigate (docker). I had run a test setup w/o a TPU for a few weeks with just one camera for a few weeks without issue. However, once my Coral arrived I passed it through to my docker and added my 2 other cameras. 2. I did also upgrade to 6.10.3 at that same time. Now I am experiencing the crashes. It's almost certain the Frigate setup or update is to blame as that is what changed when I started having issues. Hoping someone can look at the diagnostics and help me figure out what the specific issue is. Thanks you in advanced ur01-diagnostics-20220722-1359.zip
  9. I am not 100% sure about this since I don't really use it, and have only been using paperless-ng for a few days now, but the original version of paperless had a defined format for interpreting date, correspondent, title, tags, etc. from the filename. My guess is that paperless-ng uses this same logic. See here: https://paperless.readthedocs.io/en/latest/guesswork.html If you get your tags and corespondent text matching setup well you should not have to bother. It will find the info in the OCR text from the coument and set those fields along with the data automatically for you. Of course that doesn't always work - but its pretty good most of the time.
  10. EDIT: I figured it out. It was exactly what it sounded like in the error... the file (.pdf) was missing. What I forgot is that some time ago I had an issue with a drive, and I messed up the replacement process. I ended up losing a number of files, including some from the paperless media directory. I assume the migration was failing because the file was referenced in the paperless DB but not there in the folder. I just put a "fummy" pdf in the folder with the appropriate name and started it again. It would then identify a different missing file. I repeated that process until I got all of the missing files replaced, and then the migration ran successfully! Thanks again for you work on this Docker. ---Leaving this for posterity, though I doubt anyone else will run into what I did--- Thanks for all of your hard work on this docker T0a. I am trying to migrated from an unraid based paperless container I have had for years (thepaperlessproject/paperless) and running into an issue. I may just be doing it entirely wrong.... I installed theredis container and then I made copies of my original papaerless appdata and user shares (with media, consume, & export dirs). When deploying the paperless-ng docker I pointed the appdata, consume, export, and media directories to those copies I made. When I start the docker I get this, and then the container stops: Paperless-ng docker container starting... Mapping UID and GID for paperless:paperless to 99:100 creating directory /tmp/paperless Apply database migrations... Operations to perform: Apply all migrations: admin, auth, authtoken, contenttypes, django_q, documents, paperless_mail, sessions Running migrations: Traceback (most recent call last): File "manage.py", line 11, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 395, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 330, in run_from_argv self.execute(*args, **cmd_options) File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 371, in execute output = self.handle(*args, **options) File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 85, in wrapped res = handle_func(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 245, in handle fake_initial=fake_initial, File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 117, in migrate state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial) File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial) File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 227, in apply_migration state = migration.apply(state, schema_editor) File "/usr/local/lib/python3.7/site-packages/django/db/migrations/migration.py", line 124, in apply operation.database_forwards(self.app_label, schema_editor, old_state, project_state) File "/usr/local/lib/python3.7/site-packages/django/db/migrations/operations/special.py", line 190, in database_forwards self.code(from_state.apps, schema_editor) File "/usr/src/paperless/src/documents/migrations/1003_mime_types.py", line 34, in add_mime_types f = open(source_path(d), "rb") FileNotFoundError: [Errno 2] No such file or directory: '/usr/src/paperless/src/../media/documents/originals/0001216.pdf' Applying documents.1003_mime_types... A snapshot of my docker settings is attached, and here are the directories: root@ur01:~# tree -d /mnt/user/paperless-ng/ /mnt/user/paperless-ng/ ├── consume ├── export ├── media │ └── documents │ ├── originals │ └── thumbnails └── temp 7 directories root@ur01:~# tree -d /mnt/disks/ssd1/appdata/paperless-ng/ /mnt/disks/ssd1/appdata/paperless-ng/ └── data └── index 2 directories root@ur01:~# Any idea what I am doing wrong? Thanks in advanced!
  11. Found a solution to my issue. In case anyone happes to encounter the same issue in the future: Turns out LinuxServers has a dockerr for the sqlitebrowser I installed that and mounted up my paperless appdata share, opened up the database and found the offending date in thee documents table(the year was 0020 instead of 2020). I changed the value, applies, and wrote the change. tada! all better.
  12. thanks for this docker, i had previously used one from Git hub, and migrated to yours some time ago. its been working awesome. But... I have now run into a problem, with papereless, not your docker. It appears to be a know issue where a bad year value causes the web interface to fail to load when you click on Documents. See Here: https://github.com/the-paperless-project/paperless/issues/414 So I need to get into the sqlite db and find the bad value to clear it out. However, I cannot figure out how to accomplish this inside the docker. If i drop into my docker (docker exec -it paperless /bin/bash) and try to run "./manage.py dbshell" it failed because sqlite3 is not installed: bash-5.0# ./manage.py dbshell CommandError: You appear not to have the 'sqlite3' program installed or on your path. bash-5.0# which sqlite3 bash-5.0# Any ideas on how i can most easily get in there? PS. I know this thread is fairly old, but there were a few request for scanner recommendations. Anyone looking for a scanner recommendation - Iook into Raven. I had a neatdesk scanner for many many years, but they quite supporting the hardware and as a result I could no longer get it to work with modern operating systems. And it was really only designed to work with their software so you had to export to a pdf to get it into paperless. The time had come to replace it and I found out about the Raven and it seemed perfect. I just purchased a raven scanner (the original not the pro) and i am extremely happy with it. It does not require an computer (has a built in android tablet), does OCR automatically, and supports directly scanning to SMB shares. So i have it configured to drop them right in my /consume directory from the unraid share - its great! Read the reviews - their customer service is top notch and they continue to improve the product. When I was looking at the scanner I did a live chat on their website and was immediately connected to someone who was able to very quickly and accurately answer my very specific questions. There was a coupon when I first looked, but I decided to pull the trigger and buy the next day and the coupon was gone. I went to their website and chatted with them and then enable a new coupon right then! Then Raven reached out and asked to setup a time to talk to me after my purchase to get my feedback and answer any questions I might have. Keep in mind, I'm just a regular guy - not given a promo or anything like that. They opened a feature request based on one of my suggestions and were going to look into a small bug/issues. I was given nothing for this recommendations - I am just really thrilled to see a geat product with excellent customer support and I want them to succeed! I am a very happy customer!
  13. it was user scripts. Once i removed that one the array started. THANK YOU BOTH!
  14. ah sure, thanks for the clarification. I rebooted into safe mode and was able to start the array successfully. So I guess the question is how do I figure out what is hosing things up.
  15. ok i upgraded to 6.8.1 - no change I was able to start the array in maintenance mode (i presume thats what you means by safe mode). Not sure what I should do from here.