Cannot download emonhub logs

qris · 2019-04-09T19:40:11.274Z

I click on Setup > Emonhub, which takes me to http://emonpi.local/emoncms/config/view.

I click on Download Log, and I get a file which contains only the following line:

/var/log/emonhub/emonhub.log does not exist!

Instead of the actual logs.

Greebo · 2019-04-10T04:17:36.616Z

See this thread (specifically the last line of the last post):

EmonHub log systemd emonHub

Most of the changes are in this commit passthru("journalctl -u emonhub -n 30 --no-pager"); We just needed to add the www-data users to the systemd-journal group to allow it to read, this has been added to emonPi update and the emonhub config module readme sudo usermod -a -G systemd-journal www-data We still need to fix the log download button.

borpin · 2019-04-10T09:34:45.833Z

Assuming you are on an EmonPi, run the EmonPi update and it should correct the issue.

pb66 · 2019-04-10T09:42:33.153Z

borpin:

run the EmonPi update and it should correct the issue.

There has been no changes to the emoncms/config repo since that “we still need to fix” post was written.

The code still tries to access the log file that no longer exists

github.com

emoncms/config/blob/1.1.0/config_controller.php#L53-L72


      
          else if ($route->action == 'downloadlog')
          {
              header("Content-Type: application/octet-stream");
              header("Content-Transfer-Encoding: Binary");
              header("Content-disposition: attachment; filename=\"" . basename($emonhub_logfile) . "\"");
              header("Pragma: no-cache");
              header("Expires: 0");
              flush();
              if (file_exists($emonhub_logfile))
              {
                ob_start();
                readfile($emonhub_logfile);
                echo(trim(ob_get_clean()));
              }
              else
              {
                echo($emonhub_logfile . " does not exist!");
              }
              exit;
          }

borpin · 2019-04-10T09:48:25.231Z

OK, I mistakenly thought I was still seeing the emonhub.log in the logs folder (can’t check) but that the logging was being replicated in the syslog thus exacerbating the filling up log folder issue.