Techie Talks

It is easy to create your own speedtest utility in Python. You will require Speedtest-CLI module to build your utility. To install Speedtest-cli, run “ pip install speedtest-cli ” command Once speedtest-cli is installed, import it into your Python file. import speedtest result = speedtest . Speedtest ()   Following code will help you to find the best Speedtest server depending on your location best_server = result . get_best_server () print ( f "Checking speedtest using server located in { best_server [ 'country' ] } " )   Now, run the speed test for Download, Upload and ping result. # Running the download speed print ( "Running download speedtest..." ) dw_result = result . download () # Running the upload spped print ( "Running upload speedtest..." ) up_result = result . upload () # Running a ping test ping_result = result . results . ping   Using below code, you can covert the result in to Mbps and truncate the value to 2 decima

Here is the Python script that helps to find out the AWS account id. # The script helps you to find out AWS account number import boto3 # Configure AWS access key and secret access key to access AWS resources access_key_id = "test-key" secret_access_key_id = "secret-key" sts = boto3 . client (     "sts" , aws_access_key_id = access_key_id , aws_secret_access_key = secret_access_key_id , ) account_id = sts .get_caller_identity()[ "Account" ] # Print account number print ( account_id ) # The following code helps you to return AWS account number when IAM role based permissions are used account_id = boto3 . client ( "sts" ).get_caller_identity()[ "Account" ] # Print account number print ( account_id ) Hope you find it useful. Disclaimer: www.TechieTalks.co.uk does not conceal the possibility of error and shortcomings due to human or technical factors. www.TechieTalks.co.uk does not bear responsibility upon any loss or da

The following Python script will help you to export list of any all the CloudWatch logs with their retention time and size of the log group an AWS account. The script also helps you to save the output within CSV file. #!/usr/bin/env python3.8 #This script will save the list of CloudWatch log group names, their retention time and # size (in MBs) in to CSV file import boto3 import time import csv # Setting up AWS profile and region profile = "default" region = "us-east-1" session = boto3 . Session ( profile_name = profile , region_name = region ) #getting current date and time date_time = time . strftime ( " %d %m%Y_%H%M" ) # setting up file name fname = "CloudWatch-Logs_" ftime = date_time fext = ".csv" filename = fname + ftime + fext # open file to write output with open ( filename , 'w' ) as f :     print ( 'Profile, Region,Log Group Name, Retention Time (in days), Size (in MB)' , file = f )   cw_logs =

The following Python script will help to export list of any open pull requests from CodeCommit repositories from an AWS account. The output will be saved within CSV file. #!/usr/bin/env python3.8 # This script is used to find out any open pull requests from all the repositories # from an account and write output to the csv file # Importing boto3, csv and time module import boto3 import csv import time # Setting up AWS profile and region profile = "default" region = "us-east-1" session = boto3 . Session ( profile_name = profile , region_name = region ) repo_client = session . client ( 'codecommit' ) repos = repo_client .list_repositories(     sortBy = 'repositoryName' ) repo_list = repos repo_name = repo_list [ 'repositories' ] # Getting current date and time date_time = time . strftime ( " %d %m%Y_%H%M%S" ) # Setting up file name fname = "Open_PullReqsIDs_" ftime = date_time fext = ".csv" filename

While trying to run a CURL command in the Windows command prompt following error message occurs: Error: curl: (1) Protocol"https" not supported or disabled in libcurl For some reason, Windows doesn't like single quotes with the URL. To resolve this, please use the double quotes with the URL. For e.g. curl -J "http://localhost:8080"   Hope you find it useful.   Disclaimer: www.TechieTalks.co.uk does not conceal the possibility of error and shortcomings due to human or technical factors. www.TechieTalks.co.uk does not bear responsibility upon any loss or damage arising from conduct or activities related to the use of data and information contained in this blog.

Recently, I had come across following error message when one of the users was trying to copy files to Network folder. His folder was setup with offline files option so that files are available to user when network connection to server is either poor or not available. Error 0x80070718: Not enough quota is available to process this command After doing it bit of a search, I found a following solution to above error message. This is caused by Offline files. I have followed these steps on Windows 7 Pro 64 bit PC.           Open Control Panel           Go to Sync centre           Select Manage offline Files from left side column           An Offline files box will appear, click on Disk Usage tab           Click on Change limits button, change limit to required space.           Click on OK button twice. Hope you find it useful. Disclaimer: www.TechieTalks.co.uk does not conceal the possibility of error and shortcomings due to human or technical factors. www.Tech

I have Nagios Xi 4.3.2 installed on Red Hat Enterprise Linux 7.3 (Mapio) . Recently, I had an issue with my Nagios monitoring tool. It stopped monitoring my devices. When I checked further, I found out that NDO2DB service stopped working. Because of that, I could not see most recent status of any of the devices monitored by Nagios. I logged on to Read hat box and tried below command to check the status of the service: #systemctl status ndo2db You can also use following command to check any service status #Service ndo2db status I tried following commands to start/restart ndo2db service. #systemctl start ndo2db OR #systemctl restart ndo2db After applying above commands, I ran following command again to check status but it failed to start #systemctl status ndo2db After doing bit of searching on this issue, I found the solution. I entered following commands to start NDO2DB service. #service nagios stop #service ndo2db stop #rm -f /usr/