kohadevbox:koha(backport/bookings)$ ./misc/cronjobs/holds/← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 00:07 | mbridge joined #koha | |
| 01:07 | mbridge joined #koha | |
| 02:07 | mbridge joined #koha | |
| 03:07 | mbridge joined #koha | |
| 04:07 | mbridge joined #koha | |
| 05:05 | lds joined #koha | |
| 05:07 | mbridge joined #koha | |
| 06:08 | mbridge joined #koha | |
| 07:07 | mbridge joined #koha | |
| 08:07 | mbridge joined #koha | |
| 09:07 | mbridge joined #koha | |
| 10:07 | mbridge joined #koha | |
| 11:07 | mbridge joined #koha | |
| 11:20 | lds joined #koha | |
| 11:44 | lds joined #koha | |
| 12:07 | mbridge joined #koha | |
| 13:03 | Dyrcona joined #koha | |
| 13:07 | mbridge joined #koha | |
| 13:26 | mbridge | [mattermost] <haykmanukyan> Hello everyone. I had updated from 16 to 22. after update did zebra rebuild. Everything are working well. Only there is one issue. Holds queue is empty. There is not any records. I looked for db, and there exist records. Also, I add a new one but no effect, this new one do not show too. |
| 13:26 | [mattermost] <haykmanukyan> On old server everything is ok. | |
| 13:27 | [mattermost] <haykmanukyan> Please help me. Did you have any issue like this | |
| 13:27 | [mattermost] <jpahd> Look into the logs under `/var/log/koha/<YOUR_INSTANCE>`. | |
| 13:27 | [mattermost] <jpahd> Maybe you'll find something. | |
| 13:28 | [mattermost] <cait> 16 or 22 are not Koha version, you always need to include the second number as well | |
| 13:28 | [mattermost] <cait> we do 2 releases each year, the first number reflects the year, the second the month | |
| 13:28 | [mattermost] <cait> also holds queue is built by a cron job - it depends on when you did the update and if it has since been run to schedule. Then if it runs you could check for errors like @paulderscheid suggested | |
| 13:30 | [mattermost] <haykmanukyan> from Koha 16.0512000 to 22.05 | |
| 13:31 | [mattermost] <haykmanukyan> Oh, I am sorry. From 16.0512000 to 22.05 | |
| 13:34 | [mattermost] <cait> 22.05 won't receive any security updates anymore - if you are to update, I'd recommend to go at elast to 22.11 LTS which will still be supported for a while | |
| 13:35 | [mattermost] <haykmanukyan> @paulderscheid I can't see any specific error related this page | |
| 13:39 | [mattermost] <haykmanukyan> @cait Is best practice is | |
| 13:39 | [mattermost] <haykmanukyan> 1. create a mysql dump file of the project | |
| 13:39 | [mattermost] <haykmanukyan> 2. remove the project and install new version | |
| 13:39 | [mattermost] <haykmanukyan> 3. before opening installation wizard import the dumped db on the new database schema | |
| 13:39 | [mattermost] <haykmanukyan> is it right way? | |
| 13:40 | [mattermost] <haykmanukyan> @cait Is best practice for updating is | |
| 13:40 | [mattermost] <haykmanukyan> 1. create a mysql dump file of the project | |
| 13:40 | [mattermost] <haykmanukyan> 2. remove the project and install new version | |
| 13:40 | [mattermost] <haykmanukyan> 3. before opening installation wizard import the dumped db on the new database schema | |
| 13:40 | [mattermost] <haykmanukyan> is it right way? | |
| 13:44 | [mattermost] <cait> I would for sure create a database dump first | |
| 13:44 | [mattermost] <cait> but we usually don't uninstall | |
| 13:45 | [mattermost] <cait> the database dump is used in case you need to go back or run into a dabase update issue | |
| 13:45 | [mattermost] <cait> usually you'd update the packages as for ohter linux tools too | |
| 13:56 | [mattermost] <haykmanukyan> @cait Do you think after update it will solve this issue? | |
| 13:57 | [mattermost] <cait> not certainly | |
| 13:57 | [mattermost] <cait> I think what you hsould do is run the job manually and see if there are any errors | |
| 13:57 | [mattermost] <cait> it#s in misc/holds | |
| 13:57 | [mattermost] <jpahd> I think it is worth a try. | |
| 13:57 | [mattermost] <jpahd> But as cait says, success not guaranteed. | |
| 13:58 | [mattermost] <haykmanukyan> @cait I did't find it | |
| 13:59 | [mattermost] <haykmanukyan> Do you mean I should run manually cronjob command | |
| 13:59 | [mattermost] <haykmanukyan> ? | |
| 14:00 | [mattermost] <haykmanukyan> If yes, please can you help me find the file witch must be runned, I can't find it | |
| 14:03 | [mattermost] <haykmanukyan> I mean this path is not exist in my server | |
| 14:03 | [mattermost] <haykmanukyan> misc/cronjobs/holds/build_holds_queue.pl | |
| 14:03 | [mattermost] <cait> @paulderscheid i think it should still be in misc for packages? | |
| 14:04 | [mattermost] <jpahd> ```sh | |
| 14:04 | [mattermost] <jpahd> rootkohadevbox:koha(backport/bookings)$ ./misc/cronjobs/holds/ |
|
| 14:04 | [mattermost] <jpahd> auto_unsuspend_holds.pl build_holds_queue.pl cancel_expired_holds.pl cancel_unfilled_holds.pl holds_reminder.pl | |
| 14:04 | [mattermost] <jpahd> ``` | |
| 14:04 | [mattermost] <jpahd> Yes | |
| 14:05 | [mattermost] <jpahd> Hmm, then I would definitely suggest to update again. | |
| 14:05 | [mattermost] <jpahd> So that the debian package can place these scripts where they belong. | |
| 14:06 | [mattermost] <haykmanukyan> Please can you give me full path of the file | |
| 14:07 | mbridge joined #koha | |
| 14:09 | mbridge | [mattermost] <jpahd> `/usr/share/koha/bin/cronjobs/holds/build_holds_queue.pl` |
| 14:09 | [mattermost] <jpahd> This is on pod. | |
| 14:09 | [mattermost] <jpahd> This is on prod. | |
| 14:09 | [mattermost] <jpahd> This is the path for prod. | |
| 14:13 | [mattermost] <haykmanukyan> Ok, thank you. I will try this commant a little later | |
| 14:13 | [mattermost] <haykmanukyan> But I have another question, is there any good practice for boost speed opac | |
| 14:14 | [mattermost] <haykmanukyan> first page and search | |
| 14:14 | [mattermost] <haykmanukyan> ? | |
| 14:14 | [mattermost] <haykmanukyan> But I have another question, is there any good practice for boost speed opac? | |
| 14:14 | [mattermost] <jpahd> Yes | |
| 14:15 | [mattermost] <jpahd> Do you know why it is slow? | |
| 14:15 | [mattermost] <jpahd> Do you have an underpowered machine? Or rather a lot of patrons? | |
| 14:17 | [mattermost] <haykmanukyan> I have 2400 patrons. The server have 8 gb ram 4 core and ssd storage | |
| 14:17 | [mattermost] <jpahd> How many plack workers have you configured? | |
| 14:18 | [mattermost] <haykmanukyan> I tryed to configure it, but after server restart it was braked the whall instance | |
| 14:19 | [mattermost] <haykmanukyan> I tryed to configure it, but after server restart it was braked the whole instance | |
| 14:20 | [mattermost] <jpahd> If you don't have any plack workers configured, then it's understandable that performance is bad. | |
| 14:20 | [mattermost] <jpahd> Maybe this will help: | |
| 14:20 | [mattermost] <jpahd> https://wiki.koha-community.org/wiki/Plack | |
| 14:21 | [mattermost] <cait> also when running the script above, switch into koha-shell first | |
| 14:21 | [mattermost] <cait> sudo koha-shell instance - then run the script | |
| 14:23 | [mattermost] <haykmanukyan> @cait You mean before this command yes? | |
| 14:23 | [mattermost] <haykmanukyan> /usr/share/koha/bin/cronjobs/holds/build_holds_queue.pl | |
| 14:23 | [mattermost] <jpahd> Yes | |
| 14:25 | [mattermost] <jpahd> So it would be | |
| 14:25 | [mattermost] <jpahd> ```sh | |
| 14:25 | [mattermost] <jpahd> # koha-shell <instance> -c '/usr/share/koha/bin/cronjobs/holds/build_holds_queue.pl' | |
| 14:25 | [mattermost] <jpahd> ``` | |
| 14:25 | [mattermost] <haykmanukyan> Oh, that is greate | |
| 14:25 | [mattermost] <haykmanukyan> thank you very much | |
| 14:26 | [mattermost] <jpahd> No worries | |
| 15:07 | mbridge joined #koha | |
| 15:14 | mbridge | [mattermost] <haykmanukyan> That is working for me. Thank you very much |
| 15:14 | [mattermost] <haykmanukyan> I have another issue | |
| 15:16 | [mattermost] <haykmanukyan> after deleting a item from reservers I get error Error 500. And find this problem "The following ids exist in both tables reserves and old_reserves: | |
| 15:16 | [mattermost] <haykmanukyan> 2974" | |
| 15:16 | [mattermost] <haykmanukyan> Please can you help to solve this issue too | |
| 15:17 | [mattermost] <cait> go to the about page > system information | |
| 15:17 | [mattermost] <cait> it will list duplicate IDs | |
| 15:17 | [mattermost] <cait> the easiest is to delete these entries from the old_ or deleted tables listed | |
| 15:17 | [mattermost] <cait> considering your Koha was quite old, you might also need to check into an OS update for a newer DBMS version | |
| 15:17 | [mattermost] <cait> see the wiki page linked there - it's a DBMS problem with certain older versions | |
| 15:21 | [mattermost] <haykmanukyan> Ok, I get you | |
| 15:21 | [mattermost] <haykmanukyan> Thank you | |
| 15:22 | [mattermost] <haykmanukyan> And one more question, witch version is the best choice for updateing | |
| 15:22 | [mattermost] <haykmanukyan> And one more question, witch version is the best choice for updating | |
| 15:22 | [mattermost] <haykmanukyan> 23.11 or 24.05? | |
| 15:28 | [mattermost] <cait> I'd wait a bit longer for 24.05 - we had some big architecture changes and there are still some issues popping up. 23.11 or LTS 22.11 would be my opinion, but others might have a different one :) | |
| 15:29 | [mattermost] <cait> 22.11 seems pretty stable right now and you are doing a big jump | |
| 15:33 | [mattermost] <haykmanukyan> I get you | |
| 15:33 | [mattermost] <haykmanukyan> Thank you very much | |
| 15:34 | [mattermost] <haykmanukyan> 👍 | |
| 16:07 | mbridge joined #koha | |
| 17:07 | mbridge joined #koha | |
| 18:07 | mbridge joined #koha | |
| 19:07 | mbridge joined #koha | |
| 20:01 | mbridge | [mattermost] <?/θ> Hello! Most of the Koha Community conversation is now over on Mattermost. Come and join us! https://chat.koha-community.org |
| 20:07 | mbridge joined #koha | |
| 21:07 | mbridge joined #koha | |
| 22:07 | mbridge joined #koha | |
| 23:07 | mbridge joined #koha |
← Previous day | Today | Next day → | Search | Index
