acurcione
-
Posts
272 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by acurcione
-
-
This has been asked several times and I don't see any answer. Autostart doesn't work with Crashplan. Logs point to this:
openbox-xdg-autostart requires PyXDG to be installed
What needs to be done to fix this?
-
I installed OwnCloud not too long ago to keep some files synced between desktop and laptop and it's been working great so far. However I think I screwed something up when I installed it and don't know what I can do to correct it.
When I installed it I pointed the data directory to a drive on my array cause I didn't want the synced files to live on the cache drive. So I have this mapping:
/var/www/html/data >> /mnt/user/Media/owncloud/data
It works, but it's always keeping a connection open to the one drive (currently anyway) that the files sit on. So that drive is never spinning down as a result.
I see a database file in the data directory along with some other files and of course the directory that I'm actually syncing. IF it's these other files that are keeping the drive from spinning down, how do I move those to the cache drive but keep the actual user files on the array??
Here's a full list of my mappings:
/var/www/html/apps >> /mnt/cache/appdata/owncloud/apps
/var/www/html/config >> /mnt/cache/appdata/owncloud/config
/var/www/html/data >> /mnt/user/Media/owncloud/data
Thanks in advance.
Anybody?
As a test of my theory I stopped owncloud and the drive with all the data spun down normally. What I don't get is why since the media share uses cache so anything being written should go there until moved. So the drive should spin down. Why isn't it?
Sent from my iPad using Tapatalk
Never mind folks. After digging around I didn't see any easy way to do this so I just moved the damn data directory to a drive that is already spun up 24/7.
-
I installed OwnCloud not too long ago to keep some files synced between desktop and laptop and it's been working great so far. However I think I screwed something up when I installed it and don't know what I can do to correct it.
When I installed it I pointed the data directory to a drive on my array cause I didn't want the synced files to live on the cache drive. So I have this mapping:
/var/www/html/data >> /mnt/user/Media/owncloud/data
It works, but it's always keeping a connection open to the one drive (currently anyway) that the files sit on. So that drive is never spinning down as a result.
I see a database file in the data directory along with some other files and of course the directory that I'm actually syncing. IF it's these other files that are keeping the drive from spinning down, how do I move those to the cache drive but keep the actual user files on the array??
Here's a full list of my mappings:
/var/www/html/apps >> /mnt/cache/appdata/owncloud/apps
/var/www/html/config >> /mnt/cache/appdata/owncloud/config
/var/www/html/data >> /mnt/user/Media/owncloud/data
Thanks in advance.
Anybody?
As a test of my theory I stopped owncloud and the drive with all the data spun down normally. What I don't get is why since the media share uses cache so anything being written should go there until moved. So the drive should spin down. Why isn't it?
Sent from my iPad using Tapatalk
-
I installed OwnCloud not too long ago to keep some files synced between desktop and laptop and it's been working great so far. However I think I screwed something up when I installed it and don't know what I can do to correct it.
When I installed it I pointed the data directory to a drive on my array cause I didn't want the synced files to live on the cache drive. So I have this mapping:
/var/www/html/data >> /mnt/user/Media/owncloud/data
It works, but it's always keeping a connection open to the one drive (currently anyway) that the files sit on. So that drive is never spinning down as a result.
I see a database file in the data directory along with some other files and of course the directory that I'm actually syncing. IF it's these other files that are keeping the drive from spinning down, how do I move those to the cache drive but keep the actual user files on the array??
Here's a full list of my mappings:
/var/www/html/apps >> /mnt/cache/appdata/owncloud/apps
/var/www/html/config >> /mnt/cache/appdata/owncloud/config
/var/www/html/data >> /mnt/user/Media/owncloud/data
Thanks in advance.
-
Wow. Don't I feel like a class A idiot. Thanks much!
-
I recently added another docker app (Crashplan) and when I got ready to start a backup I noticed a docker.img file in the base of the /mnt/user directory. But when I first setup Docker up I told it create the image on the cache drive. I have a file in each location, the same size, and approximately the same modifications stamp. Is that normal? If not, what the heck did I do??
-
Never mind. I'm going to keep it to one drive only for the time being to keep things clean and whatnot.
-
I've setup a user share on unRAID to act as a holder for backups from Crashplan (from 1 computer) and also system backups (from 2 Windows computers). Everything is working so far, but I noticed that I neglected to check the included disk when I setup the share so it's using all disks instead of just one. Does this matter? Should I remove all the contents of that share and start over to keep all the content on just one disk?
Thanks.
-
Yeah docker hub sucks for that, it works on github. https://github.com/hurricanehrndz/docker-containers/tree/master/ubooquity
Thank you very for you generosity. PS Feel free to open issues on github too. It's better for me in order to keep track of them and ensure they get resolved in timely manner.
You're most welcome! I'll try to remember to open issues on Github in the future.
Sent from my iPhone using Tapatalk
-
FYI - The Paypal donation button at the bottom doesn't actually render on your page. It's just showing the HTML. I just copied the URL to get it to you.
-
Thanks. I will address that as well. Should have something out shortly. Thanks for all your feedback. I love new users because they test the crap out of everything.
Awesome! Thanks so much for all the help and all the work you do for us! I sure as hell wouldn't know where to begin with most of this stuff!
Yeah, no worries. Feel free to donate if you find it helpful or if you have something to spare.
New build was initiated. Hope you have fun and that it works for you.
Yeah man. It's now seeing my comics again! Donation incoming. Thanks so much!
-
Thanks. I will address that as well. Should have something out shortly. Thanks for all your feedback. I love new users because they test the crap out of everything.
Awesome! Thanks so much for all the help and all the work you do for us! I sure as hell wouldn't know where to begin with most of this stuff!
-
Drop into the command line.
and execute the following:
docker exec ubooquity udpate
Replace ubooquity with the name of your container.
This is the quote from the README.
Maintenance
Upgrading:
If you have installed our systemd service file, you can update by
executing the following command:
sudo systemctl restart ubooquity.service
Additionally you can update by:
docker exec ubooquity update
Is that not clear in the instructions? If ain't please advise and I will try and make it more clear.
The issue is that the container build is based on ubooquity's rss feed, unfortunately it doesn't seem like the developer updates that info. So I will rework the update logic.
Since your last statement said the update wouldn't actually work due to the RSS feed I wasn't expecting this to actually work per se. I did expect it to actually run though. Here's what I saw when I tried to run it manually and the command I used.
docker exec Ubooquity update
/bin/update: line 4: curl: command not found
Stopping ubooquity...
Updating ubooquity...
/bin/update: line 9: curl: command not found
unzip: cannot find or open /tmp/, /tmp/.zip or /tmp/.ZIP.
Starting ubooquity...
Not sure what it's complaining about though. I can update via the GUI so wouldn't that mean everything is where it needs to be to do it?
-
Drop into the command line.
and execute the following:
docker exec ubooquity udpate
Replace ubooquity with the name of your container.
This is the quote from the README.
Maintenance
Upgrading:
If you have installed our systemd service file, you can update by
executing the following command:
sudo systemctl restart ubooquity.service
Additionally you can update by:
docker exec ubooquity update
Is that not clear in the instructions? If ain't please advise and I will try and make it more clear.
The issue is that the container build is based on ubooquity's rss feed, unfortunately it doesn't seem like the developer updates that info. So I will rework the update logic.
Ah. I'm sorry man. I'm new to Docker and some things still don't make much sense. For some reason I was thinking that command wouldn't update the jar file (in this case), but rather the supporting container. If that makes any sense to you. I guess my mind is stuck on them being separate.
-
I wrote up a modified version of the procedure (found here) that may or may not be of interest. It works with whole drives, so it doesn't fit what you are wanting to do, using a temporary space to copy to and from. But the rsync discussion may be useful.
Started on this yesterday after swapping the memory since that may well have been part of the problem. So far so good.
I had a couple rsync errors on 2 files that had extended attributes it didn't like or something. I copied those 2 files over manually before starting the process on the next drive. Many more hours to go on this one and then on to the last one.
Anyway, thank you for the alternative way of doing this. Works like a charm!
-
New build was triggered. I'm hoping the automated build server of mine will be up by the end of the weekend. No promises though.
Thanks. I read through the update/upgrade parts, but that doesn't exactly tell me how to update Ubooquity to the latest inside the container. Unless I'm missing something - totally possible.
Also saw an update pop-up in unRAID for the container so I updated, but Ubooquity is still the 1.10.0 version and not the updated 1.10.1 with the bug fix. So I'm guessing this build was just to get ready for the automation you have planned?
-
I will build a new container soon as well. Sorry my automated build server is not up yet
Sent from my D6603 using Tapatalk
Thank you. Patiently waiting so I can get this thing running again. Bummer that version had a bug for secured files, but I have quite a bit of them so definitely need that to work! At least we know it was nothing on your side though!
-
Install Community Applications and forget about using template repos. In this case, after you've removed the container and image, just readd Ubooquity via CA's available apps sectionDid you read the docker page? Docker exec ubooquity update
Sent from my D6603 using Tapatalk
Sorry to be so dense, but I've been looking for info and I can't find squat. Not sure I understand the statement.
I also don't know that I removed the old one properly. I removed the container and image, but I guess I didn't remove the template cause I have no idea how to do that. I only have one template repo set, but I don't think that's the same thing.
That's what I did so I guess I'm good on that front. I only use the CA plugin.
-
Did you read the docker page? Docker exec ubooquity update
Sent from my D6603 using Tapatalk
Sorry to be so dense, but I've been looking for info and I can't find squat. Not sure I understand the statement.
I also don't know that I removed the old one properly. I removed the container and image, but I guess I didn't remove the template cause I have no idea how to do that. I only have one template repo set, but I don't think that's the same thing.
-
It looks like a known issue according to this:
https://ubooquity.userecho.com/topics/260-error-when-scanning-library/
Unfortunately I can't update to 1.10.1. How do we update the jar file now??? It obviously isn't done manually anymore cause I've tried like 3 times.
-
Saw there was an auto-update for Ubooquity and updated. Then found out that was a bad idea so I remove the docker image and template and downloaded again. Now I can't get the thing to see any of my 2000+ comics! I have no idea what I'm configuring wrong here, but nothing I've tried actually gets Ubooquity to see more than one comic. Below is from the logs and attached are my settings for it. Help?!
20160523 11:01:06 [main] INFO com.ubooquity.Ubooquity - Loading preferences
20160523 11:01:06 [main] INFO com.ubooquity.c - Starting internal server...
20160523 11:01:06 [scanner thread] INFO com.ubooquity.data.feeder.a - Scanning books directories
20160523 11:01:06 [scanner thread] INFO com.ubooquity.data.feeder.a - Finished scanning books directories, populating folders content cache
20160523 11:01:06 [scanner thread] INFO com.ubooquity.data.feeder.a - Books folder content cache populated
20160523 11:01:06 [scanner thread] INFO com.ubooquity.data.feeder.a - Scanning comics directories
20160523 11:01:06 [scanner thread] INFO com.ubooquity.b.c - Reading metadata of comic file: /mnt/comics/Shi/Shi_Way_of_the_Warrior_01.pdf
20160523 11:01:06 [scanner thread] INFO com.ubooquity.fileformat.pdf.b - Reading metadata of pdf file: /mnt/comics/Shi/Shi_Way_of_the_Warrior_01.pdf
20160523 11:01:06 [main] INFO com.ubooquity.c - Reverse proxy prefix is not activated
20160523 11:01:06 [main] INFO com.ubooquity.c - Internal server started. Listening on port 2202
Enter Q to exit
20160523 11:01:06 [scanner thread] ERROR com.ubooquity.Ubooquity - Uncaught exception on thread: Scanner thread
java.lang.NoClassDefFoundError: org/bouncycastle/jce/provider/BouncyCastleProvider
at org.apache.pdfbox.pdmodel.encryption.PDEncryption.<init>(PDEncryption.java:96) ~[pdfbox-2.0.0.jar.3689588534321667898.tmp:2.0.0]
at org.apache.pdfbox.pdfparser.PDFParser.prepareDecryption(PDFParser.java:282) ~[pdfbox-2.0.0.jar.3689588534321667898.tmp:2.0.0]
at org.apache.pdfbox.pdfparser.PDFParser.initialParse(PDFParser.java:199) ~[pdfbox-2.0.0.jar.3689588534321667898.tmp:2.0.0]
at org.apache.pdfbox.pdfparser.PDFParser.parse(PDFParser.java:249) ~[pdfbox-2.0.0.jar.3689588534321667898.tmp:2.0.0]
at org.apache.pdfbox.pdmodel.PDDocument.load(PDDocument.java:847) ~[pdfbox-2.0.0.jar.3689588534321667898.tmp:2.0.0]
at org.apache.pdfbox.pdmodel.PDDocument.load(PDDocument.java:803) ~[pdfbox-2.0.0.jar.3689588534321667898.tmp:2.0.0]
at org.apache.pdfbox.pdmodel.PDDocument.load(PDDocument.java:757) ~[pdfbox-2.0.0.jar.3689588534321667898.tmp:2.0.0]
at com.ubooquity.fileformat.pdf.b.a(SourceFile:34) ~[ubooquity.jar:1.10.0]
at com.ubooquity.b.c.a(SourceFile:58) ~[ubooquity.jar:1.10.0]
at com.ubooquity.data.feeder.a.b(SourceFile:512) ~[ubooquity.jar:1.10.0]
at com.ubooquity.data.feeder.a.c(SourceFile:470) ~[ubooquity.jar:1.10.0]
at com.ubooquity.data.feeder.a.b(SourceFile:35) ~[ubooquity.jar:1.10.0]
at com.ubooquity.data.feeder.a$1.run(SourceFile:123) ~[ubooquity.jar:1.10.0]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_77]
Caused by: java.lang.ClassNotFoundException: Failure to load: org.bouncycastle.jce.provider.BouncyCastleProvider
at com.ubooquity.e.c.loadClass(SourceFile:992) ~[ubooquity.jar:1.10.0]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_77]
... 14 common frames omitted
20160523 11:01:07 [Timer-1] INFO com.ubooquity.Ubooquity - Checking latest available Ubooquity version from website
20160523 11:01:08 [Timer-1] INFO com.ubooquity.Ubooquity - Latest version available: 1.10.1 - Current version: 1.10.0
-
When I did memtest it was immediately obvious. Then I did memtest with each stick in each slot and it was definitely a bad stick. I was able to run without it fine until I got another one.
Yours looks like a stuck bit somewhere since it always comes up "returned 00008 instead of 00000". The bit could be stuck elsewhere in the system I guess, controller or somewhere. In any case it sounds like a recipe for data corruption. If you had another disk I guess you could try it just to make sure it isn't really something with the disk. Could be stuck in the drive electronics I suppose.
So after I posted this I rebooted the thing and ran a single preclear. It finished successfully so the mystery deepens. I still have new memory that should arrive today and since this would be the second unexplained incident, I'll go ahead and swap it. Then test the hell out of it.
And I should probably run another preclear cycle once that's all done just to be extra sure, but that might be overkill.
-
When I did memtest it was immediately obvious. Then I did memtest with each stick in each slot and it was definitely a bad stick. I was able to run without it fine until I got another one.
Yours looks like a stuck bit somewhere since it always comes up "returned 00008 instead of 00000". The bit could be stuck elsewhere in the system I guess, controller or somewhere. In any case it sounds like a recipe for data corruption. If you had another disk I guess you could try it just to make sure it isn't really something with the disk. Could be stuck in the drive electronics I suppose.
Ah. Well, I ordered some new ram anyway. I haven't had any errors elsewhere, but it can't hurt.
I'll run a very long memtest when I get them and then run preclear again. If I still have problems it's either the drive or something else as you state. I just don't want a chance for data corruption!
-
I had this once. Turned out to be bad RAM.
Wow. Ram prices sure have dropped since my build. Should I just buy new ram anyway? Honestly have nothing else to go on, but Ram was the first suggestion to my other issue as well. Figured a 3 hour passed memtest was good though.
[CONTAINER] CrashPlan & CrashPlan-Desktop
in Docker Containers
Posted
Hmm. Well why would some people have the same issue with the same error? I don't know of a way to add that package.
Sent from my iPad using Tapatalk