Seems like every time I open the dev console these days I get this message:     The Developer Console didn't set the DEVELOPER_LOG trace flag on your   user. Having an active trace flag triggers debug logging. You have 403   MB of the maximum 250 MB of debug logs. Before you can edit trace   flags, delete some debug logs.   I've had to manually query ApexLog using the Tooling API and delete the existing logs every time for new logs to start recording again.   I did hear somewhere that SF switched from a time limit on debug logs to a size limit... But is there a setting change that allows SF to go back to deleting the oldest logs when the size limit is reached?
121628
Recently I have regularly been getting the error message below when opening the Developer Console:     The Developer Console didn't set the DEVELOPER_LOG trace flag on your   user. Having an active trace flag triggers debug logging. You have 316   MB of the maximum 250 MB of debug logs. Before you can edit trace   flags, delete some debug logs.   It happens in sandbox and scratch orgs. Haven't tried in production.  This only started happening recently. It goes away after clearing the logs but comes back after a few test runs.  Also: the Debug->Clear->Log Panel action is not working for me -- the logs stay put. I can remove them using the Query Editor as described , but it's pretty tedious.  Two questions:   Does anyone know a way to prevent the logs from exceeding the max level? Perhaps by having old logs cleared out automatically? Is there a known issue with the Clear Log Panel action? I am using Chrome btw.   Thanks!
48842
I'm creating my first full framework using Selenium and TestNG and recently implemented the ability to have logging enabled which will track every action (before and after).  public class CustomLogs {     //Set Logging_Level to "Debug" to enable logging     public String Logging_Level = "OFF";      public void Log(String message) {         if (Logging_Level == "Debug")         {System.out.println(message);         } else {         }     } }   Then, in my page objects, EVERY action method has a log statement before and after EVERY action.  public class LoginPage extends BrowserConfig {      final WebDriver driver;     private static CustomLogs customlogs = new CustomLogs();      //Elements on Page     @FindBy(id = "userId")     private WebElement userNameField;      //Constructor     public LoginPage(WebDriver driver) {         this.driver = driver;     }      //Fill Username     public void FillUsername(String userNameEntry) {         userNameField.clear();         customlogs.Log("Entering Username: "+userNameEntry+"...");         userNameField.sendKeys(userNameEntry);         customlogs.Log("Username entered.");   It seems like this is very beneficial, not only for debugging, but also because you can now print out every single action step, so keeping records or showing others what steps were completed is very straightforward.  But I can also see how this is cluttering the page object code.  Is this a good idea?  And/or is there a better way to do this?
119075
How do I limit a SQL Server Profiler trace to a specific database? I can't see how to filter the trace to not see events for all databases on the instance I connect to.
6268
A few days ago I realized my Ubuntu machine wouldn't load after login. After some digging around on a liveCD I realized my HDD was at 100% capacity, so I deleted some large files and was able to log in. I didn't have sudo permissions any more and had to boot into recovery mode and change the sodoers file, but eventually recovered root permissions.   I then noticed my machine was a little sluggish, and top was showing cupsd using 100% CPU. I've never seen this program before but I soon realized it was a legitimate program.   I the deleted about 40GB worth of videos, only to see my drive space deplete almost instantly in front of my eyes. With a little research and intuition, I realized it might be a a log file being blown up, and sure enough ls -lh /var/log/cups/ shown me an error_log file that was 80GB+ large.   I deleted the file sudo rm -rf /var/log/cups/error_log, killed the service with sudo service cups end, and went on my business. I realized after that it would have been a good idea to check out the contents of error_log before I deleted it, but I wanted to get rid of the thing before I was locked out again.  That was yesterday. Today, I started my laptop again and saw cupsd running again at 100% cpu, and sure enough I see my disk space depleting. I stopped the service and run tail -f /var/log/cups/error_log, and there are millions of lines of this:  W [15/Jul/2015:11:23:03 -0700] Notifier for subscription 911 (dbus://) went away, retrying! E [15/Jul/2015:11:23:03 -0700] File "/usr/lib/cups/notifier/dbus" has insecure permissions (0100777/uid=0/gid=0).   ==EDIT=================================================================  ls -l /usr/lib/cups/notifier/dbus shows permissions and ownership as -rwxrwxrwx 1 root root when they should be -rwxr-xr-x 1 daemon root, as described in the comments. sudo chown root:root /usr/lib/cups/notifier/dbus also did not fix the ownership problems.   Finally I removed and reinstalled cups, but to no avail. These links were given as potentially helpful guides,(,) but they ultimately result in suggesting a reinstall of the OS itself.
82365
A colleague once told me that the last option when everything has failed to debug on Linux was to use .  I tried to learn the science behind this strange tool, but I am not a system admin guru and I didn’t really get results.  So,   What is it exactly and what does it do? How and in which cases should it be used? How should the output be understood and processed?   In brief, in simple words, how does this stuff work?
37002
I'm trying to watch for any new output of a log file. Another script (not under my control) is deleting the file then creating a new one with the same name. Using tail -f doesn't work because the file is being deleted.
35165
I am working on a performance critical multi-threaded application. I looked at rlog, Ace and Boost logging. I chose rlog because I read it was the fastest (when logging is disabled, it has the least overhead).  The problem I have is it shows the file name, line number etc. even in release mode. If you can tell me how to shut that information off, my problem might be solved. In any case what is the most efficient logger in C++ for my situation?
86141
Possible Duplicate:          I deleted an open file and the disk usage was not reduced.  Will it free up the space if I deleted the link in /proc/PID/fd/N ? what will happen to the process (in general)?  To be specific: The server is running Zimbra and the sync.log just gone crazily big occasionally (it's Zimbra's bug)
76908
I'm trying to do some debugging in Android and I am running a live logcat in the Terminal, but the problem is that there is too much information generated so that when I am finished and try to copy all the information received by choosing "Select All" and then "Copy" a lot of the early output which is produced isn't copied. I was aware of history, but that just provides a list of commands that have previously been entered, not the output.  Can I see a history of all the output that the terminal gives, or perhaps can I have the terminal save as a text file all the output that it is producing?
60638
I am fixing an acquaintance's computer that ran out of disk space. Space was so critical that the OS did not launch any apps. I booted in Safe Mode (holding Shift during startup), deleted 1.5 GB of applications, and was able to launch the OS in normal mode and inspect the file system.  A search with du -sh * by hand revealed log files in ~/Library/Containers/com.apple.mail/Data/Library/Logs/Mail, in the format imagp.gmail.com-&lt;UID&gt;.txt that were 29 GB and 6 GB. I understood from  that these files are simply a log of all connections to the Gmail server:     Gmail is having trouble with the mac Mail client for quite some time. ... The Mail logs keep a record of the connection process, they're useful to to diagnose problems, ... It's safe to delete those logs.   I inspected the files: they contain both the records of the connections (error codes, server names) and also the content of emails (headers, plain text bodies, and mime-type attachments).  To prevent these problems in the future, does the OS have a way to limit the size of those logs, e.g. keeping only the last 30 days of connection, or doing a first-in-first-out of lines up to a certain file size?
24849
In previous versions of OS X the Console.app had buttons to allow you to see earlier or later in the logs.  In Sierra it seems to only show entries from when you start Console.app.  How do you get Console.app to show earlier entries?  e.g. I want to see the logs before my last reboot to see why it hung.
43053
Following a lot of people's advice, I am trying to use Mavensmate. Coming from developer console, there are still things I am not used to. One thing is I can't find where the debug log is. I tried everything I can think of under Mavensmate > debugging, but it seems to just processing for a while and then tell me it is a pass - but where is the log?   I assume that the debug log is not auto-generated like in developer console - so need to generate either a quick or debug log before opening it. Is that correct?
51719
I have been asked this question in two consecutive interviews, but after some research and checking with various systems administrators I haven't received a good answer. I am wondering if somebody can help me out here.  A server is out of disk space. You notice a very large log file and determine it is safe to remove. You delete the file but the disk still shows that it is full. What would cause this and how would you remedy it? And how would you find which process is writing this huge log file?
100372
As a sysadmin I sometimes face situations, where a program behaves abnormally, while not creating errors at all or creating nonsense error-messages.  In the past - before java came in - there were two counter-measures:   If nothing else helps - RTFM ;-) If even 1. does not help - trace the system-calls and see what is happening   I usually use strace -f for this task with Linux (other OS have similar trace-tools). Now while this usually works well for any old-fashioned program, the trace gets very fuzzy when doing the same on a java-process. There are so many system-calls seemingly unrelated to any real action, that it is terrible to search through such a dump.  Are there better ways to do that (if the source-code is not available)?
35439
Seems like there are around 5,000 wifi logs, each 2MB each, totaling nearly 10GB on my disk in /private/tmp. Can I delete these logs, or will macOS automatically delete them itself? I tried making a file using the mkfile command until I had about 2GB of disk space left, but nothing was automatically cleared.
2744
( deals with a similar issue, but it talks about a rotated log file.)  Today I got a system message regarding very low /var space.   As usual I executed the commands in the line of sudo apt-get clean which improved the scenario only slightly. Then I deleted the rotated log files which again provided very little improvement.  Upon examination I find that some log files in the /var/log has grown up to be very huge ones. To be specific, ls -lSh /var/log gives,   total 28G -rw-r----- 1 syslog            adm      14G Aug 23 21:56 kern.log -rw-r----- 1 syslog            adm      14G Aug 23 21:56 syslog -rw-rw-r-- 1 root              utmp    390K Aug 23 21:47 wtmp -rw-r--r-- 1 root              root    287K Aug 23 21:42 dpkg.log -rw-rw-r-- 1 root              utmp    287K Aug 23 20:43 lastlog    As we can see, the first two are the offending ones. I am mildly surprised why such large files have not been rotated.  So, what should I do? Simply delete these files and then reboot? Or go for some more prudent steps?  I am using Ubuntu 14.04.  UPDATE 1  To begin with, the system is only several months old. I had to install the system from scratch couple of months back after a hard disk crash.  Now, as advised in ,  I first checked the offending log files using tail, no surprise there. Then, for deeper inspection, I executed this script from the .  for log in /var/log/{syslog,kern.log}; do    echo "${log} :"   sed -e 's/\[[^]]\+\]//' -e 's/.*[0-9]\{2\}:[0-9]\{2\}:[0-9]\{2\}//' ${log} \   | sort | uniq -c | sort -hr | head -10 done   The process took several hours.  The output was in the line of,   /var/log/syslog : 71209229  Rafid-Hamiz-Dell kernel:  sda3: rw=1, want=7638104968240336200, limit=1681522688 53929977  Rafid-Hamiz-Dell kernel:  attempt to access beyond end of device 17280298  Rafid-Hamiz-Dell kernel:  attempt to access beyond end of device    1639  Rafid-Hamiz-Dell kernel:  EXT4-fs warning (device sda3): ext4_end_bio:317: I/O error -5 writing to inode 6819258 (offset 0 size 4096 starting block 54763121030042024)        &lt;snipped&gt;  /var/log/kern.log.1 : 71210257  Rafid-Hamiz-Dell kernel:  attempt to access beyond end of device 71209212  Rafid-Hamiz-Dell kernel:  sda3: rw=1, want=7638104968240336200, limit=1681522688    1639  Rafid-Hamiz-Dell kernel:  EXT4-fs warning (device sda3): ext4_end_bio:317: I/O error -5 writing to inode 6819258 (offset 0 size 4096 starting block 954763121030042024)    (/dev/sda3 is  my home directory. As we can find,   lsblk /dev/sda NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT sda      8:0    0 931.5G  0 disk  ├─sda1   8:1    0 122.1G  0 part / ├─sda2   8:2    0   7.6G  0 part [SWAP] └─sda3   8:3    0 801.8G  0 part /home    Why a process will want to write beyond the limit is actually outside the scope of my comprehension. Perhaps I will want to ask a different question in this forum if this continues even after a system update.)  Then, from  (you may want to check  for a deeper understanding), I executed,   sudo su - &gt; kern.log &gt; syslog   Now, these files have zero sizes. The system is running fine before and after a reboot.   I will watch these files (along with others) in the next few days and report back should they behave out-of-line.  As a final note, both  the offending files (kern.log and syslog), are set to be rotated, as inspection of the files (grep helped) inside  /etc/logrotate.d/ shows.  UPDATE 2  The log files are actually rotated. Looks like the large sizes were attained on a single day.
38501
I want to have a way to report the stack trace to the user if an exception is thrown. What is the best way to do this? Does it take huge amounts of extra code?  To answer questions:  I'd like it to be portable if possible. I want information to pop up, so the user can copy the stack trace and email it to me if an error comes up.