search

kurtosis-tech / kurtosis

A platform for packaging and launching ephemeral backend stacks with a focus on approachability for the average developer.
https://docs.kurtosistech.com/
Apache License 2.0
311 stars 42 forks source link

Kurtosis service start not working #1685

Open piwonskp opened 8 months ago

piwonskp commented 8 months ago

What's your CLI version?

0.85.1

Description & steps to reproduce

Related to #1684.

When trying to start stopped service kurtosis is throwing an error that it's already started:

kurtosis service start broadcaster el-3-geth-lighthouse
INFO[2023-11-03T12:09:43Z] Starting service 'el-3-geth-lighthouse'      
Error:  An error occurred running command 'start'
  Caused by: An error occurred calling the run function for command 'start'                                                                            
  Caused by: An error occurred starting service 'el-3-geth-lighthouse' from enclave 'broadcaster'                                                      
  Caused by: An unexpected error occurred on Starlark for starting service                                                                             
  Caused by: An error occurred executing instruction (number 1) at DEFAULT_PACKAGE_ID_FOR_SCRIPT[3:20]:                                                
  start_service(name="el-3-geth-lighthouse")                                                                                                           
  Caused by: Failed starting service with unexpected error                                                                                             
  Caused by: An error occurred while starting services                                                                                                 
  Caused by: Service 'el-3-geth-lighthouse' is already started                                                                                         
root@localhost ➜  ~ kurtosis enclave inspect broadcaster                   
Name:            broadcaster
UUID:            4782664e9d1a
Status:          RUNNING
Creation Time:   Fri, 03 Nov 2023 02:04:26 UTC

========================================= Files Artifacts =========================================
UUID           Name
8ff23f14105a   2-lighthouse-nethermind-0-63
a48563c349b8   cl-genesis-data
fb8c710fa69d   dora-config
bba721d92500   el-genesis-data
8d1b77df6821   floral-rose
032fdd88b0fa   genesis-generation-config-cl
b2ccb1ec751e   genesis-generation-config-el
63f8586e8d64   geth-prefunded-keys
0570ed90459d   grafana-config
d55b1fb7e8b3   grafana-dashboards
e51df3a8db42   prometheus-config
bc3495029b2d   prysm-password
dbe06f9a9f83   silent-pine
0d01e37f242d   task-1a69c1c8-825b-4431-9e83-d4f7644d7fb5-python-script
7f68aaa6478f   validator-ranges

========================================== User Services ==========================================
UUID           Name                                             Ports                                                  Status
880887055a8e   beacon-metrics-gazer                             http: 8080/tcp -> http://127.0.0.1:35433/               RUNNING
688ca5edef7b   blob-spammer                                     <none>                                                 RUNNING
0c9563f87d68   broadcaster                                      http: 8080/tcp -> http://127.0.0.1:35427/               RUNNING
9602ce28c6bc   cl-1-lighthouse-geth                             http: 4000/tcp -> http://127.0.0.1:35418/               RUNNING
                                                                metrics: 5054/tcp -> http://127.0.0.1:35417/            
                                                                tcp-discovery: 9000/tcp -> 127.0.0.1:35416             
                                                                udp-discovery: 9000/udp -> 127.0.0.1:33197             
2e358d8f595d   cl-2-lighthouse-nethermind                       http: 4000/tcp -> http://127.0.0.1:35421/               RUNNING
                                                                metrics: 5054/tcp -> http://127.0.0.1:35420/            
                                                                tcp-discovery: 9000/tcp -> 127.0.0.1:35419             
                                                                udp-discovery: 9000/udp -> 127.0.0.1:33198             
4c54467926af   cl-2-lighthouse-nethermind-validator             http: 5042/tcp -> 127.0.0.1:35423                      RUNNING
                                                                metrics: 5064/tcp -> http://127.0.0.1:35422/            
6ad7811babe1   cl-3-lighthouse-geth                             http: 4000/tcp -> http://127.0.0.1:35426/               RUNNING
                                                                metrics: 5054/tcp -> http://127.0.0.1:35425/            
                                                                tcp-discovery: 9000/tcp -> 127.0.0.1:35424             
                                                                udp-discovery: 9000/udp -> 127.0.0.1:33199             
6836f79cd0e0   dora                                             http: 8080/tcp -> http://127.0.0.1:35434/               RUNNING
100446621efb   eip4788-contract-deployment                      <none>                                                 RUNNING
9ff5585a3f75   el-1-geth-lighthouse                             engine-rpc: 8551/tcp -> 127.0.0.1:35403                RUNNING
                                                                metrics: 9001/tcp -> 127.0.0.1:35402                   
                                                                rpc: 8545/tcp -> 127.0.0.1:35405                       
                                                                tcp-discovery: 30303/tcp -> 127.0.0.1:35401            
                                                                udp-discovery: 30303/udp -> 127.0.0.1:33194            
                                                                ws: 8546/tcp -> 127.0.0.1:35404                        
ecfbdc9af14d   el-2-nethermind-lighthouse                       engine-rpc: 8551/tcp -> 127.0.0.1:35408                RUNNING
                                                                metrics: 9001/tcp -> 127.0.0.1:35407                   
                                                                rpc: 8545/tcp -> 127.0.0.1:35410                       
                                                                tcp-discovery: 30303/tcp -> 127.0.0.1:35406            
                                                                udp-discovery: 30303/udp -> 127.0.0.1:33195            
                                                                ws: 8546/tcp -> 127.0.0.1:35409                        
77baf4019285   el-3-geth-lighthouse                             engine-rpc: 8551/tcp                                   STOPPED
                                                                metrics: 9001/tcp                                      
                                                                rpc: 8545/tcp                                          
                                                                tcp-discovery: 30303/tcp                               
                                                                udp-discovery: 30303/udp                               
                                                                ws: 8546/tcp                                           
f01d926ea97e   grafana                                          http: 3000/tcp -> http://127.0.0.1:35436/               RUNNING
2864d99c2688   mev-boost-1                                      api: 18550/tcp -> 127.0.0.1:35432                      RUNNING
3bca6f8d6319   mev-custom-flood                                 <none>                                                 RUNNING
259e96f674ce   mev-relay-api                                    api: 9062/tcp -> 127.0.0.1:35430                       RUNNING
8e47568a397b   mev-relay-housekeeper                            <none>                                                 RUNNING
66a74b3d232d   mev-relay-website                                api: 9060/tcp -> http://127.0.0.1:35431/                RUNNING
71dd9b58fad6   postgres                                         postgresql: 5432/tcp -> postgresql://127.0.0.1:35429   RUNNING
0e909b23b82d   prelaunch-data-generator-cl-genesis-data         <none>                                                 RUNNING
7d0c9763f371   prelaunch-data-generator-cl-validator-keystore   <none>                                                 RUNNING
32d826f95eb4   prelaunch-data-generator-el-genesis-data         <none>                                                 RUNNING
5e38798d612f   prometheus                                       http: 9090/tcp -> http://127.0.0.1:35435/               RUNNING
8bc3b9bcbcd7   redis                                            client: 6379/tcp -> 127.0.0.1:35428                    RUNNING
76d0faf26d69   task-1a69c1c8-825b-4431-9e83-d4f7644d7fb5        <none>                                                 RUNNING
a107c00dfa8c   transaction-spammer                              <none>                                                 RUNNING

Desired behavior

The service should start

What is the severity of this bug?

Painful; this is causing significant friction in my workflow.

What area of the product does this pertain to?

CLI: the Command Line Interface

h4ck3rk3y commented 8 months ago

Hey @piwonskp thanks for the bug report. I had a short fix in mind but that doesn't really fix the problem; so I will have to spend more cycles on this for a fix

In the interim I recommend using docker ps -a to get the container id of the dead container & you can start it via docker start containerId