News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Debugging syslog

Started by Ackis, June 03, 2016, 04:33:26 PM

Previous topic - Next topic

Ackis

Hello - I'm trying to get syslog to work with my server - I have the IP and whatnot set up however I'm not receiving any logs from the device.

Other devices are able to send logs to my server - I can't actually find a way to read hte logs on the obi device to see what's going wrong.

Anyone able to point me in the right direction?

restamp

When I first got my OBi, I fooled around with syslog for the better part of several days.  I never did get it to work, finally concluding that whatever they are implementing on the OBi, it is incompatible with the standard  *nix syslogs.  I seem to recall that I did eventually get it to record something, but again, the format wasn't right so the syslog daemon did not know where to put it, and the content was of little use anyway.  (Doesn't OBi publish a program somewhere that can be run under Windows that receives the debug data and stores it in a file?)

NoelB

Quote from: Ackis on June 03, 2016, 04:33:26 PM
Hello - I'm trying to get syslog to work with my server

Anyone able to point me in the right direction?

It actually works very well and the syslog window fills with each sip pkt that comes into or exits that sip trunk .
I dont have GV but doubt it would show anything meaningful.
Download the syslogd program from here to your desktop and note the pc IP address.
https://www.obitalk.com/info/faq/Troubleshooting-sec/collect-syslog-from-OBi

Then log into the obi trunk you wish to monitor and dropdown to "Log All Messages" in X_SipDebugOption then submit and OK
Then in System Management /Device Admin enter the Syslog Server (desktop) IP and submit ok and Reboot.
Then double click the desktop syslogd icon to open the syslog window .
That's all. Messages will start to appear . When you want to stop just close the window and look for the log file that is left on your desktop.

Lavarock7

My first thought was probably so far off, but here goes..

Is your Obi connected via wifi? If so then some routers have the ability to keep wifi traffic from being able to access systems on the LAN. This keeps people who are on the wifi side from being able to easily hack the LAN users.

As I say, probably not your case but it was my first thought.
My websites: Kona Coffee: http://itskona.com and Web Hosting: http://planetaloha.info<br />A simplified Voip explanation: http://voip.planet-aloha.com

Ackis

Quote from: restamp on June 03, 2016, 06:59:00 PM
When I first got my OBi, I fooled around with syslog for the better part of several days.  I never did get it to work, finally concluding that whatever they are implementing on the OBi, it is incompatible with the standard  *nix syslogs.  I seem to recall that I did eventually get it to record something, but again, the format wasn't right so the syslog daemon did not know where to put it, and the content was of little use anyway.  (Doesn't OBi publish a program somewhere that can be run under Windows that receives the debug data and stores it in a file?)

NoelB posted the program - I'm able to get syslog messages to it, but not with my syslog daemon on my server.  Must be what you've said that it isn't really syslog and it's something proprietary.

Quote from: NoelB on June 03, 2016, 09:51:34 PM
It actually works very well and the syslog window fills with each sip pkt that comes into or exits that sip trunk .
I dont have GV but doubt it would show anything meaningful.
Download the syslogd program from here to your desktop and note the pc IP address.
https://www.obitalk.com/info/faq/Troubleshooting-sec/collect-syslog-from-OBi

Then log into the obi trunk you wish to monitor and dropdown to "Log All Messages" in X_SipDebugOption then submit and OK
Then in System Management /Device Admin enter the Syslog Server (desktop) IP and submit ok and Reboot.
Then double click the desktop syslogd icon to open the syslog window .
That's all. Messages will start to appear . When you want to stop just close the window and look for the log file that is left on your desktop.

Thanks for the link.  I want it to be able to log directly to my syslog server, not some client program on a random PC I'm running.  Based on the fact that it works with their program, but doesn't work with standard syslog servers I can't say that the syslog implementation works very well.

Quote from: Lavarock7 on June 04, 2016, 11:02:17 AM
My first thought was probably so far off, but here goes..

Is your Obi connected via wifi? If so then some routers have the ability to keep wifi traffic from being able to access systems on the LAN. This keeps people who are on the wifi side from being able to easily hack the LAN users.

As I say, probably not your case but it was my first thought.

Nope, not on wifi - wired LAN. :)  Thanks though.