Astaro User Bulletin Board
Go Back   Astaro User Bulletin Board > Astaro Gateway Products > Hardware, Installation, Up2Date, Licensing
Reload this Page 7.402 filling up the logs
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

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.

Page 2 of 2 1 2
Reply
 
LinkBack Thread Tools Display Modes
  #11 (permalink)  
Old 05-11-2009, 02:31 PM
Junior Member
  
Join Date: Apr 2009
Posts: 5
Default
Same Problem here, when is the 7.403 expected?
This is not good, today we had 100% cpu load on one of the nodes and the network-connection broke, very bad as this system is located in egypt
Reply With Quote
  #12 (permalink)  
Old 05-23-2009, 03:31 AM
Member
  
Join Date: Mar 2009
Posts: 62
Default
Quote:
Originally Posted by BAlfson View Post
That is the nightly PostgreSQL database rollup. Have you considered adding RAM to your device?
I did try your advice though the system already had 2G.
I added a few more DIMMs and it now has 8G. Unfortunately, though BIOS shows/detects all the 8G during booting, ASG kernel doesn't seem to support PAE, thus can only see/use 3.5G.
Anyway, RAM upgrade doesn't seem to help the nightly cpu spikes. Worse part is the cpu spike kills my HA heartbeat as I mentioned here http://www.astaro.org/astaro-gateway...tbeat-nic.html
Reply With Quote
  #13 (permalink)  
Old 05-23-2009, 04:32 AM
BAlfson's Avatar
Moderator
  
Join Date: Mar 2007
Location: Oklahoma City
Posts: 5,390
Default
Can you try turning off HyperThreading?

I know that sounds random, but so does your problem.
__________________
ACE V7 - Astaro Preferred Partner since V3
Addicted to my iPhone!
Reply With Quote
  #14 (permalink)  
Old 05-28-2009, 02:29 PM
Member
  
Join Date: Jul 2008
Posts: 64
Default Logs get filled by 7.402
Hi,

i´ve got the same situation here with my ASG 220 Cluster since updating on 7.402

But i´ve no performance bottlenecks, only the logs getting filled and the second node seemed not to be updated as it should be

the up2date log shows up as follows:

2009:05:28-00:19:01 FW2-2 audld[1958]: >================================================= ========================
2009:05:28-00:19:01 FW2-2 audld[1958]: running on HA slave system or cluster node, exiting
2009:05:28-00:19:01 FW2-2 audld[1958]:
2009:05:28-00:19:01 FW2-2 audld[1958]: 1. main::run:190() audld.pl
2009:05:28-00:19:01 FW2-2 audld[1958]: 2. main::top-level:33() audld.pl
2009:05:28-00:20:02 FW2-2 auisys[2009]: Starting Up2Date Package Installer (Version 1.65)
2009:05:28-00:20:02 FW2-2 auisys[2009]: Searching for available up2date packages for type 'ips'
2009:05:28-00:20:02 FW2-2 auisys[2009]: id="371D" severity="info" sys="system" sub="up2date" name="No up2date packages available for installation" status="failed" action="preinst_check" package="ips"
2009:05:28-00:18:01 FW2-1 audld[17574]: Starting Up2Date Package Downloader (Version 1.57)
2009:05:28-00:20:07 FW2-2 auisys[2009]: Searching for available up2date packages for type 'avira'
2009:05:28-00:20:07 FW2-2 auisys[2009]: Installing up2date package file '/var/up2date//avira/u2d-avira-7.734-735.patch.tgz.gpg'
2009:05:28-00:20:07 FW2-2 auisys[2009]: Verifying up2date package signature
2009:05:28-00:20:07 FW2-2 auisys[2009]: Unpacking installation instructions
2009:05:28-00:20:08 FW2-2 auisys[2009]: Unpacking up2date package container
2009:05:28-00:20:08 FW2-2 auisys[2009]: Running pre-installation checks
2009:05:28-00:20:08 FW2-2 auisys[2009]: Starting up2date package installation
2009:05:28-00:20:08 FW2-2 auisys[2009]: >================================================= ========================
2009:05:28-00:20:08 FW2-2 auisys[2009]: Failed testing RPM installation (command: 'rpm --test -U /var/up2date//avira-install/u2d-avira-7.735/rpms/u2d-avira-7.734-735.patch.rpm')
2009:05:28-00:20:08 FW2-2 auisys[2009]:
2009:05:28-00:20:08 FW2-2 auisys[2009]: 1. Internal::Systemstep::real_installation:2292() auisys.pl
2009:05:28-00:20:08 FW2-2 auisys[2009]: 2. main:erform_work:919() auisys.pl
2009:05:28-00:20:08 FW2-2 auisys[2009]: 3. main::auisys_prepare_and_work:496() auisys.pl
2009:05:28-00:20:08 FW2-2 auisys[2009]: 4. main::top-level:33() auisys.pl
2009:05:28-00:20:08 FW2-2 auisys[2009]: |================================================= ========================
2009:05:28-00:20:08 FW2-2 auisys[2009]: Error details:
2009:05:28-00:20:08 FW2-2 auisys[2009]: (stdout):$VAR1 = [];
2009:05:28-00:20:08 FW2-2 auisys[2009]: (stderr):$VAR1 = [
2009:05:28-00:20:08 FW2-2 auisys[2009]: 'error: Failed dependencies:
2009:05:28-00:20:08 FW2-2 auisys[2009]: ',
2009:05:28-00:20:08 FW2-2 auisys[2009]: ' u2d-avira = 7-734 is needed by u2d-avira-7-735
2009:05:28-00:20:08 FW2-2 auisys[2009]: '
2009:05:28-00:20:08 FW2-2 auisys[2009]: ];
2009:05:28-00:20:08 FW2-2 auisys[2009]:
2009:05:28-00:20:08 FW2-2 auisys[2009]: 1. Internal::Systemstep::real_installation:2293() auisys.pl
2009:05:28-00:20:08 FW2-2 auisys[2009]: 2. main:erform_work:919() auisys.pl
2009:05:28-00:20:08 FW2-2 auisys[2009]: 3. main::auisys_prepare_and_work:496() auisys.pl
2009:05:28-00:20:08 FW2-2 auisys[2009]: 4. main::top-level:33() auisys.pl
2009:05:28-00:20:08 FW2-2 auisys[2009]: |================================================= ========================
2009:05:28-00:20:08 FW2-2 auisys[2009]: id="371O" severity="error" sys="system" sub="up2date" name="Fatal: Up2Date package installation failed: An error occured during the RPM pre-installation test (1)" status="failed" action="install" code="1" package="avira"
2009:05:28-00:20:08 FW2-2 auisys[2009]:
2009:05:28-00:20:08 FW2-2 auisys[2009]: 1. main::alf:71() auisys.pl
2009:05:28-00:20:08 FW2-2 auisys[2009]: 2. main:erform_work:965() auisys.pl
2009:05:28-00:20:08 FW2-2 auisys[2009]: 3. main::auisys_prepare_and_work:496() auisys.pl
2009:05:28-00:20:08 FW2-2 auisys[2009]: 4. main::top-level:33() auisys.pl


and the ha-log shows severals entries within a minute

2009:05:28-00:02:35 FW2-2 ctsyncd: Got SIGUSR1, set status to SLAVE
2009:05:28-00:02:35 FW2-2 ctsyncd: Got SIGUSR1, set status to SLAVE


Any ideas?



CU
Thomas
__________________
--------------------------------
2xASG 220 HA Cluster mode, V7.x,
SMTP Proxy, Webproxy, Mail-Spam/virus/encryption enabled.
Reply With Quote
  #15 (permalink)  
Old 05-28-2009, 06:13 PM
Junior Member
  
Join Date: May 2008
Location: Vilnius, Lithuania
Posts: 22
Default
Hi Thomas,

Astaro support fixed this problem in my 2xASG320 Cluster.
__________________
2 x ASG320 HA Cluster v7.502
4 x ASG110 v7.502
Reply With Quote
  #16 (permalink)  
Old 06-03-2009, 08:40 AM
Member
  
Join Date: Jul 2008
Posts: 64
Default
ok,

i´ll try the support option. Maybe they can lead me, how to handle this problem.

Cu
Thomas
__________________
--------------------------------
2xASG 220 HA Cluster mode, V7.x,
SMTP Proxy, Webproxy, Mail-Spam/virus/encryption enabled.
Reply With Quote
  #17 (permalink)  
Old 06-23-2009, 12:36 PM
Member
  
Join Date: Jul 2008
Posts: 64
Default
hi,

7.403 update with re-release 06/21/ solved the problem.
__________________
--------------------------------
2xASG 220 HA Cluster mode, V7.x,
SMTP Proxy, Webproxy, Mail-Spam/virus/encryption enabled.
Reply With Quote
Reply
Page 2 of 2 1 2

« Previous Thread | Next Thread »
Thread Tools
Display Modes
Linear Mode Linear Mode

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 12:21 AM.

 
Contact Us - Astaro User Bulletin Board - Archive - Top

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.