Skip to content
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

Installation fails #658

Closed
Routout opened this issue May 17, 2019 · 4 comments
Closed

Installation fails #658

Routout opened this issue May 17, 2019 · 4 comments

Comments

@Routout
Copy link

Routout commented May 17, 2019

Rpi3
Fresh install fails.
Full install log: https://pastebin.com/8DLFNt4q

~ $ systemctl status mycodo.service
● mycodo.service - Mycodo server
   Loaded: loaded (/home/pi/Mycodo/install/mycodo.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2019-05-17 09:01:47 EEST; 28min ago
  Process: 7097 ExecStart=/var/mycodo-root/env/bin/python /var/mycodo-root/mycodo/mycodo_daemon.py (code=exited,
May 17 09:01:47 Myco systemd[1]: Starting Mycodo server...
May 17 09:01:47 Myco python[7097]: Traceback (most recent call last):
May 17 09:01:47 Myco python[7097]:   File "/var/mycodo-root/mycodo/mycodo_daemon.py", line 40, in <module>
May 17 09:01:47 Myco python[7097]:     import rpyc
May 17 09:01:47 Myco python[7097]: ImportError: No module named 'rpyc'
May 17 09:01:47 Myco systemd[1]: mycodo.service: Control process exited, code=exited status=1
May 17 09:01:47 Myco systemd[1]: Failed to start Mycodo server.
May 17 09:01:47 Myco systemd[1]: mycodo.service: Unit entered failed state.
May 17 09:01:47 Myco systemd[1]: mycodo.service: Failed with result 'exit-code'.

And:

~ $ journalctl -xe
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mycodo.service has begun starting up.
May 17 09:01:47 Myco python[7097]: Traceback (most recent call last):
May 17 09:01:47 Myco python[7097]:   File "/var/mycodo-root/mycodo/mycodo_daemon.py", line 40, in <module>
May 17 09:01:47 Myco python[7097]:     import rpyc
May 17 09:01:47 Myco python[7097]: ImportError: No module named 'rpyc'
May 17 09:01:47 Myco systemd[1]: mycodo.service: Control process exited, code=exited status=1
May 17 09:01:47 Myco systemd[1]: Failed to start Mycodo server.
-- Subject: Unit mycodo.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mycodo.service has failed.
--
-- The result is failed.
May 17 09:01:47 Myco systemd[1]: mycodo.service: Unit entered failed state.
May 17 09:01:47 Myco systemd[1]: mycodo.service: Failed with result 'exit-code'.
May 17 09:01:47 Myco sudo[3174]: pam_unix(sudo:session): session closed for user root
May 17 09:17:01 Myco CRON[7122]: pam_unix(cron:session): session opened for user root by (uid=0)
May 17 09:17:01 Myco CRON[7126]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 17 09:17:01 Myco CRON[7122]: pam_unix(cron:session): session closed for user root
May 17 09:25:33 Myco influxd[6596]: ts=2019-05-17T06:25:33.970341Z lvl=info msg="Retention policy deletion check
May 17 09:25:33 Myco influxd[6596]: ts=2019-05-17T06:25:33.970705Z lvl=info msg="Retention policy deletion check
lines 1807-1831/1831 (END)
@kizniche
Copy link
Owner

This is the same old issue with building bcrypt. You can fix this manually by lowering the version number of bcrypt in requirements.txt and reinstalling. I'll fix this in the next release.

@Routout
Copy link
Author

Routout commented May 17, 2019

Yes, 3.1.4 version fixed this.

@kizniche
Copy link
Owner

kizniche commented May 17, 2019

Just released v7.5.3 that should fix this issue. Thanks for the bug report.

@rizkhal
Copy link

rizkhal commented Jun 24, 2019

i use v7.x in raspberry 3, but i have same problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants