marioolf commented on issue #722:
URL:
https://github.com/apache/incubator-teaclave/issues/722#issuecomment-1822724465
After removing every docker image related to teaclave, it seems that the
program actually is on SIM mode.
Now receiving this error:
```
teaclave-scheduler-service | [TRACE
rustls::server::tls12::client_hello] sending server hello Message { version:
TLSv1_2, payload: Handshake { parsed: HandshakeMessagePayload { typ:
ServerHello, payload: ServerHello(ServerHelloPayload { legacy_version: TLSv1_2,
random: a09be0c325eeedb6c1251a1725ccf363563be71b17941f58444f574e47524401,
session_id: 3f66b3d2bebb6d47f6630a81d4386e2c7f9d87160e09850ee2b62545fd3c980e,
cipher_suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, compression_method:
Null, extensions: [Protocols([ProtocolName(6832)]), ServerNameAck,
RenegotiationInfo(), ExtendedMasterSecretAck] }) }, encoded:
0200005e0303a09be0c325eeedb6c1251a1725ccf363563be71b17941f58444f574e47524401203f66b3d2bebb6d47f6630a81d4386e2c7f9d87160e09850ee2b62545fd3c980ec02c00001600100005000302683200000000ff0100010000170000
} }
teaclave-scheduler-service | [DEBUG rustls::server::tls12] Session
saved
teaclave-frontend-service exited with code 0
teaclave-authentication-service | [INFO
teaclave_authentication_service_enclave] Starting Authentication: Platform
first launch, admin user created ...
teaclave-authentication-service | [INFO
teaclave_authentication_service_enclave] Starting Authentication: setup API
endpoint finished ...
teaclave-authentication-service | [INFO
teaclave_authentication_service_enclave] Starting Authentication: setup
Internal endpoint finished ...
teaclave-authentication-service | [TRACE mio::poll] registering event
source with poller: token=Token(0), interests=READABLE | WRITABLE
teaclave-authentication-service | [TRACE mio::poll] registering event
source with poller: token=Token(1), interests=READABLE | WRITABLE
teaclave-scheduler-service | [DEBUG
teaclave_scheduler_service_enclave::service] Pulling task/cancel queue
teaclave-execution-service | [DEBUG
teaclave_execution_service_enclave::service] heartbeat_with_result response:
HeartbeatResponse { command: NoAction }
teaclave-scheduler-service | [DEBUG
teaclave_scheduler_service_enclave::service] Pulling task/cancel queue
teaclave-scheduler-service | [DEBUG
teaclave_scheduler_service_enclave::service] Pulling task/cancel queue
teaclave-execution-service | [DEBUG
teaclave_execution_service_enclave::service] heartbeat_with_result response:
HeartbeatResponse { command: NoAction }
teaclave-scheduler-service | [DEBUG
teaclave_scheduler_service_enclave::service] Pulling task/cancel queue
teaclave-execution-service | [DEBUG
teaclave_execution_service_enclave::service] heartbeat_with_result response:
HeartbeatResponse { command: NoAction }
teaclave-scheduler-service | [DEBUG
teaclave_scheduler_service_enclave::service] Pulling task/cancel queue
teaclave-scheduler-service | [DEBUG
teaclave_scheduler_service_enclave::service] Pulling task/cancel queue
teaclave-execution-service | [DEBUG
teaclave_execution_service_enclave::service] heartbeat_with_result response:
HeartbeatResponse { command: NoAction }
teaclave-scheduler-service | [DEBUG
teaclave_scheduler_service_enclave::service] Pulling task/cancel queue
```
Last two lines just loop.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@teaclave.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@teaclave.apache.org
For additional commands, e-mail: notifications-h...@teaclave.apache.org
