Loch

Docker is working fine here, except the conversion part. If you are having issues getting the ebook conversion working in this docker, I finally found a solution. After adding in the directory (/usr/bin/) for the Path to Calibre Binaries section, I kept getting the "missing binaries" error. Change your variable DOCKER_MODS=lscr.io/linuxserver/mods:universal-calibre-v7.16.0 https://github.com/linuxserver/docker-calibre-web/issues/306#issuecomment-2342923994 It will take a bit longer to load the first time but I have all the conversions now listed. Perhaps this will help someone.

Wow, that was uneventful. Upgraded from 6.12.14 -> 7.0. Took longer to read the forum for issues than to upgrade. I have a basic system but no issues yet. Good job guys! For those worried about the 2GB flash drive issue, I use a 2GB flash drive and 7.0 seems to use ~200MB more than 6.12.14, but I still have ~600MB free on mine.

A bit old now, but for anyone else, to set up a mariadb container I referred back to @SpaceInvaderOne tutorial on setting up Nextcloud Here Very quick and simple. After reading through a Reddit debate on multiple databases per install, I went with a separate mariadb designated for Photoview. I've been looking for a good photo gallery for me and sharing with family/friends. I wish I could get rid of the Info sidebar (supposedly coming) and I wish it had some internal photo management stuff (moving/tagging) but so far not too bad.

Just for clarification (perhaps I'm just a bit dense today). paths are what messed me up. Host: /config = appdata: /binhex-crafty/ so server path = /config/crafty/servers/CoolServerName then put your jar in that folder. Start it and it makes the files/dir you need and errors out telling you that you have to agree to the EULA Click FILES button, click eula.txt to open and change "false" to "true" (no quotes). Save Restart server Notes: 1) My Docker container started filling up rapidly and it turns out it was making Server Backups every minute and the default backup location was in the container so you may want to turn this off in TASKS or edit it to /config/crafty/Backup or wherever you want via the BACKUP button 2) Getting "Unable to Connect" errors on some servers (older versions) so I can't see #of players, etc. But terminal and commands seem to work fine

I played around with those instructions but no luck (perhaps just be me). Other option is to just start fresh. I found https://dev.to/joenas/pixelfed-beta-with-docker-and-traefik-35hm which is old but seems to have instructions using docker-compose that may work. Hopefully someone with more experience than me might be able to help.

+1 Found this https://blog.pixelfed.de/2020/05/29/pixelfed-in-docker/ which has the dock-compose file. I guess I need to just spend some time figure out how to use that in unRaid.

See my post above. Good luck trying to find the cause. I just nuked the Docker image , deleted the app dir and reinstalled from the Unraid Docker template. I was up and running in <15 min (although I spent an hour or two trying to "fix" it before that). My set up isn't fancy so I don't really know what all you may loose. I feel like updating Nextcloud is like putting it all on red at the roulette table.

@BrunoVic@jmial I've been running NC since like vers 12 or so and about every other time I upgrade it bonks totally. When I upgraded NC this time I ran into the same "internal Service Error". According to the NC forums that pretty much the generic error message. Instead of going through the logs I decided to just nuke the Docker image and delete the appdata directory. I was on vers 18 and was only really using it for file serving/backup which I have all going to a directory outside the appdata directory and Docker so I figured those files were all safe anyway. I tried deleting and starting from my back-up NC appdata folder but it gave me the same error. After you delete the NC image and dir (I actually moved it instead for backup - although it doesn't work), you can just load your NC template and start from scratch. It will automatically install the newest version (v20) and recreate the appdata directory. You will need to connect it to the old database so NOTE: If you want to keep your users/pw you will need to know your user/database/pw for your Nextcloud database on Maraidb (assuming you did the SpaceInvader video you can go there and maybe you used the same?? Fortunately I wrote mine down). O/w you will need to start fresh with a new db and users, etc The issue I ran into here was it would not let me use the same admin account I used before so I had to create a new admin username/pw and then use the old database. But with that, it set up and everything was still there including my upload history and such for other users. This is what worked for me. Good luck. But you may want to make back-ups of everything just in case. I like Nextcloud and it has gotten much better over time, but it is still very temperamental! If it's not something easily googled, I just wipe it and start over.

Quick google search suggests this has been around for many years. https://github.com/gpodder/gpodder/issues/508 https://bugs.gpodder.org/show_bug.cgi?id=369 Suggests manually editing the config (up to 1000) and then restarting. Don't know if this will help you or not.

Sorry, late to the party but I had this same issue. Website doesn't work in Chrome but works fine in Firefox in case this helps others.

Just adding my experience. Not a huge Nextcloud user and I've had trouble with every update. From past experience I decided to go 16->17->18. 16->17 via GUI. Borks several times but with some retries it finally finishes but all I get is Maintenance mode. go to the manual guide, disable it and I get the upgrade screen, again which borks but it's still using CPU so I give it time and once the CPU goes to 0 it lets me log in and I'm at 17 17->18 No GUI option so I do the manual route below. Way more smooth (just use the click->console from the unRaid GUI). Upon restart it takes a long time to finish executing (7-10 min but it's not the fastest processor) but finally finishes and I'm at 18. Haven't tried any of the new Office stuff but everything seems to working fine so far.

Just tried. You aren't alone

Just a quick reply on my experience with the Adoption loop. Docker installed fine and started fine in bridge mode (I had to change the communication port to 8083 since I was already using 8080 for something else). Tried to adopt APs but just kept looping. Tried to change to host mode but it would always revert to using port 8080 for communication (even when the run command listed 8083 or whatever I put in the config??). So I tried setting a different IP for the Unifi-Controller (same subnet). Worked like a breeze. Didn't have to override Hostname/IP on the controller or log into the APs to force inform. This may be a possible solution for those running into problems. Anyone see any issues with running it this way?

@xthursdayx Just updated. Works great. Just tick the extension for autoconversion and once downloaded any mp4 podcasts will automatically convert over to mp3 and delete the original. Thanks!

There is an extension in GPodder which will auto convert to mp3 on download but you need to have ffmpeg installed on the system with it. I thought if you added the ffmpeg install to the container it might work.

Thanks for this. Less of a resource hog than Airsonic when now I only need the podcatcher component. Would you be able to update it to include ffmpeg or avconv? My Sansa mp3 player seems to have problems with m4a files so it would be nice to autoconvert them on d/l. If not I'll have to script something up. Thanks

Ran into the “Updates between major versions and downgrades are unsupported” when trying to upgrade from NextCloud version 14 to the new 16. This solved my issue and made the upgrade fairly straightforward : https://mergy.org/2018/10/nextcloud-14-upgrade-error-updates-between-major-versions-and-downgrades-are-unsupported-fix/ Simply comment out 3 lines in the upgrade in Updater.php and you prevent the halt from the version check. Went straight from v14 to v16 without issue Hopefully this may help some folks.

Nevermind. Deleted the entire JAVA_OPTS entry and it works now. Seems rather slow but functional for my needs.

Anyone else still getting the "Too Small Initial Heap" error? I've tried with and without the JAVA_OPTS including making sure the "m" is there but can't seem to get it started. Does anyone have any ideas?

Are the following settings the same in my.service.xml in both C:\ProgramData\CrashPlan\conf and <path to your Crashplan docker setup files>\conf? <serviceUIConfig> <serviceHost>0.0.0.0</serviceHost> <servicePort>4243</servicePort> I found that if the settings were different, it didn't matter what was defined in the my.service.xml in the docker conf folder; the settings in C:\ProgramData\CrashPlan\conf\my.service.xml overrode the server side settings. Thanks Hoopster. Changed my Docker to the above and now the Mate container connects fine. Still can't get the old fashion way using the Windows client and Putty. Made sure the same things were set on the Windows machine but it keeps loading the local client despite SSHing the Service port or setting the IP/port. Well at least I have some way to manage the Docker.

I am still having problems connecting to the Crashplan Docker. Everything seems to be backing up fine, but I can not connect from either my Windows PC (using SSH tunnel) or via the Mate Desktop. All the .ui_info files are the same. I've reloaded the Mate desktop and played with the ServerHost and ServicePort settings on both clients with no effect. Mate desktop just times out and the Windows client ALWAYS connects locally. Any thoughts? It would be terrific if Limetech created/supported an official CP Docker (or something like it). It could be a pain to have to keep up with all the modifications CP seems to have been making recently. Thanks

I may have to play with this DCM4CHEE docker. The GUI is often the sticking point of many of these open-source PACS. They can be very difficult to use and set up. As you mentioned, Osirix is a terrific alternative. You could always try loading a MacOS VM and load it on there.

I recently had a very similar occurrence with parity drive (ST4000D) throwing off a huge number of read errors, but no sync errors during parity check. I replaced the drive and ran multiple preclear cycles on it. Although pending sectors decreased with each preclear cycle, they never went to zero. Reallocated sector count continued to increase. After the preclear cycles I ran a full badblock cycle, expecting to find a lot of problems, but interestingly, it found no errors at all. Like you, I'm not sure if the drive was really bad, but since it was still under warranty, I decided to RMA it. Thanks Raz. Did you have any issues with the RMA? I'll probably check it out with the WD diag tool but my guess is that it will check out fine. Since I don't feel good about the drive, I'll probably attempt an RMA (only have ~2 weeks left under warranty). Might as well try to get something back that I feel a bit more comfortable with. Even with a slight drop in Pending sectors, the uncorrectable sectors are still concerning to me.

Just to update. Re-ran parity check. ~another 800 read errors but no sync errors. New short SMART shows: 1 Raw Read Error Rate 0x002f 200 200 051 Pre-fail Always Never 11982 3 Spin Up Time 0x0027 180 178 021 Pre-fail Always Never 6000 4 Start Stop Count 0x0032 099 099 000 Old age Always Never 1394 5 Reallocated Sector Ct 0x0033 200 200 140 Pre-fail Always Never 0 7 Seek Error Rate 0x002e 100 253 000 Old age Always Never 0 9 Power On Hours 0x0032 079 079 000 Old age Always Never 15525 10 Spin Retry Count 0x0032 100 100 000 Old age Always Never 0 11 Calibration Retry Count 0x0032 100 253 000 Old age Always Never 0 12 Power Cycle Count 0x0032 100 100 000 Old age Always Never 15 192 Power-Off Retract Count 0x0032 200 200 000 Old age Always Never 7 193 Load Cycle Count 0x0032 182 182 000 Old age Always Never 55343 194 Temperature Celsius 0x0022 129 108 000 Old age Always Never 21 196 Reallocated Event Count 0x0032 200 200 000 Old age Always Never 0 197 Current Pending Sector 0x0032 200 200 000 Old age Always Never 37 198 Offline Uncorrectable 0x0030 200 200 000 Old age Offline Never 64 199 UDMA CRC Error Count 0x0032 200 193 000 Old age Always Never 16 200 Multi Zone Error Rate 0x0008 192 192 000 Old age Offline Never 3505 So Pending went down but Uncorrectable and CRC stayed constant. My thought is it is flaky but probably not enough for them to replace. Suggestions? This is my most used disk so would you replace it anyway? Thanks

