You haven't changed anything in your models right? Just do a fake
migration. Or simply turn migrations off since you don't need them in
production.
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
-
Err wait a minute the table has actually been dropped?
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are
Yeah... everything was fine one moment then it all just stopped... when I
looked at the file it was 0kb. I have no idea what happened... cannot
access database admin... site still runs except for the functions that
access that table...
On Saturday, 6 September 2014 02:22:31 UTC+10, Greg
I wasn't working on the site at the time... I was notified by some of the
employees... yes it looks like the table has been dropped... I cannot for
the life of me work out how that could have happened though.
On Saturday, 6 September 2014 02:41:30 UTC+10, Leonel Câmara wrote:
Err wait a
It can happen if you run out of disk space. You should check it.
Btw, maybe just .table got corrupted... Make sure to backup everything, and
then do a fake migrate.
Marin
On Fri, Sep 5, 2014 at 6:51 PM, Greg Vaughan greg.s.vaug...@gmail.com
wrote:
I wasn't working on the site at the time...
Tried fake_migrate... production site on pythonanywhere so disk space
wasn't the issue... scratching my head with this...
On Saturday, 6 September 2014 02:55:23 UTC+10, Marin Pranjić wrote:
It can happen if you run out of disk space. You should check it.
Btw, maybe just .table got
Version
Enter code here...
web2py™ Version 2.8.2-stable+timestamp.2013.11.28.13.54.07 Python Python
2.7.5+: /usr/local/bin/uwsgi (prefix: /usr) Traceback
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
Traceback (most recent call last):
File /home/gsv/enertek/web2py/gluon/restricted.py,
Fixed Thankfully...
1) Renamed the table in the model
2) Uploaded the backup csv file to the renamed table... was about a week
out of date
3) Manually deleted the corrupt file from the database
4) Created a new table with the old table name without fields and set
migrate and fake_migrate to
This error:
RuntimeError: File /home/gsv/enertek/web2py/applications/welcome/databases/
c8b669d15150d7109e5f7ab36744a5b7_sales_leads.table appears corrupted
As Marin says, makes it seem it's just the table file that got corrupted,
so you didn't lose anything. Just erase it and do a fake
9 matches
Mail list logo
