rix

Community Developer
 View Profile  See their activity

  • Posts

    423

  • Joined

 Content Type 

Posts posted by rix

    [Plugin] Appdata.Backup

    in Plugin Support

    Posted

    I really like this new approach to app data backups.

    Have you also noticed the auto-cleanup is broken for failed backups?

    I regularly have to manually delete backups where a failure happened that are older than the set age limit.

    [support] rix's Docker Repository

    in Docker Containers

    Posted · Edited by rix

    After the recent ungrateful comments and hostility I have decided to unfollow the thread starting with this post to not post on this forum anymore - this includes DMs (exceptions will be made for the Unraid/Mod team).

    Github issues / discussions are still welcome - and allow me to moderate what I spend my precious free time on.

     

    Feel free to discuss my work here and help each other out - so no need to lock this thread. This has worked well in the past.

     

    I will continue to work on my projects and publish them (also to the Unraid template repo), for people who find them useful.

     

    EDiT: I have removed all links to this thread from my template repo.

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    1 hour ago, SimonF said:

    It is ripping a Blue Ray in non priv mode. Created two containers, second one found disk, but issue is my drive does funny things if not used for a while and needs to be reset hence the disk still loading and not able to reboot my server to fix, but looks like it should work as expected. Will test CD on the one ripping to confirm also.

     

    image.thumb.png.89b62ee7f2f820d08b96eec286934ffa.png

     

    Sounds good. Thanks for investing your free time to help others.

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    2 minutes ago, SimonF said:

    The reason the container can see both drives is if the docker is running in priviledged mode it has complete access to all devices, so will ignore the device statements. I dont know any other effects of turning off privileged mode with the docker. @rix DM me if you want me to to any testing for you.

     

    image.thumb.png.434660f9128def71c273226038ed7add.png

      

    # makemkvcon -r --cache=1 info disc:9999
MSG:1005,0,1,"MakeMKV v1.16.5 linux(x64-release) started","%1 started","MakeMKV v1.16.5 linux(x64-release)"
MSG:5074,0,0,"Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server.","Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server."
DRV:0,0,999,0,"BD-RE ASUS BW-16D1HT 3.01 SIK9GH6KA463","","/dev/sr0"
DRV:1,0,999,0,"BD-RE HL-DT-ST BD-RE BU40N 1.03 MZUJ5KF3531","","/dev/sr1"
DRV:2,256,999,0,"","",""
DRV:3,256,999,0,"","",""
DRV:4,256,999,0,"","",""
DRV:5,256,999,0,"","",""
DRV:6,256,999,0,"","",""
DRV:7,256,999,0,"","",""
DRV:8,256,999,0,"","",""
DRV:9,256,999,0,"","",""
DRV:10,256,999,0,"","",""
DRV:11,256,999,0,"","",""
DRV:12,256,999,0,"","",""
DRV:13,256,999,0,"","",""
DRV:14,256,999,0,"","",""
DRV:15,256,999,0,"","",""
MSG:5010,0,0,"Failed to open disc","Failed to open disc"
TCOUNT:0
#

     

     

     

    image.thumb.png.9f237f284b1f18b07b61c13e71ad4da7.png

      

    # makemkvcon -r --cache=1 info disc:9999
MSG:1005,0,1,"MakeMKV v1.16.5 linux(x64-release) started","%1 started","MakeMKV v1.16.5 linux(x64-release)"
MSG:5074,0,0,"Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server.","Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server."
DRV:0,0,999,0,"BD-RE HL-DT-ST BD-RE BU40N 1.03 MZUJ5KF3531","","/dev/sr1"
DRV:1,256,999,0,"","",""
DRV:2,256,999,0,"","",""
DRV:3,256,999,0,"","",""
DRV:4,256,999,0,"","",""
DRV:5,256,999,0,"","",""
DRV:6,256,999,0,"","",""
DRV:7,256,999,0,"","",""
DRV:8,256,999,0,"","",""
DRV:9,256,999,0,"","",""
DRV:10,256,999,0,"","",""
DRV:11,256,999,0,"","",""
DRV:12,256,999,0,"","",""
DRV:13,256,999,0,"","",""
DRV:14,256,999,0,"","",""
DRV:15,256,999,0,"","",""
MSG:5010,0,0,"Failed to open disc","Failed to open disc"
TCOUNT:0
#

     

     

    That makes sense. It's one of the reasons why the privileged flag is not part of the default config in the Readme.

     

    Some users were unable to use ripper without the flag though so it's usefulness may differ between various use cases.

     

    So what you are saying is it works for you if you don't run the container as privileged?

    [support] rix's Docker Repository

    in Docker Containers

    Posted · Edited by rix

    15 minutes ago, Squid said:

    This just needs to calm down here @stayupthetree, @rix before it gets out of control.

     

    The "tag" of Community Developer is not handed out like candy here, and after the initial round of giving this title (when the forum first supported it), it is actually fairly hard to come by and rarely given.

     

    Being nasty or sarcastic isn't going to accomplish anything in this circumstance.  

     

    Arguing by a dev of a container and a user between the various use cases for a container (that the author may have absolutely zero way to test or implement) isn't helpful.  As a general rule, all the authors / maintainers etc do everything for free in their spare time with no compensation at all.  @rix does appear at first glance to support his applications whether you are a sponsor or not.

     

    That being said, it seems to me that because of how containers work there is absolutely no "real" reason why with proper mappings of the devices that multiple instances each with a separate drive mapped to them wouldn't work.  I am however also completely unable to replicate any such situation, as I haven't seen a need for any optical drive installed on any system I own (server or otherwise) in over 10 years, so can't say for sure either way.

     

    This app was initially added to CA January 13, 2017 and the latest update was 7 days ago, so the application is obviously still supported and not abandoned 

     

     

    Thanks for chiming in so quickly, @squid.

     

    I have decided not to respond to hostile comments. I am less than willing to spend my free time on internet trolls.

     

    To clear things up: as per https://github.com/rix1337/docker-ripper#do-you-offer-support I happily am able to confirm, I am not able to offer any support on this issue. Transparency is always important in open source projects - that's why that passage was added to the readme.

     

    Ripper generally works well and anyone is free to solve issues and improve the project by sending a pull request.

     

    @stayupthetree if you need further assistance and do not want to become a sponsor, then you can either:

    a) ask others in the community how they managed to get multiple drives working

    b) ship me a secondary optical drive for free (ideally your exact model) so I can try and diagnose this

     

    Edit: To further facilitate transparency I have reworded the https://github.com/rix1337/docker-ripper/blob/master/README.md#how-do-i-rip-from-multiple-drives-simultaneously section in Ripper's readme. ;)

    • Haha 1

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    11 minutes ago, stayupthetree said:

    The commenter's post clearly states they made two containers.

     

    I've tried all the methods to use 2 drives and 2 containers, but it always picks up the other drive. It is pulling the information from somewhere else. The creator only cares to support for $ 

     

    Good luck getting support for a passion project with that attitude ;)

    [support] rix's Docker Repository

    in Docker Containers

    Posted · Edited by rix

    On 1/6/2022 at 4:25 PM, doesntaffect said:

    I am using a USB CDRW Drive and want to rip Audio CDs. When I put a CD in the drive the log shows following after a few moments: 

     

    eject: tried to use `devtmpfs' as device name but it is no block device

    /config/ripper.sh: line 128: /usr/bin/ripit: No such file or directory

     

    The container log shows following: 

     

    06.01.2022 17:04:57 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds.
    *** Booting runit daemon...
    *** Runit started as PID 40
    Jan 6 17:04:57 Ryzen cron[44]: (CRON) INFO (pidfile fd = 3)
    Jan 6 17:04:57 Ryzen cron[44]: (CRON) INFO (Running @reboot jobs)
    06.01.2022 17:04:58 : Disk tray open
    06.01.2022 17:05:58 : Disc still loading
    06.01.2022 17:06:59 : CD detected: Saving MP3 and FLAC
    06.01.2022 17:06:59 : Done! Ejecting Disk
    chown: cannot access '/out/Ripper/CD': No such file or directory
    chown: cannot access '/out/Ripper/CD': No such file or directory
    06.01.2022 17:08:02 : CD detected: Saving MP3 and FLAC
    06.01.2022 17:08:02 : Done! Ejecting Disk
    chown: cannot access '/out/Ripper/CD': No such file or directory
    chown: cannot access '/out/Ripper/CD': No such file or directory

     

    I changed the out folders a few times and created /Ripper/CD manually in /out - no luck.

     

    The drive also ejects the CD. I read the GitHub page and still I am not 100% clear how to use this container. Any advise? 

     

     

    Try deleting everything from the config path.

     

    What version and tag of the image are you using?

     

    The reason I am asking is, ripit has long been removed from the image (replaced by abcde). It is highly likely that you ripper.sh ist too old and needs to be deleted. Ripper should then place the latest version at /config.

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    5 hours ago, NajChris11 said:

    Hey guys. I've been having an issue and I'm not really sure if I'm just misunderstanding. I have two separate dvd drives that I'd like to use for ripping, so I've made two containers. Unfortunately, despite the fact that I've changed the parameters in the image config, both images want to rip from the same drive.

    In my case, my drives are /dev/sr0 /dev/sg8 and /dev/sr1 /dev/sg9.
    I've tried mapping both containers to the full paths I've shown above as well as formatting it the way it's formatted by default.
    I've also tried switching it within the .sh file. I'm not sure if that's supposed to work because that's within the container but I still tried it.

    Am I missing something?
    Thanks!

    The Github readme clearly states you need to run one container per optical drive.

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    2 hours ago, W0nderW0lf said:

    In that case, maybe a "rolling" log would be a good idea to implement

    That log size is insane, creating a unified log with rolling support is not trivial in bash. Ill gladly accept a pull request for that.

     

    I still managed to fix this: using Stack Overflow codeTM the web ui now loads (up to) the last 100 lines from the logfile.

    If the log is larger than 1 MegaByte a warning to consider clearing the log is shown as well.

     

    This worked with a file of 400 MB size in my testing, so no more error should show in your case.

     

    Enjoy and show some love for this project, if you can 😉

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    20 hours ago, W0nderW0lf said:

    I use "latest"

    The log is pretty silent. Doesnt mention the webui, although I provided credentials and web path "/"

     

    Here fresh log after update: 

    *** Running /etc/my_init.d/10_syslog-ng.init...
[2021-12-19T18:15:53.993562] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.25 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file; config-version='3.13'
[2021-12-19T18:15:54.887488] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!;
Dec 19 18:15:54 f9b4ad4fa244 syslog-ng[13]: syslog-ng starting up; version='3.25.1'
Dec 19 18:15:54 f9b4ad4fa244 syslog-ng[13]: WARNING: log-fifo-size() works differently starting with syslog-ng 3.22 to avoid dropping flow-controlled messages when log-fifo-size() is misconfigured. From now on, log-fifo-size() only affects messages that are not flow-controlled. (Flow-controlled log paths have the flags(flow-control) option set.) To enable the new behaviour, update the @version string in your configuration and consider lowering the value of log-fifo-size().;
*** Running /etc/my_init.d/ripper.sh...
Using this daily? Please sponsor me at https://github.com/sponsors/rix1337 - any amount counts!
19.12.2021 18:15:55 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds.

     

    Is there a way to find out, why some disc infos cannot be red? I mean my Slipknot CD is brand new and has not a single scratch and either the album name nor the track names are extracted. Its like 20% of my collection has this problem.

    Thank you for posting this.

     

    You have noticed a bug. Both versions of ripper (latest and manual-latest) should now correctly display the web UI.

    Please pull the updated image before proceeding.

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    23 hours ago, W0nderW0lf said:

    Hi,

    first thx for making ripper! Coffee donation arrives new years eve.

     

    I wanted to ask what trick I have to use to enable the WebUI? I already provided credentials in the customization. But nothing happens after that. The log is not showing errors, nor does unRAID provide the "webui" button. Manually going to ip+port via http isnt working too. I want to find out why Some of my CD's are "unknown albums" with nameless tracks. Tried to import Slipknot - Iowa and some others..

    Glad you like it.

     

    To further assist you we need more info:

    What specific tag of the docker image are you running?

    What does your log look like (specifically after the "Starting web ui" message?

     

    The tag should be visible in your "Docker" tab, the log is accessible through the unraid UI

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    39 minutes ago, wildfire305 said:

    I can pass escape characters to ddrescue and it works fine in terminal. So the problem has something to do with the ripper.sh script. What I don't know is why it fails when the script sends $ISOPATH to it with a volume with spaces in its name. I'm not good enough in linux to diagnose or fix that yet. I don't know what I need to change in the script to make that work. I would like to have it replace the spaces with underscores, but I don't know the syntax to get that done.

    Try the latest version. I have included quotes around isopath.

    You of course need to delete your local ripper.sh for the update to take effect.

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    7 hours ago, wildfire305 said:

    I'm having an unusual problem. First time I'm trying to use the Ripper docker to rip an iso. I've already used it successfully to rip audio, dvd, blu-ray. When I try to rip an iso (insert data disc):

    The unraid docker log shows it loading the disc

    then it "looks like it works"

    then it says it completed successfully

    then it ejects the disc

    Upon inspection of the out path - the folder structure for the disc is created in ../DATA, but no iso or files are created in the folder.

    Inspection of the Ripper.log reveals the line: ddrescue: Too many files

     

    I opened the ripper.sh in nano to inspect the command. I can manually type in my ssh unraid terminal: ddrescue /dev/sr0 iso.iso and it works to create an iso from the disc.

     

    What do I need to do to correct the error? Multiple data discs were tried with the same result. I am a bit of a noob so please go easy on me I might be missing something obvious.

    Your first starting point is editing the ripper.sh

     

    You will find a command for ddrescue there

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    On 11/16/2021 at 6:08 PM, TomK1412 said:

     

    Deleted and loaded again:

     

    Container ID: fc8add089874
    By: rix1337/docker-ripper

     manual-lates...

      

    16.11.2021 18:00:12 : Disc still loading
16.11.2021 18:01:13 : CD detected: Saving MP3 and FLAC
16.11.2021 18:01:13 : Done! Ejecting Disk
16.11.2021 18:02:16 : Disk tray open

     

    CD-Folder empty

      

    # cat Ripper.log

MSG:1005,0,1,"MakeMKV v1.16.5 linux(x64-release) started","%1 started","MakeMKV v1.16.5 linux(x64-release)"
MSG:5074,0,0,"Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server.","Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server."
MSG:3332,16908288,2,"Saved FW dump file as file:///tmp/MakeMKV-0x68d-2.tmp/dump_FW_046941B5173AE11A4C78.tgz","Saved %1 dump file as %2","FW","file:///tmp/MakeMKV-0x68d-2.tmp/dump_FW_046941B5173AE11A4C78.tgz"
MSG:3347,131072,2,"Please send the file \"file:///tmp/MakeMKV-0x68d-2.tmp/dump_FW_046941B5173AE11A4C78.tgz\" to [email protected]","Please send the file \"%1\" to %2","file:///tmp/MakeMKV-0x68d-2.tmp/dump_FW_046941B5173AE11A4C78.tgz","[email protected]"
DRV:0,2,999,1,"BD-RE PIONEER BD-RW   BDR-S12 1.01 TJDL001379WL","DVDVolume","/dev/sr0"
DRV:1,256,999,0,"","",""
DRV:2,256,999,0,"","",""
DRV:3,256,999,0,"","",""
DRV:4,256,999,0,"","",""
DRV:5,256,999,0,"","",""
DRV:6,256,999,0,"","",""
DRV:7,256,999,0,"","",""
DRV:8,256,999,0,"","",""
DRV:9,256,999,0,"","",""
DRV:10,256,999,0,"","",""
DRV:11,256,999,0,"","",""
DRV:12,256,999,0,"","",""
DRV:13,256,999,0,"","",""
DRV:14,256,999,0,"","",""
DRV:15,256,999,0,"","",""
MSG:3007,0,0,"Using direct disc access mode","Using direct disc access mode"
MSG:3024,4096,2,"Complex multiplex encountered - 15 cells and 10637 VOBUs have to be scanned. This may take some time, please be patient - it can't be avoided.","Complex multiplex encountered - %1 cells and %2 VOBUs have to be scanned. This may take some time, please be patient - it can't be avoided.","15","10637"
[ERROR] abcde: lame is not in your path.
[INFO] Define the full path to the executable if it exists on your system.
[INFO] Hint: sudo apt-get install lame

      

    # find / -iname lame

#

     

    Seems now is "lame" missing

    Should be available with the next push.

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    1 hour ago, TomK1412 said: 
    # find / -iname abcde*
/etc/abcde.conf
find: ‘/sys/kernel/slab’: Input/output error
/usr/bin/abcde
/usr/bin/abcde-musicbrainz-tool
/usr/share/doc/abcde
/var/lib/dpkg/info/abcde.conffiles
/var/lib/dpkg/info/abcde.list
/var/lib/dpkg/info/abcde.md5sums
/var/lib/dpkg/info/abcde.preinst
/ripper/abcde.conf

    Seems to be there, but inserting a Music CD, the CD was still ejected after 2 to 3 seconds

    Error in log-file -> 

    root@UNRAID:/mnt/user/appdata/ripper2# cat Ripper.log
[ERROR] abcde: eyeD3 is not in your path.
[INFO] Define the full path to the executable if it exists on your system.
[INFO] Hint: sudo apt-get install

      

    # find / -iname exed3*

# find / -iname eyeD3* 

# find / -iname eyeD3

     

    Seems eye3D to be missing

     

     

     


     

     

    Try the latest build please.

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    2 hours ago, JaseNZ said:

    Just a question re ripper.
    Have installed this via docker , not using it on my unraid system it's just installed in a linux distro.
    I have two dvd drives, One is an old sata one and the other is out of a laptop with the adapter to change it to usb

    Sata shows as /dev/sr0 and the usb one as /dev/sr1

     

    The sata one works great drop a dvd in and wham its doing its thing. It does not seem to pickup the usb one though even though its showing as a dvd drive.

    No drama about it was just wondering if there would be anything stopping it from seeing the usb one or where else I could look for clues.

     

    Both are mapped fine in the container

    One drive per container instance, see:

    https://github.com/rix1337/docker-ripper#how-do-i-rip-from-multiple-drives-simultaneously

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    10 minutes ago, TomK1412 said:

    Try to do so... 

    # find / -iname abcde*
/ripper/abcde.conf

    I think /usr/bin/abcde is missing

      

    # find / -iname makemkvcon       
/usr/local/bin/makemkvcon

    makemkvcon seams to be there

      

    # find / -iname ddrescue*

    did not fidn anything, so ddrescue is missing

     

    "eject" seems to work, like every other command in "ripper.sh"

     

    Hope that helps,

     

    Tom

     

    Seems both tools got lost when I fixed the setup

     

    abcde and ddrescue should be available once the new build is complete

    [support] rix's Docker Repository

    in Docker Containers

    Posted

    1 hour ago, TomK1412 said:

    Hello @rix

     

    first of all thank you for the docker.

    I encountered problems after installation.
    The docker that is pulled is the manual build. Among other things, abcde is missing in this build , but also various other binaries. 

    Result, the CD/DVD/Blueray are read briefly and then immediately ejected with no furhter action...

     

    After a search on your Github and Docker page, I manually changed the container to "rix1337/docker-ripper:latest". With this everything seems to work.

     

    Means the "Manuel build" might not be quite ok at the moment?

     

    Greetings
    Tom

     

    Please list all missing binaries and libraries you encountered