|
Couldn't retrieve tunnel info
![[us]](/s/countries/us.gif) Shadow Hawkins on Wednesday, 17 December 2008 13:57:25
My tunnel didn't survive my computer hibernation last night, and when I tried to start it this morning, this is what I received:
C:\Users\cholzhauer\Desktop>aiccu-2008-03-15-windows-console.exe start
[error] Couldn't retrieve first tunnel for the above reason, aborting
C:\windows\aiccu.conf exists, and nothing else has changed (that I'm aware of)
I checked and my tunnel is not disabled.
Couldn't retrieve tunnel info
That means that you can't reach the TIC server.
Either you have connectivity issues, or you hammered the TIC server by repeatingly trying to contact it, and then it blocks you out. For the latter case, try again in an hour or so.
What you of course should do is set the 'verbose true' flag so that you get output from AICCU, that will help you diagnose issues a lot more.
Couldn't retrieve tunnel info
Shadow Hawkins on Wednesday, 17 December 2008 14:10:06
I haven't come across the verbose flag yet....what is it?
Thanks
Couldn't retrieve tunnel info
The flag which makes AICCU give out verbose output so that you can see what it is doing.
From the README:
WARNING: never run AICCU from DaemonTools or a similar automated
'restart' tool/script. When AICCU does not start, it has a reason
not to start which it gives on either the stdout or in the (sys)log
file. The TIC server *will* automatically disable accounts which
are detected to run in this mode. Use 'verbose true' to see more
information which is especially handy when starting fails.
Couldn't retrieve tunnel info
Shadow Hawkins on Wednesday, 17 December 2008 14:06:25
And now it works. I was contemplating a reboot, but I didn't get that far and figured I'd try the tunnel one more time...now it's connecting. Has anyone seen something like this before?
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 17 December 2008 14:06:04
Posting is only allowed when you are