indy.error.IndyError: ErrorCode.CommonInvalidState about greenlight HOT 18 CLOSED

Hi @mehmetaydar,

We recently made some significant changes to permitify.

Can you please ensure that you are running the very latest code from the master branch of https://github.com/bcgov/von-network, https://github.com/bcgov/TheOrgBook, and https://github.com/bcgov/permitify?

Once you have the latest code, run ./manage rm on all 3 of the environment to clean their state.

Once you've done this, you should be able to try running the environments again like you did previously.

Let me know if those steps work for you.

from greenlight.

FYI - on the permitify instructions - there are two scripts "manage" and "manage.sh". Use the one "manage.sh" for now - it's the right one. We'll fix that shortly.

from greenlight.

I checkout the latest versions from master branch for TheOrgBook, von-network, and permitify. I was able to build them. The von-network (http://localhost:9000/ ) and TheOrgBook (http://10.206.61.105:8080) successfuly loads. However there is a confusion on how to start the permitify. @swcurran mentioned that we should use manage.sh under permitify/docker. I used manage.sh to build permitify. However manage.sh does not have registerDids argument. I am following the quick start guide (https://github.com/bcgov/TheOrgBook/blob/master/docker/README.md#running-a-complete-provisional-von-network ) I think the quick start guide needs to be updated.

I have run the following but I am still not able to run permitify:
From .../TheOrgBook/docker run ./manage registerDids seed=the_org_book_0000000000000000000
From .../permitify/docker run ./manage registerDids seed=issuer_service_00000000000000000
From .../permitify/docker ./manage.sh start seed=issuer_service_00000000000000000 TOB_INDY_SEED=the_org_book_0000000000000000000 ('start all' argument not working)
Now, when I run http://localhost:5000 on the browser I get: "404 Site 10.206.61.105:5000 is not served on this interface." And the logs says:

caddy_1 | 2018/09/21 13:06:43 [INFO] 10.206.61.105 - No such site at :80 (Remote: 10.122.24.89, Referer: )

Any suggestion?

from greenlight.

@mehmetaydar - try localhost:5000/demo - That should work. There is no longer need to specify the seeds, so that's dropped from the script. Sorry I forgot to mention that in the note earlier. Again - the caddyfile can be updated to address that issue, to that just localhost:5000 works.

from greenlight.

@swcurran localhost:5000/demo does not work. I am still getting

404 Site 10.206.61.105:5000 is not served on this interface
and
caddy_1 | 2018/09/24 05:38:28 [INFO] 10.206.61.105 - No such site at :80 (Remote: 10.122.24.89, Referer: )

Is it possible that you can provide an updated instructions of the "Quick Start Guide?" I might be missing something. thanks.

from greenlight.

from greenlight.

I have installed them on a server (Ubuntu based virtual machine, no graphical interface). I am accessing it from my windows machine using Chrome. So I don't use localhost:5000/demo. I use http://server-ip:5000/demo. Could that be a problem? The von-network (http://server-ip:9000) and TheOrgBook (http://server-ip:8080) work and they display a screen. However permitify (http://server-ip:5000/demo) does not work.

from greenlight.

from greenlight.

@swcurran On the Ubuntu server if I run: wget http://server-ip:5000 I get the error: "ERROR 404: Not Found." However, if I run wget http://localhost:5000 it downloads the page fine and the content of the page says that "If you see this page, Caddy container works." wget http://localhost:5000/demo also resolves to another page. So I am starting to think this is either a port forwarding or a proxy issue.

from greenlight.

from greenlight.

Made it work. I had to explicitly set the APPLICATION_URL and WEB_HOST_NAME to point to DOCKERHOST instead of localhost in permitify/docker/manage file at the end of the configureEnvironment function as below:

export APPLICATION_URL=${APPLICATION_URL-http://$DOCKERHOST:${WEB_HTTP_PORT:-5000}}

export WEB_HOST_NAME=${DOCKERHOST}

echo -e "DOCKERHOST: $DOCKERHOST"

echo -e "COMPOSE_PROJECT_NAME: $COMPOSE_PROJECT_NAME"

echo -e "LEDGER_URL: $LEDGER_URL"

echo -e "APPLICATION_URL: $APPLICATION_URL"

echo -e "WEB_HOST_NAME: $WEB_HOST_NAME"

Now the permitify loads.

from greenlight.

I am able to get to http://server-ip:5000/bcreg/incorporation. When I enter the information and click on the Submit button, it looks like to be working as I get the following output from the logs:

bcreg-agent_1 | 2018-09-25 07:27:47,209 INFO [vonx.indy.service]: Creating Indy credential offer for issuer bcreg, schema incorporation.permitify
bcreg-agent_1 | 2018-09-25 07:27:47,350 INFO [von_anchor.anchor.base]: _BaseAnchor.get_cred_def: got cred def for 6qnvgJtqwK44D8LFYnV5Yf:3:CL:44:tag from cache
bcreg-agent_1 | 2018-09-25 07:27:48,055 INFO [aiohttp.access]: 172.24.0.8 [25/Sep/2018:07:27:47 +0000] "POST /bcreg/incorporation HTTP/1.1" 200 224 "http://10.206.61.105:5000/bcreg/incorporation" "Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36"

However, in my experience the demo is not self-explanatory. The instructions are not clear about how to proceed from there. We really need an updated quick-start quide for demo purposes.

from greenlight.

from greenlight.

@swcurran thanks for your inputs. I am able to run the demo, and able to get back to the list of credentials screen. However, I had to set TOB_APP_URL and THE_ORG_BOOK_APP_URL environment variables in permitify/docker/manage file at the end of the configureEnvironment function as below:
export THE_ORG_BOOK_APP_URL=${TOB_APP_URL}
export WEB_HOST_NAME=${DOCKERHOST}

The problem I face now is that solr is not working properly. I get the following error when I try to search the business I just registered via TheOrgBook:

tob-api_1 | Traceback (most recent call last):
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/haystack/backends/solr_backend.py", line 138, in search
tob-api_1 | raw_results = self.conn.search(query_string, **search_kwargs)
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/pysolr.py", line 730, in search
tob-api_1 | response = self._select(params, handler=search_handler)
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/pysolr.py", line 428, in _select
tob-api_1 | return self._send_request('get', path)
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/pysolr.py", line 403, in _send_request
tob-api_1 | raise SolrError(error_message % (resp.status_code, solr_message))
tob-api_1 | pysolr.SolrError: Solr responded with an error (HTTP 403): [Reason: None]
tob-api_1 | <title>Corporate Proxy Notification</title>

I believe that is a proxy error. Will try to fix it.

from greenlight.

In TheOrgBook/docker/manage file I have set the following:

---#export SOLR_SERVICE_NAME="tob-solr" export SOLR_SERVICE_NAME=${DOCKERHOST} export SOLR_CORE_NAME=${CORE_NAME} export SOLR_URL=${http://$SOLR_SERVICE_NAME:8983/solr/$SOLR_CORE_NAME}`

Now I am getting the following error while trying to start TheOrgBook:

bc@FRA1000013983:~/blockchain/indy/bcgov/TheOrgBook/docker$ ./manage start tob-api seed=the_org_book_0000000000000000000
Creating tob_tob-solr_1 ... done
Creating tob_wallet-db_1 ... done
Creating tob_tob-db_1 ... done
Creating tob_tob-api_1 ... done
Attaching to tob_tob-api_1
tob-api_1 | waiting for solr ...
tob-api_1 | ---> Running application from Python script (app.py) ...
tob-api_1 | Enabling realtime indexing ...
tob-api_1 | Loading custom settings file: custom_settings_bcgov.py
tob-api_1 | INFO 2018-09-26 13:41:51,913 manager 8 140227877299968 Initializing Indy service
tob-api_1 |
tob-api_1 | Migrating database ...
tob-api_1 | Operations to perform:
tob-api_1 | Apply all migrations: admin, api, api_v2, auth, contenttypes, sessions
tob-api_1 | Running migrations:
tob-api_1 | No migrations to apply.
tob-api_1 |
tob-api_1 | Search indexing in progress ...
tob-api_1 | INFO 2018-09-26 13:41:52,167 suggest 8 140227877299968 Rebuilding Solr suggester...
tob-api_1 | Traceback (most recent call last):
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/requests/models.py", line 375, in prepare_url
tob-api_1 | scheme, auth, host, port, path, query, fragment = parse_url(url)
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/urllib3/util/url.py", line 199, in parse_url
tob-api_1 | raise LocationParseError(url)
tob-api_1 | urllib3.exceptions.LocationParseError: Failed to parse: None:None
tob-api_1 |
tob-api_1 | During handling of the above exception, another exception occurred:
tob-api_1 |
tob-api_1 | Traceback (most recent call last):
tob-api_1 | File "app.py", line 32, in
tob-api_1 | run_migration()
tob-api_1 | File "/home/indy/tob_anchor/boot.py", line 105, in run_migration
tob-api_1 | call_command("migrate")
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/django/core/management/init.py", line 131, in call_command
tob-api_1 | return command.execute(*args, **defaults)
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/django/core/management/base.py", line 330, in execute
tob-api_1 | output = self.handle(*args, **options)
tob-api_1 | File "/home/indy/api/management/commands/migrate.py", line 22, in handle
tob-api_1 | self.__update_search_indexes()
tob-api_1 | File "/home/indy/api/management/commands/migrate.py", line 35, in __update_search_indexes
tob-api_1 | SuggestManager().rebuild()
tob-api_1 | File "/home/indy/api_v2/suggest.py", line 56, in rebuild
tob-api_1 | 'suggest.build': 'true',
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/pysolr.py", line 730, in search
tob-api_1 | response = self._select(params, handler=search_handler)
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/pysolr.py", line 428, in _select
tob-api_1 | return self._send_request('get', path)
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/pysolr.py", line 376, in _send_request
tob-api_1 | timeout=self.timeout, auth=self.auth)
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/requests/sessions.py", line 525, in get
tob-api_1 | return self.request('GET', url, **kwargs)
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/requests/sessions.py", line 498, in request
tob-api_1 | prep = self.prepare_request(req)
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/requests/sessions.py", line 441, in prepare_request
tob-api_1 | hooks=merge_hooks(request.hooks, self.hooks),
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/requests/models.py", line 309, in prepare
tob-api_1 | self.prepare_url(url, params)
tob-api_1 | File "/home/indy/.pyenv/versions/3.6.3/lib/python3.6/site-packages/requests/models.py", line 377, in prepare_url
tob-api_1 | raise InvalidURL(*e.args)
tob-api_1 | requests.exceptions.InvalidURL: Failed to parse: None:None
tob_tob-api_1 exited with code 1

Any suggestion? thanks.

from greenlight.

It works now. In my case, I had to set the following:
export SOLR_SERVICE_NAME=${DOCKERHOST}
export SOLR_CORE_NAME=${CORE_NAME}
export SOLR_URL=${SOLR_URL-http://$SOLR_SERVICE_NAME:8983/solr/$SOLR_CORE_NAME}
in TheOrgBook/docker/manage. I also had to set
- NO_PROXY=${SOLR_SERVICE_NAME}
- no_proxy=${SOLR_SERVICE_NAME}
- SOLR_URL=${SOLR_URL}
in TheOrgBook/docker-compose.yml. I am facing a lot of problems during the installation. I think one of the bottlenecks is that I am working behind a corporate proxy.

from greenlight.

from greenlight.

Glad you got it working @mehmetaydar

I can't seem to reproduce this issue. I believe it is due to your network conditions.

I will close this issue for now but feel free to open a new one if you run into any issues.

from greenlight.