[ckan-dev] Build a new Harvest plugin

Tue Jun 6 14:14:03 UTC 2017

Unfortunately I still get the same error with this command
Regards

De : ckan-dev [mailto:ckan-dev-bounces at lists.okfn.org] De la part de Stefan Oderbolz
Envoyé : mardi 6 juin 2017 14:53
À : CKAN Development Discussions
Objet : Re: [ckan-dev] Build a new Harvest plugin

Did you run it with the activated virtualenv? How do you run CKAN? Using Apache and WSGI?

Maybe you could try to use the build-in webserver first (with activated virtualenv!) using this command:

paster serve /path/to/production.ini

By default, this runs CKAN on port 5000.
Do you still get the PluginNotFoundException?

- Stefan

On Tue, Jun 6, 2017 at 2:28 PM, <aurelie.gole at orange.com<mailto:aurelie.gole at orange.com>> wrote:

Thank you Stefan , but I had already did this command ( I make python setup.py install)

and it doesn't change anything...
Le 06/06/2017 à 14:21, Stefan Oderbolz a écrit :
Hi Aurélie,

you need to install the plugin in your virtualenv, e.g. like that:

source /path/to/bin/activate
cd /path/to/ckanext-odbostats (or however you called your extension)
python setup.py develop

After running setup.py develop the plugin is "known" in the virtualenv and you can then use it.

- Stefan

On Tue, Jun 6, 2017 at 2:13 PM, <aurelie.gole at orange.com<mailto:aurelie.gole at orange.com>> wrote:

Hello Stefan

Yes my plugin is loaded in the production.ini but I have the following error:

 raise PluginNotFoundException(plugin_name)
[Tue Jun 06 14:04:57.527395 2017] [:error] [pid 20596:tid 140631889151744] [remote 127.0.0.1:56175<http://127.0.0.1:56175>] PluginNotFoundException: odbostats_harvester

I had just wrote a custom harvester based on the main ckan-harvester.

Do I need to declare it in the setup.py script too and if yes how ckan make the relation between the new harvest class and the entrypoints from the setup.py?

Thanks

Aurélie

Le 06/06/2017 à 13:31, Stefan Oderbolz a écrit :
Hi Aurélie,

It's hard to tell without more details, here are a couple of things you could check:

- Make sure the plugin is loaded in your config-INI (e.g. production.ini)
- Start the RabbitMQ or Redis services for the queues
- Start the consumers (see https://github.com/ckan/ckanext-harvest#harvester-run)

Generally follow the instructions in the README of ckanext-harvest.

- Stefan

On Tue, Jun 6, 2017 at 9:14 AM, <aurelie.gole at orange.com<mailto:aurelie.gole at orange.com>> wrote:
Hello

I am working on a new harvest plugin.

I'd like to know what it could e wrong because I can't able to make it work:

 - my harvest class implements the 3 interfaces; gather_stage, import_stage and fetch_stage

- I had declared it into the entry_points of my setup.py file

Do I need to do something else so it works fine?

Thanks

Regards

Aurélie

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

_______________________________________________
ckan-dev mailing list
ckan-dev at lists.okfn.org<mailto:ckan-dev at lists.okfn.org>
https://lists.okfn.org/mailman/listinfo/ckan-dev
Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev

--
Liip AG  // Limmatstrasse 183 //  CH-8005 Zürich
Tel +41 43 500 39 80<tel:+41%2043%20500%2039%2080> // GnuPG 0x7B588C67 // www.liip.ch<http://www.liip.ch/>

_______________________________________________

ckan-dev mailing list

ckan-dev at lists.okfn.org<mailto:ckan-dev at lists.okfn.org>

https://lists.okfn.org/mailman/listinfo/ckan-dev

Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.
_______________________________________________ ckan-dev mailing list ckan-dev at lists.okfn.org<mailto:ckan-dev at lists.okfn.org> https://lists.okfn.org/mailman/listinfo/ckan-dev Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
--
Liip AG  // Limmatstrasse 183 //  CH-8005 Zürich Tel +41 43 500 39 80<tel:+41%2043%20500%2039%2080> // GnuPG 0x7B588C67 // www.liip.ch<http://www.liip.ch/>

_______________________________________________

ckan-dev mailing list

ckan-dev at lists.okfn.org<mailto:ckan-dev at lists.okfn.org>

https://lists.okfn.org/mailman/listinfo/ckan-dev

Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc