Topic: Troubleshooting
Topic type:
Helpful hints if things go wrong with your installation.
Originally written by Walter McGinnis, Kete Project Lead for Katipo Communications, Ltd.
Part of the Installation Guide
For other troubleshooting tips, be sure to look in Related Topics below.
Zebra Related Issues
Problem
After installation, on my "Browse" or search results pages, the links to items are go to "http://10.0.0.1/site/topics/show/13-welcome" for example. In other words, they are broken. If I create a new topic or item though, the link for it is correct.
or
After installation you got to "Browse" or search results and you get an error like Connection Error (109).
Solution
You probably forgot to restart your Kete server before "priming the search engine" or the priming didn't work / was incomplete. Zebra, the search engine, was thus fed bad versions of the default topics and items. You'll need to clean out and reprime the search engine. This fix will work if your zebra search index gets out of sync for any reason, though if you have a large amount of records (2,000+) it may be impractical.
(see here for instructions when using Kete 1.0 or earlier)
On Kete 1.1 or later
Kete 1.1 introduced a new web based Zebra search engine priming tool that technical administrators of the site can use to quick rebuild Zerba and solve issues. To use this, login as a user with the "tech admin" role, navigate to the "Administrators Toolbox" > "Rebuild search databases" > and configure what you need.
You may want to specify "skip private records" if your don't have any private versions of your items, but otherwise the default options will be ok. This will now initialize you search database (clear it out), restart it, and run through all items in every basket and add it to the Zebra database. When it's done, you can try Browse again.
Discuss This Topic
There are 22 comments in this discussion.
Read and join this discussion
Both errors above are related to zebra. For whatever reason, I don't seem to get zebra to pull the correct keteaccess up. I get rejected using the correct creds w/ yazclient. Here's 4 commands:
- netstat showing zebra listening;
- ps showing zebrasrv running;
- cat the keteaccess file;
- yaz-client connection attempt w/ keteaccess and port info.
kete@kohavm77:~/apps/kete_stable_dev$ netstat -a | grep 9001
tcp6 0 0 *:9001 *:* LISTEN
kete@kohavm77:~/apps/kete_stable_dev$ ps -ef | grep zebra
kete 5562 1 0 10:36 ? 00:00:00 zebrasrv -f conf/kete-zebra-servers.xml -l /home/kete/apps/kete_trunk_dev/log/zebra.log -p /home/kete/apps/kete_trunk_dev/log/zebra.pid -D
kete 5756 1 0 11:14 ? 00:00:00 zebrasrv -f conf/kete-zebra-servers.xml -l /home/kete/apps/kete_stable_dev/log/zebra.log -p /home/kete/apps/kete_stable_dev/log/zebra.pid -D
kete 6055 3164 0 12:10 pts/0 00:00:00 grep zebra
kete@kohavm77:~/apps/kete_stable_dev$ cat zebradb/keteaccess
kete:ub3r
kete@kohavm77:~/apps/kete_stable_dev$ yaz-client -u kete:ub3r localhost:9001
Authentication set to Open (kete:ub3r)
Connecting...OK.
Sent initrequest.
Connection rejected by v3 target.
ID : 81
Name : Zebra Information Server/GFS/YAZ
Version: 2.0.26/1.128/3.0.26
Init response contains 1 otherInfo unit:
1: otherInfo unit contains 1 diagnostic:
1: code=1011 (Init/AC: Bad Userid and/or Password),
addinfo=''
Options: search present delSet triggerResourceCtrl scan sort extendedServices namedResultSets negotiationModel
Accepted character set : UTF-8
Accepted code language : none
Accepted records in ...: 0
Converting between UTF-8 and UTF-8
Elapsed: 0.006869
Posted on April 5th, 2008 at 6:18 PM
Apparently the colon separator that is in the keteaccess file has to be a slash "/" on the command-line for yaz-client! So that question is answered. However, my kete problems persist...
Posted on April 5th, 2008 at 7:41 PM
I suspect that you are using a later version of YAZ and Zebra than is specified in the installation guide. See this comment for details:
http://old.kete.net.nz/documentation/topics/show/115-preinstall-assumptions#comment-51
Please confirm that you are using the correct versions of YAZ and Zebra.
I hope that we will be able to move to latest versions of Zebra and YAZ in Kete 1.1 or 1.2.
Cheers,
Walter
Posted on April 6th, 2008 at 12:26 AM
So when I go to:
site/search/rebuild_zoom_index?skip_existing=false
What does a user do if they get:
XML Parsing Error: mismatched tag. Expected: </div>.
Location: http://kete.liblime.com/site/search/rebuild_zoom_index?skip_existing=false
Line Number 120, Column 3:</body>
--^
The last time I saw this problem it was related to zebra, but my fixes from last time aren't doing the trick here.
Tags: XML Parsing Error.
Posted on April 8th, 2008 at 5:21 PM
You can work around this error by using Safari browsing in the near term. Sorry, I am at a conference and can't fix the actual bug.
Update 2008-04-09: This bug has been fix in the 1-0-stable branch and will be in trunk soon, too. So shouldn't be an issue anymore.
Tags: rebuild_zoom_index, priming, prime, Zebra
Posted on April 9th, 2008 at 2:32 AM
I finished the install and browsed to my kete installation and got this error:
I installed RMagick : gem install rmagick
but this did nothing.
If I remove the require RMagick line from the account_controller.rb file it still gives me an error to install RMagick.
Also when I do a dpkg -l | grep magick I only see; imagemagick, libmagick9, and libmagick9-dev.
Not sure what I am missing or if the above info will help
MissingSourceFile in AccountController#login
no such file to load -- RMagick
RAILS_ROOT: /home/mschell/apps/kete
Application Trace | Framework Trace | Full Trace
/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'
/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
vendor/rails/activesupport/lib/active_support/dependencies.rb:496:in `require'
vendor/rails/activesupport/lib/active_support/dependencies.rb:342:in `new_constants_in'
vendor/rails/activesupport/lib/active_support/dependencies.rb:496:in `require'
app/controllers/account_controller.rb:1
vendor/rails/activesupport/lib/active_support/dependencies.rb:203:in `load_without_new_constant_marking'
vendor/rails/activesupport/lib/active_support/dependencies.rb:203:in `load_file'
vendor/rails/activesupport/lib/active_support/dependencies.rb:342:in `new_constants_in'
vendor/rails/activesupport/lib/active_support/dependencies.rb:202:in `load_file'
vendor/rails/activesupport/lib/active_support/dependencies.rb:94:in `require_or_load'
vendor/rails/activesupport/lib/active_support/dependencies.rb:248:in `load_missing_constant'
vendor/rails/activesupport/lib/active_support/dependencies.rb:453:in `const_missing'
vendor/rails/activesupport/lib/active_support/dependencies.rb:465:in `const_missing'
vendor/rails/activesupport/lib/active_support/inflector.rb:257:in `constantize'
vendor/rails/activesupport/lib/active_support/core_ext/string/inflections.rb:148:in `constantize'
vendor/rails/actionpack/lib/action_controller/routing.rb:1426:in `recognize'
vendor/rails/actionpack/lib/action_controller/dispatcher.rb:170:in `handle_request'
vendor/rails/actionpack/lib/action_controller/dispatcher.rb:115:in `dispatch'
vendor/rails/actionpack/lib/action_controller/dispatcher.rb:126:in `dispatch_cgi'
vendor/rails/actionpack/lib/action_controller/dispatcher.rb:9:in `dispatch'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/rails.rb:76:in `process'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/rails.rb:74:in `synchronize'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/rails.rb:74:in `process'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:159:in `process_client'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:158:in `each'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:158:in `process_client'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:285:in `run'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:285:in `initialize'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:285:in `new'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:285:in `run'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in `initialize'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in `new'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel.rb:268:in `run'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/configurator.rb:282:in `run'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/configurator.rb:281:in `each'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/configurator.rb:281:in `run'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/bin/mongrel_rails:128:in `run'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/lib/mongrel/command.rb:212:in `run'
/usr/lib/ruby/gems/1.8/gems/mongrel-1.1.4/bin/mongrel_rails:281
/usr/bin/mongrel_rails:19:in `load'
/usr/bin/mongrel_rails:19
This error occurred while loading the following files:
RMagick
Request
Parameters:
{"urlified_name"=>"site"} ---
:return_to_title:
:site_admin:
:user:
flash: !map:ActionController::Flash::FlashHash {}
:return_to: /
Response
Headers:
{"cookie"=>[],
"Cache-Control"=>"no-cache"}
Posted on May 23rd, 2008 at 4:15 PM
Hi mschell,
The Debian install can be funky because of Ruby Gems and Debian packaging philosophy differences. In other words you can get things in an inconsistent state pretty easily. So tread carefully.
First, lets make sure you don't have any Rmagick on the system. During our normal installation we usually install Rmagick with apt-get.
Run this to see if you have that package:
dpkg -l librmagick-ruby1.8
You shouldn't have the gem installed directly. In other words "gem list RMagick" shouldn't return a result. If it does, there may be a conflict.
If neither of the above return anything, I would recommend running this step from the installation guide again:
apt-get install librmagick-ruby1.8 librmagick-ruby-doc
and then restart your server and see if that does the trick.
Let us know if that works or doesn't.
Good luck,
Walter
Update: we no longer suggest installing RMagick from the Debian package. See installation guide topic about installing Kete's required software.
Tags: Rmagick, Installation, Troubleshooting
Posted on May 23rd, 2008 at 8:32 PM
I'm using a freshly installed 1.1 on Debian Lenny. After completing the install and priming the zebra indexes, all searches return a HTTP 500 error. After performing an index rebuild from the admin toolbox, the backgroundrb_debug log contains an error trace starting with the line:
/var/lib/gems/1.8/gems/packet-0.1.7/lib/packet/packet_master.rb:109:in `exec': No such file or directory - packet_worker_runner 13:11:zoom_index_rebuild_worker:63:/home/kete/apps/keteclone/lib/workers:/home/kete/apps/keteclone/script/load_worker_env (Errno::ENOENT)
There is nothing but the skeletal directory tree in the zebradb/public and zebradb/private directories.
Any idea what's going on? What further steps can I take to track down the problem?
Posted on January 22nd, 2009 at 9:46 AM
Hi Clay,
I actually haven't installed on Lenny yet, so I'm not sure our steps are going to be accurate in that context. Good of you to be a pioneer!
Could you give us more details on what your installation set up is? Did you use Ruby Enterprise Edition, Apache, and Passenger or Nginx/Mongrel? Are you working off the latest code in the master branch or 1-1-stable release branch?
Also, do you have any other Rails apps running that are using Backgroundrb? I would suspect not, but if so, there is possible conflict if you don't have things configured to avoid each other.
I would also confirm that your Zebra process is running and healthy by checking log/zebra.log and using "ps auxw | grep zebra" as mentioned in the troubleshooting section.
One big thing to note is that Kete needs to have some work (we're looking for sponsers!) done to be compatible with the latest version of YAZ and Zebra. If you installed from their apt packages, I would recommend to uninstalling them and then installing teh specific versions from source as outlined in the Debian install guide.
Tags: Zebra, Troubleshooting, packet, backgroundrb
Posted on January 22nd, 2009 at 10:40 AM
Hello, Walter. Thank you for looking at this. In response to details about the setup I'm running:
- I'm using Nginx/Mongrel.
- I get the same result with either master or 1-1-stable.
- No other rails apps installed.
- zebrasrv is running. I can also connect to it with yaz-client. All searches result in a 109 error, though, because there are no database files.
- System has yaz-3.0.40 and idzebra-2.0.34 installed.
I was trying to avoid going with the source install of zebra. The conflicts arising from apt/gems are already pretty tough to contend with. However, I can try doing a source install to see if it fixes the problem. Are yaz-2.1.54 and idzebra-2.0.6 still considered the most compatible versions?
It would be helpful to have a sense of how the data gets exported from the database before being fed to zebraidx. Can you point me in the general direction for where I would find that?
Posted on January 22nd, 2009 at 6:51 PM
Your Zebra and Yaz versions are the problem, I'm almost positive. So uninstall what you have and follow the directions for installing from source in http://old.kete.net.nz/documentation/topics/show/116 for the exact versions outlined there, please.
To answer your question about how Kete uses zebraidx to create the records, it doesn't use zebraidx at all. It uses the ZOOM API's Extended Services to talk to the zebrasrv process. This is done through the acts_as_zoom Ruby on Rails plugin that we wrote for Kete. Saving an item in Kete (creating or updating a topic, image, what have you) triggers a corresponding OAI-PMH Dublin Core XML record to be sent the zebrasrv process via the ZOOM API.
The "rebuild zoom indexes" action basically clears out the Zebra databases and does the process over again in a batch for the records you specify, all records being the most common request.
See http://github.com/kete/acts_as_zoom for background info and code on acts_as_zoom if you want. However, simply downgrading your YAZ and Zebra software and then rebuilding your search indexes should do the trick.
Tags: Zebra, Installation, YAZ, Troubleshooting, ZOOM
Posted on January 22nd, 2009 at 8:37 PM
Hi there,
Anyone did run the rebuild search engine at the admin part can let me know how long it take ?
I run this, and still in progress for more than 2 hours now. I also got the Error 500, with the suggestion with start or rebuild the Zebra.
Log in ssh and I see the process still there. This is the first time I try kete, just the default data there, the amount of data is surely not the main issue that make it run so long. Just check the version of Zebra and yaz, the right one for kete 1.1
Is there any way we can track how the rebuilding going ?
Many thanks,
Ann
Posted on March 9th, 2009 at 12:24 PM
Hey Ann,
On my modern computer (2 gig RAM), from start to finish, the rebuild of default data on a new Kete installation takes about 1/2 a minute. So I suspect something is missing that the rebuilder is relying on or something is cuasing the rebuild to stop on the first record.
Take a look at log/backgroundrb_*.log files and see if you notice any errors in the logs. Serious problems will usually have a bracktrace - a few indented lines showing where each method got called. There are also a few sutle errors such as Zebra being offline (or losing its connection).
What does the message on the rebuild screen tell you after about 10-15 seconds? It should update with something to tell you why it stopped.
Regards
Kieran
Tags: rebuild, Zebra, backgroundrb
Posted on March 9th, 2009 at 1:13 PM
Thanks for following this. The error from the backgroundrb.log is
/usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/lib/packet/packet_core.rb:126:in 'bind': Address already in use - bind(2) (Errno::EADDRINUSE)
from /usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/lib/packet/packet_core.rb:126:in 'start_server'
from /usr/webpages/kete/vendor/plugins/backgroundrb/server/lib/master_proxy.rb:17:in 'initialize'
from /usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/lib/packet/packet_master.rb:19:in 'run'
from /usr/webpages/kete/vendor/plugins/backgroundrb/server/lib/master_proxy.rb:14:in 'initialize'
from script/backgroundrb:46:in 'new'
from script/backgroundrb:46
Client disconected
Client disconected
Client disconected
/usr/webpages/kete/vendor/rails/activesupport/lib/active_support/vendor/memcache-client-1.5.0/memcache.rb:663:in 'request_setup': No connection to server (MemCache::MemCacheError)
from /usr/webpages/kete/vendor/rails/activesupport/lib/active_support/vendor/memcache-client-1.5.0/memcache.rb:324:in 'set'
from /usr/webpages/kete/vendor/rails/activesupport/lib/active_support/vendor/memcache-client-1.5.0/memcache.rb:520:in '[]='
from /usr/webpages/kete/vendor/plugins/backgroundrb/server/lib/bdrb_result_storage.rb:45:in '[]='
from /usr/webpages/kete/vendor/plugins/backgroundrb/server/lib/bdrb_result_storage.rb:45:in 'synchronize'
from /usr/webpages/kete/vendor/plugins/backgroundrb/server/lib/bdrb_result_storage.rb:45:in '[]='
from /usr/webpages/kete/lib/workers/zoom_index_rebuild_worker.rb:17:in 'create'
from /usr/webpages/kete/vendor/plugins/backgroundrb/server/lib/meta_worker.rb:134:in 'worker_init'
from /usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/bin/../lib/packet/packet_worker.rb:19:in 'start_worker'
from /usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/bin/packet_worker_runner:33:in 'load_worker'
from /usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/bin/packet_worker_runner:26:in 'initialize'
from /usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/bin/packet_worker_runner:47:in 'new'
from /usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/bin/packet_worker_runner:47
from /usr/bin/packet_worker_runner:19:in 'load'
from /usr/bin/packet_worker_runner:19
Client disconected
Client disconected
Client disconected
/usr/webpages/kete/vendor/rails/activesupport/lib/active_support/vendor/memcache-client-1.5.0/memcache.rb:663:in 'request_setup': No connection to server (MemCache::MemCacheError)
from /usr/webpages/kete/vendor/rails/activesupport/lib/active_support/vendor/memcache-client-1.5.0/memcache.rb:324:in 'set'
from /usr/webpages/kete/vendor/rails/activesupport/lib/active_support/vendor/memcache-client-1.5.0/memcache.rb:520:in '[]='
from /usr/webpages/kete/vendor/plugins/backgroundrb/server/lib/bdrb_result_storage.rb:45:in '[]='
from /usr/webpages/kete/vendor/plugins/backgroundrb/server/lib/bdrb_result_storage.rb:45:in 'synchronize'
from /usr/webpages/kete/vendor/plugins/backgroundrb/server/lib/bdrb_result_storage.rb:45:in '[]='
from /usr/webpages/kete/lib/workers/zoom_index_rebuild_worker.rb:17:in 'create'
from /usr/webpages/kete/vendor/plugins/backgroundrb/server/lib/meta_worker.rb:134:in 'worker_init'
from /usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/bin/../lib/packet/packet_worker.rb:19:in 'start_worker'
from /usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/bin/packet_worker_runner:33:in 'load_worker'
from /usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/bin/packet_worker_runner:26:in 'initialize'
from /usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/bin/packet_worker_runner:47:in 'new'
from /usr/lib64/ruby/gems/1.8/gems/packet-0.1.14/bin/packet_worker_runner:47
from /usr/bin/packet_worker_runner:19:in 'load'
from /usr/bin/packet_worker_runner:19The process details is
kete 1769 0.0 0.2 39196 1260 ? Ss 10:19 0:00 zebrasrv -f conf/kete-zebra-servers.xml -l /usr/webpages/kete/log/zebra.log -p /usr/webpages/kete/log/zebra.pid -DThe other thing when running the load_initial records
kete@kete:~> rake zebra:load_initial_records
(in /usr/webpages/kete)
Error while adding record to public zebra instance (Connect failed (10000) localhost:9901).
Initial record added to private zebra instance (OAI identifier: oai::bootstrap:Bootstrap:1).The web page just display the start rebuilding... in progress, and that 's it.
Regards,
Ann
Posted on March 9th, 2009 at 3:46 PM
Looks to be a few issues here. Firstly, something seems to have a lock on the port packet/backgroundrb is trying to use (possible an older instance of backgroundrb). Run the following from the kete root directory:
script/backgroundrb stopThen open config/backgroundrb.yml, change the port number to something else (5 random digets in the 11k range should work). And run the following:
script/backgroundrb startSecondly, it seems that memcached is not accessible. Backgroundrb uses memcached for results storage, so if it's offline, thats likely the cause for the continous spinner you're seeing when rebuilding. Firstly, check if memcache is running.
ps aux | grep memcacheIf not, run the following:
/usr/bin/env memcached -d -m128Then try the ps command again to ensure it's on. If problems persist, google for some help articles about memcached.
Finally, it looks like zebra isn't started when you try to load initial records (Connect failed). Try the following commands in sequence.
rake zebra:stop
rake zebra:init ZEBRA_DB=public
rake zebra:load_initial_records ZEBRA_DB=public
rake zebra:init ZEBRA_DB=private
rake zebra:load_initial_records ZEBRA_DB=privateIf anything goes wrong, then either your password or ports in the database don't match those of the zebra db. Run through the installation again to resolve this.
Tags: rebuild, Zebra, backgroundrb, memcached
Posted on March 9th, 2009 at 5:19 PM
Thanks for following this Kieran.
I already did what you suggested. I just a little concerned about the ip in the backroundrb.yml, I change from 127.0.0.1 to the server address which is similar to 192.168.1.12.
The memcache already started. But I still got the error said
kete@kete:~> rake zebra:load_initial_records ZEBRA_DB=public
(in /usr/webpages/kete)
Error while adding record to public zebra instance (Connect failed (10000) localhost:9901).
Initial record exists, skipping in private.
kete@kete:~> rake zebra:load_initial_records ZEBRA_DB=private
(in /usr/webpages/kete)
Error while adding record to public zebra instance (Connect failed (10000) localhost:9901).
Initial record added to private zebra instance (OAI identifier: oai::bootstrap:Bootstrap:1).
kete@kete:~>
Besides, I just remember the rmagick installtion have some problem, so i try to install it again
gem install rmagick
Building native extensions. This could take a while...
ERROR: Error installing rmagick:
ERROR: Failed to build gem native extension.
/usr/bin/ruby extconf.rb install rmagick
checking for Ruby version >= 1.8.2... yes
checking for gcc... yes
checking for Magick-config... no
Can't install RMagick 2.9.1. Can't find Magick-config in /usr/local/bin:/usr/bin:/sbin:/usr/sbin:/bin:/usr/X11R6/bin:/usr/games:/usr/lib/mit/bin:/usr/lib/mit/sbin
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers. Check the mkmf.log file for more
details. You may need configuration options.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/usr/bin/ruby
Gem files will remain installed in /usr/lib64/ruby/gems/1.8/gems/rmagick-2.9.1 for inspection.
Results logged to /usr/lib64/ruby/gems/1.8/gems/rmagick-2.9.1/ext/RMagick/gem_make.out
I will try to install the whole thing again.
Thanks.
Posted on March 10th, 2009 at 1:49 PM
You may encounter firewall issues (port blocked) if you use the server IP rather than 127.0.0.1 (localhost). Usually the default policy is to allow connections from localhost to localhost. However even that isn't a given.
Have you checked your firewall rules? Are there any rules that might block any of your services ports (Zebra, BackgroundRB, Memcached)?
Posted on March 11th, 2009 at 11:00 AM
Ann Le
said Zebra rebuild
Thanks for your advice about the firewalls. After edit the allow ports and reboot the server. the Zebra seems running now.
I run the rebuils search index engine on the admin tool box, and get this , at least it run and give some feedback.
There was a problem with the rebuild: Init/AC: Bad Userid and/or Password (1011) kete
And here is the log from zebra.log
11:59:22-13/03 [log] zebra_start 2.0.6 ../conf/zebra-private.cfg
11:59:22-13/03 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-marc.so
11:59:22-13/03 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-safari.so
11:59:22-13/03 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-text.so
11:59:22-13/03 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-xml.so
11:59:22-13/03 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-alvis.so
11:59:22-13/03 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-regx.so
11:59:22-13/03 [log] zebra_start 2.0.6 ../conf/zebra-public.cfg
11:59:22-13/03 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-marc.so
11:59:22-13/03 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-safari.so
11:59:22-13/03 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-text.so
11:59:22-13/03 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-xml.so
11:59:22-13/03 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-alvis.so
11:59:22-13/03 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-regx.so
11:59:22-13/03 [server] Adding dynamic listener on tcp:localhost:9902 id=1
11:59:22-13/03 [server] Adding dynamic listener on tcp:@:9901 id=2
11:59:22-13/03 [server] Starting server zebrasrv pid=3798
11:59:25-13/03 zebrasrv(1) [session] Session - OK 1 tcp:127.0.0.1 3808
11:59:25-13/03 zebrasrv(1) [request] Auth idPass kete -
11:59:25-13/03 zebrasrv(1) [request] Init ERROR 1011 ID:81/81 Name:ZOOM-C/YAZ Version:1.116/2.1.54
11:59:25-13/03 zebrasrv(2) [session] Session - OK 2 tcp:127.0.0.1 3809
11:59:25-13/03 zebrasrv(2) [request] Auth idPass kete -
11:59:25-13/03 zebrasrv(2) [request] Init ERROR 1011 ID:81/81 Name:ZOOM-C/YAZ Version:1.116/2.1.54
11:59:25-13/03 zebrasrv(3) [session] Session - OK 3 tcp:127.0.0.1 3810
11:59:25-13/03 zebrasrv(3) [request] Auth idPass kete -
11:59:25-13/03 zebrasrv(3) [request] Init ERROR 1011 ID:81/81 Name:ZOOM-C/YAZ Version:1.116/2.1.54
11:59:25-13/03 zebrasrv(4) [session] Session - OK 4 tcp:127.0.0.1 3811
11:59:25-13/03 zebrasrv(4) [request] Auth idPass kete -
11:59:25-13/03 zebrasrv(4) [request] Init ERROR 1011 ID:81/81 Name:ZOOM-C/YAZ Version:1.116/2.1.54
11:59:25-13/03 zebrasrv(5) [session] Session - OK 5 tcp:127.0.0.1 3812
11:59:25-13/03 zebrasrv(5) [request] Auth idPass kete -
11:59:25-13/03 zebrasrv(5) [request] Init ERROR 1011 ID:81/81 Name:ZOOM-C/YAZ Version:1.116/2.1.54
Is there something with the database account username and password ?
I am able to connect to mysql with
mysql -u kete -p kete_production
Many thanks again,
Ann
Posted on March 13th, 2009 at 12:16 PM
Good to hear you are making progess.
Zebra also uses the terminology "databases" to describe its distinct domains of indexes. So that authentication error is Zebra.
I suspect that you are using a later version of Zebra and YAZ than is specified in the Installation Guide. This is the usual cause of this error.
If this is the case, you will need to uninstall Zebra and YAZ and install versions Zebra idzebra-2.0.6 and YAZ yaz-2.1.54.
If you have these versions, then I would check permissions on zebradb/keteaccess are correct. You should also match that the username/password match what is set up by using Administrator's Toolbox > Z39.50 search databases to see what your settings are there.
Hope this helps,
Walter
P.S. - We would love sponsorship to do the work to make Kete work with later versions of Zebra and YAZ.
Tags: Zebra, Installation, YAZ, Troubleshooting, ZOOM
Posted on March 15th, 2009 at 10:57 AM
Just a tip, I was installing kete on Lenny recently and saw this error:
ActionView::TemplateError (unable to read font `/usr/local/lib/ImageMagick-6.4.3/config//usr/share/ghostscript/fonts/n019003l.pfb': `(null)') on line #55 of account/signup.rhtml:And realized I had forgotten to add the compile option to ImageMagick which was mentioend here:
root@host: # ./configure --with-gs-font-dir=/usr/share/fonts/type1/gsfonts
Posted on July 6th, 2009 at 7:16 PM
In the configuration file that Kete set up for the public Zebra database it used to specify "@" for what hosts were allowed. This notation apparently is no longer acceptable as of Zebra 2.0.45 and Kete will be unable to connect to the public Zebra database.
So if you have upgrade Zebra to 2.0.45 or above, to fix this (unless you want to allow non-localhost requests, in which case you will need to do further research) edit zebradb/conf/kete-zebra-servers.xml to replace this:
<listen id="publicserver">tcp:@:9901</listen>with this:
<listen id="publicserver">tcp:localhost:9901</listen>Then restart zebra like so (from your app directory as your app user, i.e. kete user):
rake zebra:stop
rake zebra:start
Hopefully that should do the trick for you.
Note: the latest Kete code does this change for you and you shouldn't notice a difference if you are doing a fresh install.
Tags: Zebra, Troubleshooting, xml, configuration, upgrading zebra
Posted on March 7th, 2011 at 12:19 PM
Joe Atzberger
said XML error
When I request the first link in "stable", I get an XML error.
XML Parsing Error: mismatched tag. Expected: </div>.
Location: http://kete.liblime.com/site/search/rebuild_zoom_index?skip_existing=false
Line Number 120, Column 3:
</body>
--^
When I try it on "trunk", I get:
NoMethodError in SearchController#rebuild_zoom_index
RAILS_ROOT: /home/kete/apps/kete_trunk_dev
Request
Parameters:
{"skip_existing"=>"false","urlified_name"=>"site"}
Show session dump
--- :skip_existing: "false" :record_count: 0 :return_to: / :site_admin: true :done: false :user: 1 :return_to_title: Welcome :number_of_results_per_page: 10 :start_id: 1 :last: 1 :zoom_db: :zoom_class: Topic :end_id: end flash: !map:ActionController::Flash::FlashHash {}Response
Headers:
{"Status"=>"200 OK","cookie"=>[],
"Content-Type"=>"text/xml",
"Cache-Control"=>"no-cache"}