[Koha] INTERNAL SYSTEM ERROR

[Tomas Cohen Arazi]

You need to open both logs while reproducing the failure do you can
identify the problem

El sáb., 9 de marzo de 2019 10:03, Shafendi <shaffendi at gmail.com> escribió:

> here is my mysql error log
>
> 2019-03-09 12:00:35 140561744152320 [Note] /usr/sbin/mysqld: Normal
> shutdown
> 2019-03-09 12:00:36 140561744152320 [Note] Event Scheduler: Purging the
> queue. 0 events
> 2019-03-09 12:00:36 140561184954112 [Note] InnoDB: FTS optimize thread
> exiting.
> 2019-03-09 12:00:36 140561744152320 [Note] InnoDB: Starting shutdown...
> 2019-03-09 12:00:36 140561744152320 [Note] InnoDB: Waiting for page_cleaner
> to finish flushing of buffer pool
> 2019-03-09 12:00:38 140561744152320 [Note] InnoDB: Shutdown completed; log
> sequence number 12224433643
> 2019-03-09 12:00:38 140561744152320 [Note] /usr/sbin/mysqld: Shutdown
> complete
>
> 2019-03-09 12:00:39 140048342834560 [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.
>
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB: Using mutexes to ref
> count buffer pool pages
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB: The InnoDB memory heap
> is
> disabled
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB: Mutexes and rw_locks use
> GCC atomic builtins
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB: GCC builtin
> __atomic_thread_fence() is used for memory barrier
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB: Compressed tables use
> zlib 1.2.8
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB: Using Linux native AIO
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB: Using generic crc32
> instructions
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB: Initializing buffer
> pool,
> size = 128.0M
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB: Completed initialization
> of buffer pool
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB: Highest supported file
> format is Barracuda.
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB: 128 rollback segment(s)
> are active.
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB: Waiting for purge to
> start
> 2019-03-09 12:00:39 140048342834560 [Note] InnoDB:  Percona XtraDB
> (http://www.percona.com) 5.6.41-84.1 started; log sequence number
> 12224433643
> 2019-03-09 12:00:40 140047420487424 [Note] InnoDB: Dumping buffer pool(s)
> not yet started
> 2019-03-09 12:00:40 140048342834560 [Note] Plugin 'FEEDBACK' is disabled.
> 2019-03-09 12:00:40 140048342834560 [Note] Server socket created on IP:
> '0.0.0.0'.
> 2019-03-09 12:00:40 140048342834560 [Note] /usr/sbin/mysqld: ready for
> connections.
> Version: '10.1.37-MariaDB-0+deb9u1'  socket: '/var/run/mysqld/mysqld.sock'
> port: 3306  Debian 9.6
> 2019-03-09 20:52:15 140048341997312 [Warning] IP address '10.116.12.207'
> could not be resolved: Name or service not known
>
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>