SixXS::Sunset 2017-06-06

My aiccu died!
[nl] Shadow Hawkins on Monday, 15 March 2010 20:15:06
Yesterday everything worked great, today I booted and I received:
* Starting SixXS Automatic IPv6 Connectivity Client Utility (aiccu)... [fail]
I have checked the time settings, but that doesn't seem to be the problem. I've checked the firewall, but that's not the issue, even though Ubuntu Hardy still has the bug that it automatically drops IPv6 traffic. I change that setting on boot though. This line keeps returning in my /var/log/syslog file since today:
Couldn't retrieve first tunnel for the above reason, aborting
There is no above reason given, and I don't know where to find the remaining data, for I can't imagine this is all that's logged.
My aiccu died!
[nl] Shadow Hawkins on Monday, 15 March 2010 21:10:55
Don't know how you did it, but you fixed it. Thanks!
My aiccu died!
[de] Shadow Hawkins on Monday, 15 March 2010 21:22:00
Hi Bart, I have some similar problem over here with Ubnutu Karmic: Most of the time it works without thought, but from time to time it just won't start. Syslog/messages just tell me that Aiccu "Couldn't retrieve first tunnel for the above reason, aborting" but it gives no reason to be above. Very uncommunicative for a unix tool... However, I found out that sometimes it wouldn't start because it couldnt query any (IPv4) Nameserver to ask at that time, because DHCP had not replied with one yet. Manual setup of an NS in resov.conf helped. Alternatively, a static entry for the tic-server in hosts could also fix that. But on ther times when it doesn't start, I cannot figure out any reason, and the hint to 'above reason' gets quite sarcastic with time. Today I found that killing an arbitrary process which had the string "aiccu" as parameter helped. Looks like aiccu just greps if ps outputs anything with aiccu and then aborts without any more information. Well, I'll keep observing that when it fais next time. /Flo
My aiccu died!
[ch] Jeroen Massar SixXS Staff on Monday, 15 March 2010 21:46:13
Syslog/messages just tell me that Aiccu "Couldn't retrieve first tunnel for
the above reason, aborting" but it gives no reason to be above. Very
uncommunicative for a unix tool...
Then turn on non-daemon + verbose mode. Syslog contains the rest of the message already btw.
However, I found out that sometimes it wouldn't start because it couldnt
query any (IPv4) Nameserver to ask at that time, because DHCP had not replied
with one yet. Manual setup of an NS in resov.conf helped.
Without IPv4 you can't make a tunnel, thus why are you then trying to start it?
Alternatively, a static entry for the tic-server in hosts could also fix that.
And then we cycle the TIC server to another host and you are bust. For reasons of redundancy and failover that will automatically happen.
Today I found that killing an arbitrary process which had the string "aiccu"
as parameter helped. Looks like aiccu just greps if ps outputs anything with
aiccu and then aborts without any more information.
This leads me to think that you already had a daemon running and are trying to restart it. In that case the newly run version just tells the old one to reload it's configuration, the new one then exits and tells you so.
My aiccu died!
[ch] Jeroen Massar SixXS Staff on Monday, 15 March 2010 21:43:05
Try running it in non-daemon verbose mode, as the README tells you to do and also the /contact/ page... Then you get full debug out output (including a heartbeat password which you want to strip out) which you can paste in the forum or heck, if you think it is a SixXS-side problem in a ticket. With that information we (SixXS Staff) but also other users who participate in the forum can look at it and we can tell you more. Just stating "it is dead" does not really help now does it.
There is no above reason given, and I don't know where to
find the remaining data, for I can't imagine this is all that's logged.
/var/log/messages or other such file depending on your syslog settings. But running in non-daemon and verbose mode will tell you a lot more.
My aiccu died!
[nl] Shadow Hawkins on Wednesday, 17 March 2010 17:42:08
I did put it in non-deamon and verbose mode, but all it did was print to screen what it would do to the log, and aiccu happened to be in verbose mode already somehow, so I wasn't getting any further information. I googled though for ways to retrieve more information, but I couldn't find any other ways. The DNS problem sounds familiar, my gateway somehow refuses to forward any DNS queries sent to it. The solution I found to that was setting the DNS server addresses in the resolv.conf file, though I suppose that wasn't enough. The tunnel works now, so I'm going to leave it as it is (same configuration as when it stopped), and I'm not going to touch it, until I really need to. Thanks for the help I received, and if you can tell me where I can find more details, I'll bring them back here, for I don't know where to look for them.
My aiccu died!
[ch] Jeroen Massar SixXS Staff on Saturday, 20 March 2010 11:47:29
All the details that AICCU produces are shown when setting non-daemonize + verbose, or looking in the appropriate log file...
My aiccu died!
[nl] Shadow Hawkins on Wednesday, 17 March 2010 17:58:31
In the /var/log/messages file I can only find the following
Mar 15 19:26:36 Lamp kernel: [ 40.925803] ip6_tables: (C) 2000-2006 Netfilter Core Team Mar 15 19:26:50 Lamp kernel: [ 57.109156] IPv6 over IPv4 tunneling driver Mar 15 19:26:50 Lamp kernel: [ 57.110001] sit0: Disabled Privacy Extensions Mar 15 19:26:50 Lamp kernel: [ 57.150486] tun: Universal TUN/TAP device driver , 1.6 Mar 15 19:26:50 Lamp kernel: [ 57.150497] tun: (C) 1999-2004 Max Krasnyansky < maxk@qualcomm.com>
which is repeated a couple of times, as I tried to get the service to run (even by restarting the entire system).

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker