After booting the NAS, domus.Link always needs a two step process to start

[Sag]

Hi Brad,

Let me tell an issue starting domus.Link after rebooting the NAS.

First, I check heyu status:
[~] # ps | grep heyu
10316 admin       564 S   grep heyu

So, heyu is not running
After that, I run domus.Link, that ask to start heyu.  Then I get:
Error
Exec: heyu start
heyu_engine is running - use 'heyu restart' to reconfigure

New check:
[~] #  ps | grep heyu
10480 httpdusr    568 S < heyu_relay DATA/.qpkg/Optware/bin/heyu -c /share/MD0_
10711 admin       556 S   grep heyu

So, I must stop heyu:

[~] # heyu stop

And after that, domus.Link ask to start and do it properly

Last checking:

[~] #  ps | grep heyu
10797 httpdusr    512 S < heyu_relay DATA/.qpkg/Optware/bin/heyu -c /share/MD0_
10800 httpdusr    592 S < heyu_engine ATA/.qpkg/Optware/bin/heyu -c /share/MD0_
12068 admin       560 S   grep heyu


Can you figure out why domus.Link always fails to start the first attemp?

Kind regards.

[Brad]

Do you have a log dir set for heyu? Would like to know what it contains for messages. If you have the auto engine start directive in the heyu conf, it should start the first time.

Brad

[Sag]

Keeping on the same behavior.

Auto engine start directive is present.
Log dir is set. But no log file is created on the first attempt, the failing one. After stopping heyu and clicking start, the second and successful attempt, "heyu.log.ttyUSB0" is created with normal message:
"10/11 00:39:59  Engine started".

Weird!

[Brad]

Don't know what to look for. This might be something to post in the heyu yahoo group as there are people in there that use the NAS as the server as well.

Brad