When I run the Local Network Controller I get this error:
/home/testing/MaidSafe/src/common/src/maidsafe/common/sqlite3_wrapper.cc(81): Throw in function maidsafe::sqlite::Transaction::Transaction(maidsafe::sqlite::Databes&)
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN8maidsafe12common_errorEEEEE
std::exception::what: Unstable to handle request
When I cd into:
/home/testing/MaidSafe/src/common/src/maidsafe/common/
and do git branch it says it is on the next branch.
@testing I was getting errors, I’m not sure if the same or different, but repeated runs eventually worked. Apparently it is due to timing issues and magic numbers, which are being eliminated. I’m not sure you are hitting the same thing, but it is possible that running more times will eventually work.
I have tried a couple dozen times. I selected 1 to start a new network on this machine and then hit enter to go with the five default choices. This is what I now consistently get:
Creating 16 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
Starting vault 13
Starting vault 14
Starting vault 15
Starting vault 16
Started Network of 16 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.
### Path to vault executable.
### VaultManager listening port.
### Number of Vaults to start.
### Commands end.
Throw location unknown (consider using BOOST_THROW_EXCEPTION)
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN8maidsafe14maidsafe_errorEEEEE
std::exception::what: Defaulted
g++ --version
g++ (Ubuntu 4.8.2-19ubuntu1) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
It’s the standard install on a ubuntu 14.04.1 LTS system.
Alright, back to square one :). @testing, can you run similar commands?
@hillbicks, can you build with clang-3.5 release instead of debug? Make a new build folder by rerunning the cmake configuration and add this build type flag:
You’re welcome, thank you for helping us out. The local network controller is a temporary tool we are looking to put out of service and move to the vault manager as a proper daemon. In the meantime though, there are bugs that need to rooted out.
The I can find two bugs in LNC, one relates to start_network.cc - failure to retrieve the stored PMID keys, that can be patched. The one both of you report on is less clear where it is coming from. On two of my machines (both ubuntu) LNC works reliably, but on a third ubuntu I can reproduce the errors you are reporting. So we need to find out what is the differentiating factor.
a quick update, if I transfer the executables built on a system where it works to the failing third machine, then it runs successfully. So that indicates to me not a hardware but compiler configuration difference that causes the bug.
g++ (Ubuntu 4.8.2-19ubuntu1) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
