Friskby module in failed state

[oyta]

The Friskby module is having some trouble. I upgraded to the "pip install" version ahead of the last meeting and I think it has been struggling with something since then. The output from Friskby in the control panel is as follows:

2017-05-01 23:30:45	Unit friskby.service entered failed state.
2017-05-01 23:30:45	friskby.service: main process exited, code=exited, status=203/EXEC
2017-05-01 23:30:45	Started Friskby logger.
2017-05-01 23:30:45	Starting Friskby logger...
2017-05-01 23:30:45	Stopping Friskby logger...
2017-05-01 23:30:45	friskby.service holdoff time over, scheduling restart.
2017-05-01 23:29:45	Unit friskby.service entered failed state.
2017-05-01 23:29:45	friskby.service: main process exited, code=exited, status=203/EXEC
2017-05-01 23:29:45	Failed at step EXEC spawning /usr/local/friskby/bin/fby_client: No such file or directory
2017-05-01 23:29:45	Started Friskby logger.
2017-05-01 23:29:45	Starting Friskby logger...
2017-05-01 23:29:45	Stopping Friskby logger...
2017-05-01 23:29:45	friskby.service holdoff time over, scheduling restart.
2017-05-01 23:28:45	Unit friskby.service entered failed state.
2017-05-01 23:28:45	friskby.service: main process exited, code=exited, status=203/EXEC
2017-05-01 23:28:45	Failed at step EXEC spawning /usr/local/friskby/bin/fby_client: No such file or directory
2017-05-01 23:28:45	Started Friskby logger.
2017-05-01 23:28:45	Starting Friskby logger...

..and so on.

[semafor]

The fby_client was renamed fby_manager, and what is happening here is that systemd is most likely just trying to exec that file, even though it doesn't exist. So best case, do $ sudo systemctl daemon-reload and maybe then $ sudo systemctl restart friskby.

Normally, the fby_manager does this automatically: https://github.com/FriskByBergen/python-friskby/blob/master/friskby/friskby_manager.py#L73

[semafor]

Sorry, you'll have to update the rpiparticle to get the new systemd unit file.

[pgdr]

That is strange because that name was changed almost a month ago in FriskByBergen/RPiParticle#129.

Can you check which version of rpiparticle you have? I.e.

>>> import rpiparticle
>>> rpiparticle.__version__
'0.9.1'

[oyta]

The current version is:

pi@FriskPI06:~ $ python
Python 2.7.9 (default, Sep 17 2016, 20:26:04) 
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import rpiparticle
>>> rpiparticle.__version__
'0.9.1'