[#INSTRM-50] [xcuActor] xcuActor not starting on BEE booting

[INSTRM-50] [xcuActor] xcuActor not starting on BEE booting Created: 27/Dec/16 Updated: 30/May/18 Resolved: 30/May/18
Status:	Won't Fix
Project:	Instrument control development
Component/s:	None
Affects Version/s:	None
Fix Version/s:	None

Type:

Task

Priority:

Major

Reporter:

arnaud.lefur

Assignee:

cloomis

Resolution:

Won't Fix

Votes:

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Description

This issue was initially filed into JIRA by 'arnaud.lefur' at 11/Jan/16 1:32 PM.

xcuActor does not automatically start when the BEE boots.
I don't what happened, it was the case before

Comments

Comment by arnaud.lefur [ 18/May/17 ]

For the bee-r1, I think that's working and could be considered as done, but I have to check I will pay attention next time.

For the bee-r2, It's not the case, there is no /etc/rc.local.
But since we considered that dewar as a r0 for thermal test and not a r2. Your startBee.sh script would not have worked anyway.
Either we create a startBee-r0.sh script or we keep doing it manually what do you think fmadec ?

Comment by fmadec [ 18/May/17 ]

don't know....

either we could do that.
either we could change the dnsmasq according: change r2 into r0

My concern is also that we need to track which component was/is use with which CU, meaning that r0 will become r2 at some point. but the track should be done with serial number ...

Comment by hassan [ 30/May/18 ]

Problem described is now out-of-date. Resolving as won't fix.

Generated at Sat Feb 10 16:20:59 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.

[INSTRM-50] [xcuActor] xcuActor not starting on BEE booting Created: 27/Dec/16 Updated: 30/May/18 Resolved: 30/May/18