Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint
I noticed one other thing that surprised me. I don't know the username for logging into the administrative interface, so I looked to see what I could find in the database was empty. Thinking that I must have munged something, I tried to create a new instance with another name. The new instance's database was also empty: toolchest monk # koha-create --create-db monasterylibrary Koha instance is empty, no staff user created. Starting Zebra server for monasterylibrary * Starting Koha indexing daemon for monasterylibrary [ OK ] toolchest monk # mysql -uroot -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 39 Server version: 10.0.29-MariaDB-0ubuntu0.16.04.1 Ubuntu 16.04 Copyright (c) 2000, 2016, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> use koha_monasterylibrary; Database changed MariaDB [koha_monasterylibrary]> show tables; Empty set (0.00 sec) Is this intended? Thx, On Wed, Jul 26, 2017 at 3:19 PM, C.J.S. Hayward <cjsh@cjshayward.com> wrote:
I am not noticing a "[main page]" link below the login form.
Is there any command (or authoritative source) that will get the Koha administrator's username like "koha-passwd library" will get the Koha administrator's password?
On Tue, Jul 25, 2017 at 8:45 PM, Liz Rea <liz@catalyst.net.nz> wrote:
Hi,
There is currently a bug in Koha where it looks like the DB password is being rejected, but if you click "[main page]" below the login form, you are logged in. It's worth checking that you're not coming up against this bug.
Cheers, Liz
The credentials are in the config section, close to the database entry, not in the serverinfo section. The username must be something like 'koha_library' (if you created it using koha-create).
On Tue, 25 Jul 2017 at 20:42 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
I think my installation is corrupt.
(koha-password displayed a password, but it didn't work for logging in as kohauser either.)
I want to uninstall and reinstall. Any words of advice besides being meticulous about the wiki instructions?
Thanks
On Tue, Jul 25, 2017 at 6:03 PM, Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
You should not modify it, you can know the password of the database user using `sudo koha-passwd kohadev`, but the command will return the same value as the xml config file. Try to connect to mysql using `mysql -u koha_library -p` and enter the password. If it is rejected, you did something wrong when you create the instance. If it is not rejected it should not be rejected from the interface either.
On Tue, 25 Jul 2017 at 19:38 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
My suspicion is that you already had Listen lines predefined and you double-punched on at least one port.
I moved all Listen lines to ports.conf, removing them from the sites, and maintaining only one Listen line per port. The behavior is, so far as I can tell, identical. The .../library/koha-conf.xml credentials are rejected every single time.
Is there a command line way (bash or mysql) to set the password for kohauser?
Thanks,
On Tue, Jul 25, 2017 at 5:18 PM, Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
> I tried to add the "Listen" lines and it breaks everything for me. > What is the behaviour if you remove them? Do you access the staff > interface > (login form) or the opac interface (maintenance screen)? > > On Tue, 25 Jul 2017 at 18:51 C.J.S. Hayward <cjsh@cjshayward.com> wrote: >> Ok; I can clean that up. >> >> But let me see if the same symptoms appear next time I work on it; my >> expectation is that the behavior is identical (i.e. I am not able to > log in >> through the web interface with credentials in
On 26/07/17 13:24, Jonathan Druart wrote: library/koha-conf.xml),
> even >> if I should move the Listen lines. >> >> >> Thanks, >> >> On Tue, Jul 25, 2017 at 4:27 PM, Jonathan Druart < >> jonathan.druart@bugs.koha-community.org> wrote: >> >>> I think the 2 "Listen" lines should go to ports.conf >>> >>> On Tue, 25 Jul 2017 at 18:11 C.J.S. Hayward <cjsh@cjshayward.com> > wrote: >>>> Thank you. This server is multipurpose and has multiple webapps that >>>> listen on 8080 by default. My library entry in >>> /etc/apache2/sites-enables >>>> reads, with /etc/hosts assigning "opac" and "library" to 127.0.0.1: >>>> # Koha instance library Apache config. >>>> >>>> # OPAC >>>> >>>> Listen 7027 >>>> <VirtualHost *:7027> >>>> <IfVersion >= 2.4> >>>> Define instance "library" >>>> </IfVersion> >>>> Include /etc/koha/apache-shared.conf >>>> # Include /etc/koha/apache-shared-disable.conf >>>> # Include /etc/koha/apache-shared-opac-plack.conf >>>> Include /etc/koha/apache-shared-opac.conf >>>> >>>> ServerName opac >>>> SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml" >>>> AssignUserID library-koha library-koha >>>> >>>> ErrorLog /var/log/koha/library/opac-error.log >>>> # TransferLog /var/log/koha/library/opac-access.log >>>> # RewriteLog /var/log/koha/library/opac-rewrite.log >>>> </VirtualHost> >>>> >>>> # Intranet >>>> Listen 7028 >>>> <VirtualHost *:7028> >>>> <IfVersion >= 2.4> >>>> Define instance "library" >>>> </IfVersion> >>>> Include /etc/koha/apache-shared.conf >>>> # Include /etc/koha/apache-shared-disable.conf >>>> # Include /etc/koha/apache-shared-intranet-plack.conf >>>> Include /etc/koha/apache-shared-intranet.conf >>>> >>>> ServerName intranet >>>> SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml" >>>> AssignUserID library-koha library-koha >>>> >>>> ErrorLog /var/log/koha/library/intranet-error.log >>>> # TransferLog /var/log/koha/library/intranet-access.log >>>> # RewriteLog /var/log/koha/library/intranet-rewrite.log >>>> </VirtualHost> >>>> ~ >>>> >>>> >>>> I had earlier tried to access opac:7027 and got the reported error. > Now >>> I >>>> am trying to access intranet:7028 and I can't tell a difference. >>>> >>>> Do I need to be doing more if I reassign port numbers? >>>> >>>> >>>> Thanks,
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- -- Liz Rea Catalyst.Net Limited Level 6, Catalyst House, 150 Willis Street, Wellington. P.O Box 11053, Manners Street, Wellington 6142
GPG: B149 A443 6B01 7386 C2C7 F481 B6c2 A49D 3726 38B7
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/>.
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - fundraiser <https://GoFundMe.com/the-holy-mountain> - website <https://cjshayward.com/> .
Hi
I don't know the username for logging into the administrative interface, so I looked to see what I could find in the database was empty.
You will find the password of the administrative user as follows: $ INSTANZ="yourinstance" $ sudo xmlstarlet sel -t -v 'yazgfs/config/pass' /etc/koha/sites/$INSTANZ/koha-conf.xml && echo The result will be some string like e1ePP6qq5g7u40Ex
Thinking that I must have munged something, I tried to create a new instance with another name. The new instance's database was also empty:
toolchest monk # koha-create --create-db monasterylibrary Koha instance is empty, no staff user created. Starting Zebra server for monasterylibrary * Starting Koha indexing daemon for monasterylibrary [ OK ]
toolchest monk # mysql -uroot -p ... MariaDB [(none)]> use koha_monasterylibrary; Database changed MariaDB [koha_monasterylibrary]> show tables; Empty set (0.00 sec)
Is this intended?
Yes, the database will only be populated after you have gone through the steps of the webinstaller. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch
I am now the proud new owner of a live Koha installation. Thanks to all of the people who addressed my questions! (-: On Wed, Jul 26, 2017 at 8:48 AM, Michael Kuhn <mik@adminkuhn.ch> wrote:
Hi
I don't know the username for logging into the administrative interface, so
I looked to see what I could find in the database was empty.
You will find the password of the administrative user as follows:
$ INSTANZ="yourinstance" $ sudo xmlstarlet sel -t -v 'yazgfs/config/pass' /etc/koha/sites/$INSTANZ/koha-conf.xml && echo
The result will be some string like
e1ePP6qq5g7u40Ex
Thinking that
I must have munged something, I tried to create a new instance with another name. The new instance's database was also empty:
toolchest monk # koha-create --create-db monasterylibrary Koha instance is empty, no staff user created. Starting Zebra server for monasterylibrary * Starting Koha indexing daemon for monasterylibrary [ OK ]
toolchest monk # mysql -uroot -p
...
MariaDB [(none)]> use koha_monasterylibrary; Database changed MariaDB [koha_monasterylibrary]> show tables; Empty set (0.00 sec)
Is this intended?
Yes, the database will only be populated after you have gone through the steps of the webinstaller.
Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - fundraiser <https://GoFundMe.com/the-holy-mountain> - website <https://cjshayward.com/> .
What was the problem finally? :) On Wed, 26 Jul 2017 at 14:48 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
I am now the proud new owner of a live Koha installation.
Thanks to all of the people who addressed my questions! (-:
On Wed, Jul 26, 2017 at 8:48 AM, Michael Kuhn <mik@adminkuhn.ch> wrote:
Hi
I don't know the username for logging into the administrative interface, so
I looked to see what I could find in the database was empty.
You will find the password of the administrative user as follows:
$ INSTANZ="yourinstance" $ sudo xmlstarlet sel -t -v 'yazgfs/config/pass' /etc/koha/sites/$INSTANZ/koha-conf.xml && echo
The result will be some string like
e1ePP6qq5g7u40Ex
Thinking that
I must have munged something, I tried to create a new instance with another name. The new instance's database was also empty:
toolchest monk # koha-create --create-db monasterylibrary Koha instance is empty, no staff user created. Starting Zebra server for monasterylibrary * Starting Koha indexing daemon for monasterylibrary [ OK ]
toolchest monk # mysql -uroot -p
...
MariaDB [(none)]> use koha_monasterylibrary; Database changed MariaDB [koha_monasterylibrary]> show tables; Empty set (0.00 sec)
Is this intended?
Yes, the database will only be populated after you have gone through the steps of the webinstaller.
Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 <+41%2061%20261%2055%2061> · E mik@adminkuhn.ch · W www.adminkuhn.ch
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - fundraiser <https://GoFundMe.com/the-holy-mountain> - website < https://cjshayward.com/> . _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
There are a few things. The main thing was that as I thought I was instructed on at least one screen, I was looking in koha-conf.xml for a username and password not offered in that file. Given that I did not recognize that the administrative account for a library identified as "monastery" would be "koha_monastery" and the password was such as one would obtain by running koha-passwd, I spent a lot of time trying to log in. I think at least partway through I had two conflicting (possibly partial) installations. There may have been other things too, but I don't remember doing anything heroic to fix them. I think it was mostly a case of my barking up the wrong tree for credentials... On Thu, Jul 27, 2017 at 10:49 AM, Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
What was the problem finally? :)
On Wed, 26 Jul 2017 at 14:48 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
I am now the proud new owner of a live Koha installation.
Thanks to all of the people who addressed my questions! (-:
On Wed, Jul 26, 2017 at 8:48 AM, Michael Kuhn <mik@adminkuhn.ch> wrote:
Hi
I don't know the username for logging into the administrative interface, so
I looked to see what I could find in the database was empty.
You will find the password of the administrative user as follows:
$ INSTANZ="yourinstance" $ sudo xmlstarlet sel -t -v 'yazgfs/config/pass' /etc/koha/sites/$INSTANZ/koha-conf.xml && echo
The result will be some string like
e1ePP6qq5g7u40Ex
Thinking that
I must have munged something, I tried to create a new instance with another name. The new instance's database was also empty:
toolchest monk # koha-create --create-db monasterylibrary Koha instance is empty, no staff user created. Starting Zebra server for monasterylibrary * Starting Koha indexing daemon for monasterylibrary [ OK ]
toolchest monk # mysql -uroot -p
...
MariaDB [(none)]> use koha_monasterylibrary; Database changed MariaDB [koha_monasterylibrary]> show tables; Empty set (0.00 sec)
Is this intended?
Yes, the database will only be populated after you have gone through the steps of the webinstaller.
Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 <+41%2061%20261%2055%2061> · E mik@adminkuhn.ch · W www.adminkuhn.ch
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - fundraiser <https://GoFundMe.com/the-holy-mountain> - website < https://cjshayward.com/> . _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - fundraiser <https://GoFundMe.com/the-holy-mountain> - website <https://cjshayward.com/> .
participants (3)
-
C.J.S. Hayward -
Jonathan Druart -
Michael Kuhn