EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #03955
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: Bazaar command line install
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Re: Bazaar command line install
- From: Andrew Beeken <anbeeken@lincoln.ac.uk>
- Date: Thu, 19 Feb 2015 11:06:22 +0000
Thanks Peter! Yes, it seems to be related to the stream it’s receiving. I’m wondering if the URL is misconfigured somewhere - what address should it be going to to retrieve the list? On 19/02/2015 09:58, "peter" <pjw@repositoryservices.co.uk> wrote: >Hi > >To install a bazaar package from the command line you could use Tim's >gitaar tools available at: https://github.com/eprintsug/gitaar (which >will help you work wth the rioxx2 github project at >https://github.com/eprintsug) plus the epm tools from >https://github.com/eprints/eprints/tree/3.3/tools (n.b. not sure I have >selected the right branch). > >I am assuming that your problem is that it is just the "available" >screen that is not working i.e. that the other parts of the repository >are working fine. The reason for this assumption is that it could mean >that the xml parse errors relate to the data being parsed rather than >the libxml libraries being used to do the parsing. If that is the case >then it would be worth using wget to verify what you get when you >request the available packages from the server that is showing the error >i.e. do you get valid xml or is the request failing in some way? > >If this is your live server then obviously backup all your data before >changing anything with the bazaar (some packages will tidy up after >themselves and thus remove any data created using that bazaar package). >Once you have good backups you can also try looking in your lib/epm dir >to see what packages are installed/enabled and then use the tools/epm >utility to disable them N.B. did you read that warning about lost data >when you disable a bazaar package :) > >If my assumption is wrong please ignore the above :) > >Thanks >Peter > > > >On 19/02/15 09:16, Andrew Beeken wrote: >> Okay, following up this and doing some research of my own it looks like >> the GUI is our only option here (trying to get the recently released >>Rioxx >> plugin working) - so, let¹s try and get the Bazaar working. I¹ve had a >> look in the Apache error log and this is what I see: >> >> [Thu Feb 19 09:12:40 2015] [error] Empty Stream at >> /usr/lib/perl5/XML/LibXML.pm line >> 877\n\tXML::LibXML::parse_fh('XML::LibXML=HASH(0x7f488b4a6f38)', >> 'GLOB(0x7f488b68a610)') called at /usr/lib/perl5/XML/LibXML/SAX.pm line >> 99\n\teval {...} called at /usr/lib/perl5/XML/LibXML/SAX.pm line >> 98\n\tXML::LibXML::SAX::_parse('XML::LibXML::SAX=HASH(0x7f488b4c3d58)') >> called at /usr/lib/perl5/XML/LibXML/SAX.pm line >> >>54\n\tXML::LibXML::SAX::_parse_bytestream('XML::LibXML::SAX=HASH(0x7f488b >>4c >> 3d58)', 'GLOB(0x7f488b68a610)') called at >> /usr/share/eprints3/perl_lib/XML/SAX/Base.pm line >> 2602\n\tXML::SAX::Base::parse('XML::LibXML::SAX=HASH(0x7f488b4c3d58)', >> 'HASH(0x7f488b479630)') called at >> /usr/share/eprints3/perl_lib/XML/SAX/Base.pm line >> >>2631\n\tXML::SAX::Base::parse_file('XML::LibXML::SAX=HASH(0x7f488b4c3d58) >>', >> 'GLOB(0x7f488b68a610)') called at >> /usr/share/eprints3/perl_lib/EPrints/XML/LibXML.pm line >> 137\n\tEPrints::XML::event_parse('GLOB(0x7f488b68a610)', >> 'EPrints::DataObj::SAX::Handler=ARRAY(0x7f488b4d4370)') called at >> /usr/share/eprints3/perl_lib/EPrints/DataObj/EPM.pm line >> 293\n\tEPrints::DataObj::EPM::new_from_file('EPrints::DataObj::EPM', >> 'EPrints::Repository=HASH(0x7f488b693dd8)', 'GLOB(0x7f488b68a610)') >>called >> at /usr/share/eprints3/perl_lib/EPrints/DataObj/EPM.pm line >> 250\n\tEPrints::DataObj::EPM::new('EPrints::DataObj::EPM', >> 'EPrints::Repository=HASH(0x7f488b693dd8)', 'irstats2') called at >> /usr/share/eprints3/perl_lib/EPrints/DataObj/EPM.pm line >> 232\n\tEPrints::DataObj::EPM::map('EPrints::DataObj::EPM', >> 'EPrints::Repository=HASH(0x7f488b693dd8)', 'CODE(0x7f488b4d0b30)') >>called >> at >> >>/usr/share/eprints3/perl_lib/EPrints/Plugin/Screen/Admin/EPM/Available.pm >> line >> >>326\n\tEPrints::Plugin::Screen::Admin::EPM::Available::render_results('EP >>ri >> nts::Plugin::Screen::Admin::EPM::Available=HASH(0x7f488b4...') called at >> >>/usr/share/eprints3/perl_lib/EPrints/Plugin/Screen/Admin/EPM/Available.pm >> line >> >>285\n\tEPrints::Plugin::Screen::Admin::EPM::Available::render('EPrints::P >>lu >> gin::Screen::Admin::EPM::Available=HASH(0x7f488b4...') called at >> /usr/share/eprints3/perl_lib/EPrints/Plugin/Screen/Admin/EPM.pm line >> >>149\n\tEPrints::Plugin::Screen::Admin::EPM::render('EPrints::Plugin::Scre >>en >> ::Admin::EPM=HASH(0x7f488b4a2410)') called at >> /usr/share/eprints3/perl_lib/EPrints/ScreenProcessor.pm line >> 377\n\tEPrints::ScreenProcessor::process('EPrints::ScreenProcessor', >> 'session', 'EPrints::Repository=HASH(0x7f488b693dd8)', 'template', >>undef, >> 'url', '/cgi/users/home') called at /usr/share/eprints3/cgi/users/home >> line >> >>25\n\tModPerl::ROOT::ModPerl::Registry::usr_share_eprints3_cgi_users_home >>:: >> handler('Apache2::RequestRec=SCALAR(0x7f488f751a10)') called at >> /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204\n\teval {...} called >>at >> /usr/lib/perl5/ModPerl/RegistryCooker.pm line >> >>204\n\tModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x7f488f86ab7 >>0) >> ') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line >> >>170\n\tModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0 >>x7 >> f488f86ab70)') called at /usr/lib/perl5/ModPerl/Registry.pm line >> 31\n\tModPerl::Registry::handler('ModPerl::Registry', >> 'Apache2::RequestRec=SCALAR(0x7f488f751a10)') called at -e line >>0\n\teval >> {...} called at -e line 0\n at /usr/lib/perl5/XML/LibXML/SAX.pm line >> 109\n\tXML::LibXML::SAX::_parse('XML::LibXML::SAX=HASH(0x7f488b4c3d58)') >> called at /usr/lib/perl5/XML/LibXML/SAX.pm line >> >>54\n\tXML::LibXML::SAX::_parse_bytestream('XML::LibXML::SAX=HASH(0x7f488b >>4c >> 3d58)', 'GLOB(0x7f488b68a610)') called at >> /usr/share/eprints3/perl_lib/XML/SAX/Base.pm line >> 2602\n\tXML::SAX::Base::parse('XML::LibXML::SAX=HASH(0x7f488b4c3d58)', >> 'HASH(0x7f488b479630)') called at >> /usr/share/eprints3/perl_lib/XML/SAX/Base.pm line >> >>2631\n\tXML::SAX::Base::parse_file('XML::LibXML::SAX=HASH(0x7f488b4c3d58) >>', >> 'GLOB(0x7f488b68a610)') called at >> /usr/share/eprints3/perl_lib/EPrints/XML/LibXML.pm line >> 137\n\tEPrints::XML::event_parse('GLOB(0x7f488b68a610)', >> 'EPrints::DataObj::SAX::Handler=ARRAY(0x7f488b4d4370)') called at >> /usr/share/eprints3/perl_lib/EPrints/DataObj/EPM.pm line >> 293\n\tEPrints::DataObj::EPM::new_from_file('EPrints::DataObj::EPM', >> 'EPrints::Repository=HASH(0x7f488b693dd8)', 'GLOB(0x7f488b68a610)') >>called >> at /usr/share/eprints3/perl_lib/EPrints/DataObj/EPM.pm line >> 250\n\tEPrints::DataObj::EPM::new('EPrints::DataObj::EPM', >> 'EPrints::Repository=HASH(0x7f488b693dd8)', 'irstats2') called at >> /usr/share/eprints3/perl_lib/EPrints/DataObj/EPM.pm line >> 232\n\tEPrints::DataObj::EPM::map('EPrints::DataObj::EPM', >> 'EPrints::Repository=HASH(0x7f488b693dd8)', 'CODE(0x7f488b4d0b30)') >>called >> at >> >>/usr/share/eprints3/perl_lib/EPrints/Plugin/Screen/Admin/EPM/Available.pm >> line >> >>326\n\tEPrints::Plugin::Screen::Admin::EPM::Available::render_results('EP >>ri >> nts::Plugin::Screen::Admin::EPM::Available=HASH(0x7f488b4...') called at >> >>/usr/share/eprints3/perl_lib/EPrints/Plugin/Screen/Admin/EPM/Available.pm >> line >> >>285\n\tEPrints::Plugin::Screen::Admin::EPM::Available::render('EPrints::P >>lu >> gin::Screen::Admin::EPM::Available=HASH(0x7f488b4...') called at >> /usr/share/eprints3/perl_lib/EPrints/Plugin/Screen/Admin/EPM.pm line >> >>149\n\tEPrints::Plugin::Screen::Admin::EPM::render('EPrints::Plugin::Scre >>en >> ::Admin::EPM=HASH(0x7f488b4a2410)') called at >> /usr/share/eprints3/perl_lib/EPrints/ScreenProcessor.pm line >> 377\n\tEPrints::ScreenProcessor::process('EPrints::ScreenProcessor', >> 'session', 'EPrints::Repository=HASH(0x7f488b693dd8)', 'template', >>undef, >> 'url', '/cgi/users/home') called at /usr/share/eprints3/cgi/users/home >> line >> >>25\n\tModPerl::ROOT::ModPerl::Registry::usr_share_eprints3_cgi_users_home >>:: >> handler('Apache2::RequestRec=SCALAR(0x7f488f751a10)') called at >> /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204\n\teval {...} called >>at >> /usr/lib/perl5/ModPerl/RegistryCooker.pm line >> >>204\n\tModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0x7f488f86ab7 >>0) >> ') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line >> >>170\n\tModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0 >>x7 >> f488f86ab70)') called at /usr/lib/perl5/ModPerl/Registry.pm line >> 31\n\tModPerl::Registry::handler('ModPerl::Registry', >> 'Apache2::RequestRec=SCALAR(0x7f488f751a10)') called at -e line >>0\n\teval >> {...} called at -e line 0\n >> >> Which is pretty much error soup to me. Can anyone make head or tail as >>to >> what¹s going on? I think it¹s a result of a bad update that was >>performed >> last year which brought our system down for a few days (while I was on >> leave, no less!) as that was when the problems seemed to start. >> >> >> On 18/02/2015 14:30, "Andrew Beeken" <anbeeken@lincoln.ac.uk> wrote: >> >>> Hello all! >>> >>> Currently trying to use the command line install for our bazaar as the >>> GUI is broken - I¹ve found the instructions here >>> http://wiki.eprints.org/w/EPrints_Package_Manager but they seem to be >>>out >>> of date as there is no ep_bazaar file in the bin folder. Any thoughts? >>> >>> Andrew >>> >>> The University of Lincoln, located in the heart of the city of Lincoln, >>> has established an international reputation based on high student >>> satisfaction, excellent graduate employment and world-class research. >>> >>> The information in this e-mail and any attachments may be confidential. >>> If you have received this email in error please notify the sender >>> immediately and remove it from your system. Do not disclose the >>>contents >>> to another person or take copies. >>> >>> Email is not secure and may contain viruses. The University of Lincoln >>> makes every effort to ensure email is sent without viruses, but cannot >>> guarantee this and recommends recipients take appropriate precautions. >>> >>> The University may monitor email traffic data and content in accordance >>> with its policies and English law. Further information can be found at: >>> http://www.lincoln.ac.uk/legal. >>> >>> *** Options: >>>http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech >>> *** Archive: http://www.eprints.org/tech.php/ >>> *** EPrints community wiki: http://wiki.eprints.org/ >>> *** EPrints developers Forum: http://forum.eprints.org/ >> >> *** Options: >>http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech >> *** Archive: http://www.eprints.org/tech.php/ >> *** EPrints community wiki: http://wiki.eprints.org/ >> *** EPrints developers Forum: http://forum.eprints.org/ >> > >-- >Peter J. West >Digital Repository Services Ltd > > >*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech >*** Archive: http://www.eprints.org/tech.php/ >*** EPrints community wiki: http://wiki.eprints.org/ >*** EPrints developers Forum: http://forum.eprints.org/
- References:
- [EP-tech] Re: Bazaar command line install
- From: Andrew Beeken <anbeeken@lincoln.ac.uk>
- [EP-tech] Re: Bazaar command line install
- From: peter <pjw@repositoryservices.co.uk>
- [EP-tech] Re: Bazaar command line install
- Prev by Date: [EP-tech] Re: Bazaar command line install
- Next by Date: [EP-tech] Re: Bazaar command line install
- Previous by thread: [EP-tech] Re: Bazaar command line install
- Next by thread: [EP-tech] Re: Bazaar command line install
- Index(es):