Set up a Simplex virtual environment again with today's ISO: stx-2018-11-01-8-master.iso
Status "Enabling Compute Services" faced again, seems that Controller-0 is good but after some minutes it went down and reboot with status: "Critical failure, Auto-recovery, re-enabling" presented again:
Broadcast message from root@controller-0 (Thu 2018-11-01 14:06:34 UTC):
The system is going down for reboot NOW!
During the time when Controller-0 is up and running, could not get any Error messages in /var/log/puppet/latest/puppet.log. There are not Error messages.
From /var/log/sm/log I just get:
2018-11-01T13:24:19.000 controller-0 sm: err fmSocket.cpp(140): Socket Error: Failed to write to fd:(63), len:(1584), rc:(-1), error:(Broken pipe)
Set up a Simplex virtual environment again with today's ISO: stx-2018- 11-01-8- master. iso
Status "Enabling Compute Services" faced again, seems that Controller-0 is good but after some minutes it went down and reboot with status: "Critical failure, Auto-recovery, re-enabling" presented again:
Broadcast message from root@controller-0 (Thu 2018-11-01 14:06:34 UTC):
The system is going down for reboot NOW!
During the time when Controller-0 is up and running, could not get any Error messages in /var/log/ puppet/ latest/ puppet. log. There are not Error messages.
From /var/log/sm/log I just get:
2018-11- 01T13:24: 19.000 controller-0 sm: err fmSocket.cpp(140): Socket Error: Failed to write to fd:(63), len:(1584), rc:(-1), error:(Broken pipe)
Can someone replicate this issue?