Time Nick Message 02:10 kidclamp @later tell cait order of pushing does not indicate how much I like the developers (except when it totally does) ;-b BUT in your case I like you and your patches, they will be pushed 02:10 huginn kidclamp: The operation succeeded. 02:11 kidclamp @later tell ashimema bug 21095 02:11 huginn kidclamp: The operation succeeded. 04:06 mtompset Have a great day (24 hour period), #koha 05:03 * Oak waves 05:03 Oak So, what's the default interval set for the zebra re-indexing cron job? 05:06 Oak I don't see it mentioned here, surprisingly https://wiki.koha-community.org/wiki/Troubleshooting_Zebra 05:33 marcelr hi #koha 06:03 Oak Ah, the indexing daemon! I've fallen behind times. 06:48 reiveune hello 07:14 ashimema morning #koha 07:16 ashimema ooh.. oops. Thanks for that catch kidclamp 08:44 saa after upgrading koha while checking in items following error is coming "The item has not been checked in due to a configuration issue in your system. You must ask an administrator to take a look at the about page and search for the "data problems" section" 08:45 saa i have tried to use the https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix commands and created file and restarted mysql but no luck 08:46 saa what could be best way to get out of this error current 17.11.07 is ruuning on the system 08:46 saa can someone pl help 08:47 cait the commands don't fix the problem 08:47 cait they prevent it from happening again 08:47 cait the easiest way is to delete the doubled up ids from the deleted tables 08:47 cait what does about.pl > system information tell you? 08:49 saa it shows couple of ids 08:49 saa hw do i delete them 08:49 saa Checkouts The following ids exist in both tables issues and old_issues: 296, 275, 274, 290, 304, 323, 276, 280, 310, 294, 305, 303, 285, 314, 322, 317, 301, 328, 295, 286, 325, 327, 309, 278, 288, 302, 319, 284, 287, 279, 313, 316, 326, 308, 289, 282, 281, 283, 312, 320, 315, 1, 324, 172, 307, 292, 329, 306, 321, 277, 311, 293, 318, 297, 299, 298, 300, 291 08:50 saa Items The following ids exist in both tables items and deleteditems: 3314, 3230, 3000, 3001, 3002, 3003, 3053, 3054, 3055, 3370, 3381, 3407, 5148, 5153 08:50 saa Data problems Some of your tables have problems with their auto_increment values which may lead to data loss. You should not ignore this warning. The problem is that InnoDB does not keep auto_increment across SQL server restarts (it is only set in memory). So on server startup the auto_increment values are set to max(table.id)+1. To know how to avoid this problem see the related wiki page: DBMS auto increment fix 08:51 cait so the problems with the checkout sis issues 08:51 cait you could try to delete those numbers from deleteditems with sql 08:51 cait that will fix the problem 08:51 cait but of course the data will be lost (just so you are aware) 08:51 cait and then you can check in 08:51 saa which data will be lost 08:51 saa these ids is it 08:53 cait say you have reports looking at the deleteditems table for statistics 08:53 cait ah sorry deletedissues 08:53 cait old_issues 08:54 saa old data is nt thr that is fine i think 08:54 saa wht exactly is the syntax to delete those ids 08:55 cait this one could help: https://openschoolsolutions.org/fix-koha-auto-increment-problem/ 08:55 cait sorry, have to leave for a while 08:56 saa ok thx 08:56 saa will chk 08:56 saa thx again 10:31 marcelr bye 11:09 kohaputti Hey :) 13:16 Joubu whaou, 16.05.00 for more than two years and consider it stable! 14:08 fridolin 16.05 is like a granpa now ;) 14:14 ashimema great (16.05), great (16.11), grandpa (17.05) at least I'd say ;) 14:18 Joubu I was more talking about the .00 ; 14:18 Joubu ;) 14:19 ashimema lol 14:19 ashimema very good point.. 14:19 Joubu 16.05.x could be in good health, but .00? 14:19 ashimema I entirely missed that.. :'( 15:07 reiveune bye