Most Powerful Open Source ERP

Re: Can't deploy erp5

  • Last Update:2020-02-06
  • Version:001
  • Language:en
Document Reference
Re: Can't deploy erp5
Publication Information
Embedded
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

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.