Syslog filled with pixelserv-tls errors (Failed to create conn_handler thread. err: 11)

  • ATTENTION! You'll notice a Prefix dropdown when you create a thread. If your post applies to one of the topics listed, please use that Prefix for your post. When browsing the thread list you can use the Prefix to filter the view.
  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Sas

Regular Contributor
I have installed and configured Diversion and pixelserv-tls, and everything SEEMS ok (I think). But I keep seeing a ton of lines like this in my syslog:
Code:
Jul 20 22:23:01 pixelserv-tls[18436]: Failed to create conn_handler thread. err: 11
Especially when I visit certain sites (like cnn.com). My ads do seem to be blocked, so maybe I should just ignore this, but does anyone have any advice on if this is something to be concerned about and if so what to try to fix it? I am on an RT-86U with latest 384.18, installed all of the above on the command line via amtm app, and I have my router WebUI served up on my LAN at 192.168.10.1:443 and it would APPEAR that pixelserv-tls is at 192.168.10.2:443 (although other ports are also open at that address). Thanks!
 

elorimer

Very Senior Member
80 and 443 are the default ports for pixelserv. You can move the WebUI to 8443 (that's my default) or you can use the -k switch for pixelserv to move it off 443 to, like 5443. Don't know if that is the source of your problem though.

I don't quite see how pixelserv can start if 443 is already in use though. Diversion will toss ad requests to 10.2 though even if pixelserv isn't running and they will be blocked.
 

pdc

Regular Contributor
I get that too, I have been ignoring it thus far. According to this link:
  • The error is most likely transient. Only to do with a particular request. Occasionally you will see it when your router is short of resources such as RAM. If you're seeing this error more frequently, it's a good indication your router might be working too hard.
You could try adding a swap file to see if that helps (amtm has the ability to do that).
 

Sas

Regular Contributor
I get that too, I have been ignoring it thus far. According to this link:
  • The error is most likely transient. Only to do with a particular request. Occasionally you will see it when your router is short of resources such as RAM. If you're seeing this error more frequently, it's a good indication your router might be working too hard.
You could try adding a swap file to see if that helps (amtm has the ability to do that).

I added swap file and the messages have gone away. Thanks for the tip!
 
  • Like
Reactions: pdc

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top