Bruce, here are some more suggestions:
1. When it comes to the logs, perhaps a command such as these (and
similar) will reveal when and how something went wrong:
grep -inr --include \*.log 'koha-common' /var/log/
zgrep -in 'koha-common' /var/log/dpkg.log*
2. You should double-check that your installation source file is
correct, as covered by
https://wiki.koha-community.org/wiki/Koha_on_Debian#Set_up_package_sources.
For example, mine shows after the following command:
~# cat /etc/apt/sources.list.d/koha.list
deb [signed-by=/usr/share/keyrings/koha-keyring.gpg]
https://debian.koha-community.org/koha 22.05 main
3. If APT seems to be working, then you could install 'debsums' (apt
install debsums) and see what it reveals with this command:
debsums --all --silent
dpkg --verify koha-common
dpkg --audit koha-common
Those are going to look for errors in packages and list the
configuration files that have been altered from their default. It
listed nicely the files that I already knew I changed for both Koha
and Apache.
4. You may want to try the following commands, too:
apt --fix-broken install
apt --fix-missing install
5. If the Koha installation is incomplete, despite what the system
seems to report, then you may want to use 'dpkg' to remove
'koha-common' and then reinstall with 'apt' according to the
instructions.
dpkg --remove koha-common
6. When it comes to listing the databases, here's what you might expect to see:
~# mysql -uroot -p
Enter password:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 348
Server version: 10.5.19-MariaDB-0+deb11u2 Debian 11
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| koha_library |
| mysql |
| performance_schema |
+--------------------+
4 rows in set (0.000 sec)
MariaDB [(none)]> quit
Bye
Since our instance is named 'library', you can see that our database
is named 'koha_library'. It is customary for the instance creation
process to use the 'koha_' prefix for the database name. Does yours
show something similar?
On Tue, May 16, 2023 at 6:40 PM Bruce A. Metcalf
<libr...@augustansociety.org> wrote:
>
> On 5/15/23 16:35, David Liddle wrote:
>
> > Bruce, it’s an intriguing problem.... But I do have some more
> > questions:
> >
> > - What other services are running on that server? Are they all still
> > working correctly?
>
>
> There is another Apache server and a MediaWiki server (which may also
> run under Apache). Both are working as before with no problems or
> noticeable slowdowns.
>
>
> > - What clues are there in the logs in /var/log/?
>
>
> The only logs with any entries are access logs which show that the
> Chinese and Eastern Europeans are trying to hack the system. I don't
> think those are relevant.
>
> What may be relevant is that TOP does not show that Koha is running,
> though this could be just that the command isn't obvious.
>
>
> > - Is the apt installer working generally, or do you perhaps have a
> > broken Debian installation? Can you update or install other packages
> > successfully?
>
>
> The apt installer appears to be working, but it is not updating Koha
> apps, and there have been several updates since this began. The
> repository link appears to be correct; I'm (trying to run) on
> "oldoldstable".
>
>
> > - Can you access the database server to do a manual dump of the Koha
> > database?
>
>
> Not using any Koha tools or commands. I might be able to do so manually,
> but am clueless about how to do so.
>
> Thanks for your continuing efforts.
>
> 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
