If the PATTON SN4638 does something it should not (although it is running a seemingly correct configuration) a debug-session can come in handy. The SN4638 supports debug output only via syslog. The fact that I could not find any useful information with a straight search on Google has made me write this short explanation.<\/p>\n
On the server machine (in this example Ubuntu where rsyslogd is the standard syslog daemon) open the file<\/p>\n
\/etc\/default\/rsyslog<\/pre>\nand check for the following line:<\/p>\n
RSYSLOGD_OPTIONS=\"-c5\"<\/pre>\nIf it looks different you will have to change it according to the line above.<\/p>\n
Next open the file<\/p>\n
\/etc\/rsyslog.conf<\/pre>\nand find the following lines:<\/p>\n
# provides UDP syslog reception\r\n#$ModLoad imudp\r\n#$UDPServerRun 514<\/pre>\nChange them to look like this:<\/p>\n
# provides UDP syslog reception\r\n$ModLoad imudp\r\n$UDPServerRun 514<\/pre>\nSave and exit.<\/p>\n
Run these commands in a terminal window:<\/p>\n
$ sudo su -\u00a0\r\n# cat \/dev\/null > \/var\/log\/syslog\r\n# service rsyslog restart<\/pre>\nThis clears the current syslog and restarts the syslog daemon using root credentials.<\/p>\n
Next open the web interface of the SN4638 in a browser.<\/p>\n
Under\u00a0Various \u2192 Syslog<\/em>\u00a0enter the\u00a0IP address of the server machine in the Host<\/em>\u00a0field and put the number 514 <\/em>in the\u00a0Port<\/em>\u00a0field. Press the enter key.<\/p>\n
A new entry is now available. Click on the IP address.<\/p>\n
Under\u00a0Facility<\/em>\u00a0select the entry sip\u00a0<\/em>in the dropdown menu\u00a0and under\u00a0Severity<\/em>\u00a0select the entry\u00a0debug<\/em>. Click on the\u00a0create icon<\/em>.<\/p>\n
Under\u00a0Facility<\/em>\u00a0select the entry\u00a0isdn<\/em>\u00a0in the dropdown menu and under\u00a0Severity<\/em>\u00a0select the entry\u00a0debug<\/em>.\u00a0Click on the\u00a0create icon<\/em>.<\/p>\n
You will find the messages on the sever machine in the file<\/p>\n
\/var\/log\/syslog<\/pre>\nPlease note: the file grows fast! Make sure to disable syslog output in the web interface of the SN4638 after the debug session!<\/p>\n
Source:\u00a0http:\/\/os4.org\/wiki\/rsyslog.html<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
If the PATTON SN4638 does something it should not (although it is running a seemingly correct configuration) a debug-session can come in handy. The SN4638 supports debug output only via syslog. The fact that I could not find any useful … Weiterlesen