All Results in discussion
showing 246-250 results of 478 [ ]
Zebra Issues Looks like the cause was that that publicserver and privateserver values in zerba/conf/kete-zebra-servers.xml had the protocol and host, but were missing port numbers. A quick look at the
rake zebra:load_initial_records(in /home/kete/apps/kapkete/releases/20091015004405)rake aborted!uninitialized constant SITE_NAME and with --trace: kete@kete-prod:~/apps/kapkete/current$ rake zebra:load_initial_records --trace(in /home/kete/apps/kapkete/releases/20091015004405)** Invoke zebra:load_initial_records (first_time)** Invoke environment (first_time)** Execute environment** Execute zebra:load_initial_recordsrake aborted!uninitialized constant SITE_NAME/home/kete/apps/kapkete/releases/20091015004405/vendor/rails/activesupport/lib/active_support/dependencies.rb:443:in `load_missing_constant'/home/kete/apps/kapkete/releases/20091015004405/vendor/rails/activesupport/lib/active_support/dependencies.rb:80:in `const_missing'/home/kete/apps/kapkete/releases/20091015004405/vendor/rails/activesupport/lib/active_support/dependencies.rb:92:in
Update: the below comment is no longer relevant. You may use the latest versions of YAZ and Zebra. The comment is left in place to reflect the history of the
Ok, it's good to verify that that is not the cause. I'll see if I can replicate the issue over here. If I need further information, I 'll email you.
hello , i used this command : rake zebra:load_initial_records but there is no change , the error is the same before Unsupported Truncation attribute (120) 3 and the zebra log
