Elyps is a regulated investment platform giving investors access to digital assets, featuring a Euro current account and an International VISA card

Elyps

This interview series celebrates all the phenomenal . Congratulations! Well-Deserved, Champion.The HackerNoon community is excited to learn more about you! Startups of the Year Winners Lugano Startup in the ranking. What does it mean for you to win this title? Winning HackerNoon's prestigious Startups of the Year 2023 title is a monumental achievement for us at Elysium, especially as a burgeoning startup from Lugano. This award validates our early efforts and fuels our ambition to revolutionize digital asset management using Lugano as the first market approach and testing pool. Starting our journey in Lugano, where over 400 merchants accept crypto payments, is just the beginning. Our aspirations stretch far beyond, aiming to redefine the self-custody experience for users worldwide. What sets you apart from the competition? What sets Elysium apart is our pioneering Onboarding algorithm and Assets Management system, designed with a user-centric philosophy. Unlike traditional wallets focusing on key storage, Elysium innovates on key creation and reconstruction, ensuring unmatched security and user convenience. Our approach to self-custody, where users' needs shape the technology, establishes Elysium as the first of its kind - a wallet that's as dynamic and flexible as its users. What do you love about your team, and why are you the ones to solve this problem? The strength of Elysium lies in our team's commitment and shared vision. Each professional member brings a unique blend of passion and expertise, united by the goal of building the future, being part of the blockchain space since 2017, and not just following trends. This collective drive is our most incredible people in addressing the complexities of digital asset management. We are proud of everyone on the team who has decided to be part of the journey. If you weren’t building your startup, what would you be doing? Should Elysium not have been our path, our inherent drive to innovate would have found another channel to contribute to the world. Solving humanity's challenges through innovation is not just what we do; it's who we are. At the moment, how do you measure success? What are your core metrics? As an early-stage startup, our success is measured by the positive feedback from professionals, investors, and beta testers. With our official market launch set for 2024, we anticipate this year to be pivotal in achieving real market traction and setting new benchmarks in digital asset management. Tell us how your startup is changing the world. Elysium is not just a wallet; it's a gateway to a more secure, efficient, and user-friendly digital asset ecosystem. Our Algorithms and focus on seamless asset management and payments mark the dawn of a new era in self-custody. What goals are you looking forward to accomplishing in 2024? Our roadmap for 2024 is ambitious, including securing additional funding, launching in Europe and beyond, improving our business model, and exploring the B2B side of our product. Each milestone is a step towards realizing our vision of becoming the "Neo-Bank Like" for Bitcoin and digital assets. Which trend(s) are you most excited about in 2024? Share your reasons. We're particularly excited about the potential of real-world assets on the blockchain, advancements in Bitcoin payments, AI-driven automation and optimization, and the applications of Zero Knowledge proof for digital identity. These trends represent the frontier of innovation in our industry. 2023 had been another crazy year, especially in tech, with layoffs and the Generative AI takeover! Which trend are you most concerned about? Be as brief or as detailed as you like. Indeed, AI has advantages and disadvantages, and we are concerned that every team member uses it to increase the quality of work; for us, AI is not a substitute but an enhancement that will be part of our growth. On the cybersecurity and social intelligence side, we are monitoring developments with our cybersecurity experts and building strategies to mitigate cyber threats related to identity simulation for social attacks and other AI and cybersecurity attacks. Any words of wisdom you’d like to share with us? Reflecting on Theodore Roosevelt's words, we're reminded that true achievement lies in effort, striving towards great goals, and resilience in facing challenges. As we navigate the complexities of the digital asset space, we're committed to daring greatly, driven by the belief that the greatest victories belong to those who dare to venture into the future.

Meet Elysium Lab, Winner of the Startups of the Year in Lugano, CH

Co-authored by Brennon Hampton The ixo protocol defines how data packaged within hashed and signed messages get processed and stored. In the context of ixo, these data resources are described as verifiable impact claims. It turns out that merkelized private data stores are a fundamental piece of the architecture for most Web 3.0 applications that will have uses beyond the ixo protocol. We have ended up building a generic, highly configurable new database utility that implements core new Web 3.0 standards and uses hash-chains to ensure integrity. cryptographically Today we are excited to announce that we will make this available as an open-source release that we call Elysian. The name Elysian derives from the Ancient Greek term for reserving admission in perpetuity to those chosen by the gods, the righteous, and the heroic. The Elysian release of ixo data stores provides a powerful set of tools for controlling access to private data on a permissioned basis to those services that can prove their credentials and capabilities, using the W3C Decentralized Identifier (DID) specification. Only the chosen ones who have proven their credentials can access Elysian data stores, using the powerful capabilities of decentralized authentication and the magic of applied cryptography. For ixo, impact data must be privately owned and access controlled by the creator of an impact project. The claims relating to a project will typically include sensitive information, such as personal identifiable data. The storage of this data must comply with jurisdictional, data protection and privacy regulations. We also want these stores to be censorship-resistant, with as little reliance as possible on central agencies to host project data. To be useful for the many applications of the ixo Protocol, these data stores need to be dynamically customisable, immutable, non-repudiable and only accept requests from verifiable digital identities, driven by their credentials and capabilities. The data stores must also be fast, cheap, secure and make it easy to perform queries on the stored data. It turns out that these are core data storage requirements for many other Web 3.0 applications. ixo How these data stores are deployed in the ixo network, is that each project that is set up on the ixo network points to an independently hosted data store to which the project’s data will be directed. This data remains under the full private control and ownership of the project creator. What goes into the data store and who can write or read the data is set up dynamically and controlled at the level of the data store. This data storage is entirely ‘off-chain’ from the ixo network or any other public . However, the proofs of the data submissions are stored on the ixo public ledger, together with limited metadata that is extremely useful for tracking the performance of projects, indexing and locating the data. We call this the Global Impact Ledger. blockchain As the signed messages containing project data (impact claims) are passed through the ixo blockchain for processing, these are validated by consensus and appended to the hash-chain record within the project’s data store. Effectively, each project has its own project hash-chain/s that have been validated. Refer to the ixo White Paper for more details about how the protocol then enables verification of these claims, tokenizes the proofs of impact and enables trading of these tokens and their underlying data. Elysian data stores are highly customisable On initialising an Elysian Data Store, a dynamically customisable list of identity credentials and capabilities is established to define what actions can be performed, by which of the identified agents that will interact with the data store. These permissions can be updated or revoked at any time. Access control is fine-grained and complies with the consent requirements for data protection and privacy. Data stored within an Elysian data store is immutable as this is an append-only data store (data cannot be deleted or updated). All data operations are authenticated by confirming that the digital identifier relating to the service or agent that signed the incoming request has the capability to perform this action. The data is all verifiable, as this conforms with the W3C standards for verifiable claims and credentials. Only message payloads that match the predefined JSON submission template set up for data store can be submitted. The associated credentials, such as cryptographic signatures, must also verify. The public key associated with the digital identifier that signed the request is retrieved via the identifier blockchain record, from the identity credential provider and validated. Once verified, we insert the record and log the transaction in a timestamped transaction log with a hash that includes the previous transactions hash. To close the loop, for every verified message that passes into the Elysian data store, an event is triggered to the ixo blockchain.This ledgers the transaction and updates the publicly viewable project data. A Web 3.0 data utility for all With Elysian, we believe that we are providing a core building-block for many types of data-intensive Web 3.0 applications that will be fit for the purposes of decentralised architectures. We look forward to taking this into full production as a secure and highly useful piece of the data infrastructure for the ixo network. We encourage others to get involved in the project to help build out the exciting pipeline of features and uses of Elysian, as an open-source utility for all. Join the Community Learn more about ixo and how to get involved at ixo.foundation Follow ixo on Twitter Join the conversation on we’d love to answer your questions! Telegram Like ixo on Facebook See the code and contribute on Github We’re on too Reddit Subscribe to the ixo e-mail newsletter Email the team info@ixo.foundation

