Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

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.dru...@bugs.koha-community.org> wrote:

> What was the problem finally? :)
>
> On Wed, 26 Jul 2017 at 14:48 C.J.S. Hayward <c...@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 <m...@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 m...@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.hayw...@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.hayw...@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

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

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  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 m...@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  - email
 - fundraiser
 - website 
.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

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 <c...@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 <l...@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
>>
>>
>> On 26/07/17 13:24, Jonathan Druart wrote:
>> > 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 <c...@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.dru...@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 <c...@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.dru...@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) 

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

Thank you.

What is the default administrative username? Specifically, if my instance
is named "library", is it "koha_library", "kohaadmin", or something else?


Thanks,

On Tue, Jul 25, 2017 at 8:24 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> 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 <c...@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.dru...@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 <c...@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.dru...@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 <c...@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
> 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.dru...@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 <c...@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
> >> >> >> > 
> >> >> >> >   = 2.4>
> >

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

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.dru...@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 <c...@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.dru...@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 <c...@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 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.dru...@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 <c...@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
> >> >> > 
> >> >> >   = 2.4>
> >> >> >Define instance "library"
> >> >> >   
> >> >> >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
> >> >> > 
> >> >> >
> >> >> > # Intranet
> >> >> > Listen 7028
> >> >> > 
> >> >> >   = 2.4>
> >> >> >Define instance "library"
> >> >> >   
> >> >> >Include /etc/koha/apache-shared.conf
> >> >> > #  Include /etc/koha/apache-shared-disable.conf
> >> >> > #  Include /etc/koha/apache-shared-intranet-plack.conf
> 

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

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.dru...@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 <c...@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 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.dru...@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 <c...@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
> >> > 
> >> >   = 2.4>
> >> >Define instance "library"
> >> >   
> >> >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
> >> > 
> >> >
> >> > # Intranet
> >> > Listen 7028
> >> > 
> >> >   = 2.4>
> >> >Define instance "library"
> >> >   
> >> >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
> >> > 
> >> > ~
> >> >
> >> >
> >> > 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,
> >> >
> >> >
> >> > On Tue, Jul 25, 2017 at 11:47 PM, Jonathan Druart <
> >> > jonathan.dru...@bugs.koha-community.org> wrote:
> >> >
> >> >> If you reach the "system maintenance" screen that means you are
> hitting
> >> >> the
> >> >> OPAC interface, not the staff interface.
> >> >> Try on :8080
> >> >>
> >> >> On Tue, 25 Jul 2017 at 17:17 C.J.S. Hayward <c...@cjshayward.com>
> >> wrote:
> >> >>
> >> >> > Let me send off this email, and I'll report a bug.
> >

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

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

  = 2.4>
   Define instance "library"
  
   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


# Intranet
Listen 7028

  = 2.4>
   Define instance "library"
  
   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

~


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,


On Tue, Jul 25, 2017 at 11:47 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> If you reach the "system maintenance" screen that means you are hitting the
> OPAC interface, not the staff interface.
> Try on :8080
>
> On Tue, 25 Jul 2017 at 17:17 C.J.S. Hayward <c...@cjshayward.com> wrote:
>
> > Let me send off this email, and I'll report a bug.
> >
> > N.B. Koha is installed in some sense, but when I try to access the
> > webinstaller I got maintenance mode:
> >
> > System Maintenance
> >
> > The Koha online catalog is offline for system maintenance. We'll be back
> > soon! If you have any questions, please contact the site administrator
> >
> > A brief search turned up
> > https://lists.katipo.co.nz/public/koha/2013-December/038208.html which
> > picked up in a possible email typo specifying a port as 8008. This
> > suggestion appears to be irrelevant because if the OP had tried to access
> > Koha on 8008 and hadn't added anything else listening on that port, the
> > error would be "Connection refused", not "System maintenance".
> >
> > On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart <
> > jonathan.dru...@bugs.koha-community.org> wrote:
> >
> >> Try with --create-db:
> >>   koha-create --create-db library
> >>
> >> The doc says that --create-db is the default value, but it does not seem
> >> to
> >> work.
> >> Could you report the bug?
> >>
> >> On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward <c...@cjshayward.com>
> wrote:
> >>
> >> > Thank you. I've used koha-remove, and uninstalled and reinstalled
> >> > koha-common, including setting an a2enmod.
> >> >
> >> > Right now I have an /etc/koha heirarchy that has a lot of stuff in it,
> >> but
> >> > /etc/koha/sites is an empty directory *after* trying to run
> "koha-create
> >> > library":
> >> >
> >> > toolchest sites # koha-create library
> >> > failed to load external entity "/etc/koha/sites/library/koha-
> conf.xml"
> >> >
> >> > How can I create or get an appropriate koha-conf.xml? I notice that
> >> there
> >> > is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing
> to
> >> > ideally transform it to make /etc/koha/sites/library/koha-conf.xml
> (and
> >> > anything else that should be in /etc/koha/sites/library/)?
> >> >
> >> > On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden <dear...@sarsf.org>
> >> wrote:
> >> >
> >> > > If you installed using the packages I believe you can use
> koha-remove
> >> .
> >> > > See here: https://wiki.koha-community.
> org/wiki/Commands_provided_by_
> >> > > the_Debian_packages#koha-remove
> >> > >
> >> > > Doug
> >> > >
> >> > > -Original Message-
> >> > > From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

I've filed a bug at
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18983

On Tue, Jul 25, 2017 at 11:17 PM, C.J.S. Hayward <c...@cjshayward.com>
wrote:

> Let me send off this email, and I'll report a bug.
>
> N.B. Koha is installed in some sense, but when I try to access the
> webinstaller I got maintenance mode:
>
> System Maintenance
>
> The Koha online catalog is offline for system maintenance. We'll be back
> soon! If you have any questions, please contact the site administrator
>
> A brief search turned up https://lists.katipo.co.nz/
> public/koha/2013-December/038208.html which picked up in a possible email
> typo specifying a port as 8008. This suggestion appears to be irrelevant
> because if the OP had tried to access Koha on 8008 and hadn't added
> anything else listening on that port, the error would be "Connection
> refused", not "System maintenance".
>
> On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
>
>> Try with --create-db:
>>   koha-create --create-db library
>>
>> The doc says that --create-db is the default value, but it does not seem
>> to
>> work.
>> Could you report the bug?
>>
>> On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward <c...@cjshayward.com> wrote:
>>
>> > Thank you. I've used koha-remove, and uninstalled and reinstalled
>> > koha-common, including setting an a2enmod.
>> >
>> > Right now I have an /etc/koha heirarchy that has a lot of stuff in it,
>> but
>> > /etc/koha/sites is an empty directory *after* trying to run "koha-create
>> > library":
>> >
>> > toolchest sites # koha-create library
>> > failed to load external entity "/etc/koha/sites/library/koha-conf.xml"
>> >
>> > How can I create or get an appropriate koha-conf.xml? I notice that
>> there
>> > is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to
>> > ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and
>> > anything else that should be in /etc/koha/sites/library/)?
>> >
>> > On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden <dear...@sarsf.org>
>> wrote:
>> >
>> > > If you installed using the packages I believe you can use koha-remove
>> .
>> > > See here: https://wiki.koha-community.org/wiki/Commands_provided_by_
>> > > the_Debian_packages#koha-remove
>> > >
>> > > Doug
>> > >
>> > > -Original Message-
>> > > From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of
>> C.J.S.
>> > > Hayward
>> > > Sent: Tuesday, July 25, 2017 11:18 AM
>> > > To: koha@lists.katipo.co.nz
>> > > Subject: [Koha] Wiping all partial or full Koha isntallation(s) and
>> > > installing stable under Mint
>> > >
>> > > I have a virtual machine that may have two conflicting Koha
>> > installations.
>> > >
>> > > What, if anything, can I do that will wipe all Koha installations
>> > > completely, and install a new stable from scratch, following
>> > > https://wiki.koha-community.org/wiki/Debian?
>> > >
>> > > I don't know if I *exactly* need to go so far as to delete details
>> like
>> > the
>> > > Koha repository in aptitude... but I am willing to do so if I am
>> > advised. I
>> > > do think it would be better to wipe any Koha-created directory
>> > heirarchies,
>> > > and drop any Koha-related databases.
>> > >
>> > > (Note: My system doesn't contain any valuable information *in* Koha;
>> the
>> > > only loss would be the time and energy to delete and rebuild the
>> > > installation.)
>> > >
>> > > --
>> > > christos Jonathan Seth Hayward,
>> > > An Orthodox Christian author.
>> > > Amazon <http://amazon.com/author/cjshayward> - email
>> > > <christos.jonathan.hayw...@gmail.com> - website <
>> https://cjshayward.com/
>> > >.
>> > > ___
>> > > 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

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

