EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #04696
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: EPrints 3.3.13 Crash
- To: "'eprints-tech@ecs.soton.ac.uk'" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Re: EPrints 3.3.13 Crash
- From: John Salter <J.Salter@leeds.ac.uk>
- Date: Wed, 16 Sep 2015 14:20:35 +0000
Hi Greg, First thing I’d do is (get your sysadmin to) check your database server disk space. We had a build-up of old binlogs which filled our database server and made everything fall over. This caused mysqlcheck to not work too. I think this was useful in that process:
http://www.thegeekstuff.com/2011/12/mysqlcheck/ In terms of anything you have access to – I’m not sure - sorry! Cheers, John From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Greg Whitney Hello, First time for everything. Our EPrints 3.3.13 production instance crashed with the following error messages below: Version: '5.5.44-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 150915 14:06:40 [ERROR] mysqld: Table './Ecole/eprint' is marked as crashed and should be repaired
Our sysadmin tried to to a mysqlcheck on these tables and it failed. Is there any program in the /bin directory which I can run to rebuild
or check these tables periodically myself. as I don't have mysql access to EPrints.
Thanks!!
Greg Whitney Polytechnique Montreal Library |
- References:
- [EP-tech] EPrints 3.3.13 Crash
- From: Greg Whitney <greg.whitney@polymtl.ca>
- [EP-tech] EPrints 3.3.13 Crash
- Prev by Date: [EP-tech] EPrints 3.3.13 Crash
- Next by Date: [EP-tech] MARC exporter
- Previous by thread: [EP-tech] EPrints 3.3.13 Crash
- Next by thread: [EP-tech] MARC exporter
- Index(es):