Elysian Release of the ixo Data Store

When James Cameron first teased Terminator 2 back in the day, it was through a 90-second teaser that showed an automated robot factory pumping out endless rows of robots, ending with a shot of Arnold as the build process completed. Pure pulp fiction. Or was it? Fast forward to 2024, and we are now entering the era of the hyperfactory, where the main body of cars is autonomously assembled every 76 seconds. No, that’s not a mistype because Xaoimi, the smartphone OEM, has entered the electric vehicle arena with the SU7 and with it, a factory setup that is 91% automated with 400 robots armed with HD cameras and can operate in the dark. It reminds me of the time I spent on stage at the Big Data Expo in China with the chairman of Foxconn, and we debated the merits of running a smartphone factory with the lights off — because who needs lights when it’s just the robots running the show? The factory of the future will have only two employees, a man and a dog. The man will be there to feed the dog. The dog will be there to keep the man from touching the equipment.
— Warren Bennis Watching the keynote reveal is an eye-opening vision of the future of manufacturing but not in the way you think. “We have 269 welding machines to achieve 100% automated production and have the 36 robots to achieve 0.5 millimeters of assembly precision” “…industry leading seven axis coating robots with 70,000 RPM, it can make the paint coverage extremely fine balanced. This produces a natural flat and smooth finish..” “AMR robots that can replace forklifts/internal transport around the factory…” The best part is that the cars can then drive themselves off the factory line with the autopilot software that the company has introduced. In all, it’s a fascinating look at the future of car manufacturing. But there’s something else to consider. We are looking at the precursor of mass-produced, highly automated robot and drone production, something that I can’t help but compare to that dystopian movie. Because, let’s face it, everything is starting to point towards it. We have major AI players all rushing to give their hyperbolic algorithms some form of physical embodiment to contextually understand the world around them in a new dimension. The idea that military, DARPA, or even startup funding won’t find its way to a hyperfactory of this kind is ludicrous because they’ll be eyeing this up as a way to mass-produce killer drones and robotic tech in the blink of an eye if it means flooding the market with robotic slaves. One of the best (read: accurate) dystopian movies of the future to this day is Elysium by Neill Blomkamp, but even then, his vision of a robotic factory is forcing human labor to manufacture the military machines that take the piss on a daily basis. It just won’t be like that. It’s time to pay close attention to other industries for clues as to how stuff like Terminator or The Matrix could feasibly come true — our hubris in automating the human out of every job role and process will ultimately lead us to a path where automation can be easily retooled and reprogrammed to manufacture something else. And it won’t be a Roomba. When James Cameron first teased Terminator 2 back in the day, it was through a 90-second teaser that showed an automated robot factory pumping out endless rows of robots, ending with a shot of Arnold as the build process completed. Pure pulp fiction. Or was it? Fast forward to 2024, and we are now entering the era of the hyperfactory, where the main body of cars is autonomously assembled every 76 seconds. Fast forward to 2024, and we are now entering the era of the hyperfactory , where the main body of cars is autonomously assembled every 76 seconds. hyperfactory No, that’s not a mistype because Xaoimi, the smartphone OEM, has entered the electric vehicle arena with the SU7 and with it, a factory setup that is 91% automated with 400 robots armed with HD cameras and can operate in the dark. It reminds me of the time I spent on stage at the Big Data Expo in China with the chairman of Foxconn, and we debated the merits of running a smartphone factory with the lights off — because who needs lights when it’s just the robots running the show? It reminds me of the time I spent on stage at the Big Data Expo in China with the chairman of Foxconn, The factory of the future will have only two employees, a man and a dog. The man will be there to feed the dog. The dog will be there to keep the man from touching the equipment. — Warren Bennis The factory of the future will have only two employees, a man and a dog. The man will be there to feed the dog. The dog will be there to keep the man from touching the equipment. The factory of the future will have only two employees, a man and a dog. The man will be there to feed the dog. The dog will be there to keep the man from touching the equipment. — Warren Bennis — Warren Bennis Watching the keynote reveal is an eye-opening vision of the future of manufacturing but not in the way you think. keynote reveal keynote reveal “We have 269 welding machines to achieve 100% automated production and have the 36 robots to achieve 0.5 millimeters of assembly precision” “…industry leading seven axis coating robots with 70,000 RPM, it can make the paint coverage extremely fine balanced. This produces a natural flat and smooth finish..” “AMR robots that can replace forklifts/internal transport around the factory…” The best part is that the cars can then drive themselves off the factory line with the autopilot software that the company has introduced. In all, it’s a fascinating look at the future of car manufacturing. But there’s something else to consider. We are looking at the precursor of mass-produced, highly automated robot and drone production, something that I can’t help but compare to that dystopian movie. We are looking at the precursor of mass-produced, highly automated robot and drone production, something that I can’t help but compare to that dystopian movie. that dystopian movie. Because, let’s face it, everything is starting to point towards it. We have major AI players all rushing to give their hyperbolic algorithms some form of physical embodiment to contextually understand the world around them in a new dimension. The idea that military, DARPA, or even startup funding won’t find its way to a hyperfactory of this kind is ludicrous because they’ll be eyeing this up as a way to mass-produce killer drones and robotic tech in the blink of an eye if it means flooding the market with robotic slaves. The idea that military, DARPA, or even startup funding won’t find its way to a hyperfactory of this kind is ludicrous because they’ll be eyeing this up as a way to mass-produce killer drones and robotic tech in the blink of an eye if it means flooding the market with robotic slaves. One of the best ( read: accurate ) dystopian movies of the future to this day is Elysium by Neill Blomkamp, but even then, his vision of a robotic factory is forcing human labor to manufacture the military machines that take the piss on a daily basis. It just won’t be like that. read: accurate It’s time to pay close attention to other industries for clues as to how stuff like Terminator or The Matrix could feasibly come true — our hubris in automating the human out of every job role and process will ultimately lead us to a path where automation can be easily retooled and reprogrammed to manufacture something else. And it won’t be a Roomba.

