The “Log” command allows us to visualize logs in real time generated as a history of the various events on our server, either by the access of visitors to the pages of the hosted sites or by the different tools that are executed internally.
Whether you want to debug an error, monitor an application or tool (php, mail, mysql, etc) or simply detect a visitor, bot, etc., among other applications, it is important to have this tool to do it easily, quickly and in real time.
sudo log <domain> <option>
sudo log sudo log example.com sudo log example.com -error sudo log example.com -wp sudo log example.com -only-error=on sudo log -mail
Use Ctrl+C to exit or end.
How can I view my website access log?
To view the log for a particular site:
sudo log domain.com
To view the access log of all websites hosted on my server:
The above options only show the access event log, but omit the “error” events.
How can I view the error log?
For example, we might want to see the “warning” or “error” of our WordPress site generated by PHP during the execution of a particular page.
sudo log domain.com -error
Similarly, if we wanted to see the error log generated by all the sites hosted on the server, we use the following command:
sudo log -error
When we have configured the Debug mode in WordPress in the
wp-config.php file we have the option to generate a
debug.log file, usually located in the
/wp-content folder. To display in real time from the command line the events generated in this file we use the following command:
sudo log domain.com -wp
How can I see the log generated by an application or tool?
Webinoly supports the visualization of events generated by Php, MySQL and Mail.
sudo log -php
sudo log -mysql
sudo log -mail
-php options are equivalent.
Turn Off access logs
To deactivate the general access log and apply to all the new sites created after this.
sudo log -only-error=on
To deactivate the log of a particular site.
sudo log dominio.com -only-error=on
We can activate it again using the
If you have any suggestions, ideas, or comments, or if you (gasp!) found a bug, join us in the support forum.