Errors

From Titan wiki
Jump to: navigation, search

If you experience any errors, this page should help you resolve them .
If your error is not listed here, make sure to Contact Us, and we will make sure to give you a solution as well as add it on this page.


This site does not show ALL possible errors, as we haven't encountered them all yet. But please, let us know if your error is not listed here!


Common Errors

ios_base::failbit set: iostream stream error - Can't create file or insufficient permissions to write file to location.

Solution: Change the download location to a folder you have write permissions, or run Titan as an elevated user.

resolve: No such host is known - Can't resolve the given URL. Often appears when you've entered an invalid URL as a router to connect to.

Solution: Make sure you got your URL correct (protocol defined URLs are not supported. Make sure your link is like "router.titan.com" and NOT like "http://router.titan.com/") Alternatively use an IP.

connect: An operation was attempted on something that is not a socket - {Insert professional statement here}

Solution: Make sure that the specified router is online, you've entered the correct address and port, and that you are able to communicate with the router at all as they might have blocked you :-(.

read_until: A blocking operation was interrupted by a call to WSACancelBlockingCall - {insert a very professional statement here}

Solution: idk

read_until: End of file - {insert some 31337 statement here}

Solution: idk

connect: No connection could be made because the target machine actively refused it - The machine is refusing your connection attempt.

Solution: Make sure the machine you're trying to connect to is accepting connections through the port you've specified, and that it's running a Titan router.

Invalid session key or password. - You've either entered wrong password to connect to this router, or you've provided an invalid session key.

Solution: First; enter the correct password. Second; reconnect.

OS Specific Errors

*nix:

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
what(): eventfd_select_interrupter: Too many open files
Aborted
OR
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
what(): epoll: Too many open files

This is a limitation by your OS (we've seen this on Fedora and OSX so far), but it can be solved!

  • Solution1: Close Demonsaw, go to the .toml file and reduce the number of threads. Restart Demonsaw.
  • Solution2: You can increase the maximum amount of open files your OS supports. To do so, do the following:
Open up a terminal, go su, then do echo 300000 > /proc/sys/fs/file-max ; echo USER hard nofile 64000 >> /etc/security/limits.conf ; echo "ulimit -n 4096" >> /home/USER/.bashrc ; echo "ulimit -n 4096" >> /home/USER/.bash_profile.
"USER" being the name of the user that this will affect (the one that runs demonsaw). The values here should be sufficient.
Log out and back in with the user specified.
If you now do ulimit -n, it will show you the value you entered above.

Read about it here and here.