|
Ticket ID: SIXXS #5019189 Ticket Status: User PoP: chzrh02 - Init7 AG (Zurich)
AW: [SixXS] Tunnel Downtime for DTG4-SIXXS's 2001:1620:f00:125::2 => Please reactivate our SixXs account
![[ch]](/s/countries/ch.gif) Shadow Hawkins on Thursday, 23 June 2011 09:32:42
Hello SixXs team
Our IPv6 tunnel is down, because your robot deactivated our SixXs account. Please reactivate our account so I am able to get the tunnel up again.
---
Username : DTG4-SIXXS
Password :
URL : http://www.sixxs.net/home/
---
2011:06:23-08:02:33 astaro-1 aiccu[13952]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:03:04 astaro-1 aiccu[14047]: AICCU running as PID 14047
2011:06:23-08:03:04 astaro-1 aiccu[14047]: TIC Server is currently not available
2011:06:23-08:03:04 astaro-1 aiccu[14047]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:03:35 astaro-1 aiccu[14327]: AICCU running as PID 14327
2011:06:23-08:03:35 astaro-1 aiccu[14327]: TIC Server is currently not available
2011:06:23-08:03:35 astaro-1 aiccu[14327]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:04:06 astaro-1 aiccu[14412]: AICCU running as PID 14412
2011:06:23-08:04:06 astaro-1 aiccu[14412]: TIC Server is currently not available
2011:06:23-08:04:06 astaro-1 aiccu[14412]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:04:37 astaro-1 aiccu[14482]: AICCU running as PID 14482
2011:06:23-08:04:37 astaro-1 aiccu[14482]: TIC Server is currently not available
2011:06:23-08:04:37 astaro-1 aiccu[14482]: Couldn't retrieve first tunnel for the above reason, aborting
---
Kind regards
David Tschan
CTO FF GROUP
FERROFLEX AG, Neue Industriestrasse 2, CH-4852 Rothrist T 062 785 84 24, F 062 785 84 17
Ein Unternehmen der FF GROUP. Besuchen Sie unsere Website unter www.ferroflex.ch
FERROFLEX AG, Informatik Helpdesk: support@ferroflex.ch, T 062 785 84 44
-----Ursprngliche Nachricht-----
Von: SixXS [mailto:info@sixxs.net]
Gesendet: Donnerstag, 23. Juni 2011 01:15
An: Tschan David
Betreff: [SixXS] Tunnel Downtime for DTG4-SIXXS's 2001:1620:f00:125::2
Dear David Tschan,
This is the tunnelrobot at SixXS, mailing you to inform you that your tunnel to Init Seven AG has not been replying to pings for a period of time Here's the information regarding the tunnel:
Handle : DTG4-SIXXS
PoP Name : chzrh02 (ch.init7 [AS13030])
Your Location: Rothrist, ch
SixXS IPv6 : 2001:1620:f00:125::1/64
Your IPv6 : 2001:1620:f00:125::2/64
SixXS IPv4 : 213.144.148.74
Your IPv4 : 195.141.110.130
Last known responding: 2011-06-20 19:53:34
We use ICMPv6 ping to reach your IPv6 endpoint every hour.
Pings originate from the PoP and your box should reply from your endpoint over the tunnel, but it doesn't.
We try our utmost to keep a stable IPv6 deployment for you, and expect you to do the same for us. Therefor, we would like you to fix your tunnel endpoint 195.141.110.130 and re-establish the tunnel to as soon as possible, after 7 days of downtime the tunnel will automatically be set to user disabled state, thus avoiding us sending tunneled packets to the endpoint to which you requested the tunnel.
If your endpoint changed one is able to change the endpoint using the website.
The website (http://www.sixxs.net) also shows ping times and traffic graphs.
Check the FAQ section of the SixXS website for more information.
Regards,
The SixXS tunnelrobot.
P.S. This is an automated message, sent out once a day at maximum. For more information, please reply to this message (or mail to info@sixxs.net)
State change: user
The state of this ticket has been changed to user
AW: [SixXS] Tunnel Downtime for DTG4-SIXXS's 2001:1620:f00:125::2 => Please reactivate our SixXs account
When you stop hammering the TIC server the robot will automatically re-enable the tunnel.
As you can see there you are continuously restarting AICCU, don't do that.
Astaro has a fix for this for a long long time already, but unfortunately they don't seem to distribute it per default. Contact them for more information and complain that they are delivering broken setups to their customers.
Also, obviously your account is not disabled, otherwise you could not post here...
AW: [SixXS] Tunnel Downtime for DTG4-SIXXS's 2001:1620:f00:125::2 => Please reactivate our SixXs account
Shadow Hawkins on Thursday, 23 June 2011 10:38:22
I opened an ticket at Astaro, as we have an running support contract and installed the fix provided by Astaro. But our tunnel can't be re-establish , although our Astaro applicance isn't "hammering" your systems for the last couple of hours.
How long will I take to allow the TIC connect again ?
---
2011:06:21-21:28:42 astaro-1 aiccu[14434]: AICCU running as PID 14434
2011:06:21-21:28:43 astaro-1 aiccu[14434]: TIC Server is currently not available
2011:06:21-21:28:43 astaro-1 aiccu[14434]: Couldn't retrieve first tunnel for the above reason, aborting
---
Today I tested the access again, but no success:
---
2011:06:23-08:01:28 astaro-1 aiccu[13222]: AICCU running as PID 13222
2011:06:23-08:01:28 astaro-1 aiccu[13222]: TIC Server is currently not available
2011:06:23-08:01:28 astaro-1 aiccu[13222]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:01:31 astaro-1 aiccu[13251]: AICCU running as PID 13251
2011:06:23-08:01:31 astaro-1 aiccu[13251]: TIC Server is currently not available
2011:06:23-08:01:31 astaro-1 aiccu[13251]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:01:45 astaro-1 aiccu[13517]: AICCU running as PID 13517
2011:06:23-08:01:46 astaro-1 aiccu[13517]: TIC Server is currently not available
2011:06:23-08:01:46 astaro-1 aiccu[13517]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:02:02 astaro-1 aiccu[13771]: AICCU running as PID 13771
2011:06:23-08:02:02 astaro-1 aiccu[13771]: TIC Server is currently not available
2011:06:23-08:02:02 astaro-1 aiccu[13771]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:02:33 astaro-1 aiccu[13952]: AICCU running as PID 13952
2011:06:23-08:02:33 astaro-1 aiccu[13952]: TIC Server is currently not available
2011:06:23-08:02:33 astaro-1 aiccu[13952]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:03:04 astaro-1 aiccu[14047]: AICCU running as PID 14047
2011:06:23-08:03:04 astaro-1 aiccu[14047]: TIC Server is currently not available
2011:06:23-08:03:04 astaro-1 aiccu[14047]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:03:35 astaro-1 aiccu[14327]: AICCU running as PID 14327
2011:06:23-08:03:35 astaro-1 aiccu[14327]: TIC Server is currently not available
2011:06:23-08:03:35 astaro-1 aiccu[14327]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:04:06 astaro-1 aiccu[14412]: AICCU running as PID 14412
2011:06:23-08:04:06 astaro-1 aiccu[14412]: TIC Server is currently not available
2011:06:23-08:04:06 astaro-1 aiccu[14412]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:04:37 astaro-1 aiccu[14482]: AICCU running as PID 14482
2011:06:23-08:04:37 astaro-1 aiccu[14482]: TIC Server is currently not available
2011:06:23-08:04:37 astaro-1 aiccu[14482]: Couldn't retrieve first tunnel for the above reason, aborting
---
2011:06:23-08:36:15 astaro-1 aiccu[19716]: AICCU running as PID 19716
2011:06:23-08:36:15 astaro-1 aiccu[19716]: TIC Server is currently not available
2011:06:23-08:36:15 astaro-1 aiccu[19716]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:36:29 astaro-1 aiccu[19834]: AICCU running as PID 19834
2011:06:23-08:36:29 astaro-1 aiccu[19834]: TIC Server is currently not available
2011:06:23-08:36:29 astaro-1 aiccu[19834]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:37:00 astaro-1 aiccu[20137]: AICCU running as PID 20137
2011:06:23-08:37:00 astaro-1 aiccu[20137]: TIC Server is currently not available
2011:06:23-08:37:00 astaro-1 aiccu[20137]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:37:31 astaro-1 aiccu[20384]: AICCU running as PID 20384
2011:06:23-08:37:31 astaro-1 aiccu[20384]: TIC Server is currently not available
2011:06:23-08:37:31 astaro-1 aiccu[20384]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:38:02 astaro-1 aiccu[20521]: AICCU running as PID 20521
2011:06:23-08:38:02 astaro-1 aiccu[20521]: TIC Server is currently not available
2011:06:23-08:38:02 astaro-1 aiccu[20521]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:38:33 astaro-1 aiccu[20636]: AICCU running as PID 20636
2011:06:23-08:38:33 astaro-1 aiccu[20636]: TIC Server is currently not available
2011:06:23-08:38:33 astaro-1 aiccu[20636]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:39:04 astaro-1 aiccu[20797]: AICCU running as PID 20797
2011:06:23-08:39:04 astaro-1 aiccu[20797]: TIC Server is currently not available
2011:06:23-08:39:04 astaro-1 aiccu[20797]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:39:35 astaro-1 aiccu[20869]: AICCU running as PID 20869
2011:06:23-08:39:35 astaro-1 aiccu[20869]: TIC Server is currently not available
2011:06:23-08:39:35 astaro-1 aiccu[20869]: Couldn't retrieve first tunnel for the above reason, aborting
2011:06:23-08:40:06 astaro-1 aiccu[21022]: AICCU running as PID 21022
2011:06:23-08:40:06 astaro-1 aiccu[21022]: TIC Server is currently not available
AW: [SixXS] Tunnel Downtime for DTG4-SIXXS's 2001:1620:f00:125::2 => Please reactivate our SixXs account
But our tunnel can't be re-establish , although our Astaro applicance isn't "hammering" your systems for the last couple of hours.
And then below that you paste a reconnect every 30 seconds.... fix your setup. AICCU exits for a reason, because there is an error, do not automatically restart it in that case.
AW: [SixXS] Tunnel Downtime for DTG4-SIXXS's 2001:1620:f00:125::2 => Please reactivate our SixXs account
Shadow Hawkins on Thursday, 23 June 2011 13:37:10
I think you've got another understanding of hammering than me.
AW: [SixXS] Tunnel Downtime for DTG4-SIXXS's 2001:1620:f00:125::2 => Please reactivate our SixXs account
Repetitively restarting a tool is not solving the problem that you have -> that the tool exits with a valid reason. Fix that part instead of just restarting it, your connectivity is not working if it exits.
AICCU only needs to start ONCE, it then fetches the information and keeps on working. The AYIYA and heartbeat protocols take care of network changes, AICCU does not need restarts.
|
on Thursday, 23 June 2011 10:21:39
Posting is only allowed when you are