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 Jan 6, 2020. It is now read-only.
The first time I started up the local_network_controller, it died (see below). Come to think of it now though, a os x dialog box did pop up asking me if i wanted to allow this to connect to the network. I did say yes, but probably not quickly enough. Then when I ran local_network_controller again it worked. So an idea would be to prompt the user to please allow access to the network instead of dying in this case.
[11:03][theuser@Bryans-MacBook-Pro:~/Programs/MSBinaries]
$./local_network_controller
MaidSafe Local Network Controller 0.8.100: Main Options
=======================================================
Initial options.
Please choose from the following options ('q' to quit):
1. Start a new network on this machine.
2. Connect to an existing VaultManager on this machine.
>> 1
Start Network
Path to VaultManager root directory. 'Enter' to use default
"/var/folders/q4/h7sl0_fd13s1y8l83frmmhgh0000gn/T/MaidSafe_TestNetwork"
Create VaultManager root directory. Do you wish to create
"/var/folders/q4/h7sl0_fd13s1y8l83frmmhgh0000gn/T/MaidSafe_TestNetwork"?
Enter 'y' or 'n'.
y
Path to vault executable. 'Enter' to use default
"/Users/theuser/Programs/MSBinaries/./vault"
VaultManager listening port. This should be between
1025 and 65536 inclusive. ('Enter' to use default 44444)
Number of Vaults to start.
This must be at least 10.
There is no upper limit, but more than 20 on one PC will probably
cause noticeable performance slowdown. 'Enter' to use default 12
Creating 12 sets of Pmid keys (this may take a while)
Creating two zero state routing nodes
Creating VaultManager and ClientInterface
Starting vault 1
Starting vault 2
Shutting down zero state routing nodes
Starting vault 3
Starting vault 4
Starting vault 5
Starting vault 6
Starting vault 7
Starting vault 8
Starting vault 9
Starting vault 10
Starting vault 11
Starting vault 12
Started Network of 12 Vaults - waiting for network to stabilise
Storing PublicPmid keys (this may take a while)
Sequence of entered commands:
Commands begin.
Initial options.
1
Path to VaultManager root directory.
Create VaultManager root directory.
y
Path to vault executable.
VaultManager listening port.
Number of Vaults to start.
Commands end.
/Users/theuser/Programs/MaidSafe/src/vault_manager/src/maidsafe/vault_manager/tools/actions/start_network.cc(204): Throw in function maidsafe::vault_manager::tools::::PublicPmidStorer::PublicPmidStorer()
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN8maidsafe13routing_errorEEEEE
std::exception::what: Not connected
The text was updated successfully, but these errors were encountered:
The first time I started up the local_network_controller, it died (see below). Come to think of it now though, a os x dialog box did pop up asking me if i wanted to allow this to connect to the network. I did say yes, but probably not quickly enough. Then when I ran local_network_controller again it worked. So an idea would be to prompt the user to please allow access to the network instead of dying in this case.
Start Network
Path to VaultManager root directory. 'Enter' to use default
"/var/folders/q4/h7sl0_fd13s1y8l83frmmhgh0000gn/T/MaidSafe_TestNetwork"
Create VaultManager root directory. Do you wish to create
"/var/folders/q4/h7sl0_fd13s1y8l83frmmhgh0000gn/T/MaidSafe_TestNetwork"?
Enter 'y' or 'n'.
Path to vault executable. 'Enter' to use default
"/Users/theuser/Programs/MSBinaries/./vault"
VaultManager listening port. This should be between
1025 and 65536 inclusive. ('Enter' to use default 44444)
Number of Vaults to start.
This must be at least 10.
There is no upper limit, but more than 20 on one PC will probably
cause noticeable performance slowdown. 'Enter' to use default 12
Creating 12 sets of Pmid keys (this may take a while)
Creating two zero state routing nodes
Creating VaultManager and ClientInterface
Starting vault 1
Starting vault 2
Shutting down zero state routing nodes
Starting vault 3
Starting vault 4
Starting vault 5
Starting vault 6
Starting vault 7
Starting vault 8
Starting vault 9
Starting vault 10
Starting vault 11
Starting vault 12
Started Network of 12 Vaults - waiting for network to stabilise
Storing PublicPmid keys (this may take a while)
Sequence of entered commands:
Commands begin.
Initial options.
1
Path to VaultManager root directory.
Create VaultManager root directory.
y
Path to vault executable.
VaultManager listening port.
Number of Vaults to start.
Commands end.
/Users/theuser/Programs/MaidSafe/src/vault_manager/src/maidsafe/vault_manager/tools/actions/start_network.cc(204): Throw in function maidsafe::vault_manager::tools::::PublicPmidStorer::PublicPmidStorer()
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN8maidsafe13routing_errorEEEEE
std::exception::what: Not connected
The text was updated successfully, but these errors were encountered: