Skip to main content

rsyslogd for Mageia6

I've been having trouble with occasional segfaults with my desktop workstation. It would be nice to look at the logs to see where the problem might be, but the logs show nothing.

It might be easier, I thought, if I enabled remote logging. That way I would have a copy of the desktops' logs on a working computer, a Shuttle X35 I use as a http server running lighttpd, serving static pages for several hobby-related websites.

Installing rsyslog was easy using urpmi. It was the configuration that was tricky. The configuration file for Mageia is kept in /etc/rsyslog.d and consists of a single file, 00_common.conf. The modules that can be called by rsyslog can be found in /usr/lib64/rsyslog.

The man page states:
The main configuration file /etc/rsyslog.conf or an alternative file,given with the -f option, is read at startup. Any  lines  that  begin with the hash mark (``#'') and empty lines are ignored. If an error occurs during parsing the error element is ignored. It  is  tried  to parse the rest of the line.
That seems easy enough. The receiving host is configured to receive and the sending host is configured to send, both using the same file. Using advice from TheGeekStuff, you can cobble together a file that might work. Note that that sites' HOWTO page is dated 2012. The homepage for rsyslog also has rather extensive documents that tends to overwhelm.

One thing not found in the default 00_common.conf is the  "template" description that either generates the log file on the receiver, or configures rsyslog to send log info to the receiver.

RECEIVER

# This one is the template to generate the log 
# filename dynamically,depending on the
# client's IP address.

$template FILENAME,"/var/log/%fromhost-ip%/syslog.log"

SENDER

NOTE: 192.168.1.1 is used only as an example of the receiver's IP address.

# Provides UDP forwarding.
# The IP is the server's IP address

*.* @192.168.1.1:514 

# Provides TCP forwarding.
# But the current server runs on UDP

# *.* @@192.168.1.1:514

And, since I use sshutout and it needs to read /var/log/messages, the following needs to be added to the configuration file:

# Log info messages to messages file
#
*.=info;\
mail,news.none /var/log/messages

A FIX

If rsyslog will not start because of a missing dependency, it's because systemd is not configured correctly for rsyslog. This can be fixed with:

#systemctl enable rsyslog

Which creates the needed symlink.

The logs for my sender workstation are now included in my receiver workstation's /var/log/syslog

RESOURCES









Comments

Popular posts from this blog

DOS4GW.EXE Version 2.01a and Alternative DOS Extenders

DOS4GW.EXE The Tenberry DOS extender DOS4GW.EXE was used by many early DOS games. I still enjoy playing many of these games and DOS4GW.EXE is usable with DOSBox , so they can be played on Linux. However, the version of DOS4GW.EXE that was included with the game was whatever was current at the time. The most recent version that includes many bugfixes that possibly affected the games when used with DOSBox have been fixed in the latest version, 2.01a. It's not free at US$49, but you can downloaded it here . Simply substitute it for whatever version of DOS4GW.EXE your game provided and enjoy the bug-fixed goodness. Tenberry also makes a "high-performance" "pro" version of DOS4GW.EXE, but it costs $300. I think that they could sell quite a few of these to hobby users (since, you know, DOS is dead) for US$5. Open Souce to the Rescue There are better performing, free and Open Source alternatives available and worth a look. DPMI Explained Let's unders...

Unpack those .EXE game files from GOG.com (Plus other un-packers)

I just came upon innoextract today. I have many of the wonderful games from GOG.com, some of which have native Linux Clients. Before now, I've had to use PlayOnLinux or Crossover to install these for use with WINE, then add the Linux client. InnoSetup as a way to create an installer to install the games on Windows.  Daniel Scharrer has created innoextract to allow the unpacking of those archives on a non-Windows platform. The website provides information on using innoextract , but this information from the page is very useful: GOG.com Installers GOG.com installers with a 2.x.x version number on the download page or in the filename use InnoSetup 5.5.0 and cannot be extracted by innoextract 1.2 and older. Older installers use InnoSetup 5.2.3 and usually have no version in the filename. Some GOG.com multi-part installers with version 2.1.x or higher use RAR archives (renamed to .bin) to store the game data. These files are not part of the InnoSetup installer and require...

Medal of Honor: Allied Assault on Modern Linux

Medal of Honor: Allied Assault contains the original MOH and the two expansion packs, Spearhead and Breakthrough. MOH was first released in 2002. There is a Linux installer , released by Iculus, for the game, but it is for the original version and is a beta release. The libraries it needs are not available in a modern Linux. There is a standalone Linux binary available here . To use it, install the game on a Windows computer, patch it up to the latest level and then copy the installed game to a Linux computer. Place this downloaded archive in the root of the MOH directory and launch the game with ./mohaa_lnx . An attempt to use Crossover 16 to install the game failed as it was not possible to switch to the second DVD disc. There is a possible solution to this by creating a single DVD installation disk for MOH:AA. This process is described here . Reminder:   DVD5 = 4.70 GB DVD9 = 7.95 GB Better yet would be to create a single DVD that would encompass the original MOH...