[1.810] After updating to 7.280 device is not connecting [NOTABUG]

[Henrik]

Hi,

don't know if to call this a bug, but still posting it. I've selected an
appliance in the ACC and chose to updated it to 7.280. The updated
started and the appliance is working. But the connection to ACC is not
working any longer.

What it say's in the ACC you can see on the screenshot. After I connected
to the appliance the message on the Astaro Command Center page says:

ACC SSL-connect: 'IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0)'.

In the log file it says:

2008:08:15-20:28:38 fw device-agent[11510]: ACC connection failure, retrying (ip=83.64.86.214, port=4433). SSL-connect: 'IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0)'
2008:08:15-20:28:53 fw device-agent[11510]: ACC connection failure, retrying (ip=83.64.86.214, port=4433). SSL-connect: 'IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0)'
2008:08:15-20:29:08 fw device-agent[11510]: ACC connection failure, retrying (ip=83.64.86.214, port=4433). SSL-connect: 'IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0)'
2008:08:15-20:29:18 fw device-agent[11510]: Init iWatcher dropping file 0 '/etc/raid/status'.

A telnet from the appliance to the ACC work's.

And last but not least I've connected via SSH to the appliance and this is what I found there:

11510 ? S 0:24 /usr/sbin/acc-agent.pl --verbose=3 --daemon

So no idea why it's not connecting.

A /var/mdw/scripts/nextgen-agent restart solved the problem.

Regards,
Henrik

[megaposer]

Hi Henrik,

do you still have the packetfilter logfile from that date/time where we could check whether the outbound connection to tcp:4433 was dropped? Looks like some kind of race-condition to me ...

Cheers,
Henning

[Henrik]

Hi,

in the packetfilter.log from the time/date is nothing with dstport=4433.

I could make a telnet from the appliance to the acc with port 4433 while
this happend.

Regards,
Henrik

[megaposer]

Hello Henrik,

we are trying to reproduce this here, but did not encounter this behavior during the Up2Date from 7.270 -> 7.280 in our previous tests. Thanks for the report.

One thing I'd like to ask: Could you send the whole device-agent.log to acc-beta@astaro.com so I can have a glimpse there.

One more question: You triggered the Up2Date from the ACC ... did you already use 1.810 or the previous version 1.800?

Thanks again.

Regards,
Henning

[megaposer]

Hi Henrik,

Thanks for the logfile.

From a first look at it it seems that the disconnect you are talking about is not directly Up2Date related but occurred three times on last Friday:

• around 0400 in the morning
• around 1600 in the afternoon
• around 2020 in the evening

Anything strange going on? Was your Internet uplink lost?

Regards,
Henning

[Henrik]

Hi,

I couldn't say for sure but I don't think so. But what about the fact,
that no information was shown any longer?

Regards,
Henrik

[megaposer]

Hi,

you mean the missing information in the Inventory from your other thread were the ASG 110 appliance had issues after Up2Date from 7.270->7.280 ???

Cheers,
Henning

[Henrik]

OK, I'm sorry! After a reboot the IP of the ASG changed and that
was the reason why it couldn't connect.

I've updated to 7.290 and now the information is shown again. Let's see
for how long.

One again sorry for the trouble.

Regards,
Henrik

[megaposer]

Hello Henrik,

no problem at all, no need to be sorry.

Next time we also think of checking the packetfilter on the ACC itself - it should have revealed the mystery to us

We are glad that the issue seems resolved. I will leave this thread at the current status because I want to see if the previously lost information stays intact this time.

Cheers,
Henning

[megaposer]

I am now closing this issue as we have detected the glitch with missing information elsewhere and distributed points to reporters accordingly.