Sponsored Content
Top Forums Programming Programming a Telegram Bot Using Node-RED, PHP, and MySQL Post 303045166 by Neo on Thursday 12th of March 2020 11:45:07 PM
Old 03-13-2020
Good job Ravinder.

Always a pleasure to see people learning new things and using that knowledge to solve real-world problems.

Can you use kind of system at your work?
This User Gave Thanks to Neo For This Post:
 

7 More Discussions You Might Find Interesting

1. Red Hat

Can't uninstall MYSQL from RED HAT ES

Hi Everyone Could you kindly advise on how I should do a chkconfig and uninstalling mysql rpm on Red hat ES.Please check the errors that I'm getting below. :eek: I need to uninstall MySQL completely from my linux system ver 2.4.21-37 and use the chkconfig command to switch it on... (15 Replies)
Discussion started by: CollenM
15 Replies

2. What is on Your Mind?

Telegram Bots - Bot Code Examples

I'm currently looking into ways to integrate the Telegram API into the forums: Telegram Bots - Bot Code Examples I'm thinking, first off, to use the Telegram API to get forum alerts and notifications (to Bot or Not?). Second, I thinking of ways to more deeply integrate Telegram into the... (5 Replies)
Discussion started by: Neo
5 Replies

3. Web Development

Node.js and mysql - ER_ACCESS_DENIED_ERROR

This problem has been killing me all day, and I cannot solve it. Basically, I am using node.js with the mysql module and it will not connect to the database. Here is the JS code snippet in node.js: app.get("/test", function(req, res) { var mysql = require("mysql"); var con =... (4 Replies)
Discussion started by: Neo
4 Replies

4. Infrastructure Monitoring

Using Node-RED and MQTT to Monitor Server and Application Stats

After setting up MQTT and testing some ESP8266 and ESP32 modules, where I noted that testing in Programming ESP32 (ESP-WROOM-32) as an MQTT Client Subscribed to Linux Server Load Average Messages, I was so impressed with MQTT that I installed MQTT on three different computers, instantly and... (2 Replies)
Discussion started by: Neo
2 Replies

5. Programming

Publish and Subscribe to AES-256 Encrypted MQTT Messages to Node-RED from PHP Scripts

Various Node-Red crypto modules do not work with PHP, so to send an encrypted message from a PHP script (in this case from a Ubuntu server) to Node-RED we need our own code. After a few hours of searching, testing various libs, more testing and debugging, I got this PHP to Node-RED code... (0 Replies)
Discussion started by: Neo
0 Replies

6. Programming

Node-RED: Writing MQTT Messages to MySQL DB with UNIX timestamp

First, I want to thank Neo (LOL) for this post from 2018, Node.js and mysql - ER_ACCESS_DENIED_ERROR I could not get the Node-RED mysql module to work and searched Google until all my links were purple! I kept getting ER_ACCESS_DENIED_ERROR with the right credentials. Nothing on the web was... (0 Replies)
Discussion started by: Neo
0 Replies

7. What is on Your Mind?

MQTT, Node-RED, Linux, Apache2, MySQL, PHP, Telegram, ESP32, ESP8266, Arduino

I have just completed the first phase of integrating all these devices and technologies: MQTT, Node-RED, Linux, Apache2, MySQL, PHP, Telegram, ESP32, ESP8266, and the Arduino Uno The glue that binds all this together is MQTT. In fact, MQTT makes this kind of integration nearly trivial to... (1 Reply)
Discussion started by: Neo
1 Replies
condor_userlog(1)					      General Commands Manual						 condor_userlog(1)

Name
       condor_userlog Display - and summarize job statistics from job log files.

Synopsis
       condor_userlog [-help] [-total | -raw] [-debug] [-evict] [-j cluster | cluster.proc] [-all] [-hostname] logfile ...

Description
       condor_userlog  parses  the  information  in job log files and displays summaries for each workstation allocation and for each job. See the
       manual page for condor_submiton page for instructions for specifying that Condor write a log file for your jobs.

       If -totalis not specified, condor_userlogwill first display a record for each workstation allocation, which includes the following informa-
       tion:

       Job

	  The cluster/process id of the Condor job.

       Host

	  The  host  where  the job ran. By default, the host's IP address is displayed. If -hostnameis specified, the host name will be displayed
	  instead.

       Start Time

	  The time (month/day hour:minute) when the job began running on the host.

       Evict Time

	  The time (month/day hour:minute) when the job was evicted from the host.

       Wall Time

	  The time (days+hours:minutes) for which this workstation was allocated to the job.

       Good Time

	  The allocated time (days+hours:min) which contributed to the completion of this job. If the job exited during the allocation, then  this
	  value  will  equal  ``Wall Time.'' If the job performed a checkpoint, then the value equals the work saved in the checkpoint during this
	  allocation. If the job did not exit or perform a checkpoint during this allocation, the value will be 0+00:00. This value can be greater
	  than	0  and	less  than ``Wall Time'' if the application completed a periodic checkpoint during the allocation but failed to checkpoint
	  when evicted.

       CPU Usage

	  The CPU time (days+hours:min) which contributed to the completion of this job.

       condor_userlogwill then display summary statistics per host:

       Host/Job

	  The IP address or host name for the host.

       Wall Time

	  The workstation time (days+hours:minutes) allocated by this host to the jobs specified in the query. By default, all jobs in the log are
	  included in the query.

       Good Time

	  The time (days+hours:minutes) allocated on this host which contributed to the completion of the jobs specified in the query.

       CPU Usage

	  The CPU time (days+hours:minutes) obtained from this host which contributed to the completion of the jobs specified in the query.

       Avg Alloc

	  The average length of an allocation on this host (days+hours:minutes).

       Avg Lost

	  The average amount of work lost (days+hours:minutes) when a job was evicted from this host without successfully performing a checkpoint.

       Goodput

	  This percentage is computed as Good Time divided by Wall Time.

       Util.

	  This percentage is computed as CPU Usage divided by Good Time.

       condor_userlogwill then display summary statistics per job:

       Host/Job

	  The cluster/process id of the Condor job.

       Wall Time

	  The total workstation time (days+hours:minutes) allocated to this job.

       Good Time

	  The total time (days+hours:minutes) allocated to this job which contributed to the job's completion.

       CPU Usage

	  The total CPU time (days+hours:minutes) which contributed to this job's completion.

       Avg Alloc

	  The average length of a workstation allocation obtained by this job in minutes (days+hours:minutes).

       Avg Lost

	  The average amount of work lost (days+hours:minutes) when this job was evicted from a host without successfully performing a checkpoint.

       Goodput

	  This percentage is computed as Good Time divided by Wall Time.

       Util.

	  This percentage is computed as CPU Usage divided by Good Time.

       Finally, condor_userlogwill display a summary for all hosts and jobs.

Options
       -help

	  Get a brief description of the supported options

       -total

	  Only display job totals

       -raw

	  Display raw data only

       -debug

	  Debug mode

       -j

	  Select a specific cluster or cluster.proc

       -evict

	  Select only allocations which ended due to eviction

       -all

	  Select all clusters and all allocations

       -hostname

	  Display host name instead of IP address

General Remarks
       Since  the Condor job log file format does not contain a year field in the timestamp, all entries are assumed to occur in the current year.
       Allocations which begin in one year and end in the next will be silently ignored.

Exit Status
       condor_userlogwill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.

Author
       Condor Team, University of Wisconsin-Madison

Copyright
       Copyright (C) 1990-2012 Condor Team, Computer Sciences Department, University of  Wisconsin-Madison,  Madison,  WI.  All  Rights  Reserved.
       Licensed under the Apache License, Version 2.0.

       See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu

								  September 2012						 condor_userlog(1)
All times are GMT -4. The time now is 07:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy