New answers tagged

1

In man page of dnsmasq there is a option saying -l, --dhcp-leasefile=<path> Use the specified file to store DHCP lease information. So, you can use a file to log it. And the format of the file is: 946689575 00:00:00:00:00:05 192.168.1.155 wdt 01:00:00:00:00:00:05 946689522 00:00:00:00:00:04 192.168.1.237 * 01:00:00:00:00:00:04 946689351 00:...


1

The bigger question at play is to setup a method to figure out what is happening to the machine in the first place. During those lockups, are there spikes in memory/network? Can you ask your VPS provider is there is a noisy neighbor on your node? What do you see in your access logs - is it Google scanning you and causing a ton of traffic all at once? If you ...


1

You can edit the file, but the entries added to the file while you edit it are lost, because the editor loads the log file into memory, and saves the file from memory to disk after editing. However, you can move the log file to another file with mv command, reload webserver, and then edit the other file. This way no entries are lost. Webserver starts to ...


0

Just to add some context, be aware that many Xinetd configurations now have cumulative log settings by default- meaning that service-based log settings are appended to the default settings in /etc/xinetd.conf. You will see this if the configs use += instead of = to assign their log_on_success and log_on_failure settings. The quick fix is to either use = in ...


0

This should do it. (%{GREEDYDATA:srcint}:%{GREEDYDATA:srchost})|(%{GREEDYDATA:srcint}) also test with http://grokdebug.herokuapp.com/


0

I found, it causing by 'service zabbix-agent start' command, if i start zabbix agent via '/etc/init.d/zabbix-agent start' anything similar does not occur


0

Your insert queries are being logged because they are considered slow queries — taking longer than the default operationProfiling.slowOpThresholdMs value of 100ms. As at MongoDB 3.2, there isn't any configuration for what details should be logged with slow queries as this context is useful to understand why the query is slow. You can avoid logging slow ...


0

I used Powershell Import-Module WebAdministration $iisAppName = "MySite" $site = Get-ItemProperty IIS:\Sites\$iisAppName $site.id


1

In theory you could open a process which opens the socket, forks and each of the clients can then read from the socket. But the end result is probably not what you want. Since every read will remove the data from the socket buffer only one of the processes will get the data, i.e. depending on the scheduling sometimes the first child and sometimes the second ...


0

I'm not sure you can do that (since I don't believe it is a seekable file, but a stream of bytes), but you can have rsyslog write to multiple files, including have it write to, for example, a named pipe, that your custom tool can read from. That would probably be the easiest solution.


0

If you want to log both the "yui.jar" output and the "find" one, you have to add the redirect in quotation marks, like this: find . -type d -exec bash -c "cd '{}' && pwd && java -jar /opt/yui/yui.jar -o '.css$:.css' *.css >> log" \; >> log and maybe you want to specify a different name for the log file other than "log"...


0

This command logs the output of find but not the output of yui.jar. You will need to redirect the output then, something like ...java -jar /opt/yui/yui.jar -o '.css$:.css' *.css >logfile 2>errorlog ...


0

For some reason restarting rsyslog seems not reload all the settings, a reboot of the system solved the problem.



Top 50 recent answers are included