Wed Dec 24 01:57:40 PST 2008
- Previous message: [Slony1-bugs] slony_show_configuration but no show_configuration.pl
- Next message: [Slony1-bugs] Bugs in scripts of Slony1 2.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
If DEBUGLEVEL is not defined in slon_tools.conf, slon_start can't start
slon. DEBUGLEVEL should be initialised to 0 if it does not exist in the
configuration file.
grep DEBUGLEVEL /usr/share/slony1/slon-tools.pm
my $cmd = "/usr/bin/slon -s $SYNC_CHECK_INTERVAL -d$DEBUGLEVEL
$CLUSTER_NAME '$dsn' ";
The watchdog does not start cause there is a syntax error in the script :
perl -c /usr/bin/slon_watchdog.old
syntax error at /usr/bin/slon_watchdog.old line 47, near "open "
/usr/bin/slon_watchdog.old had compilation errors.
Here is a patch that just add a semicolon :
--- /usr/bin/slon_watchdog.old 2008-12-24 10:51:34.000000000 +0100
+++ /usr/bin/slon_watchdog 2008-12-24 10:51:42.000000000 +0100
@@ -43,7 +43,7 @@
$pid = get_pid($node);
if (!($pid)) {
my ($dsn, $dbname) = ($DSN[$nodenum], $DBNAME[$nodenum]);
- my ($logfile) = "$LOGDIR/slon-$dbname-$node.err"
+ my ($logfile) = "$LOGDIR/slon-$dbname-$node.err";
open (SLONLOG, ">>$logfile");
print SLONLOG "WATCHDOG: No Slon is running for node $node!\n";
print SLONLOG "WATCHDOG: You ought to check the postmaster and slon
for evidence of a crash!\n";
Regards
--
Cyril SCETBON
**Happy Chrismukkah**
- Previous message: [Slony1-bugs] slony_show_configuration but no show_configuration.pl
- Next message: [Slony1-bugs] Bugs in scripts of Slony1 2.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list