Opened 6 years ago
Closed 4 years ago
#960 closed defect (fixed)
Syndie errors after non-graceful shutdown
| Reported by: | guest | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | apps/syndie | Version: | |
| Keywords: | syndie database corruption unclean shutdown startup | Cc: | |
| Parent Tickets: |
Description
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)
Subtickets
Attachments (2)
Change History (4)
Changed 6 years ago by guest
comment:5 Changed 5 years ago by killyourtv
- Version 0.9.6 deleted
This might be solved (or at least improved) with the upcoming release of 1.105b in which HSQLDB 2 is used.
comment:6 Changed 4 years ago by zzz
- Resolution set to fixed
- Status changed from new to closed
Yeah I'm going to optimistically declare this fixed by 1.105b. Without any actual evidence.
logfile from an oom on startup