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-2054 Instrument control development <p>The temp board s/w is started from a crontab @reboot stanza. That occasionally fails &#8211; the software then needs to be launched manually. I believe that some system requirement is not met (oh, probably for the GPIO).</p> <p>Fix. </p> INSTRM-2054

Fix unreliable temp board s/w launch on boot.

Task Major Done Done cloomis cloomis near-term Wed, 9 Aug 2023 19:57:01 +0000 Tue, 17 Oct 2023 19:03:41 +0000 Tue, 17 Oct 2023 19:03:41 +0000 ics_xcu_smb 0 3 <p>Standard systemd ordering problem: when the cron @reboot fires, the machine does not yet know its hostname.</p> <p>Until a fix is put in, the workaround is just to repeat what happens at boot. I never remember what that is so just ask crontab:</p> <ul class="alternate" type="square"> <li>log in as <tt>pi@temps-xx</tt></li> <li><tt>crontab -l</tt></li> <li>run the <tt>@reboot</tt> command.</li> </ul> <p>standard password ?</p> <p>It seems so. I did this procedure for r1 and worked (I think).</p> <p>Tagged: 1.5.3<br/> Installing now on the hosts which are up, and will apply to the rest as they come up.</p> <p>Decided to go for a middle ground between a dumb sleep and a full systemd module: the launch script in the product loops on <tt>hostname</tt> to return a real hostname.</p> <p>Was surprised to see that this can take up to 10s. Might apply this to other machines.</p> Relates INSTRM-1991 Development Rank 0|02qpjd:00r20060i200186403c1i