|
Blocked from TIC service: too many queries. Fix your client
![[pl]](/s/countries/pl.gif) Shadow Hawkins on Tuesday, 31 May 2011 20:57:40
Hello,
I was rebooting my router, and after the boot, I realized that my SixXS tunnel didn't come up.
Turning on "verbose" in AICCU's config file didn't help much, so I tried to connect manually to TIC daemon and got this output:
$ nc -v tic.sixxs.net 3874
DNS fwd/rev mismatch: tic.sixxs.net != broker04.ams.nl.sixxs.net
DNS fwd/rev mismatch: tic.sixxs.net != nlhaa01.sixxs.net
tic.sixxs.net [213.204.193.2] 3874 (sixxsconfig) open
500 Blocked from TIC service: too many queries. Fix your client; contact info@sixxs.net for more info
What's wrong? I checked client version:
# aiccu version
AICCU 2007.01.15-console-linux by Jeroen Massar
On https://www.sixxs.net/tools/aiccu/ it's the same.
The only thing it "might" make too many queries is my cron script which pings ipv6.google.com and if no reply, restarts aiccu (just once), but it runs just once per hour.
Thanks for help!
Blocked from TIC service: too many queries. Fix your client
![[us]](/s/countries/us.gif) Shadow Hawkins on Tuesday, 31 May 2011 23:42:39
Please post your script. It should kill and restart aiccu if and only if aiccu is still running, IPv4 is up, and IPv6 connectivity has been lost. Your script should not restart aiccu if it has exited: it will have done so for a reason.
A possible bug is that your script may be restarting aiccu every hour whether it needs to be restarted or not.
Blocked from TIC service: too many queries. Fix your client
Or what about NOT restarting it at all and fixing the real problem at hand?
It is mentioned quite clearly in the README of AICCU that one should not automatically restart it.
Blocked from TIC service: too many queries. Fix your client
Shadow Hawkins on Wednesday, 01 June 2011 15:30:44
Here's my script:
# cat /etc/cron.hourly/ping_ipv6
#!/bin/bash
ping6 ipv6.google.com -c4 > /dev/null
if [ $? -ne 0 ]; then
/etc/init.d/aiccu restart
/etc/init.d/snmpd restart
fi
Blocked from TIC service: too many queries. Fix your client
![[cn]](/s/countries/cn.gif) Shadow Hawkins on Tuesday, 09 April 2013 17:29:39
Dear all,
I encountered the same problem:
"root@OpenWrt:/etc# aiccu start
sock_getline() : "500 Quick Blocked from TIC service: too many queries. Fix your client; contact info@sixxs.net for more info"
TIC Server is currently not available
Couldn't retrieve first tunnel for the above reason, aborting"
I do not have any auto-restart script at all. But I did manually stop and start aiccu service when the IPv6 is broken after heavy traffic. Could such manually stop/start cause error 500? Is such behavior allowed? Or should I start it after a while? How could I trace the "too many queries" issue? Thank you!
Best Regards,
Ying Fang, { YFL1-SIXXS/T120026 } via [vnhan01.sixxs.net]
Jeroen Massar wrote:
Or what about NOT restarting it at all and fixing the real problem at hand?
It is mentioned quite clearly in the README of AICCU that one should not automatically restart it.
Blocked from TIC service: too many queries. Fix your client
I do not have any auto-restart script at all.
If you do not have a restart script, then what is causing the restarts?
Blocked from TIC service: too many queries. Fix your client
Shadow Hawkins on Wednesday, 01 June 2011 16:41:09
You must be losing IPv6 very frequently. You've got something wrong other than the known aiccu bug that sometimes causes it to hang when the ISP cycles the IP (but your script is still too simple).
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 01 June 2011 11:22:11
Posting is only allowed when you are