Certified DevSecOps Engineer Training and Certification

About

The Certified DevSecOps Engineer course is designed to equip participants with the knowledge and skills required to integrate security into DevOps practices effectively. This comprehensive training program covers essential concepts, tools, and techniques for implementing DevSecOps principles to enhance the security posture of software development and delivery pipelines.

Course Features

  • Hands-on training with real-world scenarios and projects
  • Expert-led sessions by industry professionals
  • Comprehensive curriculum covering all aspects of DevSecOps
  • Practical exercises and case studies for better understanding
  • Access to course materials and resources for future reference
  • Certification exam to validate knowledge and skills

Training Objectives

Upon completion of this course, participants will:

  • Understand the principles and importance of DevSecOps
  • Implement security throughout the software development lifecycle
  • Secure CI/CD pipelines and automate security checks
  • Apply security best practices in infrastructure as code (IaC)
  • Monitor for security threats and respond to incidents effectively

Target Audience

This course is suitable for:

  • DevOps engineers
  • Security professionals
  • Software developers
  • System administrators
  • IT professionals interested in DevSecOps practices

Training Methodology

Our training methodology emphasizes practical learning and interactive sessions. The course includes:

  • Lectures: In-depth explanations of concepts and principles by experienced trainers.
  • Hands-on Labs: Practical exercises and real-world scenarios to reinforce learning.
  • Case Studies: Analysis of real-world DevSecOps implementations and best practices.
  • Group Discussions: Collaborative learning through discussions and knowledge sharing.
  • Q&A Sessions: Opportunities to clarify doubts and engage with the instructor.
  • Final Project: Application of learned concepts in a real-world project scenario.

Participants will have access to course materials and resources, including recordings of sessions, for ongoing learning and reference.

Daywise Agenda

  • Day 1: Introduction to DevSecOps
    • Understanding DevSecOps principles
    • Importance of integrating security into DevOps practices
    • Tools and technologies overview
  • Day 2: Security in Continuous Integration
    • Implementing secure CI pipelines
    • Code scanning and vulnerability assessment
    • Automated security testing
  • Day 3: Security in Continuous Delivery
    • Secure containerization and orchestration
    • Implementing secure deployment pipelines
    • Automated security checks in CD pipelines
  • Day 4: Infrastructure as Code Security
    • Managing infrastructure securely with code
    • Security best practices for configuration management
    • Implementing security controls in IaC
  • Day 5: Monitoring and Incident Response
    • Implementing security monitoring in DevOps pipelines
    • Incident response and handling in DevSecOps
    • Security incident management and post-mortem analysis
  • Day 6: Final Project and Certification Exam

Trainers (Rajesh Kumar)

Rajesh Kumar is an experienced DevOps and cybersecurity professional with over 10 years of industry experience. He has extensive expertise in implementing DevOps practices securely and integrating security into DevOps workflows. Rajesh has conducted numerous training sessions and workshops on DevSecOps for various organizations.

FAQs

  1. Who should attend this course?
    • This course is suitable for DevOps engineers, security professionals, software developers, and anyone interested in integrating security into DevOps practices.
  2. Are there any prerequisites for this course?
    • Participants are expected to have a basic understanding of DevOps principles and practices, as well as familiarity with common DevOps tools and technologies.
  3. What certification will I receive upon completion?
    • Participants who successfully complete the course and pass the certification exam will be awarded the “Certified DevSecOps Engineer” certification.
  4. Is this course hands-on?
    • Yes, the course includes hands-on exercises and a final project to reinforce learning and practical application of DevSecOps concepts and techniques.
  5. Can I access course materials after completion?
    • Yes, participants will have access to course materials and resources for future reference.

How to Contact us?

Naraka Bladepoint: All the Things a Beginner Should Know

Naraka: Bladepoint offers a unique blend of action and adventure, set in a mythical world inspired by Asian folklore. This game combines traditional melee combat with agile movement and strategic gameplay. If you’re new to this world, this 1000-word guide is your essential companion, covering everything from basic mechanics to advanced tactics.

Understanding the Game

Naraka: Bladepoint is a battle royale game that stands out with its focus on melee combat and parkour-style movement. In each match, you fight to be the last one standing out of 60 players. The game offers a range of characters with unique abilities, adding depth and variety to the gameplay.

Choosing Your Character

One of the first things you’ll do is choose a character. Each character in Naraka: Bladepoint has unique skills and an ultimate ability. Some characters are better suited for close combat, while others excel at range or support roles. Experiment with different characters to find one that matches your playstyle.

Mastering Combat

Combat in Naraka: Bladepoint is intricate, featuring a mix of melee attacks, ranged weapons, and abilities. Understanding the basics of attacking, blocking, and dodging is crucial. The combat system is about timing and predicting your opponent’s moves. Practice different weapon types to get a feel for their strengths and weaknesses.

The Importance of Movement

Movement is a key part of Naraka: Bladepoint. You can run, climb, and even use a grappling hook to navigate the map. Mastering movement is essential for both engaging enemies and evading them. Use the environment to your advantage, moving quickly and unpredictably to outmaneuver opponents.

Exploring the Map

Familiarize yourself with the game’s map. Knowing the layout, including where resources are likely to spawn, can give you a strategic advantage. The map is also subject to a shrinking play zone, forcing players closer together over time. Keep an eye on the zone and plan your movements accordingly.

Gathering Resources and Equipment

Scavenging for equipment and resources is vital. You’ll need to find weapons, armor, and healing items to survive. Higher quality gear often means a significant edge in combat. Don’t forget to loot defeated enemies for their equipment.

Utilizing Souljades

Souljades are special items that enhance your abilities and stats. Collecting and equipping the right Souljades can significantly boost your performance in various aspects of the game, be it combat, defense, or mobility. Experiment with different Souljade combinations to enhance your character’s capabilities.

Engaging in Team Play

While solo play is thrilling, Naraka: Bladepoint also offers team modes. Playing with friends or teaming up with other players can enhance your experience. Effective communication and teamwork can turn the tide of battle, offering a more strategic approach to matches.

Learning from Each Match

Every match in Naraka: Bladepoint is a learning opportunity. Pay attention to how you engage with enemies, how you move around the map, and how you use your character’s abilities. Analyze your mistakes and successes to continuously improve your skills.

The Role of Strategy and Tactics

In Naraka: Bladepoint, brute force isn’t always the answer. Sometimes, a strategic retreat or a well-planned ambush can be more effective. Be mindful of your surroundings, choose your battles wisely, and use strategy as much as physical prowess to outplay your opponents.

Keeping Up with Updates and Community

Stay informed about the latest updates, patches, and community insights. Joining the Naraka: The Bladepoint community through forums and social media can provide valuable tips and keep you up-to-date with changes to the game.

Positive Use of Resources

For players interested in deepening their understanding of the game, exploring resources like Naraka Bladepoint hacks can offer new perspectives and insights into advanced strategies and mechanics. Such resources can complement your learning process, helping you to grasp the finer nuances of the game and enhancing your overall strategic approach.

Conclusion

Naraka: Bladepoint is a game rich in strategy, combat, and adventure. As a beginner, immerse yourself in its world, embrace the learning curve, and enjoy the journey of becoming a skilled warrior. Remember, every match is a step towards mastering this unique and captivating game. With patience, practice, and a strategic mindset, you’ll find yourself thriving in the exhilarating world of Naraka: Bladepoint.

XAMPP Error: XAMPP is currently only availably as 32 bit applicationXAMPP Error:

Error

"XAMPP is currently only availably as 32 bit application. Please use a 32 bit compatibility library for your system"

Solution

Step 1 – CHECK php version

Step 2 – Check php.ini syntax issues

./php --version
./php: /opt/lampp/lib/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /lib/x86_64-linux-gnu/libicui18n.so.66)
./php: /opt/lampp/lib/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /lib/x86_64-linux-gnu/libicuuc.so.66)

Solution

$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo apt-get install libstdc++6

Create a Symbolic Link:
If XAMPP is using an outdated version of libstdc++.so.6, you can try creating a symbolic link to the system's version of the library.

First, locate the system's version of the library:


$ find /usr/lib /lib -name 'libstdc++.so.6'
Then, backup the old version and create a symbolic link. Replace /path/to/system/libstdc++.so.6 with the path found in the previous step:


$ sudo mv /opt/lampp/lib/libstdc++.so.6 /opt/lampp/lib/libstdc++.so.6.backup
$ sudo ln -s /path/to/system/libstdc++.so.6 /opt/lampp/lib/libstdc++.so.6

Reinstall XAMPP:
If the above steps don't work, consider reinstalling XAMPP. Sometimes, a fresh installation can resolve library conflicts.

Level Up Your Campaigns: Must-Try Influencer Marketplaces for 2024

Forget the days of generic platforms and scatter-shot campaigns. The year 2024 is all about precision, authenticity, and measurable results in influencer marketing. To dominate this booming landscape, brands need the right tools in their arsenal – enter the must-try influencer marketplaces revolutionizing the game.

1. Wizbrand: The AI Matchmaker

Tired of fruitless searches and mismatched partnerships? Wizbrand’s cutting-edge AI algorithms are like cupid for brands and influencers. Forget keyword filters – analyze audience demographics, engagement patterns, and brand affinity to create hyper-targeted connections that resonate on a deeper level. Imagine Instagrammable moments that transcend demographics and connect with hearts and minds – that’s the Wizbrand magic.

2. Traackr: The Community Catalyst

Traackr understands the power of collaboration and connection. Its platform fosters vibrant ecosystems where brands and influencers connect, learn, and grow together. Interactive forums, mentorship programs, and exclusive events go beyond single campaigns, building trust and sustainable success. Think of it as a thriving digital co-working space for brands and influencers to spark magic.

3. HypeAuditor: The Global Guru

For brands with global ambitions, HypeAuditor is the gateway to untapped potential. Its extensive reach spans every major social media platform and geographical boundary, unlocking access to multilingual influencers and diverse audiences. Imagine speaking to the world through authentic voices – HypeAuditor’s powerful analytics illuminate international markets and influencer performance, guiding you towards strategic global partnerships that transcend borders.

4. AspireIQ: The Micro Mastermind

Don’t underestimate the power of small! AspireIQ champions the micro-influencer revolution. Their platform connects brands with niche content creators who boast highly engaged, dedicated communities. Think local coffee shops partnering with food bloggers or fitness brands collaborating with yoga instructors – AspireIQ lets you leverage hyper-targeting and authenticity to create impactful campaigns that resonate on a personal level and build genuine brand loyalty.

5. Creator.co: The Content Connoisseur

Move beyond generic sponsored posts and embrace bespoke collaborations with Creator.co. This platform connects brands with influencers who excel in content creation, allowing you to co-develop campaigns that truly engage your audience. Imagine working hand-in-hand with skilled storytellers to craft unique, shareable content that stands out in the noise – Creator.co unlocks the magic of collaboration for impactful brand storytelling.

This is just the tip of the iceberg! Explore the full landscape of influencer marketplaces and discover the perfect partner to take your brand to the next level.

But wait, there’s more!

Bonus Tip 1: Stay ahead of the curve by exploring platforms like Collabstr, showcasing rising stars in the influencer space, and Aspire, constantly adapting to new trends and technologies.

Bonus Tip 2: Remember, the key to success lies in:

  • Defining your campaign goals and target audience.
  • Understanding the strengths and limitations of each platform.
  • Seeking out platforms that prioritize authenticity and data-driven insights.
  • Embracing innovation and staying ahead of the curve.

With the right platform by your side, you can leverage the power of influencer marketing in 2024 and beyond, building meaningful connections, achieving measurable results, and solidifying your brand as a leader in the ever-evolving digital landscape.

So, what are you waiting for? Go forth and conquer the influencer marketing world with the perfect platform match!

Medical Tourism: Leading the Way in International Health Journeys

In the realm of medical tourism, various websites have emerged as leaders, guiding international patients through their health journeys with specialized surgeries and treatments. These platforms are distinguished for their comprehensive offerings, expert insights, and patient-centric services. Each website caters to a specific medical need, ensuring that patients have access to the best global healthcare options. Here’s an overview of some of the leading websites in medical tourism, each playing a pivotal role in international health journeys.

My Hospital Now

My Hospital Now stands out as a comprehensive resource for patients seeking a variety of medical treatments worldwide. This platform excels in offering detailed information on hospitals across multiple specialties, facilitating informed and personalized healthcare choices for international patients.

