SQL Anywhere for Linux - Anywhere Server and log entries

Author

Anywhere Server and log entries

Rado Rethmann

2005-04-05, 8:03 pm

Hello,

I'm running a Sybase Adaptive Server Anywhere Network Server Version
8.0.2.4474 on a Linux Debian Server (Kernel 2.6.8-SMP).
Everything works fine exept for the fact that the server daemon fills up
my messages log.
I'll get 1 (useless) status entry every minute, like
Nov 24 08:57:57 localhost SQLAnywhere(dbsrv1):
OS Available: 907932K,
Working Set: 69164K, Cache Target: 29863K
Nov 24 08:58:57 localhost SQLAnywhere(dbsrv1):
OS Available: 908320K,
Working Set: 69168K, Cache Target: 29863K
Nov 24 08:59:57 localhost SQLAnywhere(dbsrv1):
OS Available: 908160K,
Working Set: 69168K, Cache Target: 29863K
Nov 24 09:00:57 localhost SQLAnywhere(dbsrv1):
OS Available: 907408K,
Working Set: 69168K, Cache Target: 29863K

I don't want to get any Anywhere messages at all in my message logs.
I start the server with:
dbsrv8 -c 64M -cs -ch 512M -n DBSRV1 -x TCPIP -ud -o /opt/db/dbmessage.log
/opt/db/database/database1.db /opt/db/database/database2.db 2>&1 1>/dev/nul

I do get all the messages in the dbmessage.log file. Redirecting the
standard and error output to nul does not help.

Is there a switch for preventing the server daemon from writing to the
system logs ?

Thx for your help, Rado

Rick Blythe

2005-04-05, 8:03 pm

RTFM

start with the readme.

This is not the correct way to start the server in the background. Use
the -ud switch.

Also see:

ASA Database Administration Guide

The Database Server

The database server

Database server options

-s server option

ASA Database Administration Guide

The Database Server

The database server

Database server options

-qp server option
"Rado Rethmann" < discussion@centermai
l.net> wrote in message
news:opshyvcpuoh8ovj
h@rado-xpc.cocon...
Hello,

I'm running a Sybase Adaptive Server Anywhere Network Server Version
8.0.2.4474 on a Linux Debian Server (Kernel 2.6.8-SMP).
Everything works fine exept for the fact that the server daemon fills up
my messages log.
I'll get 1 (useless) status entry every minute, like
Nov 24 08:57:57 localhost SQLAnywhere(dbsrv1):
OS Available: 907932K,
Working Set: 69164K, Cache Target: 29863K
Nov 24 08:58:57 localhost SQLAnywhere(dbsrv1):
OS Available: 908320K,
Working Set: 69168K, Cache Target: 29863K
Nov 24 08:59:57 localhost SQLAnywhere(dbsrv1):
OS Available: 908160K,
Working Set: 69168K, Cache Target: 29863K
Nov 24 09:00:57 localhost SQLAnywhere(dbsrv1):
OS Available: 907408K,
Working Set: 69168K, Cache Target: 29863K

I don't want to get any Anywhere messages at all in my message logs.
I start the server with:
dbsrv8 -c 64M -cs -ch 512M -n DBSRV1 -x TCPIP -ud -o /opt/db/dbmessage.log
/opt/db/database/database1.db /opt/db/database/database2.db 2>&1 1>/dev/nul

I do get all the messages in the dbmessage.log file. Redirecting the
standard and error output to nul does not help.

Is there a switch for preventing the server daemon from writing to the
system logs ?

Thx for your help, Rado

Greg Fenton

2005-04-05, 8:03 pm

Rick Blythe wrote:
>
> This is not the correct way to start the server in the background. Use
> the -ud switch.
>

Actually, Rado's post does indeed use the -ud flag. This is the
appropriate way.

Rick's suggestion of using the -qp and the -s flags allow you to alter
the behaviour of the engine's logging to the system log.

Redirecting STDOUT and STDERR won't have any effect if you start the
engine with the -ud flag. This causes the engine to start as a "daemon"
which begins by separating from the parent shell, closing STDOUT, STDERR
and STDIN and chroot'ing away from the current directory.

The logging to syslogd is done explicitly in the engine code (or any
application code), it is not simply the STDOUT/STDERR output from a process.

You might also want to take a look at the -os flag if you want to limit
the growth of the -o log file.

I suggest browsing all of the server options to see if there are other
behaviours that you might want to tweak in a production setup.

Hope this helps,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

Sponsored Links