You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2020. It is now read-only.
I tried to restart both Parity UI and Parity Ethereum client: yes
_Your issue description goes here below.
I started Parity UI as always in order to do an ETH transaction. The interface does not load and instead shows first that the parity node can not be reached and with a second error message, the following:
Please attach the following debugging info:
OS: darwin
Arch: x64
Channel: beta
Error: Exit code 1, with signal null.
Please also attach the contents of the following file:
/Users/**/Library/Application Support/parity-ui/parity.log
_Your issue description goes here below.
I started Parity UI as always in order to do an ETH transaction. The interface does not load and instead shows first that the parity node can not be reached and with a second error message, the following:
Please attach the following debugging info:
OS: darwin
Arch: x64
Channel: beta
Error: Exit code 1, with signal null.
Please also attach the contents of the following file:
/Users/**/Library/Application Support/parity-ui/parity.log
The parity.log file has this in it:
stack backtrace:
0: 0x105c14d9e -
1: 0x105c15b6c -
2: 0x105c15bed -
3: 0x105c148ab -
4: 0x1040595ba -
5: 0x105c82e58 -
6: 0x105c8296c -
7: 0x105c82858 -
8: 0x105cc6181 -
9: 0x104afb37d -
10: 0x104b10ead -
11: 0x104af876f -
12: 0x104b20035 -
13: 0x104b35606 -
14: 0x104b206c4 -
15: 0x105c8ec0e -
16: 0x104b38782 -
17: 0x105c7f6a7 -
18: 0x105c636a8 -
19: 0x7fff60e92304 - __pthread_body
20: 0x7fff60e9526e - __pthread_start
Thread 'IO Worker #3' panicked at 'Error binding UDP socket: Os { code: 48, kind: AddrInUse, message: "Address already in use" }', libcore/result.rs:1009
This is a bug. Please report it at:
2019-01-17 15:05:59 Finishing work, please wait...
2019-01-17 15:06:00 Error sending a subscription update: Error(ConnectionClosed, State { next_error: None, backtrace: InternalBacktrace { backtrace: None } })
The text was updated successfully, but these errors were encountered: