Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

Database screwed up after connnection to osticket !

I am having some difficulties with osticket,
During my first connection osTicket "admin panel" I see my tikets in my database. when I change tab "open"  "overdue" "closed tickets", my database is modified.
And it is written after:There are no tickets here. (Leave a little early today).
And in my database is screwed.
Can you help me


  • We would love to try to help you, but you have not provided us with the information we would need to be able to do so.  So please help us to help you by reading and following this thread: Please read before requesting assistance.  Thank you.
  • Im sorry !
    I have a database that used osTicket 1.7.0. So I installed the same version.
    Php5, Mysql5, Apache2.4.6, Ubuntu server 13.10 64bits.

    MYSQL ERROR LOG--------------------------------------------------------------
    Version: '5.5.35-0ubuntu0.13.10.2'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
    140403  9:41:23 [Note] /usr/sbin/mysqld: Normal shutdown

    140403  9:41:23 [Note] Event Scheduler: Purging the queue. 0 events
    140403  9:41:23  InnoDB: Starting shutdown...
    140403  9:41:24  InnoDB: Shutdown completed; log sequence number 2990806
    140403  9:41:24 [Note] /usr/sbin/mysqld: Shutdown complete

    140403  9:41:50 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
    140403  9:41:50 [Note] Plugin 'FEDERATED' is disabled.
    140403  9:41:50 InnoDB: The InnoDB memory heap is disabled
    140403  9:41:50 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    140403  9:41:50 InnoDB: Compressed tables use zlib 1.2.8
    140403  9:41:50 InnoDB: Using Linux native AIO
    140403  9:41:50 InnoDB: Initializing buffer pool, size = 128.0M
    140403  9:41:50 InnoDB: Completed initialization of buffer pool
    140403  9:41:50 InnoDB: highest supported file format is Barracuda.
    140403  9:41:50  InnoDB: Waiting for the background threads to start
    140403  9:41:51 InnoDB: 5.5.35 started; log sequence number 2990806
    140403  9:41:51 [Note] Server hostname (bind-address): ''; port: 3306
    140403  9:41:51 [Note]   - '' resolves to '';
    140403  9:41:51 [Note] Server socket created on IP: ''.
    140403  9:41:51 [Note] Event Scheduler: Loaded 0 events
    140403  9:41:51 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.5.35-0ubuntu0.13.10.2'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
    140403  9:43:48 [Warning] Warning: Optimize table got errno 1 on osticket.ost_ticket_lock, retrying
    140403  9:43:54 [ERROR] /usr/sbin/mysqld: Table './osticket/ost_ticket_lock' is marked as crashed and last (automatic?) repair failed
    Ty, 64bits.
  • According to your MySQL logs "Table './osticket/ost_ticket_lock' is marked as crashed and last (automatic?) repair failed" You should probably restore from back up.
  • Yes, i have already tried !
    I took the database on the old server that is running now in the company. The database is not damaging. 
    And each time I restore from a back up and I connect to osTicket, the database is destroyed.

    Donc la base de données est propre ? non ?
    Thx for help.
  • I've moved the database countless times, and migrated and upgraded test installations hundreds of times... and I have NEVER seen what you are describing. Have you modified your osTicket installation?  How sure are you that you were actually running 1.7.0?  Did you get it from
  • I have download osTicket here:
    This is the only place I found osTicket 1.7.0, the same version on my old server.
    1.7.0  is not available on (too old?)
    I don t have modified my osticket installation. 

Sign In or Register to comment.