Let me send off this email, and I'll report a bug.

N.B. Koha is installed in some sense, but when I try to access the
webinstaller I got maintenance mode:

System Maintenance

The Koha online catalog is offline for system maintenance. We'll be back
soon! If you have any questions, please contact the site administrator

A brief search turned up
https://lists.katipo.co.nz/public/koha/2013-December/038208.html which
picked up in a possible email typo specifying a port as 8008. This
suggestion appears to be irrelevant because if the OP had tried to access
Koha on 8008 and hadn't added anything else listening on that port, the
error would be "Connection refused", not "System maintenance".

On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> wrote:

> Try with --create-db:
>   koha-create --create-db library
>
> The doc says that --create-db is the default value, but it does not seem to
> work.
> Could you report the bug?
>
> On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward <c...@cjshayward.com> wrote:
>
> > Thank you. I've used koha-remove, and uninstalled and reinstalled
> > koha-common, including setting an a2enmod.
> >
> > Right now I have an /etc/koha heirarchy that has a lot of stuff in it,
> but
> > /etc/koha/sites is an empty directory *after* trying to run "koha-create
> > library":
> >
> > toolchest sites # koha-create library
> > failed to load external entity "/etc/koha/sites/library/koha-conf.xml"
> >
> > How can I create or get an appropriate koha-conf.xml? I notice that there
> > is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to
> > ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and
> > anything else that should be in /etc/koha/sites/library/)?
> >
> > On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden <dear...@sarsf.org> wrote:
> >
> > > If you installed using the packages I believe you can use koha-remove .
> > > See here: https://wiki.koha-community.org/wiki/Commands_provided_by_
> > > the_Debian_packages#koha-remove
> > >
> > > Doug
> > >
> > > -Original Message-
> > > From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of
> C.J.S.
> > > Hayward
> > > Sent: Tuesday, July 25, 2017 11:18 AM
> > > To: koha@lists.katipo.co.nz
> > > Subject: [Koha] Wiping all partial or full Koha isntallation(s) and
> > > installing stable under Mint
> > >
> > > I have a virtual machine that may have two conflicting Koha
> > installations.
> > >
> > > What, if anything, can I do that will wipe all Koha installations
> > > completely, and install a new stable from scratch, following
> > > https://wiki.koha-community.org/wiki/Debian?
> > >
> > > I don't know if I *exactly* need to go so far as to delete details like
> > the
> > > Koha repository in aptitude... but I am willing to do so if I am
> > advised. I
> > > do think it would be better to wipe any Koha-created directory
> > heirarchies,
> > > and drop any Koha-related databases.
> > >
> > > (Note: My system doesn't contain any valuable information *in* Koha;
> the
> > > only loss would be the time and energy to delete and rebuild the
> > > installation.)
> > >
> > > --
> > > christos Jonathan Seth Hayward,
> > > An Orthodox Christian author.
> > > Amazon <http://amazon.com/author/cjshayward> - email
> > > <christos.jonathan.hayw...@gmail.com> - website <
> https://cjshayward.com/
> > >.
> > > ___
> > > 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.hayw...@gmail.com> - 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.hayw...@gmail.com> - website <https://cjshayward.com/>.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

Thank you. I've used koha-remove, and uninstalled and reinstalled
koha-common, including setting an a2enmod.

Right now I have an /etc/koha heirarchy that has a lot of stuff in it, but
/etc/koha/sites is an empty directory *after* trying to run "koha-create
library":

toolchest sites # koha-create library
failed to load external entity "/etc/koha/sites/library/koha-conf.xml"

How can I create or get an appropriate koha-conf.xml? I notice that there
is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to
ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and
anything else that should be in /etc/koha/sites/library/)?

On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden <dear...@sarsf.org> wrote:

