The first set of errors are for UDP, I believe.
The second one, about binding, I do not get here. Though I'm surprised it binds to 0.0.0.0, it should bind to 127.0.0.1. I tried setting 0.0.0.0 and it still works fine though. Does it work without torsocks (I guess you can pull the network cable to make sure nothing monero goes out) ?
In any case, a strace log would let us know what syscall is failing, and with what error.
../bitmonero-master/build/release/bin$ ./bitmonerod
Creating the logger system
2015-Jun-18 12:19:38.022305 Initializing cryptonote protocol...
2015-Jun-18 12:19:38.022613 Cryptonote protocol initialized OK
2015-Jun-18 12:19:38.023902 Initializing p2p server...
2015-Jun-18 12:19:50.336463 DNS seed node lookup either timed out or failed, falling back to defaults
2015-Jun-18 12:19:50.339200 Set limit-up to 128 kB/s
2015-Jun-18 12:19:50.339588 Set limit-down to 128 kB/s
2015-Jun-18 12:19:50.340018 Set limit to 128 kB/s
2015-Jun-18 12:19:50.340892 Binding on 0.0.0.0:18080
2015-Jun-18 12:19:50.341216 Net service bound to 0.0.0.0:18080
2015-Jun-18 12:19:50.341333 Attempting to add IGD port mapping.
sendto: Network is unreachable
2015-Jun-18 12:19:50.341795 No IGD was found.
2015-Jun-18 12:19:50.341941 P2p server initialized OK
2015-Jun-18 12:19:50.342337 Initializing core rpc server...
2015-Jun-18 12:19:50.342585 Binding on 127.0.0.1:18081
2015-Jun-18 12:19:50.342877 Core rpc server initialized OK on port: 18081
2015-Jun-18 12:19:50.343052 Initializing core...
2015-Jun-18 12:19:50.343508 Loading blockchain from folder /home/user/.bitmonero/lmdb ...
2015-Jun-18 12:19:50.717604 Blockchain initialized. last block: 0, d1079.h7.m19.s50 time ago, current difficulty: 1