Opened 8 years ago

Closed 6 years ago

#960 closed defect (fixed)

Syndie errors after non-graceful shutdown

Reported by: DISABLED Owned by:
Priority: major Milestone:
Component: apps/syndie Version:
Keywords: syndie database corruption unclean shutdown startup Cc:
Parent Tickets: Sensitive: no


When Syndie is shut down non gracefully, due to a crash, computer shutdown/restart, or anything else many odd things happen. Meta-ticket for 'shutdown issues', presumably they all have the same cause, possibly (?) due to the old version of HSQLDB used.

OOM on startup

Archives disappear and have to be re added manually, while posts remain intact

Internal error due to unexpected token (#958)

Syndie also does not seem to check for other instances already running, which almost certainly dosen't help with corruption (#861)


Attachments (2)

log-1.txt (138 bytes) - added by DISABLED 8 years ago.
logfile from an oom on startup
syndie-error.jpg (20.6 KB) - added by DISABLED 8 years ago.
startup error originally from #958

Download all attachments as: .zip

Change History (4)

Changed 8 years ago by DISABLED

Attachment: log-1.txt added

logfile from an oom on startup

Changed 8 years ago by DISABLED

Attachment: syndie-error.jpg added

startup error originally from #958

comment:5 Changed 8 years ago by killyourtv

Version: 0.9.6

This might be solved (or at least improved) with the upcoming release of 1.105b in which HSQLDB 2 is used.

comment:6 Changed 6 years ago by zzz

Resolution: fixed
Status: newclosed

Yeah I'm going to optimistically declare this fixed by 1.105b. Without any actual evidence.

Note: See TracTickets for help on using tickets.