Error running -m scripts.populate_sample_contributor_data

[rassa328]

I'm now unable to run the script "scripts.populate_sample_contributor_data ". The error I am getting is

/oppia/core/platform/datastore/cloud_datastore_services.py", line 26, in
from google.cloud import ndb
ModuleNotFoundError: No module named 'google.cloud'

It has worked fine in the past, in October so maybe something has changed? I made sure it ran with the correct pyenv, while the server was running properly. Any ideas?

[hrshkshri]

Hey @rassa32, Sorry for the late reply,
scripts.populate_sample_contributor_data doesn't work, I would recommend you create data manually.
Thanks

[rassa328]

When doing it manually i get this error from the Admin panel in the activities tab. So i appear to be stuck from doing it manually also. Any ideas?

"Load dummy new structures data (only admins)",

gives error "Server error: ConnectionTimeout caused by - ReadTimeoutError(HTTPConnectionPool(host='localhost', port=9200): Read timed out. (read timeout=30))"

[seanlip]

@rassa328 This is an odd error. Can you try again -- does this happen each time? It seems to be related to elasticsearch on your machine (which is what serves at port 9200) -- does the search functionality in /library work fine on your machine? If not then there might be some issue with how elasticsearch is being set up locally.

Also, despite the error, does the data actually load?

Finally, in terms of doing it manually, you can also try creating the data directly from the topic editor, skill editor, etc. See the instructions here for more details.

If you need further help, please post with more information about what you tried and what failed. Thanks!

[rassa328]

Thanks for the answer, I agree it's very odd. Saw some other thread from long ago where someone had the same problem without knowing the cause. He solved it by reinstalling Oppia, maybe that is whats need to be done, but it would be interesting to know the root cause.

It happens every time and the data wont load. How would i go on to test the search functionality in /library?

[seanlip]

Hmm -- @rassa328, thanks for checking. Can you try searching for something in the search bar in the /library page? When you do that, do you get any errors?

Also when you go to localhost:9200, do you see anything? Here's what I get, for comparison:

{
  "name" : "sean",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "Ir2G6OUlQkWBk2q7ZAqu4Q",
  "version" : {
    "number" : "7.17.0",
    "build_flavor" : "default",
    "build_type" : "tar",
    "build_hash" : "bee86328705acaa9a6daede7140defd4d9ec56bd",
    "build_date" : "2022-01-28T08:36:04.875279988Z",
    "build_snapshot" : false,
    "lucene_version" : "8.11.1",
    "minimum_wire_compatibility_version" : "6.8.0",
    "minimum_index_compatibility_version" : "6.0.0-beta1"
  },
  "tagline" : "You Know, for Search"
}

This post might also be relevant: https://discuss.elastic.co/t/index-command-raises-timeout-error/279761/2 (you can search for "elasticsearch read timeout localhost" and that might give you more clues as well.

[rassa328]

I can search without errors in the library page, i assume its http://localhost:8181/community-library as that is where I am redirected. I have no explorations to search for but the status codes are giving me an OK.

For localhost:9200 I get the following

{
"name" : "Rasmuss-Air-2",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "P4NpMwb5ThO_T-5sa4mbag",
"version" : {
"number" : "7.17.0",
"build_flavor" : "default",
"build_type" : "tar",
"build_hash" : "bee86328705acaa9a6daede7140defd4d9ec56bd",
"build_date" : "2022-01-28T08:36:04.875279988Z",
"build_snapshot" : false,
"lucene_version" : "8.11.1",
"minimum_wire_compatibility_version" : "6.8.0",
"minimum_index_compatibility_version" : "6.0.0-beta1"
},
"tagline" : "You Know, for Search"
}

[seanlip]

Thanks @rassa328. Yes, that's the page.

Let's get more info. Go to the /admin page, Activities tab. Click on the top button to load the Welcome exploration. Can you post the full error log and stack trace?

If that command works then try the "load dummy new structures data" command and please post the full error log with the stack trace. Thanks.