files are "empty"; cannot republish

[StaceyS]

When we try to republish books from scribe3.capitolhill we get this error message:
Error triggered: simplexml_load_file() [function.simplexml-load-file]: /home/scribe/.scriblio/scribe.xml:1: parser error : Document is empty (code 2)
file: /var/www/RePublisher/RePublisher-scribe.php
line: 827

Terminating with return value -1!

But all the files seem to be intact.

[Jude Coelho (judec)]

You'll see that the file it's referring to isn't one of the book files, but the Scribe configuration file: /home/scribe/.scriblio/scribe.xml

This file is indeed empty. How did it come to be this way? One theory is that because the disk is so full, it might have been edited at a time when there was absolutely no more room on the disk and it wrote an empty file.

In any case, we have two problems here:

1. The full disks.
2. The empty file.

The empty file can easily be recreated, but the full disks are going to keep causing problems. Can we somehow get all these lingering books onto a temporary storage until they're able to be uploaded?

As for the file, you can copy one from one of the other scribes and it should solve the issue (just change the scribe # inside the file).

[Jude Coelho (judec)]

https://bugs.launchpad.net/ia-techsupport/+bug/803425 for the full disks bug.

[Jude Coelho (judec)]

Was this ever fixed?

[StaceyS (stacey-archive)]

we deleted about 100 books that were lingering on the scribes and that seemed to solve the problem.

[StaceyS (stacey-archive)]

I am now having this issue at scribe10.capitolhill; the disk is full, the toaster won't boot enough for me to get to the desktop to run a terminal window and root around the files, and all the books at scribe10 have the same error as above. Please help!

[Hank Bromley (hank-archive)]

I have emptied root's trash on scribe10 - it was consuming 38 GB. That still leaves 180 GB in use, or 84% of total capacity. The bulk of that is in two directories: republish (32 books, total of 112 GB) and foldout (4 books, total of 21 GB).

Before I emptied it, root's trash contained mainly book directories and checkin lock files, dated from 2010-08-05 through 2011-08-31.

That leaves the mystery of why scribes in capitolhill frequently fill up root's trash, and - so far as I know - none anywhere else ever have. Is someone routinely doing work while in superuser mode?