Skip to main content

Using Ubuntu Karmic Koala for remote logging

I've few routers running DD-WRT and OpenWRT in my house, one acting as the main router, another one as AP only and the last one running APRS4R package to gate traffics from APRS/RF to APRS-IS and vice-versa. These routers are running on limited memory and I do need to sometime check the log when some of them suddenly stop working, so logging into the router itself is kind of useless (it will be gone when I restart the router) and added to the problem.

Since I've Ubuntu Karmic Koala running on my LHS, this is the best time to use it fully. One thing that I'm not so sure is, how to enable remote logging. I had Debian Lenny running on my Buffalo LinkStation II before and I didn't need to do anything fancy.. it works out of the box.. but it doesn't seem to be with my current LHS. I searched around the net with even more confusion .. but finally, I found a discussion about the logging system on Karmic .. it is no longer using syslogd but rsyslogd now. Yes, that is it .. so, I went to look for a guide on how to enable remote logging via rsyslogd and found this document:

Remove the comments for UDP/TCP syslog receptions from /etc/rsyslog.conf and rerun the rsyslog and this seems to solve this problem.


Popular posts from this blog

Configuring TechniColor TG784N V3 (Maxis issued broadband router) to use different DNS servers

Previous write up deleted. It seems to change the DNS servers in as shown on the status, but it does not really work.

Check the following website, this seems to work:

This can be done from the WEB GUI too, go into the following configuration path:

In my example above, I'm using paid service unblock-us instead of google public DNS servers.

Raspberry Pi + svxlink = Low power echolink node

What is the easiest way to get echolink node up and running on raspberry pi? Surely, get a premade image which has everything inside. I've created one image which can fit into 2GB SD card for this, just follow the following steps to get it up and running:

For hardware, you need to have the following:
Raspberry Pi for sure, with a minimum 4GB SD cardA USB echolink interface, can be commercially sourced or DIY. There are many DIY schematics out there that you could follow.  Here is the configuration on how to get the things working together, courtesy of website:

For software:
Download the following prepared image from google drive, it is based on raspbian-2015-02-16 image and has pre-installed svxlink-14.08. raspi-wheezy-svxlink.img.zipUnzip the file and copy it to your SD card using the following instructions that can be found here.Boot up the RasPi, if you do not have an HDMI monitor, you may want to access the RasPi from your terminal emulator (putty or the like), connec…

Debugging DMEE

I've come across many posting on the Internet (via google search), people asking on how to debug a DMEE for payment program. One of the few suggestion was to create a user exit just before the node that we would like to debug and put our breakpoint there. It seems that SAP has built-in this feature without needing us to create a user exit (available in ECC 6, have no idea if this is available on prior releases). Here is how you can put your breakpoint without any coding.

1. Display your DMEE tree using transaction: DMEE_DEBUG.

2. Click on the node that you would like to debug.
3. Go to conditions tab, you could see the Set Breakpoint button. Click to set.

4. Run the SAPFPAYM and specified the payment run date/id, payment format etc. SAP will stop at the node which you point your breakpoint at, as in 2.
5. To remove your breakpoint, just run the DMEE_DEBUG again, there is an option to delete all own breakpoints or all.