On Wed, 18 Nov, 2020, 4:13 am Charles Kelley, wrote
Yes, of course. I was just wondering what would happen to the current
> superduper.
>
Nothing. Stays dormant. Usually what most of my users do is to create a new
superlibrarian acct, log in using the new account, change the old
Hi, Fred!
In our latest exchange, 18 Nov. 2020 at 3:05 [JST], you wrote:
As far as I know, you can have as many superlibrarians as you want--it just
> depends on what your budget for red capes is.* In our system, 60% of our
> staff are superlibrarians. And before you all let out a collective
Hi Elaine,
Compared to what we have (19.11.11) the only difference is that we have
not set branch code.
What if you "expire" all your news and create a plain text news? or maybe
just keep your last test new?
Regards
Alvaro
Hi James
- Have you changed something lately (iptables/firewall/apache config?
- Is opac running?
- Check apache logs. (error and access, both in apache and koha logs)
- Check listening ports (sudo netstat -talpan | grep LISTEN )
Regards,
Alvaro
Hi Charles,
As far as I know, you can have as many superlibrarians as you want--it just
depends on what your budget for red capes is.* In our system, 60% of our staff
are superlibrarians. And before you all let out a collective gasp, that's three
accounts out of five.
*Actually, you don't
Hi Alvaro,
It is not a new install. The server has been running for over an year now
without any hitch.
Sudo service apache2/memcached/mysql show the services as running.
Kindly direct me further on how to check if the server is listening to the
ports and on the error logs.
Thanks a lot for
Hi James
Is it a new install? Do you have access to OPAC page?
Check that apache is really running and listening to the mentioned port.
Also check apache logs for any error/message that will help you find the
cause
Regards,
Alvaro
Hello team,
I cannot connect to my instance even when I try logging in from the
production server itself.
The browsers response "Unable to connect: Firefox can’t establish a
connection to the server at 127.0.0.1:8080"
All the processes seem to be running
Im running koha 19.11 on ubuntu 16.04
Hello, Jonathan!
In our latest exchange, on 17 Nov. 2020 at 7:03 PM [JST], you wrote:
The credentials from the koha-conf.xml file cannot be used to login
> into Koha. Use your regular user.
>
I tried superlibrarian. Failure. If it happens again -- it has happened
several times over the
Hello Darius,
What did you do? Did you just install Koha? If so, which documentation
did you follow?
There is a connection issue between Koha and your DBMS (MySQL or MariaDB).
Did you install the mariadb-server package? See
https://wiki.koha-community.org/wiki/Koha_on_Debian
You should also
Hi Charles,
The credentials from the koha-conf.xml file cannot be used to login
into Koha. Use your regular user.
Or use the misc/devel/create_superlibrarian.pl script to create a
superlibrarian user.
Regards,
Jonathan
Le mar. 17 nov. 2020 à 04:03, Charles Kelley a écrit :
>
> Hello, all!
>
>
11 matches
Mail list logo