Hi Peter,
Well...this did reveal something else, too - that search isn't working
properly. You're right; it wasn't sshfs-related, but configuration about
what path to find solr. I updated that, ran the relevant command above (I'm
using discovery) and it worked. Thanks!
--Charlene
On Thu, Dec 12, 2013 at 11:31 AM, Peter Dietz <pdiet...@gmail.com> wrote:
> I'm guessing the content not showing up is just regular DSpace stuff, and
> not entirely related to the location of your assetstore. I'm guessing that
> this is related to your index being out-of-date. i.e. You should reindex.
> I'm guessing that the reindex previously got interupted, in which many
> items got indexed, but the collections (which usually get indexed last)
> didn't get indexed.
>
> If you were using the lucene index. Then this is /dspace/bin/dspace
> index-init (or index-update, if you prefer)
>
>
>
> If you are using discovery, then do: /dspace/bin/dspace
> update-discovery-index
>
> dietz72m1:staffd peterdietz$ /dspace/bin/dspace update-discovery-index -h
>
> usage: org.dspace.discovery.IndexClient [-cbhf[r <item handle>]] or
>
> nothing to update/clean an
>
> existing index.
>
> -b (re)build index, wiping out current one if it exists
>
> -c clean existing index removing any documents that no
>
> longer exist in the db
>
> -f if updating existing index, force each handle to be
>
> reindexed even if uptodate
>
> -h print this help message
>
> -o optimize search core
>
> -r <item handle> remove an Item, Collection or Community from index
>
> based on its handle
>
>
> Peter Dietz
>
>
> On Wed, Dec 11, 2013 at 11:08 PM, Charlene Chinda Barina
> <cbar...@uw.edu>wrote:
>
>> Hi Peter,
>>
>> Thanks for the ideas and suggestions. I think the last time I tried I may
>> have just been impatient with tomcat restarting - it takes quite a while.
>>
>> Anyway, some progress - I do believe I the mount working, and confirmed
>> items showing up when doing ls's on both ends. For some reason, though, no
>> items show up in the collection summary page. They show up when browsing by
>> author, subject, issue date, etc., but just not by collections.
>>
>> Any ideas?
>>
>> Regards,
>> Charlene
>>
>>
>> On Wed, Dec 11, 2013 at 10:52 AM, Peter Dietz <pdiet...@gmail.com> wrote:
>>
>>> Hi Charlene,
>>>
>>> I would test that /mnt/assetstore, or /dspace/assetstore contains the
>>> data that is supposedly mounted there. LS /dspace/assetstore.
>>>
>>> Your site should work just fine without the assetstore, it will just
>>> throw tons of exceptions/errors when the requested asset had an
>>> IOException. Check your dspace logs.
>>>
>>> Also, while ssh'ed into your ec2 instance, install lynx. And try to
>>> visit lynx http://localhost:8080/xmlui, and see if the site works
>>> there. This might just be basic troubleshooting advice.
>>>
>>> I'm not sure how bulletproof of a solution that the sshfs will end up
>>> being. It seems reasonable.
>>>
>>> I did a quick price check, and it looks like EBS is $100/TB/month. If
>>> someone wrote an S3 gateway, the price of that ranges from $95-$76/TB/month
>>> (2nd+ TB of data is cheaper). I guess what I'm saying, is that if using the
>>> Amazon storage is in your budget, maybe you'll want to keep the assetstore
>>> locally in the cloud, and then some type of "roll-your-own" duracloud, or
>>> rsync to keep a copy of your assets on your university's storage array.
>>>
>>> Peter Dietz
>>>
>>>
>>> On Wed, Dec 11, 2013 at 12:00 PM, Charlene Chinda Barina <cbar...@uw.edu
>>> > wrote:
>>>
>>>> Thanks for the ideas - we actually are trying to put the DSpace
>>>> installations on AWS, and the files on the university network. As far as I
>>>> understand the only way to mount the assetstore in this situation is with
>>>> something like sshfs. It didn't seem to take very well - what I did was
>>>> mount /dspace/assetstore to the sshfs connection, and the site wasn't
>>>> working properly (e.g., site not coming up). I may try it again, though, to
>>>> see if I had configured something wrong or if it's more related to just
>>>> slow connection/overhead.
>>>>
>>>> --Charlene
>>>>
>>>>
>>>> On Mon, Dec 9, 2013 at 8:58 AM, helix84 <heli...@centrum.sk> wrote:
>>>>
>>>>> On Wed, Dec 4, 2013 at 11:54 PM, Charlene Chinda Barina <
>>>>> cbar...@uw.edu> wrote:
>>>>> > Hi, per what I understand about bitstream storage, the two options
>>>>> are a
>>>>> > local directory and via SRB (or iRODS, if I want to go an unsupported
>>>>> > route). Is that a correct understanding?
>>>>>
>>>>> Hi Charlene,
>>>>>
>>>>> that is correct, those are the two ways DSpace recognizes and
>>>>> supports. However, by local storage we mean *anything* that can be
>>>>> represented as a local filesystem path (i.e. mounts in unix-like
>>>>> systems and whatever the Windows equivalent is - drive mapping, hard
>>>>> links, DFS?). So if you already have a NAS or a server at your
>>>>> institution that exports directories, you can simply mount them at
>>>>> OS-level and point DSpace assetstore to the mounted directory. DSpace
>>>>> will work happily with it and won't care where it resides. Same goes
>>>>> for mostly anything else you can think of, like SMB/CIFS shares - they
>>>>> can be mounted locally and completely transparently to DSpace. The one
>>>>> thing I'd recommend against is sshfs as Peter suggested - while this
>>>>> is simply another protocol that can be used to mount remote
>>>>> directories, I'm pretty sure don't want the overhead of encryption to
>>>>> transfer files within your institution. If you had a SAN with iSCSI
>>>>> targets that you want to use, you'd connect to it from your DSpace
>>>>> system as a local block device, create a filesystem on it and mount it
>>>>> within your regular directory structure. From there it's the same
>>>>> local FS story again.
>>>>>
>>>>>
>>>>> Regards,
>>>>> ~~helix84
>>>>>
>>>>> Compulsory reading: DSpace Mailing List Etiquette
>>>>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Charlene Barina, MPH
>>>> Research Analyst 2, U.S. IMPACT Study
>>>> The Information School
>>>> 303-359-6347 | Skype: cbarina
>>>> facebook.com/ImpactSurvey | twitter.com/impactsurvey
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Rapidly troubleshoot problems before they affect your business. Most IT
>>>> organizations don't have a clear picture of how application performance
>>>> affects their revenue. With AppDynamics, you get 100% visibility into
>>>> your
>>>> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
>>>> AppDynamics Pro!
>>>>
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
>>>>
>>>> _______________________________________________
>>>> DSpace-tech mailing list
>>>> DSpace-tech@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>>>> List Etiquette:
>>>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>>>>
>>>
>>>
>>
>>
>> --
>> Charlene Barina, MPH
>> Research Analyst 2, U.S. IMPACT Study
>> The Information School
>> 303-359-6347 | Skype: cbarina
>> facebook.com/ImpactSurvey | twitter.com/impactsurvey
>>
>
>
--
Charlene Barina, MPH
Research Analyst 2, U.S. IMPACT Study
The Information School
303-359-6347 | Skype: cbarina
facebook.com/ImpactSurvey | twitter.com/impactsurvey
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
