Astaro User Bulletin Board
Go Back   Astaro User Bulletin Board > Closed Forums (read only) > ACC V2.000 BETA (closed)

Welcome to the Astaro User Bulletin Board.
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 03-13-2009, 08:00 AM
Senior Member
 
Join Date: Dec 2002
Location: Thailand
Posts: 107
Default [1.980] New device-agent is incompatible with ACC V1.4. [CHECKING]

After the upgrade to 1.950 all of the devices I manage were unable to connect. I have upgrade to 1.980 and still have the same problem.

This is what the log on the ASL (7.306) says:

2009:03:13-14:55:37 (none) device-agent[26903]: (ec) New device-agent is incompatible with ACC V1.4.

On the ASL device, the correct ACC type has been chosen (or 1.9 anyway)

Does anyone else have this problem. I have 25 firewalls reporting this problem.
Reply With Quote
  #2 (permalink)  
Old 03-14-2009, 11:45 AM
Thorsten Zachmann's Avatar
Moderator
 
Join Date: May 2007
Location: Karlsruhe
Posts: 62
Default

This error message should only be shown when the device connects to an ACC 1.4. Did you update your ACC from 1.4 to a new 1.980? If you enable the central management again do you still have the same problem?
Reply With Quote
  #3 (permalink)  
Old 03-15-2009, 07:27 AM
Senior Member
 
Join Date: Dec 2002
Location: Thailand
Posts: 107
Default

I have no 1.4 devices being managed. All of the firewalls managed are v7. I notice that now I have updated a couple of them to 7.4, they now show up as being managed. All 7.306 firewalls receive the "New device-agent is incompatible with ACC V1.4." message.
Reply With Quote
  #4 (permalink)  
Old 03-16-2009, 07:42 AM
megaposer's Avatar
Scourge of Humanity
 
Join Date: May 2006
Location: Karlsruhe, Germany
Posts: 593
Default

Hello,

could you please check that those 7.306 devices really do connect to an ACC V1.9 (or higher version)? ACC V1.9 is supported for devices with firmware 7.300 or higher, so 7.306 is not the issue here.

Maybe you can provide a logfile snippet /var/log/device-agent.log from one of the troubling devices and double-check whether the host definition of the ACC server really points to an ACC V1.9 server. Did you perchance use an ACC V1.4 earlier before switching to the newer version?

Also, a logfile snippet from your ACC server might help. You can find it in /var/log/accd.log.

Thanks and regards,
Henning
Reply With Quote
  #5 (permalink)  
Old 03-16-2009, 10:41 AM
Senior Member
 
Join Date: Dec 2002
Location: Thailand
Posts: 107
Default

There is nothing in device-agent.log

but found the error in accd.log, it writes errors to this log continuously .

2009:03:16-15:59:17 acc accd: 132144297 [0xa51f4ba0] WARN libs.io.RpcQueue null - RpcQueue::queueIn() Unsupported content type [device;ip:203.146.160.222]
2009:03:16-15:59:17 acc accd: 132144297 [0xa51f4ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during recv [device;ip:203.146.160.222]
2009:03:16-15:59:17 acc accd: 132144299 [0xb3210ba0] ERROR libs.io.Session null - send attempted after previous error [device;ip:203.146.160.222]
2009:03:16-15:59:17 acc accd: 132144300 [0xb3210ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during sendDone [device;ip:203.146.160.222]
2009:03:16-15:59:17 acc accd: 132144517 [0xa51f4ba0] WARN libs.io.RpcQueue null - RpcQueue::queueIn() Unsupported content type [device;ip:203.146.160.222]
2009:03:16-15:59:17 acc accd: 132144517 [0xa51f4ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during recv [device;ip:203.146.160.222]
2009:03:16-15:59:17 acc accd: 132144519 [0xa49f3ba0] ERROR libs.io.Session null - send attempted after previous error [device;ip:203.146.160.222]
2009:03:16-15:59:17 acc accd: 132144519 [0xa49f3ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during sendDone [device;ip:203.146.160.222]
2009:03:16-15:59:17 acc accd: 132144737 [0xa51f4ba0] WARN libs.io.RpcQueue null - RpcQueue::queueIn() Unsupported content type [device;ip:203.146.160.222]
2009:03:16-15:59:17 acc accd: 132144738 [0xa51f4ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during recv [device;ip:203.146.160.222]
2009:03:16-15:59:17 acc accd: 132144739 [0xac202ba0] ERROR libs.io.Session null - send attempted after previous error [device;ip:203.146.160.222]
2009:03:16-15:59:17 acc accd: 132144739 [0xac202ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during sendDone [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132144776 [0xa51f4ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during recv [device;ip:203.155.59.130]
2009:03:16-15:59:18 acc accd: 132144929 [0xa51f4ba0] WARN libs.io.RpcQueue null - RpcQueue::queueIn() Unsupported content type [device;ip:203.155.59.130]
2009:03:16-15:59:18 acc accd: 132144957 [0xa51f4ba0] WARN libs.io.RpcQueue null - RpcQueue::queueIn() Unsupported content type [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132144958 [0xa51f4ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during recv [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132144959 [0xa29efba0] ERROR libs.io.Session null - send attempted after previous error [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132144959 [0xa29efba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during sendDone [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132145189 [0xa51f4ba0] WARN libs.io.RpcQueue null - RpcQueue::queueIn() Unsupported content type [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132145190 [0xa51f4ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during recv [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132145191 [0xaa9ffba0] ERROR libs.io.Session null - send attempted after previous error [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132145192 [0xaa9ffba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during sendDone [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132145428 [0xa51f4ba0] WARN libs.io.RpcQueue null - RpcQueue::queueIn() Unsupported content type [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132145430 [0xa51f4ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during recv [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132145431 [0xb020aba0] ERROR libs.io.Session null - send attempted after previous error [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132145431 [0xb020aba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during sendDone [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132145652 [0xa51f4ba0] WARN libs.io.RpcQueue null - RpcQueue::queueIn() Unsupported content type [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132145653 [0xa51f4ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during recv [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132145654 [0xae206ba0] ERROR libs.io.Session null - send attempted after previous error [device;ip:203.146.160.222]
2009:03:16-15:59:18 acc accd: 132145655 [0xae206ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during sendDone [device;ip:203.146.160.222]
2009:03:16-15:59:19 acc accd: 132145893 [0xa51f4ba0] WARN libs.io.RpcQueue null - RpcQueue::queueIn() Unsupported content type [device;ip:203.146.160.222]
2009:03:16-15:59:19 acc accd: 132145894 [0xa51f4ba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during recv [device;ip:203.146.160.222]
2009:03:16-15:59:19 acc accd: 132145895 [0xb1a0dba0] ERROR libs.io.Session null - send attempted after previous error [device;ip:203.146.160.222]
2009:03:16-15:59:19 acc accd: 132145895 [0xb1a0dba0] WARN server.device.DeviceSession null - DeviceSession::clear() IO error during sendDone [device;ip:203.146.160.222]
Reply With Quote
  #6 (permalink)  
Old 03-16-2009, 11:48 AM
megaposer's Avatar
Scourge of Humanity
 
Join Date: May 2006
Location: Karlsruhe, Germany
Posts: 593
Default

Hi,

this seems weird ... the ACC is clearly telling that the devices, e.g. 203.146.160.222, which are trying to connect behave as they wanted to connect to an old ACC V1.4.

Could you maybe provide us with access to one of the troublesome devices and send the information to acc-support@astaro.com ... ?

Have you tried shutting down and reactivating the device-agent on the respective devices?

Thanks,
Henning
Reply With Quote
  #7 (permalink)  
Old 03-16-2009, 02:35 PM
Senior Member
 
Join Date: Dec 2002
Location: Thailand
Posts: 107
Default

We will arrange this tomorrow, however bear in mind there are 20 or so of these troublesome devices, and every one is a quite separate environment, and they all previously worked ok under 1.9.

I have stopped and restarted the device agents on two or three machines with no effect.
Reply With Quote
  #8 (permalink)  
Old 03-18-2009, 08:05 AM
megaposer's Avatar
Scourge of Humanity
 
Join Date: May 2006
Location: Karlsruhe, Germany
Posts: 593
Default

Could I kindly ask you to supply the /var/log/device-agent.log from one of the troubling devices in any case.

Please stop the connection to the ACC first, then reenable it again. Then wait around a minute and pull the logfile.

Thanks,
Henning
__________________
"Molest me not with this pocket calculator stuff."
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 09:05 PM.

 

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.


These pages are specifically maintained for the discussion of firewall issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases. issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases.