Oddness after update

I have several BrewPi’s and recently updated the one controlling my 1/2 barrel conical. It is an Pi/Arduino model running Rev-c and I seem to have a lot of issues.

First issue Safari on the iPhone page errors, I am pretty sure you guys are aware of this but just listing it out.
Second issue I have found is a constant “Cannot receive LCD text from Python script” and "Script not running!"
Third issue “Fermenting:” is not updating with the beer profile name currently running
Fourth issue graph has issue being rendered and I cannot zoom in on graph to get a deeper look and trying tends to lock up the browser. I have tested this on Safari, Chrome, and Firefox on OS X all with the same effect.

Here is a link to a short screen capture video so you guys can see what I see:

I scrubbed logs and this is all I see:

root@raspberrypi:/home/brewpi/logs# tail -10 stderr.txt
Jun 18 2015 03:30:46 controller debug message: INFO MESSAGE 18: Negative peak detected: 70.2, estimated: 70.2. Previous cool estimator: 1.256, New cool estimator: 1.256.
Jun 18 2015 04:13:48 controller debug message: INFO MESSAGE 18: Negative peak detected: 70.3, estimated: 70.2. Previous cool estimator: 1.256, New cool estimator: 1.256.
Jun 18 2015 04:37:57 controller debug message: INFO MESSAGE 17: Positive peak detected: 70.4, estimated: 70.3. Previous heat estimator: 0.199, New heat estimator: 0.199.
Jun 18 2015 04:50:10 controller debug message: INFO MESSAGE 18: Negative peak detected: 70.2, estimated: 70.1. Previous cool estimator: 1.256, New cool estimator: 1.256.
Jun 18 2015 05:02:58 controller debug message: INFO MESSAGE 17: Positive peak detected: 70.3, estimated: 70.3. Previous heat estimator: 0.199, New heat estimator: 0.199.
Jun 18 2015 05:26:59 controller debug message: INFO MESSAGE 18: Negative peak detected: 70.2, estimated: 69.9. Previous cool estimator: 1.256, New cool estimator: 1.256.
Jun 18 2015 08:46:44 controller debug message: WARNING 2: Temperature sensor disconnected pin 18, address 2847490806000039
Jun 18 2015 08:46:44 controller debug message: INFO MESSAGE 0: Temp sensor connected on pin 18, address 2847490806000039
Jun 18 2015 09:27:19 controller debug message: INFO MESSAGE 18: Negative peak detected: 70.9, estimated: 70.6. Previous cool estimator: 1.256, New cool estimator: 1.256.
Jun 18 2015 09:52:55 controller debug message: INFO MESSAGE 18: Negative peak detected: 69.8, estimated: 69.9. Previous cool estimator: 1.256, New cool estimator: 1.256.

root@raspberrypi:/home/brewpi/logs# tail -10 /var/log/syslog
Jun 18 09:47:01 raspberrypi /USR/SBIN/CRON[7047]: (brewpi) CMD (python $scriptpath/brewpi.py --checkstartuponly --dontrunfile $scriptpath/brewpi.py 1>/dev/null 2>>$stderrpath; [ $? != 0 ] && python -u $scriptpath/brewpi.py 1>$stdoutpath 2>>$stderrpath &)
Jun 18 09:48:01 raspberrypi /USR/SBIN/CRON[7066]: (brewpi) CMD (python $scriptpath/brewpi.py --checkstartuponly --dontrunfile $scriptpath/brewpi.py 1>/dev/null 2>>$stderrpath; [ $? != 0 ] && python -u $scriptpath/brewpi.py 1>$stdoutpath 2>>$stderrpath &)
Jun 18 09:49:01 raspberrypi /USR/SBIN/CRON[7070]: (brewpi) CMD (python $scriptpath/brewpi.py --checkstartuponly --dontrunfile $scriptpath/brewpi.py 1>/dev/null 2>>$stderrpath; [ $? != 0 ] && python -u $scriptpath/brewpi.py 1>$stdoutpath 2>>$stderrpath &)
Jun 18 09:50:01 raspberrypi /USR/SBIN/CRON[7076]: (root) CMD (sudo -u brewpi touch $stdoutpath $stderrpath; $scriptpath/utils/wifiChecker.sh 1>>$stdoutpath 2>>$stderrpath &)
Jun 18 09:50:01 raspberrypi /USR/SBIN/CRON[7075]: (brewpi) CMD (python $scriptpath/brewpi.py --checkstartuponly --dontrunfile $scriptpath/brewpi.py 1>/dev/null 2>>$stderrpath; [ $? != 0 ] && python -u $scriptpath/brewpi.py 1>$stdoutpath 2>>$stderrpath &)
Jun 18 09:51:01 raspberrypi /USR/SBIN/CRON[7092]: (brewpi) CMD (python $scriptpath/brewpi.py --checkstartuponly --dontrunfile $scriptpath/brewpi.py 1>/dev/null 2>>$stderrpath; [ $? != 0 ] && python -u $scriptpath/brewpi.py 1>$stdoutpath 2>>$stderrpath &)
Jun 18 09:52:01 raspberrypi /USR/SBIN/CRON[7097]: (brewpi) CMD (python $scriptpath/brewpi.py --checkstartuponly --dontrunfile $scriptpath/brewpi.py 1>/dev/null 2>>$stderrpath; [ $? != 0 ] && python -u $scriptpath/brewpi.py 1>$stdoutpath 2>>$stderrpath &)
Jun 18 09:53:01 raspberrypi /USR/SBIN/CRON[7102]: (brewpi) CMD (python $scriptpath/brewpi.py --checkstartuponly --dontrunfile $scriptpath/brewpi.py 1>/dev/null 2>>$stderrpath; [ $? != 0 ] && python -u $scriptpath/brewpi.py 1>$stdoutpath 2>>$stderrpath &)
Jun 18 09:54:01 raspberrypi /USR/SBIN/CRON[7107]: (brewpi) CMD (python $scriptpath/brewpi.py --checkstartuponly --dontrunfile $scriptpath/brewpi.py 1>/dev/null 2>>$stderrpath; [ $? != 0 ] && python -u $scriptpath/brewpi.py 1>$stdoutpath 2>>$stderrpath &)
Jun 18 09:55:01 raspberrypi /USR/SBIN/CRON[7123]: (brewpi) CMD (python $scriptpath/brewpi.py --checkstartuponly --dontrunfile $scriptpath/brewpi.py 1>/dev/null 2>>$stderrpath; [ $? != 0 ] && python -u $scriptpath/brewpi.py 1>$stdoutpath 2>>$stderrpath &)

