Most Powerful Open Source ERP

Re: Can't deploy erp5

  • Last Update:2020-01-30
  • Version:001
  • Language:en
Document Reference
Re: Can't deploy erp5
Publication Information
Embedded
From: Unknown User
From: Thomas Gambier

Hello, I'm responsible for upgrading the installer so that it works on Debian 10.

 

Yesterday, I fixed the problem you had in apache: https://lab.nexedi.com/nexedi/slapos/commit/e018d9df44243cf35340db0b0d1b88eafaa2e0a3

 

Today, I released a new version and push it into the playbook so you can already try the new version (see my latests commits in the installer script: https://lab.nexedi.com/nexedi/slapos.package/commits/master)

 

 I'm currently building everything and pushing it into our software cache. Once this is done, the test should work again.

 

Sorry for the inconvenience, we started to port everything to Debian 10 quite lately.

 

 

Thanks for the quick reply.

 

Funny you should mention Apache. According to a run I did on VirtualBox running Debain 9 about a week ago, the install script/playbook is responsible for installing Apache2 to provide the frontend to ERP5. I just ran the install script again yesterday around 3PM EST, but this time for the actual Debian 10.2.0 server we plan on using, and then ran the following today:
root@erp:~# systemctl status apache2

Unit apache2.service could not be found.

This means that the the install script never reaches the Apache installation instructions in the install script (which I believe to be somewhere in the playbook).

According to the slapos-node-software.log file (linked to mega due to size), the playbook does complete, but a quick search of the word error in gedit shows that the installation experiences several GCC errors, especially toward the beginning of when the build starts doing things in the background.

You did mention that you are able to install ERP5 manually by not using the script. Is there any instruction out there on how to do so? If not, I would find it beneficial to have one out there in-case the script breaks like this again, especially for new potential developers such as myself.

Although the server we are testing is meant to be used for a professional business, we are in no rush to get it up and running at the moment and are willing to lend it to be temporarily used as a testing platform for fixing the ERP5 installation on the Debian 10 distro of ERP5. The server is a brand new Dell PowerEdge T440 with 8GB RDIMM RAM and a Xeon 4210 Silver Processor. In addition, you’ll get the support of a Software Engineer as well as a Computer Engineer. We would like to help in any way we can as we see ERP5 as a way to help out other small businesses like our own looking to find an alternative ERP software that does what we need and isn’t ridiculously expensive.

I await your response and would like to know how we can help! Thank you!

Looking deeper into the Apache issue and into the logs, it looks possible that the ERP5 frontend is never installed/configured. I checked and only apache2-bin is installed on our machine (this installation seems to contain no cfg and no /var/www folder, only a binary located in /usr/sbin). I did a quick recursive search to see if I could find calls to either use or install apache and this is what I found. Based on this finding, it seems that python3 (which I a assume was installed by the original run of the script) does contain a json under libcloud that is supposed to install apache2, and then a handful of ansible modules that are supposed to check its installation.

I'm also using

tail -f /opt/slapos/log/*.log

to keep track of what is happening in the background. From what I can see, SlapOS is running, as are the partitions, as well as zope. This only leaves the ERP5/SlapOS network interface (aka the Frontend) that isn't active, which according to this instruction set, should be handled by Apache2.

Again, we are willing to help in any way we can, even if it is as simple as being guinea pigs for the script.