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

I can't install V 1.10 error 500

It really is frustrating this version 1.10, I currently have an earlier version and never had problems installing, now I did everything as always and I still give 500 error. I asked my hosting to open all permissions and nothing at all. It is a disaster I can not install, to see if it was my hosting, I enabled xampp on my pc and also can not install and it is not the version of php nor mysql. Please check it out because it is a disaster.

Comments

  • I appreciate you opening this, thank you for that.

    Please do me a favor and read the guidelines for posting so you can provide some more details about your environment.

    Posting Guidelines

  • This doesn't appear to be a suggestion or feedback. Moving to Installation and Setup Help

  • 500 is a generic internal webserver server error.  It actually tells us nothing.
    No PHP version.
    No webserver and vesion
    No mySQL version.
    No web server/php/mysql error logs included.

  • PHP: 5.6.23
    Server:Apache/1.3.41
    mySQL:5.5
    I don't know where to find logs because I have a hosting. They say they service is ok and other programs runs

  • En xampp lor error:
    2017-04-06 10:45:57 9a4 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
    2017-04-06 10:45:57 2468 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

    2017-04-06 10:45:57 2468 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    2017-04-06 10:45:57 2468 [Note] InnoDB: The InnoDB memory heap is disabled
    2017-04-06 10:45:57 2468 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
    2017-04-06 10:45:57 2468 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
    2017-04-06 10:45:57 2468 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2017-04-06 10:45:57 2468 [Note] InnoDB: Using generic crc32 instructions
    2017-04-06 10:45:57 2468 [Note] InnoDB: Initializing buffer pool, size = 16.0M
    2017-04-06 10:45:57 2468 [Note] InnoDB: Completed initialization of buffer pool
    2017-04-06 10:45:57 2468 [Note] InnoDB: Highest supported file format is Barracuda.
    2017-04-06 10:45:57 2468 [Note] InnoDB: The log sequence numbers 1835037 and 1835037 in ibdata files do not match the log sequence number 23190682 in the ib_logfiles!
    2017-04-06 10:45:57 2468 [Note] InnoDB: Database was not shutdown normally!
    2017-04-06 10:45:57 2468 [Note] InnoDB: Starting crash recovery.
    2017-04-06 10:45:57 2468 [Note] InnoDB: Reading tablespace information from the .ibd files...
    2017-04-06 10:46:06 2468 [Note] InnoDB: Restoring possible half-written data pages 
    2017-04-06 10:46:06 2468 [Note] InnoDB: from the doublewrite buffer...
    2017-04-06 10:46:07 2468 [Note] InnoDB: 128 rollback segment(s) are active.
    2017-04-06 10:46:07 2468 [Note] InnoDB: Waiting for purge to start
    2017-04-06 10:46:08 2468 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.32-79.0 started; log sequence number 23190682
    2017-04-06 10:46:08 16192 [Note] InnoDB: Dumping buffer pool(s) not yet started
    2017-04-06 10:46:08 2468 [Note] Plugin 'FEEDBACK' is disabled.
    2017-04-06 10:46:08 2468 [Note] Server socket created on IP: '::'.
    2017-04-06 10:46:09 2468 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
    Version: '10.1.19-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution

  • Please provide your webserver log for the 500 error.
Sign In or Register to comment.