|
From: Dannes W. <da...@ex...> - 2017-04-03 19:41:51
|
Hi Brad, > On 3 Apr 2017, at 14:27 , Brad Clements <bk...@mu...> wrote: > > We've been running eXist 2.2-:develop-15c5a27-20141116 for 2 couple of > years on Ubuntu 14.04 on Java 1.7.0_121 64Bit without problems. > > This weekend I edited conf.xml and adjusted the consistency-check > settings to change when full and incrementals are done. > > I restarted eXist and went home thinking all was well. but now I find > this morning that it's not actually working at all. > > It seems to be putting the database into readonly mode but I cannot find > out why. > But we have plenty of space I remember that we have been using an unreliable API to probe the available diskspace. We changed this since then and the problems have gone. I thought only windows server were affected though. On http://exist-open.markmail.org <http://exist-open.markmail.org/> I can’t find the relevant mail thread though…. > 2017-04-03 08:15:31,253 [eXistThread-35] WARN (TransactionManager.java > [execute]:164) - Failed to create transaction. Error writing to log file. > > I have rebooted the server and it's not coming up with fsck errors, so I > am pretty confused why it's failing to write to disk. > > The java process runs as root, most files are owned by a regular user.. > I don't recall a 'run as' userid setting anywhere. > Only when running via the service wrapper it is possible to set a user-id. I am not yet sure what to suggest to continue…. sorry D. |