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 1 of 2 1 2
Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 04-24-2009, 05:33 PM
Member
  
Join Date: Mar 2009
Posts: 62
Default 7.402 filling up the logs
Yesterday my firewall (7.401) saw the new release (7.402), and I authorized it to take it because it is supposed to fix some e1000 driver issues with my Intel NIC.

Now I notice my ha log is filling up like crazy. Every second, it puts 10 lines like below:

2009:04:24-09:29:17 fw-2 ctsyncd: Got SIGUSR1, set status to SLAVE
2009:04:24-09:29:17 fw-2 ctsyncd: Got SIGUSR1, set status to SLAVE
2009:04:24-09:29:17 fw-2 ctsyncd: Got SIGUSR1, set status to SLAVE

fw-2 is the node 2 (slave). Anybody else seeing that?
Reply With Quote
  #2 (permalink)  
Old 04-24-2009, 10:28 PM
BAlfson's Avatar
Moderator
  
Join Date: Mar 2007
Location: Oklahoma City
Posts: 5,396
Default
Liug, what's the status on this problem? What did Support tell you?
__________________
ACE V7 - Astaro Preferred Partner since V3
Addicted to my iPhone!
Reply With Quote
  #3 (permalink)  
Old 04-25-2009, 02:14 AM
Member
  
Join Date: Mar 2009
Posts: 62
Default
They are not sure and need to ssh to the box to do some more research. We will arrange for that and see.
Reply With Quote
  #4 (permalink)  
Old 04-25-2009, 06:36 AM
Junior Member
  
Join Date: Apr 2009
Posts: 1
Default
Quote:
Originally Posted by liug View Post
They are not sure and need to ssh to the box to do some more research. We will arrange for that and see.
We are seeing the same thing plus a few other issues since the upgrade, like:

FATAL main: Node is not initialized properly - sleep 10s
2009:04:25-01:35:48 dtg1212dtg1208k12cluster-2 slon[3811]: [1-1] CONFIG main: slon version 1.2.15 starting up
2009:04:25-01:35:48 dtg1212dtg1208k12cluster-2 slon[3810]: [1-1] CONFIG main: slon version 1.2.15 starting up
2009:04:25-01:35:48 dtg1212dtg1208k12cluster-2 slon[5604]: [2-1] ERROR cannot get sl_local_node_id - ERROR: schema "_asg_cluster" does not exist
2009:04:25-01:35:48 dtg1212dtg1208k12cluster-2 slon[5604]: [3-1] FATAL main: Node is not initialized properly - sleep 10s
2009:04:25-01:35:48 dtg1212dtg1208k12cluster-2 slon[5605]: [2-1] ERROR cannot get sl_local_node_id - ERROR: schema "_asg_cluster" does not exist
2009:04:25-01:35:48 dtg1212dtg1208k12cluster-2 slon[5605]: [3-1] FATAL main: Node is not initialized properly - sleep 10s
2009:04:25-01:35:58 dtg1212dtg1208k12cluster-2 slon[3811]: [1-1] CONFIG main: slon version 1.2.15 starting up
2009:04:25-01:35:58 dtg1212dtg1208k12cluster-2 slon[3810]: [1-1] CONFIG main: slon version 1.2.15 starting up
2009:04:25-01:35:58 dtg1212dtg1208k12cluster-2 slon[5611]: [2-1] ERROR cannot get sl_local_node_id - ERROR: schema "_asg_cluster" does not exist
2009:04:25-01:35:58 dtg1212dtg1208k12cluster-2 slon[5611]: [3-1] FATAL main: Node is not initialized properly - sleep 10s
2009:04:25-01:35:58 dtg1212dtg1208k12cluster-2 slon[5610]: [2-1] ERROR cannot get sl_local_node_id - ERROR: schema "_asg_cluster" does not exist
2009:04:25-01:35:58 dtg1212dtg1208k12cluster-2 slon[5610]: [3-1] FATAL main: Node is not initialized properly - sleep 10s


let me know if support is able to help you out, we've seen this on every HA pair we upgraded to 7.402 so far.
Reply With Quote
  #5 (permalink)  
Old 04-25-2009, 07:42 AM
Junior Member
  
Join Date: May 2008
Location: Vilnius, Lithuania
Posts: 22
Default
I have 2 x ASG320 v.7.402
My problem with HA Cluster is the same.

HA log:
2009:04:25-09:35:43 iti-vv-2 ctsyncd: Got SIGUSR1, set status to SLAVE
2009:04:25-09:35:44 iti-vv-2 ctsyncd: Got SIGUSR1, set status to SLAVE
2009:04:25-09:35:45 iti-vv-2 ctsyncd: Got SIGUSR1, set status to SLAVE
2009:04:25-09:35:47 iti-vv-2 ctsyncd: Got SIGUSR1, set status to SLAVE

