Skip to content
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

Output to log, not in database #9

Closed
pielambr opened this issue Oct 15, 2013 · 4 comments
Closed

Output to log, not in database #9

pielambr opened this issue Oct 15, 2013 · 4 comments

Comments

@pielambr
Copy link
Contributor

Hi... I have this issue that I can't see any reports in the database. They do show in the log and the log says that it can successfully insert them into the database... What can I do?

Edit:
Inserting report data failed ! #1118 : Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.

Edit: fixed by switching to MyISAM

@Medialoha
Copy link
Owner

Hi,

We also had this issue. I think we need to record the report in a file when any kind of error occured on report reception. Maybe we should send this file by email...

Thanks

@pielambr
Copy link
Contributor Author

I think you should log to the database maybe and show it on the administration panel. I find it kind of dangerous to leave sensible information in a log that everyone can read like if there is a password stored in the preferences or a username from the application...

@Medialoha
Copy link
Owner

Logging into DB is a way, and I'll have some reflection about it. The most important, as you said, is to secure the information logged.

@Medialoha
Copy link
Owner

Comming mabl release will include a logs view, and the logs directory is secured with an htaccess file which restrict access to localhost only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants