There are fundamentally two ways. One is to set up a monitoring
infrastructure, such as Nagios/Icinga. For your specific problem, that's
overkill, but I mention it because in many cases, you may find out many
more things to monitor.
For such a one-off monitoring, I would use a script called by cron. The
script could check if the process is still running, or use grep to search
through /var/log/confluent/stderr, or whatever may be appropriate for you.
Then have the script take the action you need (such as, restart confluent,
send an email, or whatever else you need).
On Thu, Oct 26, 2017 at 6:11 AM, banuchka <tyrche...@gmail.com> wrote:
> Hi,
>
> I’ve found issue but maybe it isn’t really an issue. Sometimes confluent
> writes to its console log “/var/log/confluent/stderr” for example messages
> like this one:
> ===
> Oct 25 15:59:09 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> file.write(str+terminator): Traceback (most recent call last):
> Oct 25 15:59:09 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> file.write(str+terminator): File "/usr/lib/python2.7/site-
> packages/eventlet/hubs/hub.py", line 457, in fire_timers
> Oct 25 15:59:09 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> file.write(str+terminator): timer()
> Oct 25 15:59:09 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> file.write(str+terminator): File "/usr/lib/python2.7/site-
> packages/eventlet/hubs/timer.py", line 58, in __call__
> Oct 25 15:59:09 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> file.write(str+terminator): cb(*args, **kw)
> Oct 25 15:59:09 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> file.write(str+terminator): File "/usr/lib/python2.7/site-
> packages/eventlet/greenthread.py", line 214, in main
> Oct 25 15:59:09 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> file.write(str+terminator): result = function(*args, **kwargs)
> Oct 25 15:59:09 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> file.write(str+terminator): File
> "/opt/confluent/lib/python/confluent/log.py",
> line 581, in writedata
> Oct 25 15:59:09 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> file.write(str+terminator): syslog.syslog("MSG_FROM_CONSOLE {0}
> :{1}".format(str(self.logname),str(tosyslog)))
> Oct 25 15:59:09 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> file.write(str+terminator): TypeError: [priority,] message string
> Oct 25 15:59:19 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> file.write(str+terminator): Traceback (most recent call last):
> Oct 25 15:59:19 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> file.write(str+terminator): File "/usr/lib/python2.7/site-
> packages/eventlet/hubs/hub.py", line 457, in fire_timers
> Oct 25 15:59:19 File "/usr/lib64/python2.7/traceback.py", line 13, in
> _print
> ===
> After that happen there are no new records in the consoles text log files,
> but rcons & confluent still working because i can open console etc.
> Is there any chance to connect to confluent and check its internal state.
> I know about debug port but i have now idea how does it work. Will be great
> if someone could help me with that?
>
> p.s.: i know that i may use tail or something like that to check
> confluent’s log file but that doesn’t look like the best way from my point
> of view.
>
> Thanks
>
> --
> banuchka
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> xCAT-user mailing list
> xCAT-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xcat-user
>
>
--
_______________________________________________________________________
Kevin Keane | Systems Architect | University of San Diego ITS |
kke...@sandiego.edu
Maher Hall, 192 |5998 Alcalá Park | San Diego, CA 92110-2492 | 619.260.6859
<%28619%29%20260-2298>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
