ERP5

User Information

Search Text

Search Type

Search Text

Search Button

Language

Editor Field

RSS / Atom Link

Discussion Posts

Discussion Posts

Summary
Re: Can't deploy erp5 by Unknown User at 2020/01/30 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.
Re: Can't deploy erp5 by Yusei Tahara at 2020/01/31 This is a rough quick instruction of how to setup a standalone erp5 without installation script. (https://slapos.nexedi.com/ for more details) First, your machine needs ipv6 internet connection. Then apt-get install gnupg wget -O- "https://download.opensuse.org/repositories/home:/VIFIBnexedi/Debian_10/Release.key" \| apt-key add - apt-get install slapos-node git export PATH=$PATH:/sbin slapos configure local (setup slapos node as standalone, it means that this node does not become a part of slapos cloud, instead it uses a local dummy slapos master node, slapproxy) ) slapos node format --now (It takes some minutes) git clone https://lab.nexedi.com/nexedi/slapos.git slapos supply /YOUR-SLAPOS-REPOSITORY-PATH/slapos/software/erp5/software.cfg local_computer (local_computer is your node name, look at /etc/opt/slapos/slapos.cfg) tail -f /opt/slapos/log/slapos-node-software.log (It takes several hours to build ERP5) (`slapos node software` is executed by cron /etc/cron.d/slapos-node) /opt/slapgrid/XXXX/.complete is a mark of complete. prepare a request script like this: import json software_url = '/home/a/slapos/software/erp5/software.cfg' parameter_dict = {} `request(software_url, 'my_test_erp5', filter_kw={ 'computer_guid': 'local_computer', }, software_type='default', partition_parameter_kw = { '_': json.dumps(parameter_dict, indent=2) } )` slapos console < request.py Let's wait for soem minutes. ERP5 cluster is setup automatically. (`slapos node instance` is executed by cron /etc/cron.d/slapos-node) Once setup is done, then, slapos node you will find something like this: slappart0:bootstrap-monitor EXITED Jan 31 10:31 AM slappart0:caucased-on-watch RUNNING pid 1134, uptime 0:00:07 slappart0:certificate_authority-1a4cd56cd8e659d9137c7bbd3db35a4e-on-watch RUNNING pid 1133, uptime 0:00:07 slappart0:crond-1a4cd56cd8e659d9137c7bbd3db35a4e-on-watch RUNNING pid 1130, uptime 0:00:07 slappart0:monitor-httpd-1a4cd56cd8e659d9137c7bbd3db35a4e-on-watch RUNNING pid 1131, uptime 0:00:07 slappart0:monitor-httpd-graceful EXITED Jan 31 10:31 AM slappart1:bootstrap-monitor EXITED Jan 31 10:31 AM slappart1:certificate_authority-1a4cd56cd8e659d9137c7bbd3db35a4e RUNNING pid 1138, uptime 0:00:07 slappart1:crond-1a4cd56cd8e659d9137c7bbd3db35a4e-on-watch RUNNING pid 1141, uptime 0:00:07 ... slappart6:apache RUNNING pid 1094, uptime 0:00:07 ... then, check your apache conf. In my case, it was in slappart6. less /srv/slapgrid/slappart6/etc/apache/apache.conf You will find which IP and port apache is listening. Apache uses internal IP, thus it is not accessble from outside. You need to setup your own frontend web server to publish slapos's apache. You should not change slapos apache conf by hand because it is overwritten by "slapos node instance". Once you can access to your erp5 instance, check your zope password. less /opt/slapos/slapproxy.db (find inituser-password) https://YOURERP5/erp5/ (use zope password to login)
Re: Can't deploy erp5 by Yusei Tahara at 2020/01/31 if you do not have ipv6, look at https://lab.nexedi.com/yusei/a/blob/master/slapos.cfg (slapformat section) `input_definition_file = /etc/opt/slapos/computer_definition.cfg` https://lab.nexedi.com/yusei/a/blob/master/computer_definition.cfg I don't use this option recently, but it should work.
Re: Can't deploy erp5 by Unknown User at 2020/01/31 From: Yusei Tahara This is a rough quick instruction of how to setup a standalone erp5 without installation script. (https://slapos.nexedi.com/ for more details) First, your machine needs ipv6 internet connection. Then apt-get install gnupg wget -O- "https://download.opensuse.org/repositories/home:/VIFIBnexedi/Debian_10/Release.key" \| apt-key add - apt-get install slapos-node git export PATH=$PATH:/sbin slapos configure local (setup slapos node as standalone, it means that this node does not become a part of slapos cloud, instead it uses a local dummy slapos master node, slapproxy) ) slapos node format --now (It takes some minutes) git clone https://lab.nexedi.com/nexedi/slapos.git slapos supply /YOUR-SLAPOS-REPOSITORY-PATH/slapos/software/erp5/software.cfg local_computer (local_computer is your node name, look at /etc/opt/slapos/slapos.cfg) tail -f /opt/slapos/log/slapos-node-software.log (It takes several hours to build ERP5) (`slapos node software` is executed by cron /etc/cron.d/slapos-node) /opt/slapgrid/XXXX/.complete is a mark of complete. prepare a request script like this: import json software_url = '/home/a/slapos/software/erp5/software.cfg' parameter_dict = {} `request(software_url, 'my_test_erp5', filter_kw={ 'computer_guid': 'local_computer', }, software_type='default', partition_parameter_kw = { '_': json.dumps(parameter_dict, indent=2) } )` slapos console < request.py Let's wait for soem minutes. ERP5 cluster is setup automatically. (`slapos node instance` is executed by cron /etc/cron.d/slapos-node) Once setup is done, then, slapos node you will find something like this: slappart0:bootstrap-monitor EXITED Jan 31 10:31 AM slappart0:caucased-on-watch RUNNING pid 1134, uptime 0:00:07 slappart0:certificate_authority-1a4cd56cd8e659d9137c7bbd3db35a4e-on-watch RUNNING pid 1133, uptime 0:00:07 slappart0:crond-1a4cd56cd8e659d9137c7bbd3db35a4e-on-watch RUNNING pid 1130, uptime 0:00:07 slappart0:monitor-httpd-1a4cd56cd8e659d9137c7bbd3db35a4e-on-watch RUNNING pid 1131, uptime 0:00:07 slappart0:monitor-httpd-graceful EXITED Jan 31 10:31 AM slappart1:bootstrap-monitor EXITED Jan 31 10:31 AM slappart1:certificate_authority-1a4cd56cd8e659d9137c7bbd3db35a4e RUNNING pid 1138, uptime 0:00:07 slappart1:crond-1a4cd56cd8e659d9137c7bbd3db35a4e-on-watch RUNNING pid 1141, uptime 0:00:07 ... slappart6:apache RUNNING pid 1094, uptime 0:00:07 ... then, check your apache conf. In my case, it was in slappart6. less /srv/slapgrid/slappart6/etc/apache/apache.conf You will find which IP and port apache is listening. Apache uses internal IP, thus it is not accessble from outside. You need to setup your own frontend web server to publish slapos's apache. You should not change slapos apache conf by hand because it is overwritten by "slapos node instance". Once you can access to your erp5 instance, check your zope password. less /opt/slapos/slapproxy.db (find inituser-password) https://YOURERP5/erp5/ (use zope password to login) Glad you posted those instructions. No wonder there's an install script. That being said, I would recomend that ERP5 post that somewhere so that if the script fails again, developers can use it as a reference to figure out exactly which step the installation failed. It also helped me pinpoint the issue that the install script is currently having with Debian 10. Based on everything you guys have told me and what I've found: using yesterday's build, I found that ERP5, zope, SlapOS and the apache backend are all present ( I found the apache.conf in partition 11; I also verified that the zope password already exists). This means that either the bash script or playbook completely fails at setting up the "frontend webserver to publish slapos's apache". I can't clearly tell if the frontend setup is meant to be in the bash script or in the playbook, but based on a sweep of both, neither contains instructions for setting up an apache frontend, or any frontend at all. I'm not sure I fully understand how to "publish slapos's apache" from existing backend to frontend (I've only ever programmed frontend-only apache websites), but I'm also willing to wait for the script fix if you guys think you can fix the frontend installation problem in a reasonable time. As stated before, we're willing to help test the install script for ERP5 until its functional on Debian 10. Thanks again!
Re: Can't deploy erp5 by Yusei Tahara at 2020/02/01 I'm not sure I fully understand how to "publish slapos's apache" from existing backend to frontend (I've only ever programmed frontend-only apache websites), You need a web server that works as a reverse proxy. I don't know if the erp5 installation script provides a frontend because slapos frontend system requires a public IP adress that is not usually free(need some cost to maintain it). Anyway, it is easy to setup apache manually for backend erp5, use apache mod rewrite and mod proxy. See examples below. It is enough for a try. https://lab.nexedi.com/yusei/a/blob/master/setup.sh https://lab.nexedi.com/yusei/a/blob/master/erp5apachefront.conf https://zope.readthedocs.io/en/latest/zopebook/VirtualHosting.html
Re: Can't deploy erp5 by Thomas Gambier at 2020/02/04 Hello, the script to deploy ERP5 on Debian 10 is now working fine but the problem is that the installation of slapos in your machine is broken (it still tries to install older software that will never work). The simplest is to reinstall the machine fully. Otherwise, you could do the following commands: `rm /tmp/playbook* rm -rf /tmp/tmpplaybook* rm /etc/cron.d/ansible* slapos node stop slapproxy rm /opt/slapos/slapproxy.db rm -rf /opt/slapgrid rm -rf /srv/slapgrid slapos node start slapproxy # then start the installation again wget https://deploy.erp5.net/erp5-standalone bash erp5-standalone` For information (especially for Yusei), the standalone installation scripts are installing both erp5 software release and apache-frontend software release (the backend and the frontend) so you don't need to install anything else. If your machine has a public IPv4, the apache-frontend will listen on this IPv4 so your ERP5 is directly accessible from outside. Also, for information, the slapos philosophy is to build everything from source, so you won't see anything installed through packages (except slapos and ansible and all their dependencies). All the softwares are installed under /opt/slapgrid and all the services are running inside partitions under /srv/slapgrid.
Re: Can't deploy erp5 by Unknown User at 2020/02/05 From: Thomas Gambier Hello, the script to deploy ERP5 on Debian 10 is now working fine but the problem is that the installation of slapos in your machine is broken (it still tries to install older software that will never work). The simplest is to reinstall the machine fully. Otherwise, you could do the following commands: `rm /tmp/playbook* rm -rf /tmp/tmpplaybook* rm /etc/cron.d/ansible* slapos node stop slapproxy rm /opt/slapos/slapproxy.db rm -rf /opt/slapgrid rm -rf /srv/slapgrid slapos node start slapproxy # then start the installation again wget https://deploy.erp5.net/erp5-standalone bash erp5-standalone` For information (especially for Yusei), the standalone installation scripts are installing both erp5 software release and apache-frontend software release (the backend and the frontend) so you don't need to install anything else. If your machine has a public IPv4, the apache-frontend will listen on this IPv4 so your ERP5 is directly accessible from outside. Also, for information, the slapos philosophy is to build everything from source, so you won't see anything installed through packages (except slapos and ansible and all their dependencies). All the softwares are installed under /opt/slapgrid and all the services are running inside partitions under /srv/slapgrid. I get the following errors for the following commands you gave me Thomas: root@erp:~# slapos node start slapproxy 2020-02-05 14:34:17 slapos[22608] INFO Launching supervisord with clean environment. 2020-02-05 14:34:17 slapos[22608] INFO Error: could not find config file /srv/slapgrid/etc/supervisord.conf 2020-02-05 14:34:17 slapos[22608] INFO For help, use -c -h 2020-02-05 14:34:17 slapos[22608] WARNING Supervisord unknown problem: 2020-02-05 14:34:17 slapos[22608] ERROR Failed to launch supervisord : Traceback (most recent call last): File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/entry.py", line 300, in run_subcommand result = cmd.run(parsed_args) File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/command.py", line 50, in run return self.take_action(parsed_args) File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/supervisorctl.py", line 87, in take_action super(SupervisorctlAliasCommand, self).take_action(args) File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/supervisorctl.py", line 73, in take_action forbid_supervisord_launch File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/supervisorctl.py", line 79, in do_supervisorctl launchSupervisord(instance_root=instance_root, logger=logger) File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/grid/svcbackend.py", line 196, in launchSupervisord raise RuntimeError('Failed to launch supervisord : %s' % result) RuntimeError: Failed to launch supervisord : root@erp:~# `bash erp5-standalone` ... gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now
Re: Can't deploy erp5 by Unknown User at 2020/02/06 From: Unknown User From: Thomas Gambier Hello, the script to deploy ERP5 on Debian 10 is now working fine but the problem is that the installation of slapos in your machine is broken (it still tries to install older software that will never work). The simplest is to reinstall the machine fully. Otherwise, you could do the following commands: `rm /tmp/playbook* rm -rf /tmp/tmpplaybook* rm /etc/cron.d/ansible* slapos node stop slapproxy rm /opt/slapos/slapproxy.db rm -rf /opt/slapgrid rm -rf /srv/slapgrid slapos node start slapproxy # then start the installation again wget https://deploy.erp5.net/erp5-standalone bash erp5-standalone` For information (especially for Yusei), the standalone installation scripts are installing both erp5 software release and apache-frontend software release (the backend and the frontend) so you don't need to install anything else. If your machine has a public IPv4, the apache-frontend will listen on this IPv4 so your ERP5 is directly accessible from outside. Also, for information, the slapos philosophy is to build everything from source, so you won't see anything installed through packages (except slapos and ansible and all their dependencies). All the softwares are installed under /opt/slapgrid and all the services are running inside partitions under /srv/slapgrid. I get the following errors for the following commands you gave me Thomas: root@erp:~# slapos node start slapproxy 2020-02-05 14:34:17 slapos[22608] INFO Launching supervisord with clean environment. 2020-02-05 14:34:17 slapos[22608] INFO Error: could not find config file /srv/slapgrid/etc/supervisord.conf 2020-02-05 14:34:17 slapos[22608] INFO For help, use -c -h 2020-02-05 14:34:17 slapos[22608] WARNING Supervisord unknown problem: 2020-02-05 14:34:17 slapos[22608] ERROR Failed to launch supervisord : Traceback (most recent call last): File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/entry.py", line 300, in run_subcommand result = cmd.run(parsed_args) File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/command.py", line 50, in run return self.take_action(parsed_args) File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/supervisorctl.py", line 87, in take_action super(SupervisorctlAliasCommand, self).take_action(args) File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/supervisorctl.py", line 73, in take_action forbid_supervisord_launch File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/supervisorctl.py", line 79, in do_supervisorctl launchSupervisord(instance_root=instance_root, logger=logger) File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/grid/svcbackend.py", line 196, in launchSupervisord raise RuntimeError('Failed to launch supervisord : %s' % result) RuntimeError: Failed to launch supervisord : root@erp:~# `bash erp5-standalone` ... gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now Redownloaded the script today and now its getting stuck at the "Waiting for Proxy" step of the ansible playbook: TASK [slapos-proxy : Wait for proxy] ******************************************** fatal: [127.0.0.1]: FAILED! => {"changed": false, "elapsed": 300, "msg": "Timeout when waiting for 127.0.0.1:8080"} [WARNING]: Failure using method (v2_runner_on_failed) in callback plugin (<ansible.plugins.callback./usr/share/ansible_plugins/callback_plugins/log_parse.CallbackModule object at 0x7fb3387f7b70>): 'dict' object has no attribute 'has_key' to retry, use: --limit @/tmp/tmpplaybook_unstableerp5-standalone.8941/erp5-standalone.retry From what I can tell, the error is because slapproxy refuses to start: root@erp:~# slapos node start slapproxy slapproxy: ERROR (no such process)
Re: Can't deploy erp5 by Unknown User at 2020/02/06 From: Unknown User From: Unknown User From: Thomas Gambier Hello, the script to deploy ERP5 on Debian 10 is now working fine but the problem is that the installation of slapos in your machine is broken (it still tries to install older software that will never work). The simplest is to reinstall the machine fully. Otherwise, you could do the following commands: `rm /tmp/playbook* rm -rf /tmp/tmpplaybook* rm /etc/cron.d/ansible* slapos node stop slapproxy rm /opt/slapos/slapproxy.db rm -rf /opt/slapgrid rm -rf /srv/slapgrid slapos node start slapproxy # then start the installation again wget https://deploy.erp5.net/erp5-standalone bash erp5-standalone` For information (especially for Yusei), the standalone installation scripts are installing both erp5 software release and apache-frontend software release (the backend and the frontend) so you don't need to install anything else. If your machine has a public IPv4, the apache-frontend will listen on this IPv4 so your ERP5 is directly accessible from outside. Also, for information, the slapos philosophy is to build everything from source, so you won't see anything installed through packages (except slapos and ansible and all their dependencies). All the softwares are installed under /opt/slapgrid and all the services are running inside partitions under /srv/slapgrid. I get the following errors for the following commands you gave me Thomas: root@erp:~# slapos node start slapproxy 2020-02-05 14:34:17 slapos[22608] INFO Launching supervisord with clean environment. 2020-02-05 14:34:17 slapos[22608] INFO Error: could not find config file /srv/slapgrid/etc/supervisord.conf 2020-02-05 14:34:17 slapos[22608] INFO For help, use -c -h 2020-02-05 14:34:17 slapos[22608] WARNING Supervisord unknown problem: 2020-02-05 14:34:17 slapos[22608] ERROR Failed to launch supervisord : Traceback (most recent call last): File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/entry.py", line 300, in run_subcommand result = cmd.run(parsed_args) File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/command.py", line 50, in run return self.take_action(parsed_args) File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/supervisorctl.py", line 87, in take_action super(SupervisorctlAliasCommand, self).take_action(args) File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/supervisorctl.py", line 73, in take_action forbid_supervisord_launch File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/cli/supervisorctl.py", line 79, in do_supervisorctl launchSupervisord(instance_root=instance_root, logger=logger) File "/opt/slapos/eggs/slapos.core-1.5.7-py2.7.egg/slapos/grid/svcbackend.py", line 196, in launchSupervisord raise RuntimeError('Failed to launch supervisord : %s' % result) RuntimeError: Failed to launch supervisord : root@erp:~# `bash erp5-standalone` ... gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now Redownloaded the script today and now its getting stuck at the "Waiting for Proxy" step of the ansible playbook: TASK [slapos-proxy : Wait for proxy] ******************************************** fatal: [127.0.0.1]: FAILED! => {"changed": false, "elapsed": 300, "msg": "Timeout when waiting for 127.0.0.1:8080"} [WARNING]: Failure using method (v2_runner_on_failed) in callback plugin (<ansible.plugins.callback./usr/share/ansible_plugins/callback_plugins/log_parse.CallbackModule object at 0x7fb3387f7b70>): 'dict' object has no attribute 'has_key' to retry, use: --limit @/tmp/tmpplaybook_unstableerp5-standalone.8941/erp5-standalone.retry From what I can tell, the error is because slapproxy refuses to start: root@erp:~# slapos node start slapproxy slapproxy: ERROR (no such process) Dug deeper and found out that slapproxy doesn't exist and even if I use Yusei Tahara's manual approach to generate the slapos standalone using root@erp:~# slapos configure local Which pretty much returned the same error as the script. I also tried reinstalling slapos-node manually then rerunning the script, only to get the same error. From what I can tell, it seems that the slapos program itself is now corrupted. I'll try rebooting to see if that changes anything. Otherwise, I'll leave you guys with those findings.
Re: Can't deploy erp5 by Thomas Gambier at 2020/02/07 Hello, sorry the instructions weren't complete. I just tested the following command lines: `rm /tmp/playbook* rm -rf /tmp/tmpplaybook* rm /etc/cron.d/ansible* slapos node stop slapproxy rm /opt/slapos/slapproxy.db rm -rf /opt/slapgrid rm -rf /srv/slapgrid rm -rf /etc/opt slapos configure local slapos node supervisorctl reread slapos node start slapproxy # then start the installation again wget https://deploy.erp5.net/erp5-standalone bash erp5-standalone` root@erp:~# `bash erp5-standalone` ... gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now Sorry for this error, we had a problem on one of our server yesterday preventing the installer to run correctly.