Skynet Is Not the One You Should Be Fearing - Fear Your Favourite Car Manufacturer Instead

Narrative Resilience in Online Conflict Coverage: Insights from Twitter Analysis

Storing Passwords In A Database: A Better Way to Do So

How Optimistic Rollups Enhance Ethereum's Performance and Security

The article demonstrates the advantages of loop unrolling by iterating over multiple items per cycle while adjusting the loop counter accordingly. Learning Objectives The problem with iterating using traditional loops
Advantages with loop unrolling Prerequisites for Developers Basic understanding of C# programming language.


Familiar with for loops Getting Started The problem with iterating using traditional loops Most developers will iterate over array elements and perform a mathematical operation as shown in the following code snippet. for (int i = 0; i < array.Length; i++)
    {
        array[i] = i * 2;
    } Although the above code snippet is quite clean and straightforward, it incurs a cost due to the loop control structure. Advantages with loop unrolling Please find below the refactored version of the previous code snippet int len = array.Length;
    for (int i = 0; i < len; i += 4)
    {
        array[i] = i * 2;
        if (i + 1 < len) array[i + 1] = (i + 1) * 2;
        if (i + 2 < len) array[i + 2] = (i + 2) * 2;
        if (i + 3 < len) array[i + 3] = (i + 3) * 2;
    } With refactored code, now we have reduced the loop frequency to 4 which leads to faster execution. In addition to that, it will: Reduce loop overheads which in turn decreases any conditional checks inside the loops.
Increase performance as it enhances the execution speed Complete Code Create another class named LoopUnrolling and add the following code snippet public static class LoopUnrolling
    {
        public static void BadWay() {
            const int size = 1024;
            int[] numbers = new int[size];
    
            // Traditional loop
            var watch = System.Diagnostics.Stopwatch.StartNew();
            for (int i = 0; i < numbers.Length; i++)
            {
                numbers[i] = i * 2;
            }
            watch.Stop();
            Console.WriteLine($"Traditional loop time: {watch.ElapsedTicks} ticks");
    
        }
        public static void GoodWay()
        {
            const int size = 1024;
            int[] numbers = new int[size];
            int len = numbers.Length;
            var watch = System.Diagnostics.Stopwatch.StartNew();
            for (int i = 0; i < len; i += 4)
            {
                numbers[i] = i * 2;
                if (i + 1 < len) numbers[i + 1] = (i + 1) * 2;
                if (i + 2 < len) numbers[i + 2] = (i + 2) * 2;
                if (i + 3 < len) numbers[i + 3] = (i + 3) * 2;
            }
            watch.Stop();
            Console.WriteLine($"Unrolled loop time: {watch.ElapsedTicks} ticks");
        }
    } Execute from the main method as follows #region Day 26: Loop Unrolling
    static string ExecuteDay26()
    {
        LoopUnrolling.BadWay();
        LoopUnrolling.GoodWay();
    
        return "Executed Day 26 successfully..!!";
    }
    
    #endregion Console Output Traditional loop time: 20 ticks
    Unrolled loop time: 12 ticks As the output demonstrates loop unrolling took much less time than the traditional loop approach. Complete Code here: GitHub — ssukhpinder/30DayChallenge.Net Thank you for being a part of the C# community! Before you leave: Follow us: Youtube | X | LinkedIn | Dev.to
