some database tables is marked as crashed every 2 days

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ESPOO
    New Member
    • Nov 2007
    • 13

    some database tables is marked as crashed every 2 days

    Hello !
    My vb works fine since 7 years fine , Since 1 month my vb 3.8.7 table crashed every 2 days.
    Every 2 or 3 days my database is corruption and mysql log , some tables is marked as crashed , then I repaired it and Ok , then after 2 or 3 days do again.
    I think that my server was the problem so I changed to new server and the problem does not finish ,

    So please advice about the reason for that problem ?

    Thanks for all
    Espoo
  • Lynne
    Former vBulletin Support
    • Oct 2004
    • 26255

    #2
    You need to talk to your host about this. There is no reason a table should keep crashing.

    Please don't PM or VM me for support - I only help out in the threads.
    vBulletin Manual & vBulletin 4.0 Code Documentation (API)
    Want help modifying your vbulletin forum? Head on over to vbulletin.org
    If I post CSS and you don't know where it goes, throw it into the additional.css template.

    W3Schools <- awesome site for html/css help

    Comment

    • ESPOO
      New Member
      • Nov 2007
      • 13

      #3
      thank you Lynne,
      My vb is in dedicated server .
      So what is the problem in my dedicated server ?
      And my vB the only thing on the server. There is no other php or mysql scripts in this server .

      Comment

      • Zachery
        Former vBulletin Support
        • Jul 2002
        • 59097

        #4
        Mysql doesn't just crash, regardless of the software that is using it.

        Comment

        • BirdOPrey5
          Senior Member
          • Jul 2008
          • 9613
          • 5.6.3

          #5
          Check things like disk space, make sure it is sufficient. Run tests to check the hard drives and RAM for physical defects. Check your logs to make sure the server isn't getting over-loaded at regular intervals.

          Comment

          • Wayne Luke
            vBulletin Technical Support Lead
            • Aug 2000
            • 73976

            #6
            For disk space, make sure your temporary partition is 3-4 times the size of your largest database table.
            Translations provided by Google.

            Wayne Luke
            The Rabid Badger - a vBulletin Cloud demonstration site.
            vBulletin 5 API

            Comment

            • ESPOO
              New Member
              • Nov 2007
              • 13

              #7
              I run df -h /var/lib/mysql
              result is
              Filesystem Size Used Avail Use% Mounted on
              /dev/md2 1016G 102G 863G 11% /

              so this can I check.

              is there another way to check my temporary partition ?

              For disk space, make sure your temporary partition is 3-4 times the size of your largest database table.
              so how can I check it ?

              Comment

              • Wayne Luke
                vBulletin Technical Support Lead
                • Aug 2000
                • 73976

                #8
                List all drives: fdisk -l

                List all partitions on a drive: fdisk -l /dev/md2
                Translations provided by Google.

                Wayne Luke
                The Rabid Badger - a vBulletin Cloud demonstration site.
                vBulletin 5 API

                Comment

                • ESPOO
                  New Member
                  • Nov 2007
                  • 13

                  #9
                  thank you Wayne Luke

                  fdisk -l

                  WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


                  Disk /dev/sda: 3000.6 GB, 3000592982016 bytes
                  256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
                  Units = sectors of 1 * 512 = 512 bytes
                  Sector size (logical/physical): 512 bytes / 4096 bytes
                  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
                  Disk identifier: 0x00000000

                  Device Boot Start End Blocks Id System
                  /dev/sda1 1 4294967295 2147483647+ ee GPT
                  Partition 1 does not start on physical sector boundary.

                  WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


                  Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
                  256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors
                  Units = sectors of 1 * 512 = 512 bytes
                  Sector size (logical/physical): 512 bytes / 4096 bytes
                  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
                  Disk identifier: 0x00000000

                  Device Boot Start End Blocks Id System
                  /dev/sdb1 1 4294967295 2147483647+ ee GPT
                  Partition 1 does not start on physical sector boundary.

                  Disk /dev/md1: 536 MB, 536858624 bytes
                  2 heads, 4 sectors/track, 131069 cylinders, total 1048552 sectors
                  Units = sectors of 1 * 512 = 512 bytes
                  Sector size (logical/physical): 512 bytes / 4096 bytes
                  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
                  Disk identifier: 0x00000000

                  Disk /dev/md1 doesn't contain a valid partition table

                  Disk /dev/md0: 17.2 GB, 17178746880 bytes
                  2 heads, 4 sectors/track, 4194030 cylinders, total 33552240 sectors
                  Units = sectors of 1 * 512 = 512 bytes
                  Sector size (logical/physical): 512 bytes / 4096 bytes
                  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
                  Disk identifier: 0x00000000

                  Disk /dev/md0 doesn't contain a valid partition table

                  Disk /dev/md3: 1883.4 GB, 1883361311744 bytes
                  2 heads, 4 sectors/track, 459805007 cylinders, total 3678440062 sectors
                  Units = sectors of 1 * 512 = 512 bytes
                  Sector size (logical/physical): 512 bytes / 4096 bytes
                  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
                  Disk identifier: 0x00000000

                  Disk /dev/md3 doesn't contain a valid partition table

                  Disk /dev/md2: 1099.5 GB, 1099510439936 bytes
                  2 heads, 4 sectors/track, 268435166 cylinders, total 2147481328 sectors
                  Units = sectors of 1 * 512 = 512 bytes
                  Sector size (logical/physical): 512 bytes / 4096 bytes
                  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
                  Disk identifier: 0x00000000

                  Disk /dev/md2 doesn't contain a valid partition table


                  fdisk -l /dev/md2

                  Disk /dev/md2: 1099.5 GB, 1099510439936 bytes
                  2 heads, 4 sectors/track, 268435166 cylinders, total 2147481328 sectors
                  Units = sectors of 1 * 512 = 512 bytes
                  Sector size (logical/physical): 512 bytes / 4096 bytes
                  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
                  Disk identifier: 0x00000000

                  Disk /dev/md2 doesn't contain a valid partition table

                  --------------------------------------------------------------------------------------------------------

                  So what are you see ?

                  Comment

                  widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
                  Working...