Opened 7 years ago

Closed 6 years ago

#917 closed defect (fixed)

issue web editor incremental build

Reported by: kjdon Owned by: nobody
Priority: moderate Milestone: 3.09 Release
Component: Greenstone3 Runtime Severity: major
Keywords: Cc:


When using lucene and gdbm, the web editor cannot process the metadata changes. metadata gets saved ok to the archives. The build process cmodifies the lucene indexes online, then tries to modify the gdbm database, but it cannot open it to write to it. Presumably because the server has it open.

With mgpp indexer, we are running -builddir index. It can't do incremental, so removeold is set. Does this then just delete the index and recreate it? what happens to other people using the collection???

Change History (3)

comment:1 by kjdon, 7 years ago

Sample log message:

* creating the info database and processing associated files /Scratch/kjdon/gs3-pei-jones-plus-twso/gs2build/bin/linux/txt2db: Couldn't create/open '/Scratch/kjdon/gs3-pei-jones-plus-twso/web/sites/pei-jones/collect/taonga/index/text/taonga.gdb'

Can't be writer gdbm errno = 10 OS errno = 11

gdbm_open failed: : Resource temporarily unavailable ArchivesInfPlugin: processing /Scratch/kjdon/gs3-pei-jones-plus-twso/web/sites/pei-jones/collect/taonga/archives/archiveinf-doc.gdb GreenstoneXMLPlugin: processing 3Q9_1.dir/doc.xml

Adding reconstructed 3Q3_4 into classify structures Adding reconstructed 3Q2_1a-b into classify structures Adding reconstructed 3Q2_3 into classify structures Adding reconstructed 3Q3_7 into classify structures

/Scratch/kjdon/gs3-pei-jones-plus-twso/gs2build/bin/script/ Error: Broken pipe at /Scratch/kjdon/gs3-pei-jones-plus-twso/gs2build/perllib/ line 43. Error: Failed to run: "/usr/bin/perl" -S -incremental "-incremental" "-builddir" "/Scratch/kjdon/gs3-pei-jones-plus-twso/web/sites/pei-jones/collect/taonga/index" "-site" "pei-jones" "-collectdir" "/Scratch/kjdon/gs3-pei-jones-plus-twso/web/sites/pei-jones/collect" "taonga" got SIGPIPE

comment:2 by kjdon, 7 years ago

jdbm seems to be fine. Problem just with gdbm.

comment:3 by kjdon, 6 years ago

Resolution: fixed
Status: newclosed

This has been fixed by deactivating the collection before modifying the gdbm database, then reactivating.

See ticket #902

Note: See TracTickets for help on using tickets.