Visit our other platforms: GitHub
More content at C# Programming The article demonstrates the advantages of loop unrolling by iterating over multiple items per cycle while adjusting the loop counter accordingly. Learning Objectives The problem with iterating using traditional loops Advantages with loop unrolling The problem with iterating using traditional loops Advantages with loop unrolling Prerequisites for Developers Basic understanding of C# programming language. Familiar with for loops Basic understanding of C# programming language. Basic understanding of C# programming language. Familiar with for loops Familiar with for loops Getting Started The problem with iterating using traditional loops Most developers will iterate over array elements and perform a mathematical operation as shown in the following code snippet. for (int i = 0; i < array.Length; i++)
    {
        array[i] = i * 2;
    } for (int i = 0; i < array.Length; i++)
    {
        array[i] = i * 2;
    } Although the above code snippet is quite clean and straightforward, it incurs a cost due to the loop control structure. Advantages with loop unrolling Please find below the refactored version of the previous code snippet int len = array.Length;
    for (int i = 0; i < len; i += 4)
    {
        array[i] = i * 2;
        if (i + 1 < len) array[i + 1] = (i + 1) * 2;
        if (i + 2 < len) array[i + 2] = (i + 2) * 2;
        if (i + 3 < len) array[i + 3] = (i + 3) * 2;
    } int len = array.Length;
    for (int i = 0; i < len; i += 4)
    {
        array[i] = i * 2;
        if (i + 1 < len) array[i + 1] = (i + 1) * 2;
        if (i + 2 < len) array[i + 2] = (i + 2) * 2;
        if (i + 3 < len) array[i + 3] = (i + 3) * 2;
    } With refactored code, now we have reduced the loop frequency to 4 which leads to faster execution. In addition to that, it will: Reduce loop overheads which in turn decreases any conditional checks inside the loops. Increase performance as it enhances the execution speed Reduce loop overheads which in turn decreases any conditional checks inside the loops. Increase performance as it enhances the execution speed Complete Code Create another class named LoopUnrolling and add the following code snippet public static class LoopUnrolling
    {
        public static void BadWay() {
            const int size = 1024;
            int[] numbers = new int[size];
    
            // Traditional loop
            var watch = System.Diagnostics.Stopwatch.StartNew();
            for (int i = 0; i < numbers.Length; i++)
            {
                numbers[i] = i * 2;
            }
            watch.Stop();
            Console.WriteLine($"Traditional loop time: {watch.ElapsedTicks} ticks");
    
        }
        public static void GoodWay()
        {
            const int size = 1024;
            int[] numbers = new int[size];
            int len = numbers.Length;
            var watch = System.Diagnostics.Stopwatch.StartNew();
            for (int i = 0; i < len; i += 4)
            {
                numbers[i] = i * 2;
                if (i + 1 < len) numbers[i + 1] = (i + 1) * 2;
                if (i + 2 < len) numbers[i + 2] = (i + 2) * 2;
                if (i + 3 < len) numbers[i + 3] = (i + 3) * 2;
            }
            watch.Stop();
            Console.WriteLine($"Unrolled loop time: {watch.ElapsedTicks} ticks");
        }
    } public static class LoopUnrolling
    {
        public static void BadWay() {
            const int size = 1024;
            int[] numbers = new int[size];
    
            // Traditional loop
            var watch = System.Diagnostics.Stopwatch.StartNew();
            for (int i = 0; i < numbers.Length; i++)
            {
                numbers[i] = i * 2;
            }
            watch.Stop();
            Console.WriteLine($"Traditional loop time: {watch.ElapsedTicks} ticks");
    
        }
        public static void GoodWay()
        {
            const int size = 1024;
            int[] numbers = new int[size];
            int len = numbers.Length;
            var watch = System.Diagnostics.Stopwatch.StartNew();
            for (int i = 0; i < len; i += 4)
            {
                numbers[i] = i * 2;
                if (i + 1 < len) numbers[i + 1] = (i + 1) * 2;
                if (i + 2 < len) numbers[i + 2] = (i + 2) * 2;
                if (i + 3 < len) numbers[i + 3] = (i + 3) * 2;
            }
            watch.Stop();
            Console.WriteLine($"Unrolled loop time: {watch.ElapsedTicks} ticks");
        }
    } Execute from the main method as follows #region Day 26: Loop Unrolling
    static string ExecuteDay26()
    {
        LoopUnrolling.BadWay();
        LoopUnrolling.GoodWay();
    
        return "Executed Day 26 successfully..!!";
    }
    
    #endregion #region Day 26: Loop Unrolling
    static string ExecuteDay26()
    {
        LoopUnrolling.BadWay();
        LoopUnrolling.GoodWay();
    
        return "Executed Day 26 successfully..!!";
    }
    
    #endregion Console Output Traditional loop time: 20 ticks
    Unrolled loop time: 12 ticks Traditional loop time: 20 ticks
    Unrolled loop time: 12 ticks As the output demonstrates loop unrolling took much less time than the traditional loop approach. Complete Code here: GitHub — ssukhpinder/30DayChallenge.Net Complete Code here: GitHub — ssukhpinder/30DayChallenge.Net GitHub — ssukhpinder/30DayChallenge.Net Thank you for being a part of the C# community! Before you leave: Follow us: Youtube | X | LinkedIn | Dev.to Visit our other platforms: GitHub More content at C# Programming Youtube X LinkedIn Dev.to GitHub C# Programming

30-Day .NET Challenge - Day 26: Loop Unrolling

deployments come in all shapes and sizes. We support bare metal installs on any version of , containerized installs on any version of (including Red Hat OpenShift), and installs just about anywhere you can deploy a small lightweight single binary. But with flexibility comes the inevitability that edge case issues will require debugging. MinIO Linux Kubernetes In this blog post, we’ll show you how to debug a MinIO install running in Kubernetes and also some of the common issues you might encounter when doing bare metal installation and how to rectify them. Kubernetes Debugger Pod There are a few ways to access the MinIO API running inside a Kubernetes cluster. We can use or set up a listening on to be able to access the API. Both of these methods offer a way to access the service from outside the network, but they do come with one major downside: You can only access the Service that the NodePort or Port Forwarding references on an available port (not the usual configuration for the application). For example, you have to access the MinIO API, usually found on port , via a randomly assigned port. kubectl port-forwarding Service NodePort 9000 3xxxx What if I told you there was a better way – and it's not novel? When debugging applications you want to have full access to the native run-time environment so you can use various tools to troubleshoot and debug the cluster. One way to do that is launching a “busybox” style pod and installing all the required tools needed to debug the application. First launch a into the same namespace as your MinIO install. In order to do this create a yaml file called with the following yaml. Pod debugger-pod.yaml apiVersion: v1