Anyone have any ideas here?

Cheers,
-Stephen

Found this in the Apache logs:

root@raspberrypi:/var/log/apache2# tail -f error.log
[Wed Jun 17 20:38:06 2015] [notice] caught SIGTERM, shutting down
[Wed Jun 17 20:38:08 2015] [notice] Apache/2.2.22 (Debian) PHP/5.4.41-0+deb7u1 configured – resuming normal operations
[Thu Jun 18 01:57:36 2015] [error] [client 200.95.42.163] File does not exist: /var/www/phpMyAdmin
[Thu Jun 18 01:57:39 2015] [error] [client 200.95.42.163] File does not exist: /var/www/pma
[Thu Jun 18 01:57:42 2015] [error] [client 200.95.42.163] File does not exist: /var/www/myadmin
[Thu Jun 18 10:01:33 2015] [error] [client 94.102.49.169] File does not exist: /var/www/PSIA
[Thu Jun 18 10:01:44 2015] [error] [client 94.102.49.169] File does not exist: /var/www/cgi
[Thu Jun 18 10:01:53 2015] [error] [client 94.102.49.169] script not found or unable to stat: /usr/lib/cgi-bin/rtpd.cgi
[Thu Jun 18 10:02:05 2015] [error] [client 94.102.49.169] File does not exist: /var/www/LIVE_VIEW.asp
[Thu Jun 18 10:54:13 2015] [error] [client 10.0.0.40] PHP Warning: unlink(/var/www/do_not_run_brewpi): No such file or directory in /var/www/start_script.php on line 23, referer: http://10.0.0.48/index.php

These issues have been reported a lot in Safari, but Chome behaved a lot better.
I still don’t know what causes them.

Can you try F12 in Chrome and look at the network and the console tab to see if they give you any more info?
What is happening is that the web browser is not always getting a reply on its AJAX requests from the script.

Fired up firefox and got some more useful info out. Take a peak at these pics perhaps this will help out.

Imgur

Imgur

I have a CPU profile that also may be of use, but can’t attach it here.

Cheers,
-Stephen

I took another video real quick of what I see now after a reboot. It really seems the Java is having all the issues, which in my exp is not shocking.

This is after the page has fully loaded:

And this video is on a “fresh” full page reload.

Wow, I just noticed that you have a year of data in that chart!
Damn, no wonder the web server and javascript have issues couching up all the data.

Could you try clicking on “My First BrewPi Run” and starting a new beer?
The way it is intended to be used is to start a new data set for every brew.

HA HA yeah I was using this controller for my keezer for a good long time.

Crazy enough out of the five I have this is actually my first time using it myself. I have built and sold a couple and helped friends out building them, but I have never actually had a setup where I could use one.

Thanks for the catch @Elco!

Cheers,
-Stephen

Did the problems go away after starting a new data set?

Yes everything seems to be running much much better now.

To be honest I thought the two were tied together, meaning when I set beer profile it would auto update the data logging to the running profile.

Cheers,
-Stephen

no, the two are entirely separate actually, because during a brew, you might want to switch between beer constant and beer profile.

Got ya.

With that said what is the prefered method of operation is to:

  1. Build beer profile
  2. Start new brew log
  3. Apply beer profile

Cheers,
-Stephen

Yep, that sounds like a good approach.