You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have setup learning locker on EC2 instance and trying to insert xAPI statements but getting 401 Unauthorized error.
I have setup store and client as required and also added Basic Authorization header but getting error while trying to insert statements through postman.
Hello, may I ask if your installation was successful? Does the Xapi service report no error? What is your system configuration like? After I installed it on my Ubuntu18, the Xapi service could not be started, and I have not been able to find a solution.
hello, thanks for your replying. Did you mean the ubuntu20? but the official recommendation is to use Ubuntu16 or 18. I have tried to use Ubuntu20, but the installation process prompts to use 18, so I use 18 to complete.
I have been troubled by this problem for a long time, it is very painful. If you can please tell me your configuration and your known solution, thank you. I have tried to install it many times.
数据库是分开的,与语句文件和环境文件相同。
Have you ever had such a problem? After I opened http://192.168.103.133/data/xAPI, an error of Faithfully yours, nginx. appeared. But I installed it according to the official deployLL.sh. Do I need to adjust the configuration file during the installation process? May I ask if your mongodb is configured on another server, can it run LL normally? Can the statement be sent to LRS normally?
First install learning locker using installation script and for xAPI use custom installation because it run on node version greater than >16 and learninglocker service uses node version 10.
For this we have to use 2 node versions simultaneously that can be done using node version manager ‘nvm’
We have to switch node version every time depends upon which service we want to start
Install both node versions 17.6.0 and 10.24.1 and use 17.6.0 while installing xAPI.
First install learning locker using installation script and for xAPI use custom installation because it run on node version greater than >16 and learninglocker service uses node version 10.
For this we have to use 2 node versions simultaneously that can be done using node version manager ‘nvm’
We have to switch node version every time depends upon which service we want to start
Install both node versions 17.6.0 and 10.24.1 and use 17.6.0 while installing xAPI.
May I ask, should I start the manual installation directly, or use the script to install learninglocker first, and then use node17 to start the xapi service?
If you use node10 to execute the LL installation script, then when you use node17 to install xapi, there will be a problem of inconsistent pm2 versions, and pm2 cannot start all services. How to solve this?
First install learning locker using installation script and for xAPI use custom installation because it run on node version greater than >16 and learninglocker service uses node version 10.
For this we have to use 2 node versions simultaneously that can be done using node version manager ‘nvm’
We have to switch node version every time depends upon which service we want to start
Install both node versions 17.6.0 and 10.24.1 and use 17.6.0 while installing xAPI.
I have used nvm to switch node versions, but the problem now is that if I only have one server, should I switch node10 to install pm2, and then install node17 to install pm2?
I think part of the issue is that the deployll.sh script takes the latest version of the xAPI service, which since v7.0.0 does not support node <16. You can pass a flag to the deployll.sh to specify the the version of the xAPI service to use. I think it is the -x flag then pass the version number. So something like -x v6.2.3 should tell the deploy script to use the last v6.x.x version of the xAPI service.
Hopefully this will let you just use a single node version for all processes in pm2. If node 10 worked for you previously try that again. I think this is the default in the deployll.sh script.
希望这会让您只对 pm2 中的所有进程使用单节点版本。如果节点 10 之前为您工作,请再试一次。我认为这是脚本中的默认设置deployll.sh。
I have tried to use node10 to start, but the previous problem still occurs, that is, the error sent by postman to http://192.168.103.147/data/xAPI/statements, I have explored all the solutions, I am on 16, I have tried to install LL on both 18 and 20 but failed. When I tried the method mentioned by the partner above, I wanted to use NVM to switch node to 10 to start all services except xAPI, and then switch to node 17 to initialize xAPI, but it failed.
Hi, I have installed it according to your method. The installation has been completed, and the xapi is running smoothly, but it still cannot be sent. I am thinking whether my use process is wrong?
Activity
ToranSharma commentedon Mar 24, 2023
@ksourabh45 have you selected the store in the clients xAPI section?
On Settings -> Clients expand the client you are trying to use and check that your store is selected here (will say LRS (optional) in grey if not):

ksourabh45 commentedon Mar 24, 2023
Hi @ToranSharma , Thanks for your response.
Yes it has store selected.
looperEit commentedon Apr 4, 2023
Hello, may I ask if your installation was successful? Does the Xapi service report no error? What is your system configuration like? After I installed it on my Ubuntu18, the Xapi service could not be started, and I have not been able to find a solution.


kichitan commentedon Apr 4, 2023
Do you have all in one server or Mongo is running on its own server ?
ksourabh45 commentedon Apr 4, 2023
Hi all, I was able to fix it. It was due to node libraries version mismatch in xAPI plugin and learning locker.
ksourabh45 commentedon Apr 4, 2023
Hi @looperEit ,
Have you tried with latest ubuntu?
I have had issues with the same and it works with latest version.
Thanks,
Sourabh
looperEit commentedon Apr 4, 2023
Yes, I installed all services on one server, including services such as mongoDB and Xapi.
but, I just ran the official wget -qO deployll.sh https://raw.githubusercontent.com/LearningLocker/deploy/master/deployll.sh && bash deployll.sh for automatic installation.
looperEit commentedon Apr 4, 2023
hello, thanks for your replying. Did you mean the ubuntu20? but the official recommendation is to use Ubuntu16 or 18. I have tried to use Ubuntu20, but the installation process prompts to use 18, so I use 18 to complete.
looperEit commentedon Apr 4, 2023
Could you please tell me which version I am using? I am using the officially recommended version 14.0 of nodejs.
looperEit commentedon Apr 4, 2023
I have been troubled by this problem for a long time, it is very painful. If you can please tell me your configuration and your known solution, thank you. I have tried to install it many times.
looperEit commentedon Apr 5, 2023
hello?
kichitan commentedon Apr 5, 2023
I used to, but I decided to go HA, so now the only thing running on my server is nginx and all the LRS roles.
databases are separate, same as statements files and env files.
looperEit commentedon Apr 5, 2023
ksourabh45 commentedon Apr 6, 2023
Hi @looperEit ,
I had the same error. Please follow below:
First install learning locker using installation script and for xAPI use custom installation because it run on node version greater than >16 and learninglocker service uses node version 10.
Install both node versions 17.6.0 and 10.24.1 and use 17.6.0 while installing xAPI.
looperEit commentedon Apr 6, 2023
thanks for your replying. i will try it.
looperEit commentedon Apr 12, 2023
May I ask, should I start the manual installation directly, or use the script to install learninglocker first, and then use node17 to start the xapi service?
looperEit commentedon Apr 12, 2023
目前报了这个错误
looperEit commentedon Apr 12, 2023
If you use node10 to execute the LL installation script, then when you use node17 to install xapi, there will be a problem of inconsistent pm2 versions, and pm2 cannot start all services. How to solve this?
looperEit commentedon Apr 13, 2023
I have used nvm to switch node versions, but the problem now is that if I only have one server, should I switch node10 to install pm2, and then install node17 to install pm2?
ToranSharma commentedon Apr 13, 2023
@looperEit,
I think part of the issue is that the
deployll.shscript takes the latest version of the xAPI service, which since v7.0.0 does not support node <16. You can pass a flag to thedeployll.shto specify the the version of the xAPI service to use. I think it is the-xflag then pass the version number. So something like-x v6.2.3should tell the deploy script to use the last v6.x.x version of the xAPI service.Hopefully this will let you just use a single node version for all processes in pm2. If node 10 worked for you previously try that again. I think this is the default in the
deployll.shscript.looperEit commentedon Apr 13, 2023
looperEit commentedon Apr 13, 2023
How to modify this version number?
ToranSharma commentedon Apr 13, 2023
This is passed in a the point of running
deployll.shso something like:The version number come from the releases pages for the xAPI-Service:
https://github.com/LearningLocker/xapi-service/releases
looperEit commentedon Apr 13, 2023
looperEit commentedon Apr 13, 2023
Hi, I have installed it according to your method. The installation has been completed, and the xapi is running smoothly, but it still cannot be sent. I am thinking whether my use process is wrong?
It's really painful not being able to solve it.
looperEit commentedon Apr 13, 2023
as i running the

bash test.sh, it shows thatToranSharma commentedon Apr 13, 2023
@looperEit
Is the
MONGO_URL/usr/local/learninglocker/current/xapi/.envpointing to the correct place for your mongodb server?EDIT: This now looks to be the state that it was in #1626. Maybe these updates should go in that issue.
looperEit commentedon Apr 14, 2023
Thank you very much, it is ready to use. I have found a complete solution.