Fwd: Dead Koha Resuscitation
Greetings, I have a problem with a dead Koha instance than I cannot resolve: I had Koha 21.05 installed on Debian 9 with packages. Previous updates to both had worked fine. I recently tried to update to 21.11 and Debian 10 (with packages). I did both at once because both were at end-of-life and 21.11 needs Deb 10 or better anyway. The virtual machine came back up fine, as did other apps on the machine (including other Apache servers). Koha, however, did not come back up. I tried a variety of ways to start and restart, without any response (i.e.: not even an error message). The logs don't offer any intelligible data (which may be my fault). I am also unable to locate commands like koha-create, koha-enable, koha-dump, koha-list, etc., getting a "command not found" error. I tried apt remove koha-common / apt install koha-common without a change in symptoms. Any suggestions about what to try next would be most appreciated. 1. Is there something undocumented that is needed for such an upgrade? 3. Can I install a new instance in the same virtual machine and transfer the settings and data? 4. Any other suggestions that don't involve firearms? Thanks for whatever suggestions you may have to share. Cheers, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
Hi, On Sun, May 14, 2023 at 12:38 PM Bruce A. Metcalf < library@augustansociety.org> wrote:
3. Can I install a new instance in the same virtual machine and transfer the settings and data?
Almost everything worth permanently keeping in a typical Koha system is stored in the database. Is MySQL/MariaDB running and can you get a mysqldump? If not, are there at least database files present in /var/lib/mysql? A current copy of the database could be imported into a fresh install of Koha (either in a new VM or after a wipe and recreation of the existing one - though if you do a wipe, triple-check that your database export is good!). Regards, Galen -- Galen Charlton Implementation and IT Manager Equinox Open Library Initiative gmc@equinoxOLI.org https://www.equinoxOLI.org phone: 877-OPEN-ILS (673-6457) direct: 770-709-5581
On 5/15/23 16:41, Galen Charlton wrote:
3. Can I install a new instance in the same virtual machine and transfer the settings and data?
Almost everything worth permanently keeping in a typical Koha system is stored in the database. Is MySQL/MariaDB running and can you get a mysqldump?
I'm not sure. How can one tell? There is a MySQL instance running, but I suspect that may be for one of the other servers. There is no MariaDB running, which I recall having switched to some time back. Can I buy a clue about how to run mysqldump?
If not, are there at least database files present in /var/lib/mysql?
If /var/lib/mysql/ibdata1 is the right file, then yes. It's almost a GB in size, which seems reasonable for the library's data.
A current copy of the database could be imported into a fresh install of Koha (either in a new VM or after a wipe and recreation of the existing one - though if you do a wipe, triple-check that your database export is good!).
Right. Tried to delete Koha and reinstall, but there was no change in the resultant. Wiping the whole VM is impractical due to the other servers on it, though that may prove necessary. I continue to suspect that the problem lies with the upgrades from Debian 9 to 10 and Koha 21.05 to 21.11. Something didn't upgrade correctly, or there's a hidden incompatibility, that's stopping work. Thanks for the ideas. Respectfully, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
On 5/16/23 10:51, Bruce A. Metcalf wrote:
On 5/15/23 16:41, Galen Charlton wrote:
3. Can I install a new instance in the same virtual machine and transfer the settings and data?
Almost everything worth permanently keeping in a typical Koha system is stored in the database. Is MySQL/MariaDB running and can you get a mysqldump?
I'm not sure. How can one tell? There is a MySQL instance running, but I suspect that may be for one of the other servers. There is no MariaDB running, which I recall having switched to some time back.
Can I buy a clue about how to run mysqldump?
MariaDB's process name is mysql, it doesn't matter much which you are using. you can make a backup wich mysqldump like this: mysqldump -u root -p --all-databases > backup.sql you should run this command from a directory with enough space to hold a backup of your database. you can reinstall koha-common by issuing this command: sudo apt-get install --reinstall koha-common it should pull any missing dependencies. Have you tried to backup your koha instance with "koha_dump" ? if your library instance is called "thisone", use: sudo koha_dump thisone it should put the backup on /var/spool/koha/thisone/ This process creates a mysqldump backup of just your database, and copies the rest of your koha files to a tar file. Those files can be used with koha_restore but if they can be made, your koha should be good enough for you to repair it.
If not, are there at least database files present in /var/lib/mysql?
If /var/lib/mysql/ibdata1 is the right file, then yes. It's almost a GB in size, which seems reasonable for the library's data.
A current copy of the database could be imported into a fresh install of Koha (either in a new VM or after a wipe and recreation of the existing one - though if you do a wipe, triple-check that your database export is good!).
Right. Tried to delete Koha and reinstall, but there was no change in the resultant. Wiping the whole VM is impractical due to the other servers on it, though that may prove necessary.
I continue to suspect that the problem lies with the upgrades from Debian 9 to 10 and Koha 21.05 to 21.11. Something didn't upgrade correctly, or there's a hidden incompatibility, that's stopping work.
Thanks for the ideas.
Respectfully, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
-- Hector Gonzalez cacho@genac.org
On 5/16/23 15:31, Hector Gonzalez Jaime wrote:
Can I buy a clue about how to run mysqldump?
you can make a backup wich mysqldump like this:
mysqldump -u root -p --all-databases > backup.sql
you can reinstall koha-common by issuing this command:
sudo apt-get install --reinstall koha-common
Aha! Here's a failure: root@store:/home/bruce# apt-get install --reinstall koha-common Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 42.7 MB of archives. After this operation, 0 B of additional disk space will be used. Err:1 http://debian.koha-community.org/koha oldoldstable/main i386 koha-common all 21.11.19-1 404 Not Found [IP: 67.220.127.145 80] E: Failed to fetch http://debian.koha-community.org/koha/pool/main/k/koha/koha-common_21.11.19-... 404 Not Found [IP: 67.220.127.145 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? This makes it look like the oldoldstable repository is broken?
Have you tried to backup your koha instance with "koha_dump" ?
This command is missing. Thanks again for the ideas. Any clue about the failure above could be crucial. Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
Hello, Bruce. You've been good about chasing down the information folks have asked for. I'm sorry that we haven't brought you closer to a solution. I have some follow-up questions: 1.a. Database. Once you listed the databases, did you exit the mysql prompt and back up the koha_library database with the mysqldump command? 1.b.Can you use an FTP client such as FileZilla to download such files? 2.a. Path. What is the result of this command? env | grep -i 'path' 2.b. Path. Did you already establish that the Koha commands are or are not installed? ls /usr/sbin/koha* 3. Repository and deb. Did you run "apt update" before running "apt-get install --reinstall koha-common"? The current version is 21.11.20. See https://koha-community.org/koha-21-11-20-released/ 4. Status and Apache. Yes, koha-common appears to be running, though maybe I'm reading it wrong. Have you checked the Apache config file for your instance, probably /etc/apache2/sites-available/library.conf? SSL Certificate information will be important. There are also Apache-related config files in /etc/koha, which I think could have been overwritten in the upgrade; that may or may not be important. 5. This situation is a good opportunity to research and document the elements on the server that you need to back up manually and download in the event that you need to rebuild the server from scratch. I'm guessing you don't do this work full-time, but having this information written will save you and/or your successor a lot of time when that day comes. Is this hosted server just running: 1. the main website (what platform or site-building tool?), 2. a wiki (MediaWiki?), and 3. Koha? That backup will probably come down to the databases you've listed and one or more directories for each service. On Thu, May 18, 2023 at 4:21 PM Bruce A. Metcalf <library@augustansociety.org> wrote:
On 5/16/23 15:31, Hector Gonzalez Jaime wrote:
Can I buy a clue about how to run mysqldump?
you can make a backup wich mysqldump like this:
mysqldump -u root -p --all-databases > backup.sql
you can reinstall koha-common by issuing this command:
sudo apt-get install --reinstall koha-common
Aha! Here's a failure:
root@store:/home/bruce# apt-get install --reinstall koha-common Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 42.7 MB of archives. After this operation, 0 B of additional disk space will be used. Err:1 http://debian.koha-community.org/koha oldoldstable/main i386 koha-common all 21.11.19-1 404 Not Found [IP: 67.220.127.145 80] E: Failed to fetch http://debian.koha-community.org/koha/pool/main/k/koha/koha-common_21.11.19-... 404 Not Found [IP: 67.220.127.145 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
This makes it look like the oldoldstable repository is broken?
Have you tried to backup your koha instance with "koha_dump" ?
This command is missing.
Thanks again for the ideas. Any clue about the failure above could be crucial.
Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
On 5/18/23 14:52, David Liddle wrote:
Hello, Bruce. You've been good about chasing down the information folks have asked for. I'm sorry that we haven't brought you closer to a solution.
I'm no less appreciative of your efforts for that.
I have some follow-up questions:
1.a. Database. Once you listed the databases, did you exit the mysql prompt and back up the koha_library database with the mysqldump command?
Yes, and it appeared to work. I have a 450MB file called backup.sql.
1.b.Can you use an FTP client such as FileZilla to download such files?
I assume so.
2.a. Path. What is the result of this command? env | grep -i 'path'
root@store:/# env | grep -i 'path' PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games I am aware that the path should contain several sbin directories, but I don't know how to add them.
2.b. Path. Did you already establish that the Koha commands are or are not installed? ls /usr/sbin/koha*
Yes, the usual list of commands is there. This suggests to me that the inadequate PATH command is at least part of my problem.
3. Repository and deb. Did you run "apt update" before running "apt-get install --reinstall koha-common"?
Yes. The resultant is: root@store:/# apt-get update && apt-get install --reinstall koha-common [some lines skipped] Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: koha-common : Depends: libtest-dbix-class-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages.
The current version is 21.11.20.
Right, but I haven't been able to employ any earlier version, either.
Yes, koha-common appears to be running, though maybe I'm reading it wrong. Have you checked the Apache config file for your instance, probably /etc/apache2/sites-available/library.conf
There are two links in that file, one for the OPAC and one for admin access.
SSL Certificate information will be important.
There is no mention of SSL Certificates in the file.
There are also Apache-related config files in /etc/koha, which I think could have been overwritten in the upgrade; that may or may not be important.
There are such files. I don't know what to make of them.
5. This situation is a good opportunity to research and document the elements on the server that you need to back up manually and download in the event that you need to rebuild the server from scratch. I'm guessing you don't do this work full-time, but having this information written will save you and/or your successor a lot of time when that day comes.
Yeah, I should be so lucky as to have someone take over for me! <G> The organization is a non-profit with declining participation.
Is this hosted server just running: 1. the main website (what platform or site-building tool?), 2. a wiki (MediaWiki?), and 3. Koha? That backup will probably come down to the databases you've listed and one or more directories for each service.
The virtual server is running an Online Store, a Wiki, and Koha. Minor file storage is all else that's there. What I suspect at this point is that I need to add the sbin directories to the PATH. Can someone point me to a tutorial? Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
On 5/18/23 13:46, Bruce A. Metcalf wrote:
On 5/18/23 14:52, David Liddle wrote:
Hello, Bruce. You've been good about chasing down the information folks have asked for. I'm sorry that we haven't brought you closer to a solution.
I'm no less appreciative of your efforts for that.
I have some follow-up questions:
1.a. Database. Once you listed the databases, did you exit the mysql prompt and back up the koha_library database with the mysqldump command?
Yes, and it appeared to work. I have a 450MB file called backup.sql.
1.b.Can you use an FTP client such as FileZilla to download such files?
I assume so.
2.a. Path. What is the result of this command? env | grep -i 'path'
root@store:/# env | grep -i 'path' PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
I am aware that the path should contain several sbin directories, but I don't know how to add them.
with these commands: PATH=/sbin:/usr/sbin:$PATH export PATH Assuming you are using some variant of /bin/sh You might edit your .bashrc and add that at the end of the file, and login again, or use "source ~/.bashrc " to process the file in your session.
2.b. Path. Did you already establish that the Koha commands are or are not installed? ls /usr/sbin/koha*
Yes, the usual list of commands is there. This suggests to me that the inadequate PATH command is at least part of my problem.
3. Repository and deb. Did you run "apt update" before running "apt-get install --reinstall koha-common"?
Yes. The resultant is:
root@store:/# apt-get update && apt-get install --reinstall koha-common [some lines skipped] Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: koha-common : Depends: libtest-dbix-class-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages.
You should try: apt-get dist-upgrade which would install the missing dependencies. Also apt-get -f install should fix that too.
The current version is 21.11.20.
Right, but I haven't been able to employ any earlier version, either.
Yes, koha-common appears to be running, though maybe I'm reading it wrong. Have you checked the Apache config file for your instance, probably /etc/apache2/sites-available/library.conf
There are two links in that file, one for the OPAC and one for admin access.
SSL Certificate information will be important.
There is no mention of SSL Certificates in the file.
There are also Apache-related config files in /etc/koha, which I think could have been overwritten in the upgrade; that may or may not be important.
There are such files. I don't know what to make of them.
5. This situation is a good opportunity to research and document the elements on the server that you need to back up manually and download in the event that you need to rebuild the server from scratch. I'm guessing you don't do this work full-time, but having this information written will save you and/or your successor a lot of time when that day comes.
Yeah, I should be so lucky as to have someone take over for me! <G> The organization is a non-profit with declining participation.
Is this hosted server just running: 1. the main website (what platform or site-building tool?), 2. a wiki (MediaWiki?), and 3. Koha? That backup will probably come down to the databases you've listed and one or more directories for each service.
The virtual server is running an Online Store, a Wiki, and Koha. Minor file storage is all else that's there.
What I suspect at this point is that I need to add the sbin directories to the PATH. Can someone point me to a tutorial?
Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
-- Hector Gonzalez cacho@genac.org
On 5/18/23 15:52, Hector Gonzalez Jaime wrote:
On 5/18/23 13:46, Bruce A. Metcalf wrote:
On 5/18/23 14:52, David Liddle wrote:
2.a. Path. What is the result of this command? env | grep -i 'path'
root@store:/# env | grep -i 'path' PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
I am aware that the path should contain several sbin directories, but I don't know how to add them.
with these commands:
PATH=/sbin:/usr/sbin:$PATH export PATH
Okay, that seems to have worked. Still no love from apt-get install --reinstall koha-common though.
3. Repository and deb. Did you run "apt update" before running "apt-get install --reinstall koha-common"?
Yes. The resultant is:
root@store:/# apt-get update && apt-get install --reinstall koha-common [some lines skipped] Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: koha-common : Depends: libtest-dbix-class-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages.
This unchanged after the PATH correction.
You should try: apt-get dist-upgrade which would install the missing dependencies.
This seems hopeful: root@store:/etc/koha# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libmoosex-types-perl libsub-exporter-formethods-perl The following packages have been kept back: koha-common The following packages will be upgraded: koha python-ipaddress 2 upgraded, 2 newly installed, 0 to remove and 1 not upgraded. ... etc. I am concerned by the koha-common being kept back though.
Also apt-get -f install should fix that too.
No change from that. ... and still no OPAC or admin access. Curiously: root@store:/etc/koha# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libossp-uuid-perl : Conflicts: libdata-uuid-perl E: Broken packages Suggestions? Thanks all for the continuing effort. Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
Hi Bruce We've found the problem. On 19 May 2023 7:46:58 am NZST, "Bruce A. Metcalf" <library@augustansociety.org> wrote:
On 5/18/23 14:52, David Liddle wrote:
Hello, Bruce. You've been good about chasing down the information folks have asked for. I'm sorry that we haven't brought you closer to a solution.
I'm no less appreciative of your efforts for that.
I have some follow-up questions:
1.a. Database. Once you listed the databases, did you exit the mysql prompt and back up the koha_library database with the mysqldump command?
Yes, and it appeared to work. I have a 450MB file called backup.sql.
1.b.Can you use an FTP client such as FileZilla to download such files?
I assume so.
2.a. Path. What is the result of this command? env | grep -i 'path'
root@store:/# env | grep -i 'path' PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
I am aware that the path should contain several sbin directories, but I don't know how to add them.
2.b. Path. Did you already establish that the Koha commands are or are not installed? ls /usr/sbin/koha*
Yes, the usual list of commands is there. This suggests to me that the inadequate PATH command is at least part of my problem.
3. Repository and deb. Did you run "apt update" before running "apt-get install --reinstall koha-common"?
Yes. The resultant is:
root@store:/# apt-get update && apt-get install --reinstall koha-common [some lines skipped] Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: koha-common : Depends: libtest-dbix-class-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages.
This is the issue right here, koha-common can't be installed cleanly because a package it depends on is missing. What does sudo apt install libtest-dbix-class-perl Result in? Chris
The current version is 21.11.20.
Right, but I haven't been able to employ any earlier version, either.
Yes, koha-common appears to be running, though maybe I'm reading it wrong. Have you checked the Apache config file for your instance, probably /etc/apache2/sites-available/library.conf
There are two links in that file, one for the OPAC and one for admin access.
SSL Certificate information will be important.
There is no mention of SSL Certificates in the file.
There are also Apache-related config files in /etc/koha, which I think could have been overwritten in the upgrade; that may or may not be important.
There are such files. I don't know what to make of them.
5. This situation is a good opportunity to research and document the elements on the server that you need to back up manually and download in the event that you need to rebuild the server from scratch. I'm guessing you don't do this work full-time, but having this information written will save you and/or your successor a lot of time when that day comes.
Yeah, I should be so lucky as to have someone take over for me! <G> The organization is a non-profit with declining participation.
Is this hosted server just running: 1. the main website (what platform or site-building tool?), 2. a wiki (MediaWiki?), and 3. Koha? That backup will probably come down to the databases you've listed and one or more directories for each service.
The virtual server is running an Online Store, a Wiki, and Koha. Minor file storage is all else that's there.
What I suspect at this point is that I need to add the sbin directories to the PATH. Can someone point me to a tutorial?
Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
On 5/18/23 15:53, Chris Cormack wrote:
Hi Bruce
I Chris. I remember meeting you in Reno!
We've found the problem.
root@store:/# apt-get update && apt-get install --reinstall koha-common [some lines skipped] Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: koha-common : Depends: libtest-dbix-class-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages. This is the issue right here, koha-common can't be installed cleanly because a package it depends on is missing.
What does sudo apt install libtest-dbix-class-perl Result in?
root@store:/etc/koha# apt install libtest-dbix-class-perl Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libtest-dbix-class-perl : Depends: libdata-uuid-perl (>= 1.215) E: Unable to correct problems, you have held broken packages So, I did: root@store:/etc/koha# apt install libdata-uuid-perl Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libossp-uuid16 Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: libossp-uuid-perl libsoap-lite-perl libxmlrpc-lite-perl The following NEW packages will be installed: libdata-uuid-perl 0 upgraded, 1 newly installed, 3 to remove and 1 not upgraded. Need to get 24.8 kB of archives. After this operation, 833 kB disk space will be freed. etc. Now when I do: root@store:/etc/koha# apt install libtest-dbix-class-perl It all seems to run correctly. And when I enter: root@store:/etc/koha# apt install koha-common That too seems to run correctly. But still no love for the OPAC or admin interface. Feels like good progress though. What next? Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
Hi Bruce Oh yes! That's right, way back in 2013 eh? Ok, so I think now you can try seeing if you have the koha commands back does sudo koha-list work and list your instance? If so, you might want to run a koha-dump then try restarting all the Koha services Chris Chris On 19/05/23 08:48, Bruce A. Metcalf wrote:
On 5/18/23 15:53, Chris Cormack wrote:
Hi Bruce
I Chris. I remember meeting you in Reno!
We've found the problem.
root@store:/# apt-get update && apt-get install --reinstall koha-common [some lines skipped] Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: koha-common : Depends: libtest-dbix-class-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages. This is the issue right here, koha-common can't be installed cleanly because a package it depends on is missing.
What does sudo apt install libtest-dbix-class-perl Result in?
root@store:/etc/koha# apt install libtest-dbix-class-perl Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: libtest-dbix-class-perl : Depends: libdata-uuid-perl (>= 1.215) E: Unable to correct problems, you have held broken packages
So, I did: root@store:/etc/koha# apt install libdata-uuid-perl Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libossp-uuid16 Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: libossp-uuid-perl libsoap-lite-perl libxmlrpc-lite-perl The following NEW packages will be installed: libdata-uuid-perl 0 upgraded, 1 newly installed, 3 to remove and 1 not upgraded. Need to get 24.8 kB of archives. After this operation, 833 kB disk space will be freed. etc.
Now when I do: root@store:/etc/koha# apt install libtest-dbix-class-perl It all seems to run correctly.
And when I enter: root@store:/etc/koha# apt install koha-common That too seems to run correctly.
But still no love for the OPAC or admin interface.
Feels like good progress though. What next?
Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
-- Kaihuawaere Matihiko (he/him) Kāi Tahu, Kāti Māmoe, Waitaha Catalyst.Net Limited - Expert Open Source Solutions 027 4500789 chrisc@catalyst.net.nz
On 5/18/23 16:51, Chris Cormack wrote:
Ok, so I think now you can try seeing if you have the koha commands back
does sudo koha-list work and list your instance?
Yes and yes.
If so, you might want to run a koha-dump...
Done. Seems to have worked.
... then try restarting all the Koha services
Okay, not sure how to do this, so I just rebooted the server. The other services came back up, but not Koha. Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
What does sudo koha-plack --start instancename Do? Chris On 19 May 2023 9:11:04 am NZST, "Bruce A. Metcalf" <library@augustansociety.org> wrote:
On 5/18/23 16:51, Chris Cormack wrote:
Ok, so I think now you can try seeing if you have the koha commands back
does sudo koha-list work and list your instance?
Yes and yes.
If so, you might want to run a koha-dump...
Done. Seems to have worked.
... then try restarting all the Koha services
Okay, not sure how to do this, so I just rebooted the server. The other services came back up, but not Koha.
Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
On 5/18/23 17:35, Chris Cormack wrote:
What does sudo koha-plack --start instancename Do?
root@store:/home/bruce# koha-plack --start library bash: koha-plack: command not found Which I thought was pretty odd, so I went to the /usr/sbin directory, and: root@store:/usr/sbin# ls -l koha-p* -rwxr-xr-x 1 root root 13538 May 13 23:26 koha-plack then root@store:/usr/sbin# koha-plack --start library bash: koha-plack: command not found Which seems even more weird. Are the permissions wrong? Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
On 5/18/23 19:18, Bruce A. Metcalf wrote:
On 5/18/23 17:35, Chris Cormack wrote:
What does sudo koha-plack --start instancename Do?
root@store:/home/bruce# koha-plack --start library bash: koha-plack: command not found
Which I thought was pretty odd, so I went to the /usr/sbin directory, and:
root@store:/usr/sbin# ls -l koha-p* -rwxr-xr-x 1 root root 13538 May 13 23:26 koha-plack
then
root@store:/usr/sbin# koha-plack --start library bash: koha-plack: command not found
Which seems even more weird. Are the permissions wrong? You are still missing /usr/sbin in your PATH variable. You seem to be running bash:
export PATH=/sbin:/usr/sbin:$PATH (bash can do this in one line). Copy the command exactly, CAPS are important here. Linux does not have the current directory in your PATH, which means it will not run a command from the directory you are at (this may feel strange if you come from a windows environment, but is normal) The command would have run if you had typed: /usr/sbin/koha-plack --start library your system seems to be in a strange situation, you might want to uninstall koha, remove all dependencies, and install it again: apt-get remove koha-common <- this does not affect your database or configuration files. apt-get autoremove <- this deletes every dependency that is no longer needed, which should be a ton of perl libraries. apt-get install koha-common <- this should reinstall koha, and every one of its dependencies. If your system has problems, this command would eventually fail. If this last command fails, I'd like to see the contents of your /etc/apt/sources.list file and every file at /etc/apt/sources.list.d
Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
-- Hector Gonzalez cacho@genac.org
On 5/18/23 21:35, Hector Gonzalez Jaime wrote:
What does sudo koha-plack --start instancename Do?
root@store:/usr/sbin# koha-plack --start library bash: koha-plack: command not found
Which seems even more weird. Are the permissions wrong?
You are still missing /usr/sbin in your PATH variable.
That's been added.
The command would have run if you had typed:
/usr/sbin/koha-plack --start library
Let me try: root@store:/usr/sbin# /usr/sbin/koha-plack --start library /usr/share/koha/bin/koha-functions.sh: line 285: start-stop-daemon: command not found [ ok ] Starting Plack daemon for library:. Okay, a step forward, but a new challenge. (Been a lot of that in this project!) Line 285 is: if start-stop-daemon --pidfile "/var/run/koha/${instancename}/plack.pid" \ File /var/run/koha/library/plack.pid does exist. It contains a five-digit number only. Okay, I'm stuck again! Thanks again for all the help. Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
your system seems to be in a strange situation, you might want to uninstall koha, remove all dependencies, and install it again:
apt-get remove koha-common <- this does not affect your database or configuration files. apt-get autoremove <- this deletes every dependency that is no longer needed, which should be a ton of perl libraries. apt-get install koha-common <- this should reinstall koha, and every one of its dependencies. If your system has problems, this command would eventually fail.
If this last command fails, I'd like to see the contents of your /etc/apt/sources.list file and every file at /etc/apt/sources.list.d
Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
On 5/18/23 20:46, Bruce A. Metcalf wrote:
On 5/18/23 21:35, Hector Gonzalez Jaime wrote:
What does sudo koha-plack --start instancename Do?
root@store:/usr/sbin# koha-plack --start library bash: koha-plack: command not found
Which seems even more weird. Are the permissions wrong?
You are still missing /usr/sbin in your PATH variable.
That's been added.
It mighty not have been added permanently. start-stop-daemon is at /sbin, which means that one is missing from your PATH. to verify what is on your path, you can type: echo $PATH if it is missing any of the directorios, add it with: PATH=/sbin:/usr/sbin:$PATH, followed by export PATH it might be part of .bashrc, but if you are editing root's one, you might want to check your regular user's .bashrc first.
The command would have run if you had typed:
/usr/sbin/koha-plack --start library
Let me try:
root@store:/usr/sbin# /usr/sbin/koha-plack --start library /usr/share/koha/bin/koha-functions.sh: line 285: start-stop-daemon: command not found [ ok ] Starting Plack daemon for library:.
Okay, a step forward, but a new challenge. (Been a lot of that in this project!)
Line 285 is:
if start-stop-daemon --pidfile "/var/run/koha/${instancename}/plack.pid" \
File /var/run/koha/library/plack.pid does exist. It contains a five-digit number only.
Okay, I'm stuck again!
Thanks again for all the help.
Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
your system seems to be in a strange situation, you might want to uninstall koha, remove all dependencies, and install it again:
apt-get remove koha-common <- this does not affect your database or configuration files. apt-get autoremove <- this deletes every dependency that is no longer needed, which should be a ton of perl libraries. apt-get install koha-common <- this should reinstall koha, and every one of its dependencies. If your system has problems, this command would eventually fail.
If this last command fails, I'd like to see the contents of your /etc/apt/sources.list file and every file at /etc/apt/sources.list.d
Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
-- Hector Gonzalez cacho@genac.org
On 5/19/23 15:19, Hector Gonzalez Jaime wrote:
What does sudo koha-plack --start instancename Do?
root@store:/usr/sbin# koha-plack --start library bash: koha-plack: command not found
Which seems even more weird. Are the permissions wrong?
You are still missing /usr/sbin in your PATH variable.
That's been added.
It mighty not have been added permanently.
to verify what is on your path, you can type: echo $PATH
Aha! It wasn't. I've put it back again, but results of that have already been posted with a new stop point.
if it is missing any of the directories, add it with: PATH=/sbin:/usr/sbin:$PATH, followed by export PATH
it might be part of .bashrc, but if you are editing root's one, you might want to check your regular user's .bashrc first.
Okay, you lost me here. I'm not aware of .bashrc, so am not aware if I am, or should be, editing it. Thanks again for trying. Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library
participants (6)
-
Bruce A. Metcalf -
Chris Cormack -
David Liddle -
Galen Charlton -
Hector Gonzalez Jaime -
Marcel de Rooy