My Medic Plus

My Medic Plus serves as a versatile guide in the medical tourism landscape. Renowned for its extensive hospital listings and travel assistance services, it caters to diverse medical needs, providing seamless planning for international health journeys.

Surgery Planet

Surgery Planet is a central hub for patients looking for surgical treatments abroad. The site is known for its vast network of reputable hospitals and clinics, covering various surgical procedures and making it a trusted ally in surgical medical tourism.

Best Cardiac Hospitals

Best Cardiac Hospitals is a premier destination for patients seeking cardiac care internationally. It lists the world’s top cardiac hospitals and provides insights into advanced heart treatments, positioning itself as a leader in cardiac health tourism.

Best Cosmetic Hospitals

Best Cosmetic Hospitals focuses on high-quality cosmetic and plastic surgery centers globally. The website is a go-to source for detailed information on top clinics and expert surgeons, ideal for individuals seeking cosmetic enhancements in their medical travels.

Best Dental Hospitals

Best Dental Hospitals connects patients with leading dental care facilities worldwide. Specializing in both general and cosmetic dentistry, it offers access to state-of-the-art dental treatments, ensuring the best in oral care for medical tourists.

Best Eye Hospitals

Best Eye Hospitals guides patients to top ophthalmology centers around the world. It provides essential information for those seeking specialized eye care, from routine check-ups to advanced surgeries, leading the way in ophthalmology tourism.

Best Heart Surgery

Best Heart Surgery is dedicated to providing information on world-class heart surgery centers. It lists top surgeons and facilities, making it an essential resource for patients needing advanced cardiac surgical care.

Best Spine Hospitals

Best Spine Hospitals offers access to premier spinal treatment facilities globally. It specializes in advanced spine care, from minimally invasive techniques to complex surgeries, catering to the needs of spine health travelers.

Cancer Hospitals

Cancer Hospitals lists specialized cancer treatment centers, making it a top resource for oncology care abroad. It offers insights into a range of cancer treatments, from early detection to advanced therapies, supporting patients in their oncological journeys.

Hip Hospitals

Hip Hospitals is a valuable resource for hospitals specializing in hip treatments and surgeries. It provides comprehensive information for those seeking hip replacements or orthopedic care, emphasizing quality treatment and recovery.

Knee Hospitals

Knee Hospitals focuses on knee care, offering insights into leading knee treatment centers and orthopedic surgeons. It’s a top choice for patients needing knee surgeries or treatments, demonstrating its expertise in orthopedic medical tourism.

Ask Doctor Live

Ask Doctor Live provides live consultations with medical professionals. This service is crucial for personalized medical advice and guidance, making it an essential tool in planning and navigating medical travel.

Each of these websites plays a crucial role in leading the way in international health journeys, offering specialized knowledge, resources, and personalized assistance to ensure patients receive the best medical care combined with a comprehensive travel experience.

Mysql error with Xampp – script timeout passed

Error

script timeout passed, if you want to finish import, please resubmit the same file and import will resume.

Solution

Method – 1 – import using Mysql command

set PATH=%PATH%;C:\xampp\mysql\bin

$ mysql -u root -p database_name < example.sql

Method – 1 – import using PHPMYADMIN

Here’s an example snippet with these settings in a php.ini file:

file_uploads = On
upload_max_filesize = 2M
post_max_size = 8M
max_execution_time = 300
max_input_time = 600
memory_limit = 256M

mysqli.allow_local_infile = On
mysqli.default_socket = /path/to/mysql.sock

error_reporting = E_ALL
  1. Max Upload Size in phpMyAdmin:
    • Log in to phpMyAdmin.
    • Click on the “Import” tab.
    • Below the file upload field, phpMyAdmin displays the maximum allowed file size. Ensure that this limit is appropriate for your needs.
  2. PHP Settings (Modify these in your php.ini or .htaccess file):
    • upload_max_filesize: Specifies the maximum size of uploaded files. Ensure it’s set to a value that allows the size of the files you want to upload.
    • post_max_size: Sets the maximum size of POST data that PHP will accept. It should be larger than upload_max_filesize to accommodate the entire POST request.
  3. phpMyAdmin Configuration (Modify these in phpMyAdmin’s configuration file config.inc.php):
    • Open the config.inc.php file, which is typically located in the phpMyAdmin installation directory.
    • Locate and adjust the following settings:
      • $cfg['UploadDir']: This setting specifies the directory where phpMyAdmin should store uploaded files. Make sure it’s a valid directory path, and the web server has write permissions to it.
      • $cfg['SaveDir']: This setting specifies the directory where phpMyAdmin should save exported files. Ensure it’s a valid directory path, and the web server has write permissions to it.
  4. MySQL Settings:
    • Ensure that your MySQL server allows for large file imports. You may need to adjust the MySQL server’s configuration settings, such as max_allowed_packet, to accommodate large imports.

xampp always redirect to dashboard

Write a content for .htaccess for all traffic on domain reveieved on http or http://www redirect to https://www

If XAMPP is always redirecting to the dashboard page, it’s likely due to its default configuration settings. When you access http://localhost, XAMPP is configured to redirect to its dashboard or splash page. This behavior is controlled by the Apache configuration files and can be modified if you prefer it to point to another directory or project.

Solution IF YOU HAVE MULTIPLE DOMAIN Hosted at Same Server

$ vi /opt/lampp/htdocs/.htaccess

RewriteEngine On

# Ensure mod_rewrite is enabled
<IfModule mod_rewrite.c>

    # Redirect HTTP to HTTPS with www
    RewriteCond %{HTTPS} off [OR]
    RewriteCond %{HTTP_HOST} !^www\. [NC]
    RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301,NE]

</IfModule>

Solution if you have Single Domain

Modify httpd.conf:

  • Open httpd.conf in a text editor.
  • Look for the DocumentRoot directive. It might look like this:apacheCopy codeDocumentRoot "C:/xampp/htdocs"
  • Change the path (C:/xampp/htdocs in the example) to the directory of your choice where your project or website files are located.
  • Similarly, find the <Directory> directive that corresponds to the DocumentRoot and change the path there as well.

Azure Pipeline Error:

Error

2023-12-15T04:15:34.3863280Z ##[section]Starting: Maven
2023-12-15T04:15:34.3877434Z ==============================================================================
2023-12-15T04:15:34.3877597Z Task         : Maven
2023-12-15T04:15:34.3877660Z Description  : Build, test, and deploy with Apache Maven
2023-12-15T04:15:34.3877760Z Version      : 3.231.5
2023-12-15T04:15:34.3877842Z Author       : Microsoft Corporation
2023-12-15T04:15:34.3877936Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/maven
2023-12-15T04:15:34.3878052Z ==============================================================================
2023-12-15T04:15:36.9740195Z ##[error]Unhandled: Failed to find the specified JDK version. Please ensure the specified JDK version is installed on the agent and the environment variable 'JAVA_HOME_8_X64' exists and is set to the location of a corresponding JDK or use the [Java Tool Installer](https://go.microsoft.com/fwlink/?linkid=875287) task to install the desired JDK.
2023-12-15T04:15:36.9760865Z ##[error]Error: Failed to find the specified JDK version. Please ensure the specified JDK version is installed on the agent and the environment variable 'JAVA_HOME_8_X64' exists and is set to the location of a corresponding JDK or use the [Java Tool Installer](https://go.microsoft.com/fwlink/?linkid=875287) task to install the desired JDK.
    at Object.findJavaHome (/home/rajesh/_work/_tasks/Maven_ac4ee482-65da-4485-a532-7b085873e532/3.231.5/node_modules/azure-pipelines-tasks-java-common/java-common.js:124:23)
    at Object.<anonymous> (/home/rajesh/_work/_tasks/Maven_ac4ee482-65da-4485-a532-7b085873e532/3.231.5/maventask.js:110:41)
    at Module._compile (node:internal/modules/cjs/loader:1241:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
    at Module.load (node:internal/modules/cjs/loader:1091:32)
    at Module._load (node:internal/modules/cjs/loader:938:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
    at node:internal/main/run_main_module:23:47
2023-12-15T04:15:36.9771517Z ##[section]Finishing: Maven


2023-12-15T04:17:04.4350371Z ##[section]Starting: Maven
2023-12-15T04:17:04.4363161Z ==============================================================================
2023-12-15T04:17:04.4363322Z Task         : Maven
2023-12-15T04:17:04.4363386Z Description  : Build, test, and deploy with Apache Maven
2023-12-15T04:17:04.4363487Z Version      : 3.231.5
2023-12-15T04:17:04.4363552Z Author       : Microsoft Corporation
2023-12-15T04:17:04.4363645Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/maven
2023-12-15T04:17:04.4363764Z ==============================================================================
2023-12-15T04:17:06.8280422Z ##[error]Unhandled: Failed to find the specified JDK version. Please ensure the specified JDK version is installed on the agent and the environment variable 'JAVA_HOME_11_X64' exists and is set to the location of a corresponding JDK or use the [Java Tool Installer](https://go.microsoft.com/fwlink/?linkid=875287) task to install the desired JDK.
2023-12-15T04:17:06.8517850Z ##[error]Error: Failed to find the specified JDK version. Please ensure the specified JDK version is installed on the agent and the environment variable 'JAVA_HOME_11_X64' exists and is set to the location of a corresponding JDK or use the [Java Tool Installer](https://go.microsoft.com/fwlink/?linkid=875287) task to install the desired JDK.
    at Object.findJavaHome (/home/rajesh/_work/_tasks/Maven_ac4ee482-65da-4485-a532-7b085873e532/3.231.5/node_modules/azure-pipelines-tasks-java-common/java-common.js:124:23)
    at Object.<anonymous> (/home/rajesh/_work/_tasks/Maven_ac4ee482-65da-4485-a532-7b085873e532/3.231.5/maventask.js:110:41)
    at Module._compile (node:internal/modules/cjs/loader:1241:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
    at Module.load (node:internal/modules/cjs/loader:1091:32)
    at Module._load (node:internal/modules/cjs/loader:938:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
    at node:internal/main/run_main_module:23:47
2023-12-15T04:17:06.8939984Z ##[section]Finishing: Maven\



2023-12-15T04:19:14.3677370Z Downloaded from central: https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar (251 kB at 1.8 MB/s)
2023-12-15T04:19:14.3677732Z [INFO] ------------------------------------------------------------------------
2023-12-15T04:19:14.3678044Z [INFO] BUILD FAILURE
2023-12-15T04:19:14.3678331Z [INFO] ------------------------------------------------------------------------
2023-12-15T04:19:14.3678569Z [INFO] Total time:  55.563 s
2023-12-15T04:19:14.3678810Z [INFO] Finished at: 2023-12-15T04:19:14Z
2023-12-15T04:19:14.3679111Z [INFO] ------------------------------------------------------------------------
2023-12-15T04:19:14.3683497Z [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project yoodle: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1]
2023-12-15T04:19:14.3684148Z [ERROR] 
2023-12-15T04:19:14.3684443Z [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
2023-12-15T04:19:14.3684755Z [ERROR] Re-run Maven using the -X switch to enable full debug logging.
2023-12-15T04:19:14.3684963Z [ERROR] 
2023-12-15T04:19:14.3685263Z [ERROR] For more information about the errors and possible solutions, please read the following articles:
2023-12-15T04:19:14.3685612Z [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
2023-12-15T04:19:14.3685733Z 
2023-12-15T04:19:17.8559773Z Result Attachments will be stored in LogStore
2023-12-15T04:19:17.8646491Z Run Attachments will be stored in LogStore
2023-12-15T04:19:17.9344706Z ##[error]Build failed.
2023-12-15T04:19:17.9436032Z ##[section]Async Command Start: Publish test results
2023-12-15T04:19:18.0583367Z Publishing test results to test run '3'.
2023-12-15T04:19:18.0616122Z TestResults To Publish 1, Test run id:3
2023-12-15T04:19:18.0654329Z Test results publishing 1, remaining: 0. Test run id: 3
2023-12-15T04:19:18.6536524Z Published Test Run : https://dev.azure.com/xopsschool/DevOpsXBasic/_TestManagement/Runs?runId=3&_a=runCharts
2023-12-15T04:19:18.7047357Z ##[section]Async Command End: Publish test results
2023-12-15T04:19:18.7048417Z ##[section]Finishing: Maven

2023-12-15T04:23:06.8588049Z [INFO] --- maven-install-plugin:2.4:install (default-install) @ yoodle ---
2023-12-15T04:23:06.9559774Z [INFO] Installing /home/rajesh/_work/3/s/target/yoodle-215.jar to /home/rajesh/.m2/repository/com/scmgalaxy/mavensample/yoodle/215/yoodle-215.jar
2023-12-15T04:23:06.9613258Z [INFO] Installing /home/rajesh/_work/3/s/pom.xml to /home/rajesh/.m2/repository/com/scmgalaxy/mavensample/yoodle/215/yoodle-215.pom
2023-12-15T04:23:06.9828749Z [INFO] Installing /home/rajesh/_work/3/s/target/yoodle-215-javadoc.jar to /home/rajesh/.m2/repository/com/scmgalaxy/mavensample/yoodle/215/yoodle-215-javadoc.jar
2023-12-15T04:23:06.9859952Z [INFO] 
2023-12-15T04:23:06.9947446Z [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ yoodle ---
2023-12-15T04:23:07.0502114Z [INFO] ------------------------------------------------------------------------
2023-12-15T04:23:07.0502833Z [INFO] BUILD FAILURE
2023-12-15T04:23:07.0503306Z [INFO] ------------------------------------------------------------------------
2023-12-15T04:23:07.0503736Z [INFO] Total time:  8.371 s
2023-12-15T04:23:07.0504162Z [INFO] Finished at: 2023-12-15T04:23:07Z
2023-12-15T04:23:07.0573893Z [INFO] ------------------------------------------------------------------------
2023-12-15T04:23:07.0627997Z [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project yoodle: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1]
2023-12-15T04:23:07.0628800Z [ERROR] 
2023-12-15T04:23:07.0629224Z [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
2023-12-15T04:23:07.0629845Z [ERROR] Re-run Maven using the -X switch to enable full debug logging.
2023-12-15T04:23:07.0630220Z [ERROR] 
2023-12-15T04:23:07.0664324Z [ERROR] For more information about the errors and possible solutions, please read the following articles:
2023-12-15T04:23:07.0664915Z [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
2023-12-15T04:23:07.1141592Z 
2023-12-15T04:23:07.1162269Z The process '/usr/bin/mvn' failed with exit code 1
2023-12-15T04:23:07.1170348Z Could not retrieve code analysis results - Maven run failed.
2023-12-15T04:23:10.9195120Z Result Attachments will be stored in LogStore
2023-12-15T04:23:10.9288909Z Run Attachments will be stored in LogStore
2023-12-15T04:23:10.9783250Z ##[error]Build failed.
2023-12-15T04:23:10.9866516Z ##[section]Async Command Start: Publish test results
2023-12-15T04:23:11.1026890Z Publishing test results to test run '4'.
2023-12-15T04:23:11.1058931Z TestResults To Publish 1, Test run id:4
2023-12-15T04:23:11.1096593Z Test results publishing 1, remaining: 0. Test run id: 4
2023-12-15T04:23:11.6339898Z Published Test Run : https://dev.azure.com/xopsschool/DevOpsXBasic/_TestManagement/Runs?runId=4&_a=runCharts
2023-12-15T04:23:11.6872759Z ##[section]Async Command End: Publish test results
2023-12-15T04:23:11.6873874Z ##[section]Finishing: Maven

Securing Your Digital Assets: Wallet App Development Step-by-Step

Do you want to know how to create a wallet app of your own? Building a secure wallet app requires carefully planned security measures and a user-centric approach. Let’s just say wallet app development isn’t easy (learn more details in the Topflight blog)!

A digital wallet application is a software application on your smartphone or other mobile device that securely stores and manages your digital assets. Think of it as a high-tech version of your physical wallet but for the digital age. These wallets must be secure because you won’t keep them in your pocket.

Don’t worry, though – if you stick to our guide, you can create a digital wallet app in no time.

How to create a wallet app

Before you can build your own e-wallet, you have put in months of work and a lot of time. Here’s where to start.

1. Define Your Vision and Target Audience:

Before diving into code, clearly define your app’s purpose and target audience. Will it cater to a specific blockchain or a diverse ecosystem? Is it designed for individual users or institutional clients? Understanding your target users’ needs and preferences will guide your feature selection and security protocols. Your customers will help you with the information you need to create a wallet app.

2. Choose the Right Technology Stack:

The technology stack dictates your app’s performance, security, and scalability. Popular options include:

  • Front-end: React Native for cross-platform development, Flutter for high performance, or native iOS/Android development for optimal device integration.
  • Back-end: Node.js for its flexibility and scalability, Python for its robust development tools, or Java for enterprise-grade security.
  • Blockchain Integration: Libraries like Web3.js for Ethereum or specific SDKs for other blockchains.

3. Implement Robust Security Measures:

Security is paramount, and your app should employ a multi-layered approach to protect user assets. Consider these:

  • Cryptography: Utilize robust encryption algorithms like AES-256 for data at rest and TLS/SSL for data in transit.
  • Key Management: Implement secure key generation, storage, and encryption practices. Hardware security modules (HSMs) are ideal for storing private keys.
  • Multi-Factor Authentication (MFA): Go beyond passwords with fingerprint, facial recognition, or hardware tokens for secure logins.
  • Secure Coding Practices: Employ well-established security best practices like code reviews, vulnerability scanning, and penetration testing to identify and address potential security flaws.
  • Regular Updates and Audits: Regularly update your app with the latest security patches and conduct security audits by independent third-party experts.

4. Design a User-Friendly Interface:

Security shouldn’t come at the expense of usability. Design an intuitive and user-friendly interface that makes managing digital assets seamless. Consider these:

  • Simple and Clear Navigation: Make essential features readily accessible and provide clear instructions for complex tasks.
  • Real-time Transaction Monitoring: Allow users to track their transactions and account balances easily.
  • Educational Resources: Provide in-app tutorials and FAQs to educate users about blockchain technology and best practices for secure asset management.
  • Multilingual Support: Cover a global audience by offering app functionality in multiple languages.

5. Testing and Deployment:

Thorough testing ensures your app functions flawlessly and meets security standards. Conduct unit tests, integration tests, and user acceptance testing to identify and address bugs. Deploy your app on trusted app stores with secure distribution protocols.

6. Ongoing Maintenance and Support:

When you build a mobile wallet app, the work continues after deployment. Continuously monitor your app for security vulnerabilities and user feedback. Provide prompt customer support and update your app regularly with new features and security improvements.

Additional Considerations:

  • Compliance: Ensure your app complies with relevant regulations and financial crime prevention laws.
  • Privacy: Implement transparent data privacy policies and secure user data storage practices.
  • Community Engagement: Build a strong community around your app by offering forums, support channels, and educational resources.

Remember, security is an ongoing process. By following these steps and staying vigilant, you can develop a secure and user-friendly wallet app that empowers users to manage their digital assets in the ever-evolving blockchain ecosystem confidently.

Conclusion

Don’t worry if this all seems overwhelming. You can hire a team to help you from start to finish. They will have the experience and the expertise to guide you through this entire process. Now that you know how to create a wallet app, all that’s left is to start!

And you can find out how to develop any fintech application here: https://topflightapps.com/ideas/how-to-build-a-market-ready-fintech-app-in-record-time/

Artifactory Error:

Error

root@ip-172-31-95-25:/opt/artifactory-pro-7.23.3/var/log# grep -R -i error .
./console.log:ReferenceError: globalThis is not defined
./console.log:2023-12-11T17:13:58.430Z [jfrou] [INFO ] [1def5c82561bbf87] [join_executor.go:165          ] [main                ] - Cluster join: Retry 5: Service registry ping failed, will retry. Error: Get "http://localhost:8040/access/api/v1/system/ping": dial tcp 127.0.0.1:8040: connect: connection refused
./console.log:2023-12-11T17:13:59.504Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 5: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./console.log:2023-12-11T17:14:00.501Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 5: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./console.log:[dd.trace 2023-12-11 17:14:01:136 +0000] [dd-task-scheduler] INFO datadog.trace.agent.core.StatusLogger - DATADOG TRACER CONFIGURATION {"version":"1.24.1~a9dfdcc7da","os_name":"Linux","os_version":"5.15.0-1049-aws","architecture":"amd64","lang":"jvm","lang_version":"11.0.10","jvm_vendor":"AdoptOpenJDK","jvm_version":"11.0.10+9","java_class_version":"55.0","http_nonProxyHosts":"null","http_proxyHost":"null","enabled":true,"service":"catalina","agent_url":"http://localhost:8126","agent_unix_domain_socket":"/opt/datadog/apm/inject/run/apm.socket","agent_error":true,"debug":false,"trace_propagation_style_extract":["datadog","tracecontext"],"trace_propagation_style_inject":["datadog","tracecontext"],"analytics_enabled":false,"sampling_rules":[{},{}],"priority_sampling_enabled":true,"logs_correlation_enabled":true,"profiling_enabled":false,"remote_config_enabled":true,"debugger_enabled":false,"appsec_enabled":"ENABLED_INACTIVE","telemetry_enabled":true,"dd_version":"","health_checks_enabled":true,"configuration_file":"no config file present","runtime_id":"0df78989-699f-4df3-ba1e-fb65b7bd697b","logging_settings":{"levelInBrackets":false,"dateTimeFormat":"'[dd.trace 'yyyy-MM-dd HH:mm:ss:SSS Z']'","logFile":"System.err","configurationFile":"simplelogger.properties","showShortLogName":false,"showDateTime":true,"showLogName":true,"showThreadName":true,"defaultLogLevel":"INFO","warnLevelString":"WARN","embedException":false},"cws_enabled":false,"cws_tls_refresh":5000,"datadog_profiler_enabled":true,"datadog_profiler_safe":true,"datadog_profiler_enabled_overridden":false}
./console.log:2023-12-11T17:14:04.513Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 10: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./console.log:2023-12-11T17:14:05.505Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 10: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./console.log:2023-12-11T17:14:09.518Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 15: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./console.log:[dd.trace 2023-12-11 17:14:09:769 +0000] [dd-trace-processor] WARN datadog.trace.agent.common.writer.ddagent.DDAgentApi - Error while sending 1 (size=706B) traces. Total: 1, Received: 1, Sent: 0, Failed: 1. java.io.IOException: No such file or directory (Will not log errors for 5 minutes)
./console.log:2023-12-11T17:14:10.510Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 15: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./console.log:2023-12-11T17:14:14.523Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 20: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./console.log:2023-12-11T17:14:15.514Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 20: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./console.log:2023-12-11T17:14:19.529Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 25: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./console.log:2023-12-11T17:14:20.521Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 25: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./console.log:2023-12-11T17:14:24.535Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 30: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./console.log:2023-12-11T17:14:25.527Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 30: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./console.log:2023-12-11T17:14:29.540Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 35: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./console.log:2023-12-11T17:14:30.531Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 35: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./console.log:2023-12-11T17:14:33.435Z [jfrou] [INFO ] [1def5c82561bbf87] [join_executor.go:165          ] [main                ] - Cluster join: Retry 10: Service registry ping failed, will retry. Error: Get "http://localhost:8040/access/api/v1/system/ping": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
./console.log:2023-12-11T17:14:34.549Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 40: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./console.log:2023-12-11T17:14:35.537Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 40: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./console.log:2023-12-11T17:14:39.553Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 45: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./console.log:2023-12-11T17:14:40.542Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 45: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./console.log:2023-12-11T17:14:43.231Z [jfac ] [WARN ] [2b2bd02da0ac97fb] [o.j.c.ExecutionUtils:165      ] [pool-28-thread-2    ] - Retry 10 Elapsed 5.84 secs failed: Registration with router on URL http://localhost:8046 failed with error: UNAVAILABLE: io exception. Trying again
./console.log:2023-12-11T17:14:44.560Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 50: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./console.log:2023-12-11T17:14:45.550Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 50: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./console.log:2023-12-11T17:14:48.299Z [jfac ] [WARN ] [2b2bd02da0ac97fb] [o.j.c.ExecutionUtils:165      ] [pool-28-thread-2    ] - Retry 20 Elapsed 10.91 secs failed: Registration with router on URL http://localhost:8046 failed with error: UNAVAILABLE: io exception. Trying again
./console.log:2023-12-11T17:14:48.765Z [jfrou] [WARN ] [247ce34e499a06b3] [local_topology.go:256         ] [main                ] - Readiness test failed with the following error: "required node services are missing or unhealthy"
./console.log:2023-12-11T17:14:49.567Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 55: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Failed to access :http://localhost:8046/access/api/v1/system/ping return status code : 404 [access_client]
./console.log:2023-12-11T17:14:50.557Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 55: Service registry ping failed, will retry. Error: Failed to ping access, response status: 404 Not Found (returned 404) [startup]
./console.log:2023-12-11T17:14:53.401Z [jfac ] [WARN ] [2b2bd02da0ac97fb] [o.j.c.ExecutionUtils:165      ] [pool-28-thread-2    ] - Retry 30 Elapsed 16.01 secs failed: Registration with router on URL http://localhost:8046 failed with error: UNAVAILABLE: io exception. Trying again
./console.log:2023-12-11T17:14:53.765Z [jfrou] [WARN ] [5c32b526382b6e4f] [local_topology.go:256         ] [main                ] - Readiness test failed with the following error: "required node services are missing or unhealthy"
./console.log:2023-12-11T17:14:54.581Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 60: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Failed to access :http://localhost:8046/access/api/v1/system/ping return status code : 404 [access_client]
./console.log:2023-12-11T17:14:55.918Z [jfevt] [WARN ] [5dbc5b2931adf732] [proxy_synchronizer.go:21      ] [main                ] - Proxy cache is not updated because of error: failure to get the list of proxies from Artifactory (returned 404) [proxy_cache]
./console.log:2023-12-11T17:14:55.993Z [jfevt] [WARN ] [5dbc5b2931adf732] [base_url_cache.go:68          ] [main                ] - Base URL cache is not updated because of error: failed to fetch base URL from Artifactory (returned 404) [baseurl_cache]
./console.log:2023-12-11T17:14:56.027Z [jfevt] [WARN ] [5dbc5b2931adf732] [domain_client.go:57           ] [main                ] - Error occurred when refreshing domain cache all domain endpoint failed : Fetch domains from http://localhost:8046/artifactory/api/events/domains failed (returned 404), Fetch domains from http://localhost:8046/distribution/api/v1/events/domains failed (returned 404),  [domain_client]
./console.log:2023-12-11T17:14:58.835Z [jfrou] [WARN ] [5325465ff82f1275] [local_topology.go:256         ] [main                ] - Readiness test failed with the following error: "required node services are missing or unhealthy"
./console.log:2023-12-11T17:15:03.791Z [jfrou] [WARN ] [4a301100487b2aa1] [local_topology.go:256         ] [main                ] - Readiness test failed with the following error: "required node services are missing or unhealthy"
./console.log:2023-12-11T17:15:05.937Z [jfevt] [WARN ] [5dbc5b2931adf732] [proxy_synchronizer.go:21      ] [main                ] - Proxy cache is not updated because of error: failure to get the list of proxies from Artifactory (returned 503) [proxy_cache]
./console.log:2023-12-11T17:15:06.016Z [jfevt] [WARN ] [5dbc5b2931adf732] [base_url_cache.go:68          ] [main                ] - Base URL cache is not updated because of error: failed to fetch base URL from Artifactory (returned 503) [baseurl_cache]
./console.log:2023-12-11T17:15:06.048Z [jfevt] [WARN ] [5dbc5b2931adf732] [domain_client.go:57           ] [main                ] - Error occurred when refreshing domain cache all domain endpoint failed : Fetch domains from http://localhost:8046/artifactory/api/events/domains failed (returned 503), Fetch domains from http://localhost:8046/distribution/api/v1/events/domains failed (returned 404),  [domain_client]
./console.log:2023-12-11T17:15:08.774Z [jfrou] [WARN ] [300060dfe4f22c04] [local_topology.go:256         ] [main                ] - Readiness test failed with the following error: "required node services are missing or unhealthy"
./event-service.log:2023-12-11T17:14:00.501Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 5: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./event-service.log:2023-12-11T17:14:05.505Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 10: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./event-service.log:2023-12-11T17:14:10.510Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 15: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./event-service.log:2023-12-11T17:14:15.514Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 20: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./event-service.log:2023-12-11T17:14:20.521Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 25: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./event-service.log:2023-12-11T17:14:25.527Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 30: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./event-service.log:2023-12-11T17:14:30.531Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 35: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./event-service.log:2023-12-11T17:14:35.537Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 40: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./event-service.log:2023-12-11T17:14:40.542Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 45: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./event-service.log:2023-12-11T17:14:45.550Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 50: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access/api/v1/system/ping': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [startup]
./event-service.log:2023-12-11T17:14:50.557Z [jfevt] [INFO ] [5dbc5b2931adf732] [access_thin_client.go:103     ] [main                ] - Cluster join: Retry 55: Service registry ping failed, will retry. Error: Failed to ping access, response status: 404 Not Found (returned 404) [startup]
./event-service.log:2023-12-11T17:14:55.918Z [jfevt] [WARN ] [5dbc5b2931adf732] [proxy_synchronizer.go:21      ] [main                ] - Proxy cache is not updated because of error: failure to get the list of proxies from Artifactory (returned 404) [proxy_cache]
./event-service.log:2023-12-11T17:14:55.993Z [jfevt] [WARN ] [5dbc5b2931adf732] [base_url_cache.go:68          ] [main                ] - Base URL cache is not updated because of error: failed to fetch base URL from Artifactory (returned 404) [baseurl_cache]
./event-service.log:2023-12-11T17:14:56.027Z [jfevt] [WARN ] [5dbc5b2931adf732] [domain_client.go:57           ] [main                ] - Error occurred when refreshing domain cache all domain endpoint failed : Fetch domains from http://localhost:8046/artifactory/api/events/domains failed (returned 404), Fetch domains from http://localhost:8046/distribution/api/v1/events/domains failed (returned 404),  [domain_client]
./event-service.log:2023-12-11T17:15:05.937Z [jfevt] [WARN ] [5dbc5b2931adf732] [proxy_synchronizer.go:21      ] [main                ] - Proxy cache is not updated because of error: failure to get the list of proxies from Artifactory (returned 503) [proxy_cache]
./event-service.log:2023-12-11T17:15:06.016Z [jfevt] [WARN ] [5dbc5b2931adf732] [base_url_cache.go:68          ] [main                ] - Base URL cache is not updated because of error: failed to fetch base URL from Artifactory (returned 503) [baseurl_cache]
./event-service.log:2023-12-11T17:15:06.048Z [jfevt] [WARN ] [5dbc5b2931adf732] [domain_client.go:57           ] [main                ] - Error occurred when refreshing domain cache all domain endpoint failed : Fetch domains from http://localhost:8046/artifactory/api/events/domains failed (returned 503), Fetch domains from http://localhost:8046/distribution/api/v1/events/domains failed (returned 404),  [domain_client]
./artifactory-service.log:                                                                         | -XX:OnOutOfMemoryError=kill -9 %p
./artifactory-service.log:   artifactory.binary.store.error.notification.intervalSecs              | 30
./artifactory-service.log:   artifactory.binary.store.error.notification.staleSecs                 | 30
./artifactory-service.log:   artifactory.acl.version.cache.async.waiting.on.error.time.millis      | 60000
./artifactory-service.log:   artifactory.persistentQueue.errors.check.trigger.sec                  | 30
./artifactory-service.log:   artifactory.upload.failOnChecksumValidationError                      | false
./artifactory-service.log:   artifactory.replication.errorQueue.maxErrors                          | 100
./artifactory-service.log:   artifactory.replication.errorQueue.enabled                            | false
./artifactory-service.log:   artifactory.replication.errorQueue.retryCount                         | 10
./artifactory-service.log:   artifactory.projects.storage.quota.error.tolerance.percentage         | 1
./artifactory-service.log:   artifactory.artifact.lifecycle.warm.restore.error.threshold.percent   | 10
./artifactory-service.log:   artifactory.artifact.lifecycle.warm.archive.error.threshold.percent   | 10
./access-service.log:2023-12-11T17:14:43.231Z [jfac ] [WARN ] [2b2bd02da0ac97fb] [o.j.c.ExecutionUtils:165      ] [pool-28-thread-2    ] - Retry 10 Elapsed 5.84 secs failed: Registration with router on URL http://localhost:8046 failed with error: UNAVAILABLE: io exception. Trying again
./access-service.log:2023-12-11T17:14:48.299Z [jfac ] [WARN ] [2b2bd02da0ac97fb] [o.j.c.ExecutionUtils:165      ] [pool-28-thread-2    ] - Retry 20 Elapsed 10.91 secs failed: Registration with router on URL http://localhost:8046 failed with error: UNAVAILABLE: io exception. Trying again
./access-service.log:2023-12-11T17:14:53.401Z [jfac ] [WARN ] [2b2bd02da0ac97fb] [o.j.c.ExecutionUtils:165      ] [pool-28-thread-2    ] - Retry 30 Elapsed 16.01 secs failed: Registration with router on URL http://localhost:8046 failed with error: UNAVAILABLE: io exception. Trying again
./metadata-service.log:2023-12-11T17:13:59.504Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 5: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./metadata-service.log:2023-12-11T17:14:04.513Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 10: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./metadata-service.log:2023-12-11T17:14:09.518Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 15: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./metadata-service.log:2023-12-11T17:14:14.523Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 20: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./metadata-service.log:2023-12-11T17:14:19.529Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 25: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./metadata-service.log:2023-12-11T17:14:24.535Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 30: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./metadata-service.log:2023-12-11T17:14:29.540Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 35: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./metadata-service.log:2023-12-11T17:14:34.549Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 40: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./metadata-service.log:2023-12-11T17:14:39.553Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 45: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./metadata-service.log:2023-12-11T17:14:44.560Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 50: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Get "http://localhost:8046/access/api/v1/system/ping": dial tcp 127.0.0.1:8046: connect: connection refused [access_client]
./metadata-service.log:2023-12-11T17:14:49.567Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 55: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Failed to access :http://localhost:8046/access/api/v1/system/ping return status code : 404 [access_client]
./metadata-service.log:2023-12-11T17:14:54.581Z [jfmd ] [INFO ] [7790c4438fdc1545] [accessclient.go:58            ] [main                ] - Cluster join: Retry 60: Service registry ping failed, will retry. Error: Error while trying to connect to local router at address 'http://localhost:8046/access': Failed to access :http://localhost:8046/access/api/v1/system/ping return status code : 404 [access_client]
./derby.log:derby.stream.error.file=/opt/artifactory-pro-7.23.3/var/log/derby.log
./router-service.log:2023-12-11T17:13:58.430Z [jfrou] [INFO ] [1def5c82561bbf87] [join_executor.go:165          ] [main                ] - Cluster join: Retry 5: Service registry ping failed, will retry. Error: Get "http://localhost:8040/access/api/v1/system/ping": dial tcp 127.0.0.1:8040: connect: connection refused
./router-service.log:2023-12-11T17:14:33.435Z [jfrou] [INFO ] [1def5c82561bbf87] [join_executor.go:165          ] [main                ] - Cluster join: Retry 10: Service registry ping failed, will retry. Error: Get "http://localhost:8040/access/api/v1/system/ping": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
./router-service.log:2023-12-11T17:14:48.765Z [jfrou] [WARN ] [247ce34e499a06b3] [local_topology.go:256         ] [main                ] - Readiness test failed with the following error: "required node services are missing or unhealthy"
./router-service.log:2023-12-11T17:14:53.765Z [jfrou] [WARN ] [5c32b526382b6e4f] [local_topology.go:256         ] [main                ] - Readiness test failed with the following error: "required node services are missing or unhealthy"
./router-service.log:2023-12-11T17:14:58.835Z [jfrou] [WARN ] [5325465ff82f1275] [local_topology.go:256         ] [main                ] - Readiness test failed with the following error: "required node services are missing or unhealthy"
./router-service.log:2023-12-11T17:15:03.791Z [jfrou] [WARN ] [4a301100487b2aa1] [local_topology.go:256         ] [main                ] - Readiness test failed with the following error: "required node services are missing or unhealthy"
./router-service.log:2023-12-11T17:15:08.774Z [jfrou] [WARN ] [300060dfe4f22c04] [local_topology.go:256         ] [main                ] - Readiness test failed with the following error: "required node services are missing or unhealthy"