https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-113 Instrument control development <p>Until now archiver log was created on <b>mhs machine</b> under <em>/tmp/</em> (default parameters)<br/> However there is only 10 Gb available on this partition.<br/> As a result after a month, the folder is saturated and causes the archiver to crash.</p> <p>Firstly, do we want to keep those logs ? To be honest we haven't done it so far.<br/> Secondly, is there different level of logging ? Because, currently the logfile size is growing really quickly, even quicker than the database itself.</p> <p>For now, it's save locally under another partition(500GB), but we could also use our NFS mount.</p> <p>Any thoughts ?</p> INSTRM-113

Archiver log is saturating /tmp/

Bug Major Done Done arnaud.lefur arnaud.lefur Wed, 17 May 2017 13:19:08 +0000 Tue, 29 May 2018 20:44:44 +0000 Tue, 29 May 2018 20:44:44 +0000 0 3 <p>I think the logs are basically worthless.</p> <p>committed <a href="https://github.com/Subaru-PFS/ics_archiver/commit/dd464817909a79c3321c539b9c39470a4cd6d64b" class="external-link" rel="nofollow">https://github.com/Subaru-PFS/ics_archiver/commit/dd464817909a79c3321c539b9c39470a4cd6d64b</a></p> <p>why not to have ticket specific branch??</p> <p>Yes, I could have done it that way <a href="https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=cloomis" class="user-hover" rel="cloomis">cloomis</a> ?<br/> To be clear you mean :</p> <ul> <li>create a branch named '<a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-113" title="Archiver log is saturating /tmp/" class="issue-link" data-issue-key="INSTRM-113"><del>INSTRM-113</del></a>'</li> <li>make my local change</li> <li>merge with master whenever the problem is solved</li> </ul> <p>Yes. Specifically:</p> <ul> <li>git checkout -b tickets/<a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-113" title="Archiver log is saturating /tmp/" class="issue-link" data-issue-key="INSTRM-113"><del>INSTRM-113</del></a></li> <li>work work work, all checked in.</li> <li>git checkout master</li> <li>git merge --no-ff tickets/<a href="https://pfspipe.ipmu.jp/jira/browse/INSTRM-113" title="Archiver log is saturating /tmp/" class="issue-link" data-issue-key="INSTRM-113"><del>INSTRM-113</del></a></li> </ul> <p>I believe, we'd better</p> <ul> <li>to make things possible to be tracked, especially for records at later phase including after delivery to Subaru. (somehow detailed) records of development history is a key for people working on maintenance to understand how/why code is organized as it is</li> <li>not to make multiple working versions in different branches, both for reducing maintenance load of codes and making people easy to install/use</li> <li>to have one PR per one modification, for getting clear review on both code and planning/functionality in quality and consistency point of view</li> </ul> <p>Changes long since merged. Considered resolved.</p> Duplicate INSTRM-42 Development Rank 0|ii0227: