Troubleshooting

This section explains how to solve some problems that are known or frequent.

If what you need is not in this section, please contact us without hesitation through our Gitter channel. We will be happy to help you!

Index

• 'Discovery can't be started'
• 'I don't see the logs'
• 'Plugin with id 'witness' not found'
• 'Truffle doesn't seem to work connected to RSK'

Sections

Discovery can't be started

On Windows, if you start the node and it doesn't do anything, there is a high chance you have a problem with the UDP port of the node.

The UDP port is configured with the conf file you have to provide to the app, specifically with the value listen.port. By default this port is configured to 5050. To check if that port is already taken by other application you can follow these steps:

• Open a cmd console and run netstat -ano -p UDP | findstr :5050 (or replace 5050 with the port of your preference). You'll get a result with the process (if any) already using that port for UDP.
• with the process id you got (the value at the far right) run this command tasklist /FI "PID eq processId-you-got". This will let you know which application/service is using this port.

Please make sure the port of you preference is not taken by other application. If so, change the port in the config file.

Note: we are considering the possibility of changing this port (5050) in future releases to avoid this problem.

I don't see the logs

You can configure your own log level, following this instructions.

Plugin with id witness not found

If you have this error it's possible that you have missed to run rskj's dependencies. So please, follow the instructions depending on your operation system:

• Windows
• Mac
• Linux

Truffle doesn't seem to work connected to RSK

If you can not get truffle migrate complete, you will see something like:

Writing artifacts to ./build/contracts
Using network 'development'.
Running migration: 1_initial_migration.js
  Deploying Migrations...
  ... 0xc82d661d579e40d22c732b2162734f97aeb13fa095946927cbb8cd896b26a7a3

Be sure you are using the right configuration in the truffle.js file.

Remember that you need: node host, node port, network_id and in some cases the from (by default Truffle uses the first account in the node). This last one should be an account with positive balance (because it's the one Truffle uses to deploy contract and run transactions) and it should be present between the node's accounts (you can know that by executing the web3.eth.accounts command).

So, your config file should be like this:

module.exports = {
    networks : {
        rsk: {
            from : "0xcd2a3d9f938e13cd947ec05abc7fe734df8dd826",
            host : "localhost",
            port : 4444,
            network_id : "*" // Match any network id
        }
    }
};