Happy New Year everyone. My monthly parity check ran this morning popping up 3191 read errors. Here is the short SMART: Attached to port: sdf ID# ATTRIBUTE NAME FLAG VALUE WORST THRESH TYPE UPDATED FAILED RAW VALUE 1 Raw Read Error Rate 0x002f 200 200 051 Pre-fail Always Never 11112 3 Spin Up Time 0x0027 180 178 021 Pre-fail Always Never 5991 4 Start Stop Count 0x0032 099 099 000 Old age Always Never 1393 5 Reallocated Sector Ct 0x0033 200 200 140 Pre-fail Always Never 0 7 Seek Error Rate 0x002e 100 253 000 Old age Always Never 0 9 Power On Hours 0x0032 079 079 000 Old age Always Never 15505 10 Spin Retry Count 0x0032 100 100 000 Old age Always Never 0 11 Calibration Retry Count 0x0032 100 253 000 Old age Always Never 0 12 Power Cycle Count 0x0032 100 100 000 Old age Always Never 15 192 Power-Off Retract Count 0x0032 200 200 000 Old age Always Never 7 193 Load Cycle Count 0x0032 182 182 000 Old age Always Never 55338 194 Temperature Celsius 0x0022 128 108 000 Old age Always Never 22 196 Reallocated Event Count 0x0032 200 200 000 Old age Always Never 0 197 Current Pending Sector 0x0032 200 200 000 Old age Always Never 45 198 Offline Uncorrectable 0x0030 200 200 000 Old age Offline Never 64 199 UDMA CRC Error Count 0x0032 200 193 000 Old age Always Never 16 200 Multi Zone Error Rate 0x0008 192 192 000 Old age Offline Never 3505 Syslog looks like: Jan 1 10:33:54 Tower kernel: ata5.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 1 10:33:54 Tower kernel: ata5.01: BMDMA stat 0x65 Jan 1 10:33:54 Tower kernel: ata5.01: failed command: READ DMA EXT Jan 1 10:33:54 Tower kernel: ata5.01: cmd 25/00:00:f0:86:25/00:04:3c:01:00/f0 tag 0 dma 524288 in Jan 1 10:33:54 Tower kernel: res 51/40:cf:18:87:25/40:03:3c:01:00/f0 Emask 0x9 (media error) Jan 1 10:33:54 Tower kernel: ata5.01: status: { DRDY ERR } Jan 1 10:33:54 Tower kernel: ata5.01: error: { UNC } Jan 1 10:33:54 Tower kernel: ata5.00: configured for UDMA/133 Jan 1 10:33:54 Tower kernel: ata5.01: configured for UDMA/33 Jan 1 10:33:54 Tower kernel: sd 5:0:1:0: [sdf] Unhandled sense code Jan 1 10:33:54 Tower kernel: sd 5:0:1:0: [sdf] Jan 1 10:33:54 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08 Jan 1 10:33:54 Tower kernel: sd 5:0:1:0: [sdf] Jan 1 10:33:54 Tower kernel: Sense Key : 0x3 [current] [descriptor] Jan 1 10:33:54 Tower kernel: Descriptor sense data with sense descriptors (in hex): Jan 1 10:33:54 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 01 Jan 1 10:33:54 Tower kernel: 3c 25 87 18 Jan 1 10:33:54 Tower kernel: sd 5:0:1:0: [sdf] Jan 1 10:33:54 Tower kernel: ASC=0x11 ASCQ=0x4 Jan 1 10:33:54 Tower kernel: sd 5:0:1:0: [sdf] CDB: Jan 1 10:33:54 Tower kernel: cdb[0]=0x88: 88 00 00 00 00 01 3c 25 86 f0 00 00 04 00 00 00 Jan 1 10:33:54 Tower kernel: end_request: I/O error, dev sdf, sector 5304059672 Jan 1 10:33:54 Tower kernel: ata5: EH complete Jan 1 10:33:54 Tower kernel: md: disk1 read error, sector=5304059608 Jan 1 10:33:54 Tower kernel: md: disk1 read error, sector=5304059616 Jan 1 10:33:54 Tower kernel: md: disk1 read error, sector=5304059624 Jan 1 10:33:54 Tower kernel: md: disk1 read error, sector=5304059632 Jan 1 10:33:54 Tower kernel: md: disk1 read error, sector=5304059640 Jan 1 10:33:54 Tower kernel: md: disk1 read error, sector=5304059648 Jan 1 10:33:54 Tower kernel: md: disk1 read error, sector=5304059656 ... repeated over and over The Current Pending and Offline Uncorrectable are concerning to me, but the CRC Error is high also. Could this all be due to a cabling issue (I haven't changed cables in months and almost all of these reading are newly high)? Turns out the warranty expires in <1 month so I'm inclined to RMA is ASAP. Thanks for any help. BTW, the parity check log found 0 errors. Does that make any sense? Anyone ever thought of a plugin that parses SMART data to give more newbie users thoughts on data safety? Waiting for a SMART failure seems like a long time. Something had charting of the numbers (unMenu?) which could be very useful as well.