Is this set in your config?
AppConfig[:enable_solr] = false
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Gadsby,
Eric T.
Sent: Friday, May 19, 2023 11:22 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group
Are you sure ArchivesSpace isn't already running?
ps auxww | grep archives
If netstat doesn't show anything you could try lsof or maybe nmap
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Gadsby,
Eric T.
Sent: Friday, May 19, 2023 11:
Your DB is in a bad place.
It has tables from the failed upgrade, so every time you try to run it again it
sees those tables and says "nope, can't keep going, you have this one already"
Make sure you do this on a COPY of the DB and not the live site.
drop table lang_material
./scripts/setup-databa
t box show
the domain url instead.
Robert
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Blake
Carver
Sent: Wednesday, May 10, 2023 09:10
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Error trying to loa
It looks like you're hitting a known issue, with no known fix yet. Here's the
JIRA with some details:
https://archivesspace.atlassian.net/browse/ANW-1427
Long story short, the importer just falls apart sometimes. If you can
replicate this problem reliably, be sure to comment there.
All I
o anyone in Europe, whose clocks changed this weekend, to check
your ArchivesSpace system. If everything but the home page isn't working, try
the fix below...
Andrew.
On 12/03/2023 19:57, Blake Carver wrote:
It's that time of year again! If ArchivesSpace isn't worki
Hi Heidi
I can't comment on the license issues or legal issues. I'll just say I have
heard of other places, large and small, pulling Oracle Java out of everything
they can, just in case.
ON LINUX OpenJDK works just fine, my guess would be most places use that.
That's what we use.
I don't know
Since I have a Linux box here I gave up pretty quick, but I couldn't get it to
run on my M1 either.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Joshua
D. Shaw
Sent: Thursday, March 23, 2023 10:33 AM
To: Archivesspace Users Group
Could be the indexer, could also be that ID is in the deleted_records table so
it gets deleted from the index.
Check that table and see what's in there.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Joshua
D. Shaw
Sent: Thursday, M
> Does anybody know of any issues with running two versions of ASpace on the
> same system, one with built in Solr and another with external Solr.
Other than the ports, I think that should be fine?
> Also, the introductory Lyrasis video at
> https://www.youtube.com/watch?v=1KbD0M_XfqI, shows
Could be an indexer issue.
Check the logs for ERROR or FATAL, there should be something there.
It might also help to reset the loglevels to debug
AppConfig[:backend_log_level] = "debug"
AppConfig[:frontend_log_level] = "debug"
AppConfig[:indexer_log_level] = "debug"
AppConfig[:pui_log_level]
Still sounds like the indexer is failing or caught in a fail loop and never
gets past a bad record.
Check the logs for ERROR or FATAL
It might also help to reset the loglevels to debug
AppConfig[:backend_log_level] = "debug"
AppConfig[:frontend_log_level] = "debug"
AppConfig[:indexer_log_level]
archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Blake
Carver
Sent: 28 March 2022 16:00
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2
This email was sent to you by someone outside the University.
You should only click on links
Maybe stick a date in a user defined field, call that "Publish After" and then
run a report on that once a quarter and look for those dates?
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of
McLaughlin, Brianna Jean
Sent: Tuesday, Marc
quite large (10s of thousands of AOs), so maybe that's part of the issue.
I haven't checked to see if the PUI indexer is gathering that much more data
(and traversing the tree more times - maybe?) than it was in 3.1.1, but that's
on my 'to check' list.
Joshua
That's... interesting.
That RAM allocation seems fine. That Solr timeout is way higher than I would
think is needed.
Maybe set the loglevel to debug and see if it spits out something more useful?
Maybe you'll be able to see what it's up to during that long time. I like
your theory on that.
It'll be best to stick to 8.x for now. Last I checked ArchivesSpace didn't
like 9.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Jerry
Boggio
Sent: Thursday, January 26, 2023 2:06 PM
To: archivesspace_users_group@lyralists.lyrasis
Agreeing with Andrew on that permissions error, might be important, might not
be.
For that path though, I think you want it more like
/public/locales/en.yml
I think you have an extra /public/ in there?
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
Best to stick with what's in the official ArchivesSpace config.rb
https://github.com/archivesspace/archivesspace/blob/master/common/config/config-defaults.rb#L389-L434
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Matthew
Lawson
S
even though we have that filled out. I
can’t figure out why that wouldn’t display. -Andrew
From: Blake Carver<mailto:blake.car...@lyrasis.org>
Sent: Thursday, December 15, 2022 11:48 AM
To: Archivesspace Users
Group<mailto:archivesspace_users_group@lyralists.lyrasi
ies/2/
Kirill.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
On Behalf Of Blake
Carver
Sent: Thursday, December 15, 2022 12:47 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Archivematica DIP upload into
Archivesspace problem
Are you sure the reposito
Are you sure the 3.3.1 has finished up indexing 100% of everything? Could be
it's stuck. Check the logs for ERROR or FATAL
It may also be the search just returns things a bit differently in 3 vs 2, but
I'd make sure there's not an indexing issue first.
Can you get the record to show up in results
I think the docs explain it here?
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/103209762/Public+Interface+Documentation+for+staff#PublicInterfaceDocumentation(forstaff)-CitationactionbuttonandthePreferredCitationnote
From: archivesspace_users_group-bo
Where do you have your locales en.yml file for that?
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Erhan
Tuskan
Sent: Thursday, December 15, 2022 10:38 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace
Are you sure the repository ID is 2? Could it be 3?
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Kirill
Batyuk
Sent: Thursday, December 15, 2022 12:24 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace
Try using the latest tag version on that plugin.
https://github.com/lyrasis/aspace-oauth/tags
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of David P.
Steelman
Sent: Tuesday, December 6, 2022 2:02 PM
To: Archivesspace Users Group
S
We do have a note in the tech docs:
ArchivesSpace “officially” supports the version indicated in solrconfig.xml.
That refers to a version that is used for development and tested between
release cycles.
https://github.com/archivesspace/archivesspace/blob/master/solr/solrconfig.xml#L7
Currently
>> We recently tried a hard re-index and discovered that for the PUI, subjects
>> linked only to digital objects were not re-indexed and dropped from the PUI.
>> Is this expected behavior?
Maybe related to what's in your deleted_records table? How many rows in that
table?
>> Related, is
> ASPACE_JAVA_XMX="-Xmx16144m"
If the site needs 16 gigs of RAM to keep going, something is probably wrong.
> AppConfig[:indexer_records_per_thread] = 25
> AppConfig[:indexer_thread_count] = 7
> AppConfig[:indexer_solr_timeout_seconds] = 300
Messing around with those indexer settings is general
translation missing:
validation_errors.protected_read-only_list_#/instances/0/instance_type._invalid_value__digital_object_.__must_be_one_of__box__volume__oversize_folder__reel__audio__disc__film__video__computer_disk__box-folder__reel-frame__side__sc__package__wcftr__roll__map_case__drawer__aa__a
r any help,
Wendy
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Blake
Carver
Sent: Wednesday, June 8, 2022 1:25 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of
developme
> Indicates a deprecation in the JDBC call, AND YET it successfully checks the
> tables and confirms they are set to UTF-8.
> I am using the latest MySQL Connector jar for this:
> mysql-connector-java-8.0.29.jar for Ubuntu
Yep, that's fine I think.
> It's just so weird to me that the JDBC con
That plugin hasn't been updated in a lonng time. Assuming it still even
works, it looks like you can add that missing value to your locales:
https://github.com/archivesspace/archivesspace/blob/5e1ca66f1f04f142f2695024efb7200825046325/common/locales/LOCALES_README.md
__
I've seen 2 things cause this
1. Just do a reindex, seems like sometime it just needs a kick in the
indexes for some reason.
2. The server hosting that image is blocking access so ArchivesSpace can't
grab that file. It's usually this.
From: archivesspace_u
g[:backend_log_level] = "debug"
64 AppConfig[:pui_log] = "default"
65 AppConfig[:pui_log_level] = "debug"
67 AppConfig[:indexer_log] = "default"
68 AppConfig[:indexer_log_level] = "debug"
________
From: archivesspace_users_gro
s.org
on behalf of Blake
Carver
Sent: Wednesday, June 1, 2022 5:02 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Requesting Clarification of
development vs production mode
https://archivesspace.github.io/tech-docs/development/dev.html
That explains
uld track this
down. Or maybe it is a red herring and there is something else going on in
there.
Tom
On Wed, Jun 1, 2022 at 5:10 PM Blake Carver
mailto:blake.car...@lyrasis.org>> wrote:
You might try this branch, there was a weird issue with that for a while, I
think maybe this fixe
You might try this branch, there was a weird issue with that for a while, I
think maybe this fixed that?
https://github.com/lyrasis/aspace-oauth/tree/unlock-address
This was the only change
https://github.com/lyrasis/aspace-oauth/pull/23/files
That was a while back, so things may have changed si
https://archivesspace.github.io/tech-docs/development/dev.html
That explains the development mode.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Duckett,
Brian (NIH/NLM) [C]
Sent: Wednesday, June 1, 2022 4:45 PM
To: archivesspace_us
The techdocs do have nginx settings here:
https://archivesspace.github.io/tech-docs/provisioning/https.html#Nginx
If something's not clear, let me know.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Sarah
Frieldsmith
Sent: Friday, M
etimes a
lot, other times fewer. But in the indexer.log file, I only see INFO
statements, no DEBUG.
But your suggestion above that the line is like "indexed ..." got me searching
other logs and I found a couple of lines like this in my backend log:
D, [2022-05-16T14:31:45.734159 #5273
That looks pretty bad, not sure what it means, but I would start over, maybe
something is missing or there's a bad plugin or some other mysterious thing has
failed.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Corinne
Chatnik
Sen
0898 archival_object records in repository UNDA
immediately followed by an error, how do we determine which record that is in
ArchivesSpace? We are not sure how to find the record which is indicated in
the log.
Thanks again,
Tom
On Mon, May 16, 2022 at 5:19 PM Blake Carver
mailto:blake.c
That sounds like it's not running at all. Check the archivesspace.out file in
the logs directory for errors.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Heidi R.
Pettitt
Sent: Friday, May 13, 2022 6:00 PM
To: Archivesspace User
ll in DEBUG mode in the backend log but it is not clear how to figure
out which record(s) are being flagged. What am I looking for?
Thanks,
Tom
On Thu, May 12, 2022 at 8:59 AM Blake Carver
mailto:blake.car...@lyrasis.org>> wrote:
> Could it be that we added a big record which is now havi
That sounds like it's not running at all. Check the archivesspace.out file in
the logs directory for errors.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Heidi R.
Pettitt
Sent: Thursday, May 12, 2022 11:02 AM
To: Archivesspace Use
timeout.
You might not notice you've got enough records to cause this until you do a
full re-index, or someone edits something linked to most or all records (e.g. a
repository, or a very widely-used subject), triggering the re-indexing of most
of the system's records.
these ideas after hours today, so if you can confirm that
I've got the right idea, that would help.
Tom
On Tue, May 10, 2022 at 2:17 PM Blake Carver
mailto:blake.car...@lyrasis.org>> wrote:
> Is this possible?
Short answer, Yes, it's possible your indexer is starting over.
L
> Is this possible?
Short answer, Yes, it's possible your indexer is starting over.
Long answer. This can be tricky to figure out. Something is wrong, the indexer
never wants to do that. Sometimes "something" "bad" gets into ArchivesSpace and
the indexer will just crash and start over. The prob
It's only agents and subjects? Resources look fine?
I'd really expect that error to put a FATAL or ERROR in the logs, especially on
debug. If not, did you bring over anything from the /data/ directory from 2.6
to 3.2?
If so, get rid of that stuff.
From: archivess
Joshua Shaw reported ArchivesSpace being bit by a bug in 8.11.0 back in
November.
https://www.mail-archive.com/users@solr.apache.org/msg02012.html
That was fixed in 8.11.1
I think, so far, 8.11.0 is the only version to avoid.
From: archivesspace_users_group-boun.
http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2022-March/009092.html
You can probably just:
UPDATE user set user_mtime = NOW(), system_mtime=NOW();
Though might need to:
-- AO
update archival_object set create_time = '2022-03-13 06:00:00', system_mtime =
'2022-03-13 06:00:00'
Hey Dan
Do you get access to the DB there? If so, it would be pretty easy to just do a
direct MySQL query for that and build the URLS from the IDs.
I did look at the reports on test:
https://test.archivesspace.org/staff/custom_report_templates/new
And I don't see a way to do exactly what you w
t: Re: [Archivesspace_Users_Group] Rights statements not showing up in
the public interface
There is this issue:
https://archivesspace.atlassian.net/browse/ANW-1055
But that is only about fields in the "Finding Aid Data" section, not rights
statements.
Andrew.
On 21/03/2022 18:52, Blake
I think that might be one of the fields that isn't on the PUI?
I know there's a JIRA in there somewhere that covers this. Maybe not Rights
Statements in particular, but various fileds that don't show up on the PUI.
JIRA hates me, and I can't seem to find it. Maybe someone else is better
friends w
igate this? Does everyone just wait until after
the DST change to see if things broke? Or are they ways to proactively
mitigate this?
Also, can I expect the same thing when we "Fall back"? Or is this somehow just
a Spring issue?
Thanks,
Tom
On Sun, Mar 13, 2022 at 2:34 PM Blake Ca
It should be fine to run the latest version (3.2) on MySQL 8. I think most
likely anything above version 3 should be ok.
There were some reports issues on some older versions of ArchivesSpace
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf
There's a plugin here:
https://github.com/lyrasis/aspace-oauth
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Peter
Heiner
Sent: Monday, March 14, 2022 11:40 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group]
Yet another reason to hate Daylight Savings Time...
Some of you may notice troubles this morning. There's a weird little bug that
happens when the clocks change. It doesn't hit ALL sites, but we had some
hosted sites hit this year for the first time, so I thought I'd put this at the
top O' the l
This was a bit of a error "Turducken"... it's an error bug hiding the error.
It was in older versions (maybe < 2.8?) and was fixed in a newer version (2.8.1
maybe?).
If I'm remembering correctly an error is raised and that 'pretty_inspect' barfs
on it and rather than showing the error, it just sh
That is a new bug, just found the other day.
It would be good if you could add that to the issue here:
https://archivesspace.atlassian.net/browse/ANW-1435
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Nic
Stanton-Roark
Sent: Tuesday
Looks like this is a bug in 3.1, there's a JIRA here now
https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1431
From: Blake Carver
Sent: Thursday, September 30, 2021 4:03 PM
To: Archivesspace Users Group
Subjec
Double check and make sure you have the right version, maybe somehow it has the
wrong one in place.
https://github.com/archivesspace-plugins/lcnaf
For ArchivesSpace versions 2.8.1 and earlier, use the 1.0.0 tag. For
ArchivesSpace version 3.0.0 , use the 2.0.0 tag.
I've heard of places getting
Might just be missing from the locales:
https://github.com/archivesspace/archivesspace/blob/master/public/config/locales/en.yml#L178-L179
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Nic
Stanton-Roark
Sent: Thursday, September 30, 2
Check your Apache logs for errors. Sounds like maybe it's some kind of issue
there.
Also, check the browser devtools counsel for errors, they are likely to show up
there too.
Also check the archivesspace.out log for errors, might be something in there.
From: archi
Just for the record, the problem was indeed disc space.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Peter
Heiner
Sent: Friday, September 24, 2021 7:13 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] error
Depending on your version it'll be a slightly different issue, but something
somewhere in there has an ampersand that is causing the PDF generator to barf.
There's one report here:
https://archivesspace.atlassian.net/browse/ANW-1340
I've seen these most often in notes and usually on something lik
2:in `call'
==
Scott Renton
Digital Library Development & Systems
Floor F East
Argyle House
515219
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Blake
Carver
Sent: 07 September 2021 16:23
To: Archivesspace Users
or F East
Argyle House
515219
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Blake
Carver
Sent: 07 September 2021 15:37
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Connection/l
What's happening in the logs just before that first "Unhanded exception" error?
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of RENTON
Scott
Sent: Monday, September 6, 2021 9:29 AM
To: archivesspace_users_group@lyralists.lyrasis.org
You'll probably find some ERROR or FATAL lines that are NOT RoutingError.
Usually RoutingError is just a 404.
If it's crashing you'll likely see OutOfMemoryError from java as well.
If you're not seeing those, reset the loglevel to debug and that should help
log some better errors.
Sometimes it do
> When I examine the HTML created by AS, there are issues when an input value
> contains a single apostrophe.
What value has the single apostrophe?
> The print button does not function either (see screenshot).
What does that error look like in the ArchivesSpace logs?
_
Can you also check your proxy for errors?
Was there any ERROR or FATAL lines in the ArchivesSpace logs?
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Schanz,
Megan
Sent: Tuesday, August 24, 2021 1:04 PM
To: Archivesspace Users Group
It's hard to know for sure what's going on with this.
You were running 1.3 with MySQL and everything was fine?
They did the upgrade, you login and see everything is gone and it's running on
Apache Derby... EEK!
You let them know, they connect it to MySQL again and now it's in this state.
So they p
Is there anything in the logs that has ERROR or FATAL in it?
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Bennett
Poulin
Sent: Tuesday, July 13, 2021 3:50 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Troubl
I put in a JIRA here
https://archivesspace.atlassian.net/browse/ANW-1338
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Blake
Carver
Sent: Friday, July 9, 2021 11:22 AM
To: Archivesspace Users Group
Subject: Re
Collections and Archives
Tufts University
adrienne.pru...@tufts.edu<https://exchange.tufts.edu/owa/redir.aspx?C=t5B1d8GNpPJJzaAAvUfcGAPuBinqgxXyoK8_O0ggQHCOYyG6Tc_XCA..&URL=mailto%3aadrienne.pruitt%40tufts.edu>
|617-627-0957
____
From: archivesspace_users_group-boun...@l
Can you point to an example?
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Pruitt,
Adrienne
Sent: Tuesday, July 6, 2021 2:05 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Captions for digital objects in the P
There should be an error in the logs, that should help explain what's happening.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Nic
Stanton-Roark
Sent: Tuesday, June 29, 2021 11:54 AM
To: Archivesspace Users Group
Subject: [Archivess
"Open quote is expected for attribute "href" associated with an element type
"a"."
There's some bad HTML in there. I usually export it to EAD and then just search
for "href" and look for the bad tags, hopefully it's not a record with 1000
hrefs in there
From:
archivesspace.out should for sure be "ASCII text, with very long lines"
If it's something else, there's something wrong somewhere.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of
Dyson-Smith, Bridger
Sent: Monday, June 14, 2021 3:00 PM
r to be sure, is there a way to migrate data
manually to ensure that schema matches and all the data gets migrated?
On Fri, May 14, 2021 at 10:50 AM Blake Carver
mailto:blake.car...@lyrasis.org>> wrote:
I wouldn't recommend changing the schema_info, this can put you in a really bad
pla
You can probably just override that here:
https://github.com/archivesspace/archivesspace/blob/82c4603fe22bf0fd06043974478d4caf26e1c646/frontend/app/views/welcome/index.html.erb
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Ben
Fish
I wouldn't recommend changing the schema_info, this can put you in a really bad
place.
Your error:
""The schema info version should be 120 for ArchivesSpace version v2.6.0.
However, your schema info version is set at 122"
Every release of ArchivesSpace has a schema number . All recent release
What's the JAVA version on there?
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Cory
Nimer
Sent: Friday, April 23, 2021 12:42 PM
To: Christine Di Bella ; Archivesspace Users
Group (archivesspace_users_group@lyralists.lyrasis.org)
Sometimes just restarting ArchivesSpace can make that go away. If that doesn't
do the trick, have a look at the logs, look for ERROR or FATAL.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Catie
Heitz
Sent: Wednesday, April 7, 2021
//digitalarchives.library.newschool.edu/> |
New School Histories<http://newschoolhistories.org/> |
@tnsarchives<https://twitter.com/tnsarchives>
On Wed, Mar 31, 2021 at 2:33 PM Blake Carver
mailto:blake.car...@lyrasis.org>> wrote:
There are others running on
There are others running on 8, so far the only trouble seems to be reports.
Here's a JIRA
https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1200
You're seeing it fail on two reports?
From: archivesspace_users_group-boun...@lyralists.lyr
> Blake, any insight?
Nope, it does look like a bug to me, but I'm not sure on that. I'll look into
it, and get a JIRA in if that's the case.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Anna
Robinson-Sweet
Sent: Wednesday, March
I did some experimenting this weekend, messing around with indexer speeds, and
found I could get it to succeed with the right indexer settings. I think the
answer is going to be "it depends" and you'll need to experiment with what
works on your set up with your data. I started with the defaults,
ly frustrating to have to start over on the indexing each time. It
seems that there should be some way to document progress along the way so that
the indexing can pick up where it left off. Is that something that might also
be looked at?
Thanks all. Appreciate your help.
Tom
On Tue, Mar
> I've now left my PUI indexing threads and count at the default (which I
> believe is 1 thread and 25 records/thread).
Try dropping both indexer_records_per_thread and indexer_thread_count for both
PUI and Staff indexers. Maybe in half or so. Sometimes with larger records it
just needs to be s
https://gist.github.com/Blake-/d493da28be5554a49a3a3835bbd98f05
You'll want to find the date more like '2021-03-14 02:00%' or would it be
03-13? Whatever the date was this year.
Find any date with a time between 2-3am and just change it to any real hour.
ArchivesSpace did "something" (probably re
There is a JIRA here about providing better support for right-to-left (RTL)
scripts, ideally bi-directional text
https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1144
And another about Hebrew characters printed left-to-right in staff-side PDFs
https://archivesspace.at
Those MySQL errors look like the ones already reported and are probably not
causing any problems.
https://archivesspace.atlassian.net/browse/ANW-811?atlOrigin=eyJpIjoiMWJlMDQ4MzJlNjNiNDM0MWFlYzlhNDE5OGQ3NzIzYTYiLCJwIjoiaiJ9
Turn the mysql error logging thing off and set the other loglevel errors
Are there any errors in your logs? Look for ERROR and/or FATAL
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Mark
Cyzyk
Sent: Monday, March 1, 2021 5:18 PM
To: Rachel Aileen Searcy ; Archivesspace Users Group
Subject: Re: [Archives
For this one I'd do a full reindex.
Shut down ArchivesSpace
Delete everything in /data/
Yes, every single thing in the /data/ directory, but not the directory, you
need it, just empty.
Start ArchivesSpace
It'll take a while to get all indexed.
From: archivesspace_u
Yep, that's it. ArchivesSpace is unhappy with 11.
Java 8 only:
https://archivesspace.github.io/tech-docs/administration/getting_started.html
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Philip
Webster
Sent: Monday, January 18, 2021
That part of the log isn't super helpful. I'd guess the real error is above
that someplace.
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Preston
Howell
Sent: Friday, January 8, 2021 2:37 PM
To: Archivesspace Users Group
Subject: [
Blake. Unfortunately that doesn't seem to be our problem. We've tried a
full re-index twice and they both completed without errors. I went into Solr
and queried a sample resource and one of its archival objects; and both
returned completed records.
- Megan
______
1 - 100 of 223 matches
Mail list logo
