Hi! Thanks for your answer.
Just compiling the "new" version. If the problem persists, than I would also shut down one instance. The full configured bandwidth was used, but it really wasn't stable. I got this message once a week or so ... I will give a feedback soon. ;-) Regards, On 07.02.2017 18:52, Petrusko wrote: > It's running fine since this last upgrade, on my case. > (I've reduced RAM used by shutting down an instance... no problem, full > bandwidth is used now!) > > Good luck ;) > > > diffusae : >> Hi! >> >> Didn't update right now and got the same message today. >> So, it looks like, the address field wasn't the problem. >> >> Feb 05 15:01:25.000 [warn] assign_to_cpuworker failed. Ignoring. >> Feb 05 15:01:29.000 [warn] circuit_mark_for_close_: Bug: Duplicate call >> to circuit_mark_for_close at src/or/onion.c:238 (first at >> src/or/command.c:579) (on Tor 0.2.9.8 01ab67e38b358ae9) >> Feb 05 15:01:36.000 [warn] assign_to_cpuworker failed. Ignoring. >> >> Should I I update to 2.9.9, does it solve the issue. >> >> Regards, > > > > _______________________________________________ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