Slave unit not updating patterns.
Up2Date log:
2009:04:25-00:01:01 iti-vv-2 auisys[18503]: Starting Up2Date Package Installer (Version 1.65)
2009:04:25-00:01:01 iti-vv-2 auisys[18503]: Searching for available up2date packages for type 'ips'
2009:04:25-00:01:01 iti-vv-2 auisys[18503]: id="371D" severity="info" sys="system" sub="up2date" name="No up2date packages available for installation" status="failed" action="preinst_check" package="ips"
2009:04:25-00:01:06 iti-vv-2 auisys[18503]: Searching for available up2date packages for type 'avira'
2009:04:25-00:01:06 iti-vv-2 auisys[18503]: Installing up2date package file '/var/up2date//avira/u2d-avira-7.617-639.patch.tgz.gpg'
2009:04:25-00:01:06 iti-vv-2 auisys[18503]: Verifying up2date package signature
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: Unpacking installation instructions
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: Unpacking up2date package container
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: Running pre-installation checks
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: Starting up2date package installation
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: >================================================= ========================
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: Failed testing RPM installation (command: 'rpm --test -U /var/up2date//avira-install/u2d-avira-7.639/rpms/u2d-avira-7.617-639.patch.rpm')
2009:04:25-00:01:07 iti-vv-2 auisys[18503]:
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 1. Internal::Systemstep::real_installation:2292() auisys.pl
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 2. main:erform_work:919() auisys.pl
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 3. main::auisys_prepare_and_work:496() auisys.pl
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 4. main::top-level:33() auisys.pl
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: |================================================= ========================
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: Error details:
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: (stdout):$VAR1 = [];
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: (stderr):$VAR1 = [
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 'error: Failed dependencies:
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: ',
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: ' u2d-avira = 7-617 | u2d-avira = 7-618 | u2d-avira = 7-619 | u2d-avira = 7-620 | u2d-avira = 7-621 | u2d-avira = 7-622 | u2d-avira = 7-623 | u2d-avira = 7-624 | u2d-avira = 7-625 | u2d-avira = 7-626 | u2d-avira = 7-627 | u2d-avira = 7-628 | u2d-avira = 7-629 | u2d-avira = 7-630 | u2d-avira = 7-631 | u2d-avira = 7-632 | u2d-avira = 7-633 | u2d-avira = 7-634 | u2d-avira = 7-635 | u2d-avira = 7-636 | u2d-avira = 7-637 | u2d-avira = 7-638 is needed by u2d-avira-7-639
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: '
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: ];
2009:04:25-00:01:07 iti-vv-2 auisys[18503]:
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 1. Internal::Systemstep::real_installation:2293() auisys.pl
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 2. main:erform_work:919() auisys.pl
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 3. main::auisys_prepare_and_work:496() auisys.pl
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 4. main::top-level:33() auisys.pl
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: |================================================= ========================
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 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:04:25-00:01:07 iti-vv-2 auisys[18503]:
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 1. main::alf:71() auisys.pl
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 2. main:erform_work:965() auisys.pl
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 3. main::auisys_prepare_and_work:496() auisys.pl
2009:04:25-00:01:07 iti-vv-2 auisys[18503]: 4. main::top-level:33() auisys.pl
2009:04:25-00:02:02 iti-vv-2 audld[18536]: >================================================= ========================
2009:04:25-00:02:02 iti-vv-2 audld[18536]: running on HA slave system or cluster node, exiting
__________________
2 x ASG320 HA Cluster v7.502
4 x ASG110 v7.502
Reply With Quote
  #6 (permalink)  
Old 04-25-2009, 07:56 AM
WaMaR's Avatar
Senior Member
  
Join Date: Nov 2003
Location: Biala Podlaska, POLAND
Posts: 161
Default
I have 2 x ASG320 and yesterday upgrade to v.7.402
My problem with HA Cluster is the same.
2009:04:25-00:21:35 fw-2 ctsyncd: Got SIGUSR1, set status to SLAVE2009:04:25-00:21:36 fw-2 ctsyncd: Got SIGUSR1, set status to SLAVE2009:04:25-00:21:36 fw-2 ctsyncd: Got SIGUSR1, set status to SLAVE2009:04:25-00:21:37 fw-2 ctsyncd: Got SIGUSR1, set status to SLAVERegards,
WaMaR
__________________
2x ASG320 HA, v7.402
Reply With Quote
  #7 (permalink)  
Old 04-27-2009, 08:42 AM
Senior Schall und Rauch Member
  
Join Date: Nov 2008
Posts: 260
Default
Please ask support for a fix of ctsyncd (Mantis ID #10323). This will be fixed in v7.403.
__________________
"Datenautobahn: Einrichtung zur schnellen Übertragung großer Datenmengen (z.B. über das Telefonnetz)" (DUDEN, 21. Auflage)

Mario Schmidt
QA Engineer
Astaro AG
Reply With Quote
  #8 (permalink)  
Old 04-28-2009, 07:50 PM
Member
  
Join Date: Mar 2009
Posts: 62
Default
Quote:
Originally Posted by liug View Post
They are not sure and need to ssh to the box to do some more research. We will arrange for that and see.
They sshed into the box, re-initialized the postgresql database, which got rid of the error:

ERROR cannot get sl_local_node_id - ERROR: schema "_asg_cluster" does not exist

They also installed the new version of ctsyncd, which quieted down the ha logs.

Now looking at the last few days of cpu graph, I can see it is constantly low, except that at around 2:15-2:30AM, it has one big spike node 1 (master), every day. My guess is it must be some scheduled job. Does anybody else notice this? My problem is when this happens, node 1 will miss some heartbeat from node 2 (slave) and thinks node 2 is dead, then it will get the beat again, and re-add node 2 into the cluster. So every night I am still getting those HA alerts.
Reply With Quote
  #9 (permalink)  
Old 04-29-2009, 01:16 AM
BAlfson's Avatar
Moderator
  
Join Date: Mar 2007
Location: Oklahoma City
Posts: 5,396
Default
That is the nightly PostgreSQL database rollup. Have you considered adding RAM to your device?
__________________
ACE V7 - Astaro Preferred Partner since V3
Addicted to my iPhone!
Reply With Quote
  #10 (permalink)  
Old 04-29-2009, 01:32 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 have enough RAM, and it is only 20% used, flat. Not even a single spike over the last few weeks.
Reply With Quote
Reply
Page 1 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 02: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.