Recent content by rocket4x4

stbernts, I run fermentrack under Debian Jessie without any problems, It has been a while since I did the installation but I think that it should work just as is. Let me know if you have any problems and I can update the installation-scripts.

Yep pushed, just upgraded my "live setup".. Check http://youfermentrackinstall-ip/upgrade/

I have a bunch of them lying around! Happy to test!

Sure, I think you may even be able to save all the configuration. I have not tried this but I think it should work. This is what needs to be done: Collect database (for restore) Kill all fermentrack processes (so we can remove the user) Remove the fermentrack user Run the install...

The error you get about circus not running why you get a 500 error from nginx, so the problem is that process manager circus is not running and have not started fermentrack, so login to you pi and run: sudo -u fermentrack -i source ~/venv/bin/activate crontab -r...

Thanks, that worked good! I have checked the logs and I can not see anything that should give you that error, it looks like fermentrack is actually running, one thing you could try is to restart fermentrack with: source ~/venv/bin/activate circusctl restart The actual error should be in nginx...

I made a simple shell-script that will collect logs and upload them to filebin.net to make troubleshooting easier. It can be viewed here: https://gist.github.com/stone/aa8712bc9539cb879e056fb7e63702ce and downloaded here...

Strange, I just did the update, could you check the logs? They are documented in the bottom of the page here: https://github.com/thorrak/fermentrack/blob/master/docs_mkdocs/docs/about/architecture.md There is also an /home/fermentrack/fermentrack/upgrade.log log which could give some info...

That is actually much easier than my host name base setup (I'm so used to always serving on port 80/443), but I suspect there is a syntax error or something which gives him that error message.

Hmm, do you have more hosts on this nginx than these two ones, nginx things you got more than 32.. I think there is probably a ";" missing or something other strange going on, could you post your configuration also for tiltpi?

You could check the startup log with: journalctl -xn in the console and check the nginx logfile: /var/log/nginx/error.log you can post the relevant part here and I can help.

Sure, I would create a new nginx server in /etc/nginx/sites-enabled/tiltpi and use nip.io for a hostname (maps ip to hostname) for example if the raspberry pi has ip 192.168.1.2 then use "server_name tiltpi.192.168.1.2.nip.io;" You also need to enable php which your can read about here...

What kind of app is it? Depending how it is run you only need to add an alias or you need to create a reverse proxy.

in /home/fermentrack/fermentrack/log there is a logfile for each of the controllers, example: dev-brewpi1-stdout.log, dev-brewpi1-stderr.log they should give you some more information about what is going on. You could also get the logs via: http://<ip-of-fermentrack>/api/log/stderr/1/...

There should be a install.log in the fermentrack-tools directory in your user home directory, it should give some more information about what went wrong. Open up a terminal and if your user is "pi" this should work to show the log: cat /home/pi/fermentrack-tools/install.log or...