Manual Update Process (need correct permission) about tkl-nomadic-odoo

[l-arnold]

Changing the owner of

/var/run points to /run
/run/openerp-server.pid did not work.

It does cause "stragglers" at startup however.
Reset back to "root:root"

[DocCyblade]

I'll comment on this later tonight. Don't have much time right at the moment

[l-arnold]

No prob. I'm wrestling w/ SSL. Will comment separately on that one. (so don't follow this one)

Can bring my SSL across pretty easily. Just made the mistake of trying to mod 12324 and won't mod back. (looking at how Apache nukes all this again)

[JedMeister]

Generally services should run as their own user; so I would assume "openerp"? Therefore pid/run files need to be owned by that particular user account...

[l-arnold]

I also thought that. My experience was that when I made the owner "openerp" it created the "Stragglers" which had been messing with the confconsole.txt presentation for so long.

Will look a bit at the code.

What I am really trying to do is run a "manual startup" that updates an "restored" data file from Odoo.

The command I was trying to run is:
/bin/bash openerp.init restart -d nomad -u all

(nomad) is the name of the database.
-d (I assume means use database)
-u (I assume means "update")
(all, would assume "all" parts of the database.

(was wanting to work but giving the same error no matter who owned the .pid file in the error message (a few messages up now)

Just wanting to be sure my data files are up to snuff w/ current git pulls. No errors and all migrated but "trust then verify".

[l-arnold]

Not sure this is critical for the TKL build. More of a "odoo" use question.

[DocCyblade]

@l-arnold I don't see openerp.init having those options. The code is just for starting and stopping the server. It in fact calls the openerp-server python script. Maybe these is another file your thinking of?

[l-arnold]

Likely the case. Goes back to "version 7".. difficult notes to decipher. I will ask in the OCA branches.
Pretty sure I needed to do this some time ago around the old Connector:

https://github.com/OCA/connector-magento

[JedMeister]

@l-arnold Ahh, now I understand what you mean by "stragglers" (TBH I was wondering...). So you mean the occasional lines of code that overwrite confconsole and/or the install screen?

They are completely irrelevant to anything that you are doing. Any changes are purely coincidental... At this point we don't have a fix. They are caused by SystemD (it's a synchronous boot/init system whereas the previous SysVinit was asynchronous). Please see turnkeylinux/tracker#338 & turnkeylinux/tracker#356

[l-arnold]

In terms of "fix" or not I don't think we actually have a "problem" per say. It is a course of inquiry. I have not had any problems with my 3 x test migrations so far.

Just wanting to cover bases with the question. I have seen issues in the past in the "OpenERP space" is all and was able to get fixed. Just need to find the "backdoor" just in case. If Odoo is doing it right, that "line of code" would be applied any time a Database is opened in Database Manager.

[l-arnold]

this is overlapping with issue: Do have a question posted with one OCA community leader and should have info back soon. (Will move to the following overlapping issue which also includes TKLBAM)
If an update command is desired it could also be integrated into a Odoo Specific TKLBAM script line.

#18

Closing for now.