http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/MB-7075 Couchbase Server logs on Mac OS are available under ~/Library/Application Support/Couchbase/var/lib/couchbase/logs but when clicking the "show logs" in the UI, we don't go to this path (we goto Couchbase.log under ~/Library/Logs) Only tested on MacOS MB-7075

Mac/OSX drop-down UI menu points to different log location

Bug Major Closed Fixed Public Jens Alfke Don Pinto Thu, 1 Nov 2012 12:56:08 -0500 Mon, 5 Nov 2012 23:15:33 -0600 Mon, 5 Nov 2012 17:25:27 -0600 2.0 UI 0 1 updated title <br/> <br/> Options discussed in bug-scrub... <br/> <br/> - remove the drop-down menu entry for View Logs. <br/> - fix the View Logs choice. <br/> <br/> Whatever&#39;s easier/less-intensive/less-riskier. <br/> <br/> Yaseen to followup with Jens -- leaving open, although not a blocker, per bug-scrub mtg ~/Library/Logs/Couchbase.log *is* a valid log file that the server writes to. I&#39;ve used it to diagnose Erlang exceptions launching the server. But it sounds like it&#39;s less important than the ones in the App Support folder? <br/> Changing the app to open a different log file is trivial; even easier than taking out the command. However, that log directory has a lot of files in it. Unfortunately the Console app can&#39;t be told to view a directory, just an individual file. <br/> <br/> So the choices would be: <br/> (a) Pick a single file in &#39;logs&#39; to open, if one of them is more important. <br/> (b) Make a submenu with items for all the significant log files <br/> (c) Make the menu command open the logs folder itself in the Finder (not terribly useful, because most of the files don&#39;t have filename extensions that indicate that they&#39;re text, so double-clicking them doesn&#39;t work.) I&#39;d vote for (a), and please check with alk on which one&#39;s the right one. <br/> <br/> Option (b), might be &quot;brittle&quot;, depending on how you do it. That is, if we change the logging files again in the server, it could be yet-another thing to fix in the future. <br/> <br/> i also vote for option (a) <br/> <br/> there are many files in that folder and if user needs to collect diagnostics they use cbcollect info command anyways. in bug-scrub mtg... <br/> <br/> option (d) - (alk proposes) pipe output of cbbrowse-logs to some window <br/> <br/> option (e) - remove this menu item and document the cbbrowse-logs command <br/> <br/> option (e) is the final bug-scrub mtg choice. <br/> <br/> <br/> Removed the menu command from the UI. (No code change, just deleted the menu item from the nib.) <br/> Out for review: <a href="http://review.couchbase.org/#/c/22280/">http://review.couchbase.org/#/c/22280/</a> Thanks Jens - resolving this as your fix was submitted past gerrit. verified with build 1941 Date of First Response Fri, 2 Nov 2012 13:12:33 -0500 Rank 3615 Time In Status