public npm registry not accessible after upgrade to HANA 2.0 sp3

[Former Member]

Hi,

After upgrading to HANA 2.0 sp3 I am unable to access the npm registry.

My UPSTREAM_LINK env is set to http://registry.npmjs.org/ (same as in SP 2) and no HTTP_PROXY env is set because it is not required in the server. (I am able to access npmjs.org through curl without any proxy setting).

The error I received is

http  --> ERR, req: 'GET http://registry.npmjs.org/ws', error: unable to get local issuer certificate (connecting to registry.npmjs.org:443)

All the settings were same as in sp2.

Any help is appreciated.

[draschke]

Hi Himanshu,

we are on the same SPS and are struggling with the same issue since last week.

Please could you explain me, how you did your curl. Did you use it with the XS-Client?

BR, Dirk

[Former Member]

Hi,

I have this problem, too, since this week. Every thing was working fine since I have installed HANA Express Edition 2.0 SPS03 in April.

But now suddenly this problem occurs.

Best regards

Achim

[Former Member]

Hi Dirk,

I used curl from OS level. Its a Linux command.

curl https://registry.npmjs.org/ws

Note that I am using https.

[draschke]

Hi Himanshu,

thank you. I will ask our admin for executing this curl statement.

We are getting this error message since last saturday. I'm wondering because we are been working since almost one month with SPS03 and didn't have had issues like that.

Maybe we cleared the cache last friday, when we were restarting the services di-core and some other services, so that the libs couldn't be found anymore in the cache and that's why we are struggling since this time with this issue. And this would explain why we could work without any trouble of missing NPM's since of our update to SPS03.

For example, in this case we struggle with jszip and express because they couldn't be found in the cache.

897 silly fetchPackageMetaData error for jszip@^2.6.1 No matching version found for jszip@^2.6.1
898 silly fetchPackageMetaData error for express@4.16.3 No matching version found for express@4.16.3

891 http fetch GET 304 https://hana...../jszip 218ms (from cache)
892 http fetch GET 304 https://hana...../express 220ms (from cache)
893 silly pacote version manifest for next-line@1.1.0 fetched in 9ms
894 silly pacote version manifest for debug@3.1.0 fetched in 9ms
895 silly pacote version manifest for hoek@4.2.1 fetched in 10ms
896 silly pacote version manifest for @sap/xsenv@1.2.9 fetched in 10ms
897 silly fetchPackageMetaData error for jszip@^2.6.1 No matching version found for jszip@^2.6.1
898 silly fetchPackageMetaData error for express@4.16.3 No matching version found for express@4.16.3
<br>

[Former Member]

hi Dirk,

yes that could me one possible reason you were able to get packages without any error.

For now I was able to build my using version which are present in local registry for example, use express 4.16.2 which is there n local registry. But for packages which are not present at all or if we need some specific version this would be a problem.

[draschke]

Hi,

I got response from our proxy-admin, he told me that there is a running connection between hana db and registry.npmjs.org. At this point I would assume that there is nothing wrong with our proxy-settings.

BR, Dirk

[Former Member]

Hi Dirk,

Have you used HTTP_PROXY and HTTPS_PROXY env variables?? Note value for both should be same. example:

HTTP_PROXY: http://abc:8080 and HTTPS_PROXY:http://abc:8080 also set the NO_PROXY variable too.

BR, Himanshu

[draschke]

yes, since almost two years and nothing has changed.

but nevertheless I was asking our proxy amin to be sure, that there is a connection.

I have really no idea where the issue comes from.

I have open up a ticket. hopefully someone will help soon.

[draschke]

the only difference too the installation guide is that we set them always with the xs client manually and didn't use the mtaext file.

[Former Member]

but that should not matter, anyways If you got any solution do tell me.

[draschke]

Hi Himanshu,

got response from SAP, it solved our issue. 🙂

Try this.

xs unbind-service di-local-npm-registry devx-npm-cache-fs
xs delete-service devx-npm-cache-fs

xs create-service fs-storage free devx-npm-cache-fs
xs bind-service di-local-npm-registry devx-npm-cache-fs

xs restage di-local-npm-registry
xs restart di-local-npm-registry

https://help.sap.com/viewer/1a8e7ab05a2e4119b02b702f211422f5/2.0.03/en-US/5fd9473b7e994e2aa66092da5a...

[draschke]

If this does not work for you I would recommend this old post:

https://archive.sap.com/discussions/message/16864397#16864397

[Former Member]

hi Drik,

it worked, you can post it as answer below.

these steps are mentioned here https://help.sap.com/viewer/1a8e7ab05a2e4119b02b702f211422f5/2.0.03/en-US/5fd9473b7e994e2aa66092da5a...

but I thought they are for something else. 😛 and not related to my issue.

regards,

Himanshu

[draschke]

Same too me, I tried it already before but it didn't work. But I guess, because I didn't believe that it would work, I made a mistake and skipped the point to delete this service. 🙂

[draschke · Accepted solution]

This could help:

xs unbind-service di-local-npm-registry devx-npm-cache-fs
xs delete-service devx-npm-cache-fs

xs create-service fs-storage free devx-npm-cache-fs
xs bind-service di-local-npm-registry devx-npm-cache-fs

xs restage di-local-npm-registry
xs restart di-local-npm-registry

https://help.sap.com/viewer/1a8e7ab05a2e4119b02b702f211422f5/2.0.03/en-US/5fd9473b7e994e2aa66092da5a...