kind: Pod

metadata:

  name: mc

  labels:

    app: mc

spec:

  containers:

  - image: minio/mc:latest

    command:

      - "sleep"

      - "604800"

    imagePullPolicy: IfNotPresent

    name: mc

  restartPolicy: Always The above Pod configuration is pulling the image for MinIO utility. In order to ensure the pod doesn’t just launch and then exit, we’ve added a command. mc sleep Once the yaml is saved apply the configuration to the Kubernetes namespace where the MinIO cluster is running kubectl apply -f debugger-pod.yaml Once the pod is up and running access it via shell $ kubectl exec -i -t -n default mc -c mc -- sh -c "(bash || ash || sh)"

[root@mc /]# Then with you can access the MinIO cluster mc [root@mc /]# mc alias set myminio    --insecure

Added `myminio` successfully. Now that we have a debugger pod up and running, you can perform action on the cluster directly within the same network. For example, if the replication was broken due to an site going offline or a hardware failure, you can resync any pending objects to be replicated using the following command [root@mc /]# mc admin replicate resync start minio1 minio2


[root@mc /]# mc admin replicate resync status minio1 minio2


✔ ✔ ✔

ResyncID: 		 2248d1d1-633f-4d61-b938-d8ea0b9b2d31

Status:   		 Completed

Objects:  		 2225

Versions: 		 2225

FailedObjects:     0

Throughput:   	 5.3 MiB/s

IOPs:     		 124.23 objs/s

Transferred:  	 94 MiB

Elapsed:  		 17.909833202s

CurrObjName:  	 testbucket/web-app/tsconfig.json Another reason you would run the debugger pod is if there are some file system permissions or invalid groups configurations in your pod, you can update them using the debugger pod [root@mc /]# chgrp -R 1000780050 .minio.sys/ The above debugging method can also be used in bare metal environments. For instance you can launch a busybox or bastion node with installed and follow the same instructions as above. mc Debugging Bare Metal Bare metal Linux installs are the most straightforward. In fact it just takes a few commands to get MinIO installed and running with SystemD. For details, please see . Configuring MinIO with SystemD Once in a great while, bare metal installs go awry. Here are some of the (not-so-common) pitfalls that we are asked about  in or . These pitfalls are not hardware or operating specific but can be useful to know in any kind of environment. SUBNET Slack File Permission One of the most common pitfalls is the file permissions of the MinIO binary and the configuration file. If this occurs, when you start MinIO using SystemD you will see and here is the full stack trace Assertion failed for MinIO. # systemctl status minio.service

● minio.service - MinIO

     Loaded: loaded (/etc/systemd/system/minio.service; enabled; vendor preset: enabled)

     Active: inactive (dead)

     Assert: start assertion failed at Tue 2023-12-26 18:21:38 PST; 8s ago

             AssertFileIsExecutable=/usr/local/bin/minio was not met

       Docs: https://docs.min.io


Dec 26 18:13:37 minio1 systemd[1]: minio.service: Starting requested but asserts failed.

Dec 26 18:17:50 minio1 systemd[1]: Assertion failed for MinIO.

Dec 26 18:21:38 minio1 systemd[1]: minio.service: Starting requested but asserts failed.

Dec 26 18:21:38 minio1 systemd[1]: Assertion failed for MinIO. This could be caused by a number of reasons, let's go down the list and check for each of them. : The binary, in this example located at needs to have permission for user and group, respectively. MinIO Binary /usr/local/bin/minio root:root # ll /usr/local/bin/minio

total 93804

-rwxr-xr-x 1 root    root    96018432 Nov 15 16:35  minio* : The MinIO service needs to run under a unique Linux user and group for security purposes, never run as a user. By default we use for the user and group names. In the SystemD service config file you should see something like this MinIO Service User and Group root minio-user User=minio-user

Group=minio-user : The directory where MinIO data will be stored needs to be owned by or whichever user you decide to run the MinIO service as above. MinIO Data Dir minio-user:minio-user # ls -l /mnt

total 4

drwxrwxr-x 2 minio-user minio-user 4096 Dec 27 09:58 data : Both the config files should have permissions for user and group like so SystemD and MinIO config root:root # ls -l /etc/default/minio

-rw-r--r-- 1 root root 1330 Dec 27 09:52 /etc/default/minio


# ls -l /etc/systemd/system/minio.service

-rw-r--r-- 1 root root 941 Dec 26 17:13 /etc/systemd/system/minio.service : The entire install process should be run as . You can also try if your user has permissions but the recommendation is to run as root as the install needs to place files in a bunch of places that only the user can access. Your bash prompt should have a and not a like so Run as Root root sudo root # $ vs # $ If none of the above work, the best approach is to remove the app, directories and configs and start a fresh install as a root user. Port conflict Another common issue related to deleted files which still hold on to the process, which causes port conflicts. Even when a service is not running, you may be unable to start a new service on the existing port or the service that is running will misbehave (such as not allowing you to login). # lsof -n | grep (deleted)

COMMAND PID USER FD TYPE DEVICE   SIZE 	NODE NAME

nginx   	13423 root 5u  	REG 253,3   42949672960 	17 (deleted)

minio 	13423 minio 6u    REG 253,3 	0         	      18 (deleted)

minio       13423 minio 7u    REG 253,3 	0         	      19 (deleted) You might see errors such as those below on a MinIO install Login Failed net::ERR_FAILED 500 Internal Server Error 401 Unauthorized The screenshot above shows an internal server error and an unauthorized error. While looking at the surface it looks unclear what has caused this error, we can debug with a little linux knowledge what to look for that could cause this, let's take a gander. There are several ways to debug this issue, first lets check to see if multiple MinIO processes are running on the same node # ps aux | grep -i minio

minio-u+    5048  0.3  1.7 1594008 144384 ?      Ssl  11:03   0:01 /usr/local/bin/minio server --console-address :9001 /mnt/data/disk1/minio


minio-u+    9276  0.3  1.7 1594208 144301 ?      Ssl  11:25   0:01 /usr/local/bin/minio server --console-address :9001 /mnt/data/disk1/minio As we can see above there are 2 MinIO processes running. Start by killing the process that is older or has been running the longest, in this case it seems to be the process ID . 5048 kill -9 5048 Sometimes even after killing the process the service might still not start or might still get hung up because it has reserved a process number but not let it go. This can be caused by files that have been deleted but are still being tracked by the operating system. You can find the deleted files via LSOF lsof -n | grep '(deleted)' Last but not least, if there are no deleted files left over or hung processes and if everything looks absolutely clean, the last resort is to quickly restart the node. This is a no-nonsense method that  shuts down and clears any pending files and processes so you start a fresh install. SUBNET to the rescue Although rare, installation edge cases will always exist. MinIO customers know that they have nothing to worry about because they can quickly message our engineers – who have written the code – via the portal. We've seen almost everything under the sun, so while the issue might look cryptic or mind boggling at first glance, we'll put our years of expertise debugging installations in many varied environments to work and help you in a jiffy. SUBNET If you have any questions on troubleshooting and debugging installs be sure to reach out to us on ! MinIO Slack

ELYPS

elyps.com

-- employees

Since n.d.

COMPANY RANKING

ELYPS

EVERGREEN INDEX #3581

Representing this company? Click here to claim and customize this page!

Elyps WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

ELYPS

elyps.com

-- employees

Since n.d.

COMPANY RANKING

ELYPS

EVERGREEN INDEX #3581

RELATED COMPANIESRANK

STORIES ABOUT ELYPS

Representing this company? Click here to claim and customize this page!

Elyps WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!