syslog

I have a (VoIP) device on my home network that is not performing correctly and want to start a syslog as a part of debug and error tracking - the device can be easily configured to output info to a syslog on the network. But how to get the syslog up and running? I understand that its a core technology in OSx and there was (is?) at least one app to help configure this - Syslog gen x 3 by David Cooper. However this appears to be no longer available. I want to avoid the command line if at all possible... I dumped a PC in favour of a Mac back in 1989 specifically to avoid that sort of stuff.

Any pointers?

OSx 10.4.3
iMac 20"
Sipura SPA 2000, latest fimware

Mac OS X (10.4.3)

Posted on Dec 13, 2005 3:08 AM

Reply
7 replies

Dec 13, 2005 8:37 AM in response to James Wilson

The chances are, syslogd is already installed and running on your machine.

Have you tried sending the logs to your system and seeing what happens? (the logs usually write somewhere in /var/log.

If it doesn't work you may need to edit the syslog.conf to filter the messages accordingly.

Off-hand, I don't know of a GUI way of doing this, but it isn't hard in the terminal.

Dec 13, 2005 4:08 PM in response to James Wilson

One little butt-biter with syslog is that syslogd can only write to an existing file, so if you configure it to write to it's own file, you have to create the file first. In terminal:

sudo touch /var/log/filename

Roger

Dec 13, 2005 6:32 PM in response to James Wilson

James Wilson

I have my Airport Express configured to log to Syslog host, this only needs entering the Syslog host ip address, and the Log level and results in kernel messages in the MacOS System log which you can read with your Console app.

In my case quite easy:
In the airport express configuration:

send logging to ip adddress < 10.0.1.2 > (your computer ip)
log level < 7 dedbug > (drop down list selection)

Resulting typical /var/log/system.log entry:

Dec 14 12:25:36 mac02A kernel[0]: AirPort: Link DOWN (out-of-range 0)

Hopefully your VOIP device configuration is also simple.
You might have to change the log level to higher priority if nothing shows up.

PX.


G5PMac,G4iBook Mac OS X (10.4.2)

Dec 13, 2005 9:19 PM in response to PatXie

Correction to my previous post. (Unable to edit).

Re:

Resulting typical /var/log/system.log entry:
Dec 14 12:25:36 mac02A kernel[0]: AirPort: Link DOWN (out-of-range 0

That message originate from the MacOS internal logging, I am still trying to find where/what the external Airport Express Base station status monitor logging appears. Not as easy as I thought. Will advise.

PX.

G5PMac,G4iBook Mac OS X (10.4.2)

G5PMac,G4iBook Mac OS X (10.4.2)

Dec 15, 2005 5:01 AM in response to James Wilson

Yes very useful reference, the syslogd.plist edit for permanent logging completes the story nicely.

See also Apple Tech Article ID: 107993

Link:
http://docs.info.apple.com/article.html?artnum=107993

AirPort Extreme: Remotely logging base station activity with syslog.
It is a useful example covering other generally relevant points.
But just uses terminal shell command to open the syslog udp 514 logging port.

It worked for my Airport Express Base station logging via WIFI.

Points to note-

1. MacOSX Sharing firewall.

syslogd UDP port 514 must be open for these messages.
(If the firewall Advanced option UDP Blocking is enabled )

2. /etc/syslog.conf:

A separate log file is created, but local0.* is used by the MacOSX firewall and the Airport Express and probably other devices, so you get firewall and other logging in both the ipfw.log and the AirPort.log. (grep could help here).



G5PMac,G4iBook Mac OS X (10.4.2)

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

syslog

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.