Reply to this topicStart new topic
> Enhanced Log Monitor Linux
JohnUptime
post Jul 12 2011, 03:20 PM
Post #1


Member
*

Group: Members
Posts: 8
Joined: 19-January 11
Member No.: 1,262



Anybody got the "Enhanced Log Monitor" to work on Linux?

Here is one example of the settings I've tried

Port: 9998
Password: *******
Log Directory: /var/log/
Log Files to Search (regex): auth\.log
Search String (regex): Accepted password

But no matter what settings I use, I always get the same message when I test the service monitor:

Status: WARN
Message: Process returned with warning status - Error: No lines returned from agent.
Error:: No lines returned from agent.
Response time: 1000 ms
Go to the top of the page
 
+Quote Post
Chris Kasza
post Jul 12 2011, 04:03 PM
Post #2


Guru
****

Group: Members
Posts: 233
Joined: 1-September 06
From: Vancouver
Member No.: 21



Hi John,

This suggests that something on the agent side is not configured properly. Have you gone through all the necessary steps to set up the agent side script (installed it in the correct directory with adequate permissions and added an entry to .uptmpasswd)?

- Chris
Go to the top of the page
 
+Quote Post
JohnUptime
post Aug 24 2011, 07:22 PM
Post #3


Member
*

Group: Members
Posts: 8
Joined: 19-January 11
Member No.: 1,262



I've haven't had any luck with this I'm afraid


I can run the perl script on the agent manually by using something like this as an parameter:

/var/logUPDOTTIMEauthUPDOTTIMEsessionUPSPCTIMEopenedUPDOTTIMEUPDOTTIMEOn

That works fine so I guess the perl script is OK


If I deliberately use an incorrect password when I configure the service on the server I get a different error:

Error: Output received: 'ERR'. The agent may not be configured correctly. Check the password?

So I guess the .uptmpasswd file can be read OK?


I thought I might be able to telnet to the agent on port 9998 and send this command:

rexec password /opt/uptime-agent/scripts/log_monitor.pl /var/logUPDOTTIMEauthUPDOTTIMEsessionUPSPCTIMEopenedUPDOTTIMEUPDOTTIMEOn

But that didn't work - the agent just disconnected


I set the agent to run as root (and set all the file permissions appropriately) but that had no effect


I don't know what else to check


Go to the top of the page
 
+Quote Post
Chris Kasza
post Aug 24 2011, 07:37 PM
Post #4


Guru
****

Group: Members
Posts: 233
Joined: 1-September 06
From: Vancouver
Member No.: 21



Hi John,

Are you using the latest scripts available in the Grid?

Chris
Go to the top of the page
 
+Quote Post
Chris Kasza
post Aug 24 2011, 07:37 PM
Post #5


Guru
****

Group: Members
Posts: 233
Joined: 1-September 06
From: Vancouver
Member No.: 21



Sorry, here's the link: http://support.uptimesoftware.com/the-grid...w.php?mod_id=25
Go to the top of the page
 
+Quote Post
JohnUptime
post Sep 5 2011, 03:52 PM
Post #6


Member
*

Group: Members
Posts: 8
Joined: 19-January 11
Member No.: 1,262



Yes I'm using the latest files on the server and on the agent
Go to the top of the page
 
+Quote Post
Chris Kasza
post Sep 5 2011, 08:33 PM
Post #7


Guru
****

Group: Members
Posts: 233
Joined: 1-September 06
From: Vancouver
Member No.: 21



Hi John,

Could you contact support at support@uptimesoftware.com to schedule a Webex call, so we can have a closer look at the configuration to determine what's missing?

Thanks,
Chris
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 24th May 2013 - 08:50 AM