> If you installed using the packages I believe you can use koha-remove .
> See here: https://wiki.koha-community.org/wiki/Commands_provided_by_
> the_Debian_packages#koha-remove
>
> Doug
>
> -Original Message-
> From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of C.J.S.
> Hayward
> Sent: Tuesday, July 25, 2017 11:18 AM
> To: koha@lists.katipo.co.nz
> Subject: [Koha] Wiping all partial or full Koha isntallation(s) and
> installing stable under Mint
>
> I have a virtual machine that may have two conflicting Koha installations.
>
> What, if anything, can I do that will wipe all Koha installations
> completely, and install a new stable from scratch, following
> https://wiki.koha-community.org/wiki/Debian?
>
> I don't know if I *exactly* need to go so far as to delete details like the
> Koha repository in aptitude... but I am willing to do so if I am advised. I
> do think it would be better to wipe any Koha-created directory heirarchies,
> and drop any Koha-related databases.
>
> (Note: My system doesn't contain any valuable information *in* Koha; the
> only loss would be the time and energy to delete and rebuild the
> installation.)
>
> --
> christos Jonathan Seth Hayward,
> An Orthodox Christian author.
> Amazon <http://amazon.com/author/cjshayward> - email
> <christos.jonathan.hayw...@gmail.com> - website <https://cjshayward.com/>.
> ___
> 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.hayw...@gmail.com> - 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] Wiping all partial or full Koha isntallation(s) and installing stable under Mint

[C.J.S. Hayward]

I have a virtual machine that may have two conflicting Koha installations.

What, if anything, can I do that will wipe all Koha installations
completely, and install a new stable from scratch, following
https://wiki.koha-community.org/wiki/Debian?

I don't know if I *exactly* need to go so far as to delete details like the
Koha repository in aptitude... but I am willing to do so if I am advised. I
do think it would be better to wipe any Koha-created directory heirarchies,
and drop any Koha-related databases.

(Note: My system doesn't contain any valuable information *in* Koha; the
only loss would be the time and energy to delete and rebuild the
installation.)

-- 
christos Jonathan Seth Hayward,
An Orthodox Christian author.
Amazon  - email
 - website .
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Difficulties getting 17.05.01 to talk with MariaDB under Mint 18.1

[C.J.S. Hayward]

Thank you; worked like a charm!

I quoted your email in a comment for breadacrumb purposes. Stupid question:
In Bugzilla, if a defect is essentially resolved by stated workaround, what
is the appropriate resolution? None of the suboptions for "Resolved" seemed
to match giving a workaround.

On Thu, Jun 29, 2017 at 8:56 PM, Tim Young <tim.yo...@lightsys.org> wrote:

> Hi,
>
> This sounds like it is because of an odd "feature" of mysql which is not
> always present.
>
> This page: https://askubuntu.com/questions/766334/cant-login-as-mysql-
> user-root-from-normal-user-account-in-ubuntu-16-04
>
> with the answer from "Todor", explains that mysql will change over to
> using an auth_socket "plugin."  So, instead of using password
> authentication, part of the permission is blocked by unix file-level
> permissions.
>
> The simple solution:
>
>sudo mysql -u root
>update mysql.user set plugin = 'mysql_native_password' where
> User='root';
>FLUSH PRIVILEGES;
>
> Then you should be able to connect up as root even if you are not a root
> user.
>
> After that, you should be able to run the script.
>
> - Tim
>
>
> On 6/29/2017 10:10 AM, C.J.S. Hayward wrote:
>
>> I posted https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18852
>> and
>> Katrin encouraged me to post to the list where it might get more
>> attention.
>>
>> My bug description, very lightly reformatted, is:
>>
>> As of 17.05.01, I was told there were reports of successful
>> installations. However, I have not been able to reproduce such.
>>
>> I had earlier made a couple of attempts to add Koha to a multipurpose
>> appliance, and that remains my end goal. However, when I tried to back
>> up, I saw the same issue verbatim.
>>
>> What I have done today was:
>>
>> Download a fresh Linux Mint 18.1 ISO.
>>
>> Build a VirtualBox VM with the ISO, with mostly default features and
>> with third-party addons, and also enabling auto-login, but in general
>> intended to be a plain vanilla install.
>>
>> Rebooted; installed Chrome and touched /etc/sudoers, ran "aptitude
>> update"; ran "aptitude upgrade", installed MariaDB, and rebooted
>> again.
>>
>> Followed the steps, including a couple of a2enmod enablings, and
>> created a virtual site.
>>
>> I was able to edit passwords in /etc/koha/.../koha-conf.xml, and enter
>> the web setup wizard.
>>
>> However, I experienced identical output from the installer: at a
>> certain point, it says:
>>
>>
>> Software error:
>>
>> DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed:
>> Access denied for user 'root'@'localhost' at
>> /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1492. at
>> /usr/share/koha/lib/Koha/Database.pm line 100
>>
>> For help, please send mail to the webmaster ([no address given]),
>> giving this error message and the time and date of the error.
>>
>>
>> I am having difficulties with MariaDB and my difficulties may be
>> contributing to the problem.
>>
>> My understanding, as inherited from MySQL, is that "mysql -uroot -p",
>> for any account that will run it, will check a password and, if you
>> have root's password set, will let you into the MySQL root command
>> line if and only if you type the password exactly.
>>
>> The behavior I have observed is that as root "mysql -uroot" does not
>> prompt for a password, but just logs you in, and "mysql -uroot -p"
>> prompts for a password, but will accept any password, the empty
>> password included. However, from an unprivileged account, "mysql
>> -uroot -p" prompts for a password, but none of the passwords I've
>> tried have worked; I've tried and used values as set in my customized
>> koha-conf.xml, and every single password is rejected.
>>
>> I believe that this command line behavior is a symptom of the same
>> problem quoted above: permission is being denied for user
>> 'root'@'localhost' where the action in question would be permitted for
>> any account with UID 0 and no account with any other UID.
>>
>> Again, this is after the 17.05.01 release, where it was reported to me
>> that some people have had success. The system setup shows a couple of
>> my personal idiosyncracies, but is meant to be awfully close to a
>> procedure of "Step 1: Create a new Linux Mint VM. Step 2: Install
>> Koha." The behavior is the same between the fresh new VM running
>> 17.05.01, and an "

[Koha] Difficulties getting 17.05.01 to talk with MariaDB under Mint 18.1

[C.J.S. Hayward]

I posted https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18852 and
Katrin encouraged me to post to the list where it might get more attention.

My bug description, very lightly reformatted, is:

As of 17.05.01, I was told there were reports of successful
installations. However, I have not been able to reproduce such.

I had earlier made a couple of attempts to add Koha to a multipurpose
appliance, and that remains my end goal. However, when I tried to back
up, I saw the same issue verbatim.

What I have done today was:

Download a fresh Linux Mint 18.1 ISO.

Build a VirtualBox VM with the ISO, with mostly default features and
with third-party addons, and also enabling auto-login, but in general
intended to be a plain vanilla install.

Rebooted; installed Chrome and touched /etc/sudoers, ran "aptitude
update"; ran "aptitude upgrade", installed MariaDB, and rebooted
again.

Followed the steps, including a couple of a2enmod enablings, and
created a virtual site.

I was able to edit passwords in /etc/koha/.../koha-conf.xml, and enter
the web setup wizard.

However, I experienced identical output from the installer: at a
certain point, it says:


Software error:

DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed:
Access denied for user 'root'@'localhost' at
/usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1492. at
/usr/share/koha/lib/Koha/Database.pm line 100

For help, please send mail to the webmaster ([no address given]),
giving this error message and the time and date of the error.


I am having difficulties with MariaDB and my difficulties may be
contributing to the problem.

My understanding, as inherited from MySQL, is that "mysql -uroot -p",
for any account that will run it, will check a password and, if you
have root's password set, will let you into the MySQL root command
line if and only if you type the password exactly.

The behavior I have observed is that as root "mysql -uroot" does not
prompt for a password, but just logs you in, and "mysql -uroot -p"
prompts for a password, but will accept any password, the empty
password included. However, from an unprivileged account, "mysql
-uroot -p" prompts for a password, but none of the passwords I've
tried have worked; I've tried and used values as set in my customized
koha-conf.xml, and every single password is rejected.

I believe that this command line behavior is a symptom of the same
problem quoted above: permission is being denied for user
'root'@'localhost' where the action in question would be permitted for
any account with UID 0 and no account with any other UID.

Again, this is after the 17.05.01 release, where it was reported to me
that some people have had success. The system setup shows a couple of
my personal idiosyncracies, but is meant to be awfully close to a
procedure of "Step 1: Create a new Linux Mint VM. Step 2: Install
Koha." The behavior is the same between the fresh new VM running
17.05.01, and an "everything but the kitchen sink" multitool of an
appliance.

What can I do to let Koha talk to MariaDB as 'root'@'localhost'?


Thanks,

-- 
[image: Christos Jonathan Seth Hayward]  *Christos
Jonathan Seth Hayward *, an Orthodox Christian
author (*main site * • *bookshelf
*).

If you'd like to just barely sample my writing, I invite you to read The
Angelic Letters  and Doxology
.

I am seeking to reach Mount Athos to enter monastic repentance for the rest
of my life: see
GoFundMe.com/the-holy-mountain 
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha