Michelangelo

Members
  • Posts

    15
  • Joined

  • Last visited

Michelangelo's Achievements

Noob

Noob (1/14)

3

Reputation

  1. Thanks, this worked. Very much appreciated!
  2. Is there a way to match the names again? Just for one more time haha, just to make sure i have all files before migrating to a new server. I have backups, but just to be sure.
  3. Oh yes, i'll change it! They show as wrong when I try to assign them.
  4. Hi all, I'm having issues with my disks showing up as missing at every reboot, i could not find the answer in related topics so i hope there is someone who can help! Configuration: Small mini pc with ICY BOX IB-RD3620SU3 3.5" disk cabinet connected via USB-C cable Issue: After each boot (reboot or from shutdown), random disks show as missing and cannot be assigned, when I assign them they show up as wrong. When i reboot, other disks are showing as missing. In the screenshot, only disk 4 is online, the others are not. After a reboot, it could very well be that disk 4 is missing and 1 and 2 are working for example. What did i try: Reboots, a lot of them (normally, one or two reboots would work, but this time it does not help) replaced USB-C cable with another USB-C to USB-C cable replaced USB-C cable with USB-C to USB-A Tried figuring out the logging, but don't know what to look for Changed display settings ( Display world-wide-name in device ID to Automatic.) as suggested here: Attached are the log files pulled at the time of writing this. Hope some can help. I'm working on a replacement server where everything is build into one case but untill then, I hope to keep this running. Big thanks in advance! unraid-diagnostics-20221006-0933.zip
  5. Update on my own post: Looks like i fixed it! For people who might experience the same issue, here is what I did to fix the problem: Before troubleshooting, I installed Redis via the Community apps platform. I picked the one from Bitnami. I did all configuration, with and without password, and it all worked as expected. But since I don't like the fact that my harddrive is constantly active, i started looking for a solution. Since I, with the help of jonaswinkler(developer of Paperless-NG) , figured out that the issue was happening somehwere between Paperless and Redis, I removed the Bitnami Redis and installed the Redis docker container manually via the Add container button (used redis:latest to make sure I recieved the latest version). I configured the port, removed the password line from the paperless docker settings and rebooted both dockers. After that, uploading works and the disk stops working after it's done with its tasks. Remaining question: Would you recommend using a password between Redis and Paperless-ng?
  6. Over night, the Paperless-ng docker kept my disk busy (you can hear it in this short clip: https://photos.app.goo.gl/bWBroD7MMDjMA19y7) and i've found this error in the logs. Everything in Paperless-Ng seems to be working properly and i'm not sure this error has something do to with it, but i could not find anything related in the logs. And as soon as I turn off paperless docker, the disk stops being busy. The client mentioned in the errors is my desktop. But i have no connections open to the file folder, Paperless via webbrowser or anything else to unraid. What is it doing? I can't find documentation regarding this error (or i'm looking in the wrong place). Any idea what is happening? Feb 6 20:36:04 Unraid nginx: 2021/02/06 20:36:04 [error] 26535#26535: *46095 connect() to unix:/var/tmp/Paperless-ng.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.48, server: , request: "GET /dockerterminal/Paperless-ng/ws HTTP/1.1", upstream: "http://unix:/var/tmp/Paperless-ng.sock:/ws", host: "192.168.1.11" Feb 6 20:36:15 Unraid nginx: 2021/02/06 20:36:15 [error] 26535#26535: *45970 connect() to unix:/var/tmp/Paperless-ng.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.48, server: , request: "GET /dockerterminal/Paperless-ng/token HTTP/1.1", upstream: "http://unix:/var/tmp/Paperless-ng.sock:/token", host: "192.168.1.11", referrer: "http://192.168.1.11/dockerterminal/Paperless-ng/" edit: forgot to mention that it also makes this sound / keeps busy when all client devices are turned off. Could it be that it keeps the disk busy because it is monitoring the share for new uploads?
  7. The paperless-ng docker works as expexted, but i will post the error in the paperloss topic. For now, just the paperless docker is stopped. All others are still working and the disk is quiet. It stopped doing anything. The error interval in the logs corrensponds with the "pattern" of sound that the disk made. So im pretty sure it has something to do with that error. I will investigate a bit more. Thanks. Allready love the community for such quick responses and the software is just great.
  8. Yes, Disk 1 is the one and only disk for now. I've stopped the paperless container and that indeed helped a bit. Just to be sure i have to correct log, is below the error you are mentioning? Feb 6 20:36:15 Unraid nginx: 2021/02/06 20:36:15 [error] 26535#26535: *45970 connect() to unix:/var/tmp/Paperless-ng.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.48, server: , request: "GET /dockerterminal/Paperless-ng/token HTTP/1.1", upstream: "http://unix:/var/tmp/Paperless-ng.sock:/token", host: "192.168.1.11", referrer: "http://192.168.1.11/dockerterminal/Paperless-ng/" Feb 6 20:36:15 Unraid nginx: 2021/02/06 20:36:15 [error] 26535#26535: *46126 connect() to unix:/var/tmp/Paperless-ng.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.48, server: , request: "GET /dockerterminal/Paperless-ng/ws HTTP/1.1", upstream: "http://unix:/var/tmp/Paperless-ng.sock:/ws", host: "192.168.1.11"
  9. Should have known that, thanks. Here it is! unraid-diagnostics-20210207-1133.zip
  10. HI All, I've installed Unraid yesterday, so pretty new to all of this. I tried searching the forums but could not find an answer to my question. The unraid server is installed for media playing and file sharing, thats it for now. But even when i'm not accessing the files or watching a movie, the disk seems busy and making a sound in a pattern. See the video in the following link: https://photos.app.goo.gl/bWBroD7MMDjMA19y7 It's not the ticking of a broken disk (its brand new), it really sounds as if it doing something but i can't find out what and find i strange that is keeps busy. Its been doing this all night. I started with just one disk, ones i have moved over files from my old server I will add the disk from that server to Unraid as well.
  11. Thanks for responding! I understand the reason a little bit better now, lets see how it goes with SQLite. All seems to be working perfectly, love it allready. Thanks for making this available in unraid! Two questions: 1) How does file name handling work via unraid config? Is this something i do via the command line or gui? I can't feally find the instructions in the docs, only an explanation on how the principle works. I did notice this error/notification in my logs, is it something to worry about? 06-02-2021 20:12 WARNING Cannot classify documents: [Errno 2] No such file or directory: '/usr/src/paperless/src/../data/classification_model.pickle'.
  12. I'm installing it with SQLite as we speak, lets give it a go and see how it works. And yes, i'm the only one so it will probably work good enoug.
  13. Ah that makes sense! Thanks for clarifying that! What would be the reason to use PostGreSQL if you are not using the database to store data itself? I assume SQlite is more than capable of doing the job, right?
  14. I'm completly new to the wonderfull world of unraid and dockers, so this might be a very noob question. Its just something i can't wrap my head around. I had to install REDIS, easy as just adding it via the community apps. But there is mapping to a volume, so where does it store its database? Shouldn't I be mapping a folder so that paperless-ng has enough room to store its data?