search

ngds / install-and-run

Use this repository's issue tracker to post comments, bug reports, and help questions on installing and running NGDS CKAN.
4 stars 3 forks source link

not able to harvest from GINstack installation #15

Closed ccaudill closed 9 years ago

ccaudill commented 9 years ago

Test installation up at http://ginstack.usgin.org/ Attempted to harvest from catalog.usgin.org/geothermal/csw as an NGDS CSW. The catalog is functioning and is being harvested successfully by the main aggregator at www.geothermaldata.org

ccaudill commented 9 years ago

We've found that starting a new job has the status "New" but never "Started" or "Running". This many indicate a problem with the CKAN queuing process.

FuhuXia commented 9 years ago

In the readme file, there is one step under Optional post installation. without it, your harvest job will never get started.

To enable harvester, uncomment the cron job at /etc/cron.d/ckan-harvest

jessicagood commented 9 years ago

@FuhuXia Can the install and AMI be changed so this is uncommented by default? No point in having it commented if it's something all users will have to change. Or is there some other reason it needs to commented out initially?

Along those lines, can a default sysadmin account be created automatically? Then the user will just have to change the password in the web interface instead of sshing in.

FuhuXia commented 9 years ago

Sure, let us collect all the valid feedback points and put them into the next version of rpm. For the default admin user, we might want to start with a random password, since the instance wide open to public right after launch.

ccaudill commented 9 years ago

Would it be possible for this change to be made before we send out for broad deployment? The process should be as easy as possible for users.

FuhuXia commented 9 years ago

It is possible. We need to get the changes into github, and then make a new rpm, it will have new rpm users covered. For AMI, we can either start with a new AMI, or instruct user to do a yum update ngds.ckan right after they launch an instance.

jessicagood commented 9 years ago

For the AMI, I think we will need to start with a new AMI. We don't want users to have to deal with having to ssh in to issue yum update ngds.ckan.

ccaudill commented 9 years ago

@FuhuXia Were you able to work on the AMI and script regarding the auto sysadmin user and leaving the harvest line uncommented by default?

FuhuXia commented 9 years ago

@jessica-azgs @ccaudill Can you look at the PR https://github.com/ngds/ckanext-metadata/pull/6 to see we want to include 2 bug fixes into the new rpm?

ccaudill commented 9 years ago

i would say again, why not. might as well include these as well if you're rebuilding

FuhuXia commented 9 years ago

@jessica-azgs Ok, harvested enabled by default and a sysadmin user is added when instance database is first initialized. login is admin, password is admin. New rpm is on the way. Can you update the README file accordingly?

jessicagood commented 9 years ago

@FuhuXia Great! I was able to successfully install the new rpm, login and change the default sysadmin password and then run the harvest. I updated the readme accordingly. Let me know when the new AMI is ready and I'll test that and update that section of the readme as well.

jessicagood commented 9 years ago

Ok, AMI tested. Default login and harvest works as it should. Readme updated. Thanks!

ccaudill commented 9 years ago

@FuhuXia This same behavior is happening at the dev site; http://demo.geothermaldata.org/harvest/usgs/job I cannot harvest anything in. Long ago, Adrian harvested in the AASG Geothermal resource, but the recently added Indiana and USGS will not harvest. Can this be fixed soon? 1) we need to make this site live, and 2) we need to be able to harvest in from the new nodes to complete those deliverables by the end of the year. Thank you!

ccaudill commented 9 years ago

closed, moved to https://github.com/ngds/ckanext-ngds/issues/594