-
Notifications
You must be signed in to change notification settings - Fork 9
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
Log cannot be displayed #16
Comments
Are you actually storing logs in the db? That is what the log view shows. Not the contents of /var/log/zm/ The logs view works for me using current master. Line 1938 of functions.php has to do with X10 commands. Are you using the X10 code? Your web_php.log contains bad characters (non-utf-8) which cannot be decoded. This is the core of the problem. Ideally zm would strip them out from the logs before sending. I may have to look into that. |
I think so. The link used to work. I have not used it for a few weeks. So I do not know when ist stopped working.
Not that I am aware of. I am using a POE Camera. X10 is a powerline protocol, right? |
Today was the first time I was able to see the Log ever since I created the issue. edit: I'm at commit 617cdd5 |
I'd say its safe to close the issue. Displaying the log has been working for the last couple of months. |
The log is unusable if you have a lot of log entries. It works great if you only have a few. |
So then I'll re-open the issue... |
I'm currently running ZM in Version 1.31.0 from git clone
617cdd5fd385cc0dfd75b8aa56980ef42f492df7
on Ubuntu 16.04
For quite some time I have not been able to view the log messages over the web interface. Although all logs reside under /var/log/zm . Upon clicking the Log link on the ZM interface, the file web_php.log will be flooded with 7000-8000 lines of json formated data followed by the error message
Could the problem be related to a comma at the end of every json element? As far as I know it is not supposed to be there.
Find the log excerpt here: web_php.log
The text was updated successfully, but these errors were encountered: