Closed DocCyblade closed 8 years ago
Built now. Will install and test early Sat.
VM Prepped and ready to run.
Thanks for putting this out!
Tests Proceeding well. Takes a long time to create a "demo database".. Seems longer than before perhaps.
Will wrap up soon (appointment now) but everything is working so far.
What is the specs on the VM how much vRAM and number of vCPUs?
I use 512mb plus 2 pricesaor as std test. Run 1 gb production.
Had to go to 2 gb for jobrunner but not part of current build. 512 should function.
Ideally the following commands should also work:
cd /opt/openerp /bin/bash openerp-server stop
It does work from /etc/init.d /bin/bash openerp-server stop
Is there a way to have the command also work from /opt/openerp ?
There is a file there called openerp-server (not seeing what it is just now)
It appears that each start and stop system needs to generally work in tandem with itself.
If I systemctl stop openerp-server.service then systemctl start openerp-server.service
System comes Up
If I (from anywhere it seems)
System comes up
However if I
System does not come up. I need to use /bin/bash openerp-server start
I don't actually see this to be a problem although if you want to apply some Extra Proceedures you do need to stop the system with /bin/bash openerp-server (commands)
Not finding verification of sending mail but I have not configured very much. I expect it is working find with an external server.
Would still love to know how to make postfix work for incoming and outgoing mail.
I think we are where we need to be with this however.
openerp-server is a python script and it is called by the init.d script. It needs to be called with Python and with command line options for the config file
If you look at the init.d script you can see this call
Also you should not need to do /bin/bash just ./
Ok, I will try some of that. It did seem in the past I could cycle up and down alternating methods. I don't think this matters right now however. Mainly curious.
I will browse a bit more.
Confirmed that email is sent to postfix.
Ok. Seems we can close this. Any other tests to run?
@l-arnold Just to chime in with a little more info re services. Ideally you should not be running openerp-server directly. If you ever do you should stop the service (daemon) first! Otherwise you will have multiple instances of openerp-server running trying to be the "primary" instance and conflicting with one another. Note that by default the openerp-server will spawn child processes and that's fine; but having multiple parent processes may cause weird random issues...
So for now (until the next major release of Debian at least) the following 3 commands are essentially the same! They all start the odoo 'service'!
/etc/initi.d/openerp-server start # original sysvinit style
service openerp-server start # newer sysvinit style (also worked for upstart; another init system)
systemctl start openerp-server.service # systemd style command
So if you want to use some other commandline options with Odoo (TBH I don't understand why you'd normally need to but that's another story...) then you should stop (service openerp-server stop
or similar) and then manually run odoo with /opt/openerp/openerp-server --option
(or whatever the correct path is and whatever options/switches you want to run...
Any errors or issues post a NEW issues
/etc/init.d/openerp-server
systemctl stop openerp-server.service
check the status of the service withsystemctl status openerp-server.service