[INSTRM-2054] Fix unreliable temp board s/w launch on boot. Created: 10/Aug/23 Updated: 18/Oct/23 Resolved: 18/Oct/23 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | ics_xcu_smb |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | cloomis | Assignee: | cloomis |
| Resolution: | Done | Votes: | 0 |
| Labels: | near-term | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
The temp board s/w is started from a crontab @reboot stanza. That occasionally fails – the software then needs to be launched manually. I believe that some system requirement is not met (oh, probably for the GPIO). Fix. |
| Comments |
| Comment by cloomis [ 26/Aug/23 ] |
|
Standard systemd ordering problem: when the cron @reboot fires, the machine does not yet know its hostname. |
| Comment by cloomis [ 17/Oct/23 ] |
|
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:
|
| Comment by arnaud.lefur [ 17/Oct/23 ] |
|
standard password ? |
| Comment by yuki.moritani [ 17/Oct/23 ] |
|
It seems so. I did this procedure for r1 and worked (I think). |
| Comment by cloomis [ 18/Oct/23 ] |
|
Tagged: 1.5.3 Decided to go for a middle ground between a dumb sleep and a full systemd module: the launch script in the product loops on hostname to return a real hostname. Was surprised to see that this can take up to 10s. Might apply this to other machines. |