Jump to content

Search the Community

Showing results for tags 'crashed'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Hi all One of my sites (running PW since 2014, currently v. 2.5.3) had problems with crashed tables. Last week the body field and and image field crashed – noteworthy the latter crashed in a separate DB in my working copy. A couple hours ago another field table crashed (production system again). Funnily, today's table fixed itself. The site has nearly 20,000 pages, about 100 users a day and is installed on a managed server. Unless the logs in sites/assets/logs/errors.txt I have no idea how to research the problem. The hosting company says 'system is fine' and 'mostly it's cased by the CMS'. I have seen others here having that problem, but unless fixing it immediately with repair table there wasn't much info to see what is wrong. Perhaps you guys have some tips how to debug that kind of problem. I even don't know if it is possible to fix this on my own … if it's a problem with the filesystem for example. Any ideas? My code or system failure?
  2. Good morning. I'm having a problem with my big PW site. It stopped responding less than an hour ago (except for the 500 Internal Error message). Here is what the error log says: 2014-03-17 13:07:50 ? https://wwwudev.cac.washington.edu/?/ Error: Exception: SQLSTATE[HY000]: General error: 1194 Table 'modules' is marked as crashed and should be repaired (in /nfs/bronfs/uwfs/info/wwwudev/world/uaa/advising/wire/core/Modules.php line 251) 2014-03-17 13:13:30 ? https://wwwudev.cac.washington.edu/?/ Error: Exception: SQLSTATE[HY000]: General error: 1194 Table 'fields' is marked as crashed and should be repaired (in /nfs/bronfs/uwfs/info/wwwudev/world/uaa/advising/wire/core/WireSaveableItems.php line 141) 2014-03-17 13:19:02 ? https://wwwudev.cac.washington.edu/?/ Error: Call to a member function has() on a non-object (line 36 of /nfs/bronfs/uwfs/info/wwwudev/world/uaa/advising/wire/core/Users.php) I repaired the modules and fields table but now I'm getting the last error and I don't know what is happening. The site is on a shared server; I checked to make sure I have lots of disk space. I don't know what could have changed this morning; my next step is to ask our network technicians.
×
×
  • Create New...