- Your first problem «Exit Code: 137» is not related to the Justuno module.
It is caused by a wrong Kubernetes configuration:
Exit code 137 is a signal that occurs when a container's memory exceeds the memory limit provided in the pod specification
-
Your second problem «No alive nodes found in your cluster» is not related to the Justuno module either.
It is caused by a wrong Elasticsearch configuration:
google.com/search?q="No+alive+nodes+found+in+your+cluster" -
Your third problem «ju_option: Argument #2 ($l) must be of type string, null given» is related to the Justuno module, but it was fixed a year ago, on 2023-07-20, in the
mage2pro/corepackage: github.com/mage2pro/core/issues/238
Then, on the same day (2023-07-20) I included the fix to thejustuno-com/corepackage by the following commit: github.com/justuno-com/core/commit/14b4a376
Actually, the «Argument <…> must be of type string, null given» was not a software defect.
Such code was correct until PHP 8.1.
It became deprecated in PHP 8.1: php.watch/versions/8.1/internal-func-non-nullable-null-deprecation
In July of 2023, I made the Justuno module compatible with PHP 8.1 on your request, so the problem was solved by the abovementioned commit.
The occurrence of this error in 2024 means that you use an outdated version of thejustuno-com/corepackage with a recent PHP version. -
Your fourth (and last) error «An error has happened during application run. See exception log for details.» means nothing.
You need to «see exception log for details».
Actually, the underlying error could be similar to my points 1, 2, 3 above or anything else. -
As you reported the first problem at 3:30 PM, and the last one at 01:30 AM, it looks like you spent about 10 hours dealing with these 4 problems.
Probably, you have (more or less) solved problem №1 (with Kubernetes) and problem №2 (Elasticsearch).
Probably, you have not solved problems №3 and №4.
Using my explanations above and putting in an unknown number of extra effort, you could probably solve both №3 (versions compatibility ofjustuno-com/coreand PHP) and №4 (diagnostics of messages like «See exception log for details»). -
Having had this experience, you have probably already realized that Magento is a complex system.
Magento is significantly different from SaaS systems like Shopify and Bigcommerce.
Magento is intended for large merchants that have their staff of programmers and who need customization and scaling of the system, and confidentiality of their sales and clients. -
Such a large merchant has at least 10 programmers, often 20, 30, 50.
Of course, at any moment only a part of these staff programmers work on Magento.
A large merchant has plenty of IT systems to work on, and these systems are highly customized and highly integrated.
Every staff programmer costs a large merchant about $20K a month just for salary + another $10K for a workplace, totaling about $30K a month.
10 programmers cost at least $300K a month. -
Such large merchants can make a bespoke Justuno-like service for themselves, but it is not desirable for them, because it will require them to distract their staff programmers from other important tasks or hire new programmers.
Hiring new programmers requires hiring new managers as well as a change of the project management methodology because it is impossible to manage a large team using the same methods as a small one.
The software development process became slower with every new team member.
That is why a sane manager of a large merchant would be happy to outsource the development of a Justuno-like service to a third-party company (like yours). -
But large merchants have very specific needs — not as one-size-fits-all SaaS merchants (Shopify, Bigcommerce).
The Justuno/Magento integration module (and the Justuno service itself) in its current state, where it contains standard functions and is updated once a year to be compatible with new versions of PHP and Magento, definitely is not what large Magento-based merchants need.
They need work on the integration (and the Justuno service itself) to be done permanently and done on solving their exact business problems, not just generic fit-all features.
Offering such customers standard pricing plans (justuno.com/pricing) is definitely not that large Magento-based customers need.
That is why you are (probably) losing money with your Magento-based clients, and that is why you regard the Magento module as «expensive». -
To handle Magento-based merchants profitably, you need different business processes, not those for Shopify or Bigcommerce.
Dealing with large merchants requires dedicated business analysts who will listen carefully and individually to them.
Then their individual needs need to be implemented as the corresponding individual (or customized) Justuno features, and then these Justuno features need to be carefully and individually integrated into their complex Magento stores.
That is when cash flows will be redirected: these large merchants will be happy to pay you, rather than burden their staff programmers with yet another project.
Once again: the module is expensive for you because you pay out of your pocket, and it is fundamentally wrong: the cash flow should come from merchants.