-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I cannot start the service according to the instructions #1
Comments
Hey @Valentinishe, |
Thanks for taking the time to answer)
I think so too.
Yes
I mean I tried with 3 different versions
I didn't think, thanks) But it did not help(
I tried with everyone, but now I installed near-shell |
My last idea would be trying to set Otherwise, I'd recommend doing the whole near setup from scratch again and see if that works. Those kind of issues are usually quite difficult to debug... I think the easiest approach in your situation might actually be to try one of the other warchest bots (e.g. the one in docker or the other python bot) |
Hi, Good Job)
I know that this is not your problem, but I can't start the service according to your guide.
When I execute the commands:
sudo systemctl start warchest_bot and sudo journalctl -u warchest_bot.service -f
I get an error:
I Think trouble in this line
near_warchest/warchest.py
Line 35 in 1046bb6
Because if I change this line to this,
[f "near --version"],
then the error will be repeated, but will clearly indicate that she does not see not "near"
Also the error is repeated with this line
[f "npm --help"],
,but not with this
[f "node --help"],
it's just some magic
maybe you are facing this problem?
or maybe you know how to solve this problem?
or maybe that's not the problem at all?
I hope for your help)
my env:
ubuntu 18.04
nodejs 8.5 / 10.17 / 12.0
I try use global near-shell and near-cli
The text was updated successfully, but these errors were encountered: