New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Appliance: Odoo #374

Closed
l-arnold opened this Issue May 20, 2015 · 263 comments

Comments

Projects
None yet
3 participants
@l-arnold

l-arnold commented May 20, 2015

So far so good with Odoo. (not seeing how to label "new-appliance")

odoo appliance cropped

ISO Available (long build process)
Arranged the http/https routing so that General usage defaults to HTTPS and no ports needed to be called.
Overrode tendency for TKLDEV to use the main structure from LAPP.
Need to define a new TKLBAM Profile.
Would like to bring in more Addons by Default
Fantastic and easy Migration from other Odoo (manual built).
Seemed that LAPP updated just one file which I was removed anyway to build Apache/Odoo CONF structure properly..

Issues:

  • Would like the Main feed to TKLDEV to be a Package Pull for Odoo rather than Git Clone.
  • get some scraps in the console when I start it up, but when I choose "Advanced" then "Back" they go away.
  • ISO Size 1085 so larger than desired 1024 cylinders
  • Need to update to Adminer it seems from the threads.
  • SSL for Console 12325 dropped w/ hosted domain name
  • some lag at startup

https://github.com/l-arnold/tkl-nomadic-odoo.git

@JedMeister JedMeister added this to the 14.0 milestone May 21, 2015

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister May 21, 2015

Member

Great work! 😄

I've just had a very quick look through your code and it looks like it will want a bit of pruning, consolidation and tidying; but as a first full appliance build it is a very solid effort! 👍 Odoo doesn't appear to be a very easy appliance to build/configure so well done! 👏

My 2c re your points:

  • Would like the Main feed to TKLDEV to be a Package Pull for Odoo rather than Git Clone.

From my reading, using a git clone to install Odoo is actually better as it allows end users to update easier (if they so desire). Although perhaps might be useful to just clone the latest commit --depth=1 to reduce the size of the git tree downloaded. OTOH using the pre-build deb might be easier in some respects...

  • get some scraps in the console when I start it up, but when I choose "Advanced" then "Back" they go away.

This would be related to #356 and/or #338

  • ISO Size 1085 so larger than desired 1024 cylinders

Do you mean 1085MB? As in 1GB!? If so that's huge and I suspect pulling the whole git tree in is at least part of the problem...

  • Need to update to Adminer it seems from the threads.

Not very familiar with PgSQL so not too sure about this one...

  • SSL for Console 12325 dropped w/ hosted domain name

No idea about this (question below)

  • some lag at startup
    Not sure on this either...

Some questions at this stage are:

  • Why add Samba?
    • is that going to be relevant and useful for everyone?
    • or is it just handy and 'nice to have'? (if so I argue we should remove it)
  • Why still have Odoo available via port 8069? My understanding is that to configure it to proxy properly through Apache (so it's available on ports 80/443) that makes serving it on port 8069 both redundant and a potential security risk... (It's easily disabled by setting the Odoo config to listen only on localhost/127.0.0.1)
  • What is the 'console' you refer to? I assume that it is something directly relevant to Odoo? What does it do and what is it's value?
Member

JedMeister commented May 21, 2015

Great work! 😄

I've just had a very quick look through your code and it looks like it will want a bit of pruning, consolidation and tidying; but as a first full appliance build it is a very solid effort! 👍 Odoo doesn't appear to be a very easy appliance to build/configure so well done! 👏

My 2c re your points:

  • Would like the Main feed to TKLDEV to be a Package Pull for Odoo rather than Git Clone.

From my reading, using a git clone to install Odoo is actually better as it allows end users to update easier (if they so desire). Although perhaps might be useful to just clone the latest commit --depth=1 to reduce the size of the git tree downloaded. OTOH using the pre-build deb might be easier in some respects...

  • get some scraps in the console when I start it up, but when I choose "Advanced" then "Back" they go away.

This would be related to #356 and/or #338

  • ISO Size 1085 so larger than desired 1024 cylinders

Do you mean 1085MB? As in 1GB!? If so that's huge and I suspect pulling the whole git tree in is at least part of the problem...

  • Need to update to Adminer it seems from the threads.

Not very familiar with PgSQL so not too sure about this one...

  • SSL for Console 12325 dropped w/ hosted domain name

No idea about this (question below)

  • some lag at startup
    Not sure on this either...

Some questions at this stage are:

  • Why add Samba?
    • is that going to be relevant and useful for everyone?
    • or is it just handy and 'nice to have'? (if so I argue we should remove it)
  • Why still have Odoo available via port 8069? My understanding is that to configure it to proxy properly through Apache (so it's available on ports 80/443) that makes serving it on port 8069 both redundant and a potential security risk... (It's easily disabled by setting the Odoo config to listen only on localhost/127.0.0.1)
  • What is the 'console' you refer to? I assume that it is something directly relevant to Odoo? What does it do and what is it's value?

@JedMeister JedMeister added the todo label May 21, 2015

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 21, 2015

Agreed on most counts: (aside - some markdown buttons would be helpful here)

  • (Git Clone depth= 1) Good point: might be useful to just clone the latest commit --depth=1 " I could kill the Git after cloning it and would likely also shrink it down but I like --depth=1 path
  • Port 12325 Console is simply a repositioning and tweak of index.php that is in LAPP. I find it quite helpful for checking that all the interfaces are in fact up and running. Somewhat akin to having SSH and Webmin in the Servers console on TKL/Amazon hub. (not good to have it be the landing page for the whole IP though, thus the move. I do think something of the sort would be helpful for most apps.
  • Small Lag on startup I expect is related to the process of starting Odoo which is starting via scripts that I am not watching (I used to so I know it takes a little time) (not a big deal). I will say that increasing my RAM allocation to 512 then 1024 and giving a second processor jumped the speed considerably.
  • Samba. Working on a full answer. I don't know yet but it is there now, removal is easy and by default needs a login etc. Security and Overhead are the subjects to consider. Likely can be synched with the Odoo User Base and could provide then both a shared and personal storage space (though is more needed to synch or is it all in Samba? Extplorer is not loaded and though I considered did not want to wade into the LightTPD web that is serving it on the TKL FileServer app).
    In general I can see a advantage to it in terms of keeping PDF docs generated by Odoo attached to the server rather than every users personal datastore. Making that "default" will not be easy. My friend uses it with http://sourcetreeapp.com/ to have a graphical presentation of local Odoo (and other Git) projects. I need to learn about this.
    As a base Odoo install I am not sure Samba is needed. Certainly not critical). I will run some tests and research other practical applications more.
  • Odoo Port 8069 I have already updated the services.txt to say http://localhost:8069). Next I need to update the conf file to restrict in fact. Should be pretty easy.
  • Again, my "Web Console" is a reworked version of index.php in LAPP that adds an Odoo Link and could add others (for instance links to documentation etc). It couild run alternatively on 8080 instead of 12325 but seemed worth keeping in the TKL grid.

Back to it today. Import went really well from my Postgresql App build. Did a Backup of the Database. Then Restore to the New Server. Would like to test TKLBAM but not sure it will work as I modified LAPP pretty extensively.

When manually importing, backing up, issues with Web. Once 2 Databases are populated any Web Visitor is asked to choose the Database which totally breaks the idea of web hosting with Odoo. Should be easy, but will need an InitHook declaring that Database name. Also an opportunity for breakage.

Thinking about hooking into Webmin to get some easy Control over the Odoo Config files as well as Odoo Start Stop and Git and Addon functionality. Ideally wouild access ODOO Server from the Servers Dropdown in Webmin ideally. For now though this can be addressed from FileManager (Java) or SFTP. Probably not time just now, but perhaps this is easier than I think it will be.

l-arnold commented May 21, 2015

Agreed on most counts: (aside - some markdown buttons would be helpful here)

  • (Git Clone depth= 1) Good point: might be useful to just clone the latest commit --depth=1 " I could kill the Git after cloning it and would likely also shrink it down but I like --depth=1 path
  • Port 12325 Console is simply a repositioning and tweak of index.php that is in LAPP. I find it quite helpful for checking that all the interfaces are in fact up and running. Somewhat akin to having SSH and Webmin in the Servers console on TKL/Amazon hub. (not good to have it be the landing page for the whole IP though, thus the move. I do think something of the sort would be helpful for most apps.
  • Small Lag on startup I expect is related to the process of starting Odoo which is starting via scripts that I am not watching (I used to so I know it takes a little time) (not a big deal). I will say that increasing my RAM allocation to 512 then 1024 and giving a second processor jumped the speed considerably.
  • Samba. Working on a full answer. I don't know yet but it is there now, removal is easy and by default needs a login etc. Security and Overhead are the subjects to consider. Likely can be synched with the Odoo User Base and could provide then both a shared and personal storage space (though is more needed to synch or is it all in Samba? Extplorer is not loaded and though I considered did not want to wade into the LightTPD web that is serving it on the TKL FileServer app).
    In general I can see a advantage to it in terms of keeping PDF docs generated by Odoo attached to the server rather than every users personal datastore. Making that "default" will not be easy. My friend uses it with http://sourcetreeapp.com/ to have a graphical presentation of local Odoo (and other Git) projects. I need to learn about this.
    As a base Odoo install I am not sure Samba is needed. Certainly not critical). I will run some tests and research other practical applications more.
  • Odoo Port 8069 I have already updated the services.txt to say http://localhost:8069). Next I need to update the conf file to restrict in fact. Should be pretty easy.
  • Again, my "Web Console" is a reworked version of index.php in LAPP that adds an Odoo Link and could add others (for instance links to documentation etc). It couild run alternatively on 8080 instead of 12325 but seemed worth keeping in the TKL grid.

Back to it today. Import went really well from my Postgresql App build. Did a Backup of the Database. Then Restore to the New Server. Would like to test TKLBAM but not sure it will work as I modified LAPP pretty extensively.

When manually importing, backing up, issues with Web. Once 2 Databases are populated any Web Visitor is asked to choose the Database which totally breaks the idea of web hosting with Odoo. Should be easy, but will need an InitHook declaring that Database name. Also an opportunity for breakage.

Thinking about hooking into Webmin to get some easy Control over the Odoo Config files as well as Odoo Start Stop and Git and Addon functionality. Ideally wouild access ODOO Server from the Servers Dropdown in Webmin ideally. For now though this can be addressed from FileManager (Java) or SFTP. Probably not time just now, but perhaps this is easier than I think it will be.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 21, 2015

On Test system edited Odoo Config files (ie openerp-server.conf) with the following and it blocked 8069 in http mode. Will add to the app and test on next go round.

(had no values before)

xmlrpc_interface = 127.0.0.1
netrpc_interface = 127.0.0.1

l-arnold commented May 21, 2015

On Test system edited Odoo Config files (ie openerp-server.conf) with the following and it blocked 8069 in http mode. Will add to the app and test on next go round.

(had no values before)

xmlrpc_interface = 127.0.0.1
netrpc_interface = 127.0.0.1

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 22, 2015

Excellent,
Git Clone ... --depth=1 cut the size in half (and I didn't apply to a few small gits included). Seems to have sped the build time considerably as well.

In /opt/openerp/odoo/openerp-server.conf
I have disabled port 8069 to the outside (did not work if also done in "openerp-server-man.conf in same folder, but as noted below may have been something overall system related instead)

I anticipate this will cause problems for people trying to install their SSL Certs so need to give simple guidance for opening (it is rather easy)

A small script would be ideal.
Webshell (12320) did not work on first load and now that I have rebooted, perhaps the "openerp-server-man.conf" statement above was caused by something systematic instead.

l-arnold commented May 22, 2015

Excellent,
Git Clone ... --depth=1 cut the size in half (and I didn't apply to a few small gits included). Seems to have sped the build time considerably as well.

In /opt/openerp/odoo/openerp-server.conf
I have disabled port 8069 to the outside (did not work if also done in "openerp-server-man.conf in same folder, but as noted below may have been something overall system related instead)

I anticipate this will cause problems for people trying to install their SSL Certs so need to give simple guidance for opening (it is rather easy)

A small script would be ideal.
Webshell (12320) did not work on first load and now that I have rebooted, perhaps the "openerp-server-man.conf" statement above was caused by something systematic instead.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 22, 2015

Confirm (the openerp-server-man.conf) above did not cause the system not to operate.

The changes in openerp-server.conf (and openerp-server-man.conf which may not be required) do block 8069 from being accessible from other machines including on the same network. SSL is working through Proxy, so as designed.

Basically taking 2 Reboots for a complete system to come up.

Once before InitHooks
Once after InitHooks
Seemingly a Third Reboot then all systems are working.
This is after a new MAKE today. I do not recall this problem earlier, though it could explain one or two seeming SSL Issues. Today had a variety of issues.
Webmin in Chrome came up after system showing at install reboots.
Webshell and Oddo Came up after 2 boots (ie. one more than design)
IE Explorer 8 Webmin and others only came up after 2 boots. (also one more than design)

Should probably script this if it is ongoing. May be an issue with Openerp/Odoo Server needing to restart which also could be scripted.

l-arnold commented May 22, 2015

Confirm (the openerp-server-man.conf) above did not cause the system not to operate.

The changes in openerp-server.conf (and openerp-server-man.conf which may not be required) do block 8069 from being accessible from other machines including on the same network. SSL is working through Proxy, so as designed.

Basically taking 2 Reboots for a complete system to come up.

Once before InitHooks
Once after InitHooks
Seemingly a Third Reboot then all systems are working.
This is after a new MAKE today. I do not recall this problem earlier, though it could explain one or two seeming SSL Issues. Today had a variety of issues.
Webmin in Chrome came up after system showing at install reboots.
Webshell and Oddo Came up after 2 boots (ie. one more than design)
IE Explorer 8 Webmin and others only came up after 2 boots. (also one more than design)

Should probably script this if it is ongoing. May be an issue with Openerp/Odoo Server needing to restart which also could be scripted.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 22, 2015

(FIXED in Comment Below) Found in http://www.askapache.com/htaccess/mod_rewrite-variables-cheatsheet.html#SERVER_ADDR

quest was

My reworked index.php (aka web console) is causing problems.
Standard build is to use HTTP_HOST but this is problematic when the Host Starts with a Port Number.

For Instance the standard index.php in LAPP:
$_SERVER{'HTTP_HOST'}; ?>:12321"><img
will give me (when hosted on port 12325) www.website.com:12325:12321

SERVER_ADDR works if there is no Firewall or IP Alteration involved which there is if hosted behind a firewall generally even though ports are less problematic.

$ipaddr Likewise gives the same problem as SERVER_ADDR

What is Needed is a Variable for HTTP_HOST_NOPORT
then my alterations would work.

SERVER_ADDR does work for testing inside a private network but not when public.
Likely could be buried for now.

I have tried HOSTNAME but it gets tangled between TKL Hostname and Odoo Hostname. Needs to be the TKL Hostname which would be specified in an inithook. It resolves however, to Odoo's hostname somehow, even going through Apache and not landing on the Odoo Website (at index.php)

l-arnold commented May 22, 2015

(FIXED in Comment Below) Found in http://www.askapache.com/htaccess/mod_rewrite-variables-cheatsheet.html#SERVER_ADDR

quest was

My reworked index.php (aka web console) is causing problems.
Standard build is to use HTTP_HOST but this is problematic when the Host Starts with a Port Number.

For Instance the standard index.php in LAPP:
$_SERVER{'HTTP_HOST'}; ?>:12321"><img
will give me (when hosted on port 12325) www.website.com:12325:12321

SERVER_ADDR works if there is no Firewall or IP Alteration involved which there is if hosted behind a firewall generally even though ports are less problematic.

$ipaddr Likewise gives the same problem as SERVER_ADDR

What is Needed is a Variable for HTTP_HOST_NOPORT
then my alterations would work.

SERVER_ADDR does work for testing inside a private network but not when public.
Likely could be buried for now.

I have tried HOSTNAME but it gets tangled between TKL Hostname and Odoo Hostname. Needs to be the TKL Hostname which would be specified in an inithook. It resolves however, to Odoo's hostname somehow, even going through Apache and not landing on the Odoo Website (at index.php)

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 22, 2015

use SERVER_NAME to fix all issues in index.php.

I recommend this being standard Naming for all Index.php Consoles. Updating next.

l-arnold commented May 22, 2015

use SERVER_NAME to fix all issues in index.php.

I recommend this being standard Naming for all Index.php Consoles. Updating next.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 22, 2015

Will move issues to the Root App from here out unless comments come in here. Will post a SourceForge Iso shortly as well.

l-arnold commented May 22, 2015

Will move issues to the Root App from here out unless comments come in here. Will post a SourceForge Iso shortly as well.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 27, 2015

Working ISO is here and it looks like not posted since my last comment.
https://sourceforge.net/projects/tklnomadicodoo/

l-arnold commented May 27, 2015

Working ISO is here and it looks like not posted since my last comment.
https://sourceforge.net/projects/tklnomadicodoo/

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 28, 2015

Working through the wkhtmltopdf issue again. Made it work in my original build and Jeremy referenced the same in forums, but it seems my Config File wants it to be somewhere it aint.

l-arnold commented May 28, 2015

Working through the wkhtmltopdf issue again. Made it work in my original build and Jeremy referenced the same in forums, but it seems my Config File wants it to be somewhere it aint.

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister May 29, 2015

Member

Perhaps a new enough version of wkhtmltopdf may be in Jessie?

Member

JedMeister commented May 29, 2015

Perhaps a new enough version of wkhtmltopdf may be in Jessie?

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 29, 2015

Got it working. Fonts are not as clean as in Wheezy... Working on that but might just be my eyes. Bottom line is it works and we are going away from paper. The "Portal Option" is really nice. Had a customer today login and confirm an order. Yesterday sent a nice clean "mass mailing" that also worked very well. Its a big system and lots to setup for sure but that should be done by the user generally. The wkhtmltopdf and base line addons do need to work and are as far as I can see. That was the only error I had so far.

l-arnold commented May 29, 2015

Got it working. Fonts are not as clean as in Wheezy... Working on that but might just be my eyes. Bottom line is it works and we are going away from paper. The "Portal Option" is really nice. Had a customer today login and confirm an order. Yesterday sent a nice clean "mass mailing" that also worked very well. Its a big system and lots to setup for sure but that should be done by the user generally. The wkhtmltopdf and base line addons do need to work and are as far as I can see. That was the only error I had so far.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 29, 2015

Outside of Git this gets HTML to PDF in Odoo going for Jessie

apt-get install xfonts-base
apt-get install xfonts-100dpi
wget http://downloads.sourceforge.net/wkhtmltopdf/wkhtmltox-0.12.2.1_linux-jessie-amd64.deb -i --force-depends wkhtmltox-*.deb

dpkg -i wkhtmltox-0.12.2.1_linux-jessie-amd64.deb

apt-get -y -f install

cp /usr/local/bin/wkhtmltopdf /usr/bin
cp /usr/local/bin/wkhtmltoimage /usr/bin

l-arnold commented May 29, 2015

Outside of Git this gets HTML to PDF in Odoo going for Jessie

apt-get install xfonts-base
apt-get install xfonts-100dpi
wget http://downloads.sourceforge.net/wkhtmltopdf/wkhtmltox-0.12.2.1_linux-jessie-amd64.deb -i --force-depends wkhtmltox-*.deb

dpkg -i wkhtmltox-0.12.2.1_linux-jessie-amd64.deb

apt-get -y -f install

cp /usr/local/bin/wkhtmltopdf /usr/bin
cp /usr/local/bin/wkhtmltoimage /usr/bin

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 29, 2015

To be clear. The Jessie version does not work. I had installed it with the ap. Some unclear comments to the same effect out there.

l-arnold commented May 29, 2015

To be clear. The Jessie version does not work. I had installed it with the ap. Some unclear comments to the same effect out there.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 29, 2015

Running with the Above... This is Odoo reference to the issue:

ref: https://www.odoo.com/documentation/8.0/setup/install.html#deb

#Deb
To install Odoo 8.0 on Debian-based distribution, execute the following commands as root:

wget -O - https://nightly.odoo.com/odoo.key | apt-key add -
echo "deb http://nightly.odoo.com/8.0/nightly/deb/ ./" >> /etc/apt/sources.list
apt-get update && apt-get install odoo
This will automatically install all dependencies, install Odoo itself as a daemon and automatically start it.

Danger
to print PDF reports, you must install wkhtmltopdf yourself: the version of wkhtmltopdf available in debian repositories does not support headers and footers so it can not be installed automatically. The recommended version is 0.12.1 and is available on the wkhtmltopdf download page, in the archive section. As there is no official release for Debian Jessie, you can find ours on http://nightly.odoo.com/extra/.

l-arnold commented May 29, 2015

Running with the Above... This is Odoo reference to the issue:

ref: https://www.odoo.com/documentation/8.0/setup/install.html#deb

#Deb
To install Odoo 8.0 on Debian-based distribution, execute the following commands as root:

wget -O - https://nightly.odoo.com/odoo.key | apt-key add -
echo "deb http://nightly.odoo.com/8.0/nightly/deb/ ./" >> /etc/apt/sources.list
apt-get update && apt-get install odoo
This will automatically install all dependencies, install Odoo itself as a daemon and automatically start it.

Danger
to print PDF reports, you must install wkhtmltopdf yourself: the version of wkhtmltopdf available in debian repositories does not support headers and footers so it can not be installed automatically. The recommended version is 0.12.1 and is available on the wkhtmltopdf download page, in the archive section. As there is no official release for Debian Jessie, you can find ours on http://nightly.odoo.com/extra/.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 29, 2015

I am downloading fine, but Not able to install in TKLDEV.

It looks like one should not use a second "apt-get install" command in TKLDEV. Trying that now....
Looks like we are passed the error point. Now just to see if the package is there and PDF functionalitiies (ie doing anything with a customer) work.

My closing error below.
Critcial that folks (like me) understand the small details of moving into TKLDEV.
Would be nice if the parallelism of simple "apt-gets" and "wgets" were explained around TKLDEV. For instance some wgets give you .gz's while others give you .debs... If not in the main package tree, like this one, how to handle? (read further for answer here anyway)

Did so by Removing the apt-get install -f) line you can see with a = below. It already built with the dpkg code. (prior had to be sure xfonts-75dpi and xfonts-base were installed in the main package calls. Then the wkhtmltox built.


  • Bitvise xterm - 192.168.1.123:22
    Saving to: ' wkhtmltox-0.12.2.l_linux-jessie-amd64.deb'
    wkhtmltox-0.12.2.1_ 100x[=====================>] 13.89M 2.25MB/S in 7.0s
    2015-05-29 15:00:40 <1.98 MB/s) - 'wkhtmltox-0.12.2-l_linux-jessie-amd64.deb' sa
    ved [14570310/14570310]
  • dpkg -i wkhtmltox-0.12.2.l_linux-jessie-amd64.deb
    Selecting previously unselected package wkhtmltox.
    (Reading database ... 33426 files and directories currently installed.)
    Preparing to unpack wkhtmltox-0.12.2.l_linux-jessie-amd64.deb ...
    Unpacking wkhtmltox <0.12.2.1) ...
    Setting up wkhtmltox <0.12.2.1) ...
    Processing triggers for man-db <2.7.0.2-5) ...
  • apt-get -y -f install wkhtmltox-0.12.2.l_linux-jessie-amd64.deb
    Beading package lists... Done
    Building dependency tree
    Beading state information... Done
    E: Unable to locate package wkhtmltox-0.12.2.l_linux-jessie-amd64.deb
    E: Couldn't find any package by regex ' wkhtmltox-0.12.2-l_linux-jessie-amd64.deb
    I
    /usr/share/fab/product.mk:476: recipe for target 'build/stamps/root.patched' fai
    led
    make: [build/stamps/root .patched] Error 100
    rootOtkl-odoo #

l-arnold commented May 29, 2015

I am downloading fine, but Not able to install in TKLDEV.

It looks like one should not use a second "apt-get install" command in TKLDEV. Trying that now....
Looks like we are passed the error point. Now just to see if the package is there and PDF functionalitiies (ie doing anything with a customer) work.

My closing error below.
Critcial that folks (like me) understand the small details of moving into TKLDEV.
Would be nice if the parallelism of simple "apt-gets" and "wgets" were explained around TKLDEV. For instance some wgets give you .gz's while others give you .debs... If not in the main package tree, like this one, how to handle? (read further for answer here anyway)

Did so by Removing the apt-get install -f) line you can see with a = below. It already built with the dpkg code. (prior had to be sure xfonts-75dpi and xfonts-base were installed in the main package calls. Then the wkhtmltox built.


  • Bitvise xterm - 192.168.1.123:22
    Saving to: ' wkhtmltox-0.12.2.l_linux-jessie-amd64.deb'
    wkhtmltox-0.12.2.1_ 100x[=====================>] 13.89M 2.25MB/S in 7.0s
    2015-05-29 15:00:40 <1.98 MB/s) - 'wkhtmltox-0.12.2-l_linux-jessie-amd64.deb' sa
    ved [14570310/14570310]
  • dpkg -i wkhtmltox-0.12.2.l_linux-jessie-amd64.deb
    Selecting previously unselected package wkhtmltox.
    (Reading database ... 33426 files and directories currently installed.)
    Preparing to unpack wkhtmltox-0.12.2.l_linux-jessie-amd64.deb ...
    Unpacking wkhtmltox <0.12.2.1) ...
    Setting up wkhtmltox <0.12.2.1) ...
    Processing triggers for man-db <2.7.0.2-5) ...
  • apt-get -y -f install wkhtmltox-0.12.2.l_linux-jessie-amd64.deb
    Beading package lists... Done
    Building dependency tree
    Beading state information... Done
    E: Unable to locate package wkhtmltox-0.12.2.l_linux-jessie-amd64.deb
    E: Couldn't find any package by regex ' wkhtmltox-0.12.2-l_linux-jessie-amd64.deb
    I
    /usr/share/fab/product.mk:476: recipe for target 'build/stamps/root.patched' fai
    led
    make: [build/stamps/root .patched] Error 100
    rootOtkl-odoo #
@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold May 29, 2015

ODOO Rc2 Builds well. WKHTMLTOX loads. Updated Inside and outside consoles. Likely should drop the overt instructions on both.

RC2 ISO at: https://sourceforge.net/projects/tklnomadicodoo/
GIT at: https://github.com/l-arnold/tkl-nomadic-odoo

Still having an issue with Manual Boot required during InitHooks.
Still having an issue with "stragglers" showing up after Services.txt Console Arises

http - port 12325
screenclip

clean services console (will change "8069 must" to "8069 can" in text section)
screenclip

boot services console - must choose A (Advanced) then Back to clean
screenclip

l-arnold commented May 29, 2015

ODOO Rc2 Builds well. WKHTMLTOX loads. Updated Inside and outside consoles. Likely should drop the overt instructions on both.

RC2 ISO at: https://sourceforge.net/projects/tklnomadicodoo/
GIT at: https://github.com/l-arnold/tkl-nomadic-odoo

Still having an issue with Manual Boot required during InitHooks.
Still having an issue with "stragglers" showing up after Services.txt Console Arises

http - port 12325
screenclip

clean services console (will change "8069 must" to "8069 can" in text section)
screenclip

boot services console - must choose A (Advanced) then Back to clean
screenclip

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister May 31, 2015

Member

Sounds like you are having good progress overall! 👍

Still having an issue with Manual Boot required during InitHooks.
Still having an issue with "stragglers" showing up after Services.txt Console Arises

These issues won't probably be fixed any time soon. However we will certainly look to fix them prior to the final release.

Member

JedMeister commented May 31, 2015

Sounds like you are having good progress overall! 👍

Still having an issue with Manual Boot required during InitHooks.
Still having an issue with "stragglers" showing up after Services.txt Console Arises

These issues won't probably be fixed any time soon. However we will certainly look to fix them prior to the final release.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Jun 4, 2015

Big Step: I have integrated both Odoo as well as the Connector for Magento (it can be chosen in the APPs dialog). Quite a difficult install and just coming out now for version 8.

I have a branch set without the Connector but don't see the ISO getting much bigger in the process. A few more packages were installed (doc on the forum).
ISO is: Tkl-Nomadic-Connect-v9.iso
https://sourceforge.net/projects/tklnomadicodoo/

https://github.com/l-arnold/tkl-nomadic-odoo

On other notes:
Stragglers seem to be gone (at least last install). Seems an issue of RAM. Possibly processors given. The less of both the more visuals.

Would like to do more documentation but there is a world of it out there. Will work on more specifics in Readme and related. Did a call to docs in Odoo but ownership issues are difficult. Would be better to run those docs through Odoo once I find out how.

l-arnold commented Jun 4, 2015

Big Step: I have integrated both Odoo as well as the Connector for Magento (it can be chosen in the APPs dialog). Quite a difficult install and just coming out now for version 8.

I have a branch set without the Connector but don't see the ISO getting much bigger in the process. A few more packages were installed (doc on the forum).
ISO is: Tkl-Nomadic-Connect-v9.iso
https://sourceforge.net/projects/tklnomadicodoo/

https://github.com/l-arnold/tkl-nomadic-odoo

On other notes:
Stragglers seem to be gone (at least last install). Seems an issue of RAM. Possibly processors given. The less of both the more visuals.

Would like to do more documentation but there is a world of it out there. Will work on more specifics in Readme and related. Did a call to docs in Odoo but ownership issues are difficult. Would be better to run those docs through Odoo once I find out how.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Jun 5, 2015

New ISO Posted to Sourceforge. Very happy with it.

https://sourceforge.net/projects/tklnomadicodoo/files/?source=navbar

Sometimes the smallest details cause the greatest pain. I have Dropped in what seem to be the most important OCA/Addons and made them available at install.

Ports all working (and ported in this config) and Getting a hot Documentations link.
Need to run "make clean && make" to get a successful build. Takes a bit.

In this last build no Stragglers either at end of build or at subsequent reboot.

Everything loaded.

As far as I see now I would like next to parse my desired Password InitHook Protocol. Spent the better part of a day on it this week and set it aside.

In the future I would love to do do small Edits in the ISO image and backposting them to speed the process. (Assume I could do that if I delete a few files and run make again, but didn't work well w/ my ports) That said, I can't see anything but a small alignment issue on index.php of the Webconsole. Would like more and fancier documentation but running the system is the goal.

l-arnold commented Jun 5, 2015

New ISO Posted to Sourceforge. Very happy with it.

https://sourceforge.net/projects/tklnomadicodoo/files/?source=navbar

Sometimes the smallest details cause the greatest pain. I have Dropped in what seem to be the most important OCA/Addons and made them available at install.

Ports all working (and ported in this config) and Getting a hot Documentations link.
Need to run "make clean && make" to get a successful build. Takes a bit.

In this last build no Stragglers either at end of build or at subsequent reboot.

Everything loaded.

As far as I see now I would like next to parse my desired Password InitHook Protocol. Spent the better part of a day on it this week and set it aside.

In the future I would love to do do small Edits in the ISO image and backposting them to speed the process. (Assume I could do that if I delete a few files and run make again, but didn't work well w/ my ports) That said, I can't see anything but a small alignment issue on index.php of the Webconsole. Would like more and fancier documentation but running the system is the goal.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Jun 5, 2015

One Link didn't move in last build. If using 3.5 ISO, open /var/www/index.php

ISO 3.5 (post install mini fix).
In /var/www/index.php
Under Reference and Resources section:
change the two "webconsole call" to use port 12324 and https with this code:

                     <li>
                     <a href="http://<?php print
                    $_SERVER{'SERVER_NAME'}; ?>:12325">
                      WebConsole (here) HTTP 12325 </a> 
                      <li>(Open HTTP if SSL Configuration Needed)
                    </li>
                    <li><a href="https://<?php print
                    $_SERVER{'SERVER_NAME'}; ?>:12324">WebConsole (here) HTTPS 12324 </a> 
                    <li>(Consistent with 12320, 12321, 12322 in default build) 
                    </li>

l-arnold commented Jun 5, 2015

One Link didn't move in last build. If using 3.5 ISO, open /var/www/index.php

ISO 3.5 (post install mini fix).
In /var/www/index.php
Under Reference and Resources section:
change the two "webconsole call" to use port 12324 and https with this code:

                     <li>
                     <a href="http://<?php print
                    $_SERVER{'SERVER_NAME'}; ?>:12325">
                      WebConsole (here) HTTP 12325 </a> 
                      <li>(Open HTTP if SSL Configuration Needed)
                    </li>
                    <li><a href="https://<?php print
                    $_SERVER{'SERVER_NAME'}; ?>:12324">WebConsole (here) HTTPS 12324 </a> 
                    <li>(Consistent with 12320, 12321, 12322 in default build) 
                    </li>
@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Jun 5, 2015

RC 3.6 built and working well. Fix Taken. Would love any comments. Best either on GitHub or Sourceforge I suppose (though here works).

I have worked hard on he "Web Console" concept and I really see that it can be practical in other builds as well. Folks can test basic Interface off my website at:
http www nomadic net 12325
https www nomadic net 12324

Had a real quick migration of data and SSL cert without TKLBAM just now. Tklbam backsup in webmin. Not really able to throw it up to the hub as a server which would be nice. Anyway other things to do.

l-arnold commented Jun 5, 2015

RC 3.6 built and working well. Fix Taken. Would love any comments. Best either on GitHub or Sourceforge I suppose (though here works).

I have worked hard on he "Web Console" concept and I really see that it can be practical in other builds as well. Folks can test basic Interface off my website at:
http www nomadic net 12325
https www nomadic net 12324

Had a real quick migration of data and SSL cert without TKLBAM just now. Tklbam backsup in webmin. Not really able to throw it up to the hub as a server which would be nice. Anyway other things to do.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Jun 5, 2015

Would love some help on inithooks

I need to declare the openerp user for postgresql (openuser) but give it a non-default password and also set that password to the openerp.server.conf

I can do one, it seems, via a (setpass.py).py file that is loaded from core.
I can do the other, I think, from a custom.py file that I can make.

I need to know how to do both at the same time.

I don't understand the standard (setpass.py) internal_to_core.py that is called by inithooks. Will dig into my git deletes to find the detail.

Pretty critical as adminer can loginto the whole database setup if this is not re-set right away.

Strikes me that I will study common/inithooks then try some changes in a a Test-Built Install before I go try to apply to my app.

l-arnold commented Jun 5, 2015

Would love some help on inithooks

I need to declare the openerp user for postgresql (openuser) but give it a non-default password and also set that password to the openerp.server.conf

I can do one, it seems, via a (setpass.py).py file that is loaded from core.
I can do the other, I think, from a custom.py file that I can make.

I need to know how to do both at the same time.

I don't understand the standard (setpass.py) internal_to_core.py that is called by inithooks. Will dig into my git deletes to find the detail.

Pretty critical as adminer can loginto the whole database setup if this is not re-set right away.

Strikes me that I will study common/inithooks then try some changes in a a Test-Built Install before I go try to apply to my app.

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister Jun 7, 2015

Member

The init hook that sets the default odoo db password (the one that the application uses to access it's own DB; and needs to go in the config file) should be easy. You could just rob (and tweak) the one from the Mahara appliance (also has a LAPP backend).

The one for the actual odoo admin account might be trickier although IIRC there is a commandline way to do it; which you could write an inithook to do...

Member

JedMeister commented Jun 7, 2015

The init hook that sets the default odoo db password (the one that the application uses to access it's own DB; and needs to go in the config file) should be easy. You could just rob (and tweak) the one from the Mahara appliance (also has a LAPP backend).

The one for the actual odoo admin account might be trickier although IIRC there is a commandline way to do it; which you could write an inithook to do...

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Jun 25, 2015

Working on the inithook. Didn't hook. Didn't crash either so will keep at it.
compared Tendenci and Maharaj and saw diff approaches. The passwords should be easy. I think zip have the Sedan part but a bit scared of the hash process.

Getting a window to work on this again. Will likely drop Samba,

l-arnold commented Jun 25, 2015

Working on the inithook. Didn't hook. Didn't crash either so will keep at it.
compared Tendenci and Maharaj and saw diff approaches. The passwords should be easy. I think zip have the Sedan part but a bit scared of the hash process.

Getting a window to work on this again. Will likely drop Samba,

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister Jun 25, 2015

Member

Regarding consulting Mahara, the inithook I was referring to above was the one to connect Odoo to it's DB backend. The bash script that Mahara uses (here) leverages the postgresql python inithook to set the Mahara PostgreSQL user and password.

As for the admin user setup; using their commandline app (assuming I recall correctly) to update the admin user's password might be the easiest option? Zurmo does that, see here; actually it's lines 66 & 67 that do the interaction with the commandline app. Note that the admin inithook also needs a bash script to complement it (like this one in Zurmo).

Inithooks require both a firstboot.d bash script and a (usually python) bin script. For setting up the Odoo DB you can just write the bash bit (and use the existing pgsqlconf.py to do the heavy lifting). For the other parts of the app (usually admin password, perhaps also email and setting domain if (and only if) it needs it) you'll need both bash and (probably) python scripts.

Member

JedMeister commented Jun 25, 2015

Regarding consulting Mahara, the inithook I was referring to above was the one to connect Odoo to it's DB backend. The bash script that Mahara uses (here) leverages the postgresql python inithook to set the Mahara PostgreSQL user and password.

As for the admin user setup; using their commandline app (assuming I recall correctly) to update the admin user's password might be the easiest option? Zurmo does that, see here; actually it's lines 66 & 67 that do the interaction with the commandline app. Note that the admin inithook also needs a bash script to complement it (like this one in Zurmo).

Inithooks require both a firstboot.d bash script and a (usually python) bin script. For setting up the Odoo DB you can just write the bash bit (and use the existing pgsqlconf.py to do the heavy lifting). For the other parts of the app (usually admin password, perhaps also email and setting domain if (and only if) it needs it) you'll need both bash and (probably) python scripts.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Jun 25, 2015

Thank you Jeremy.
I've got a river trip for a few days first in AM so back soon to the project.
What i want to do is

Define a Odoo Admin DB Password (not really a postgres thing, something just that allows Odoo Backups etc. Seems quite "out in the open". Will use SED into openerp-server.conf to set it and as long as no one can read the config file all set.

Give a Postgresql User and PW to "openuser" - working now but w/ default password.
When given/changed in Postgresql, either need to "not call the PW" in the openerp-server.conf (calls it now) or will change it both in PostgreSQL DB and in the openerp-server.conf file. I really don't see the need for having a visible openuser (pw) but need to be sure the user can be called by root. Seems changing the PW in Webmin should suffice after "first set", just don't want a "default pw" set. So calling the pgsqlconf.py will likely do the trick there.

This part is critical to everyday running.
Admin PW above just follows openerp-server.conf setting so whatever is called there is what needs to be entered to do the Data backups etc on the "front end".

I had been trying 2 bin files and 1 py file in Inithooks/firstboot.d.
Anyway, need to sort this out. Tuesday next. Back soon.

System otherwise is working great. Would like some balance between full Branch w/ git and --depth=1 on the git. Swings 750mb in the balance.

l-arnold commented Jun 25, 2015

Thank you Jeremy.
I've got a river trip for a few days first in AM so back soon to the project.
What i want to do is

Define a Odoo Admin DB Password (not really a postgres thing, something just that allows Odoo Backups etc. Seems quite "out in the open". Will use SED into openerp-server.conf to set it and as long as no one can read the config file all set.

Give a Postgresql User and PW to "openuser" - working now but w/ default password.
When given/changed in Postgresql, either need to "not call the PW" in the openerp-server.conf (calls it now) or will change it both in PostgreSQL DB and in the openerp-server.conf file. I really don't see the need for having a visible openuser (pw) but need to be sure the user can be called by root. Seems changing the PW in Webmin should suffice after "first set", just don't want a "default pw" set. So calling the pgsqlconf.py will likely do the trick there.

This part is critical to everyday running.
Admin PW above just follows openerp-server.conf setting so whatever is called there is what needs to be entered to do the Data backups etc on the "front end".

I had been trying 2 bin files and 1 py file in Inithooks/firstboot.d.
Anyway, need to sort this out. Tuesday next. Back soon.

System otherwise is working great. Would like some balance between full Branch w/ git and --depth=1 on the git. Swings 750mb in the balance.

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister Sep 2, 2015

Member

@DocCyblade - thanks for that... TKLDev uses systemd too so not sure there... I'll have a look a little later.

Member

JedMeister commented Sep 2, 2015

@DocCyblade - thanks for that... TKLDev uses systemd too so not sure there... I'll have a look a little later.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

Observations.
New Common Build (just dev-wip1 still ) second build w/ (kens-dev-wip1 building now too for separate test)

1: Black Box over the Root Password Entry #1 "Stopped Postgres Cluster 9.4 Main" (as earlier)
2 Admin Password (requires 6 charachters. Did not start with # this time - lets see if it writes)
3: Webmin and Webshell both work and take root password (very slow log in to IE Filemanager)
4: Apache starts w/ no Reboot
5: db_password set in (openerp-server.conf) to mcookie db_password = (yadayada)
6: openerp-server.conf admin_passwd= (set properly, but did not use any charachters first round)

7: Postgresql Actually not running at end of FirstBoot
Once Started in Webmin
8: Can't Log in to Postgres user in Adminer w/ password given at firstboot
9: Can log in to OpenUser user in Adminer w/ password written to openerp-server.conf

10: Odoo does not start at first boot: Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.

11: Stragglers on Second Boot to ConfConsole
12: Odoo Starts (quite slowly at first) on Second Boot.

l-arnold commented Sep 2, 2015

Observations.
New Common Build (just dev-wip1 still ) second build w/ (kens-dev-wip1 building now too for separate test)

1: Black Box over the Root Password Entry #1 "Stopped Postgres Cluster 9.4 Main" (as earlier)
2 Admin Password (requires 6 charachters. Did not start with # this time - lets see if it writes)
3: Webmin and Webshell both work and take root password (very slow log in to IE Filemanager)
4: Apache starts w/ no Reboot
5: db_password set in (openerp-server.conf) to mcookie db_password = (yadayada)
6: openerp-server.conf admin_passwd= (set properly, but did not use any charachters first round)

7: Postgresql Actually not running at end of FirstBoot
Once Started in Webmin
8: Can't Log in to Postgres user in Adminer w/ password given at firstboot
9: Can log in to OpenUser user in Adminer w/ password written to openerp-server.conf

10: Odoo does not start at first boot: Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.

11: Stragglers on Second Boot to ConfConsole
12: Odoo Starts (quite slowly at first) on Second Boot.

@DocCyblade

This comment has been minimized.

Show comment
Hide comment
@DocCyblade

DocCyblade Sep 2, 2015

Member

I am seeing everything you just outlined!

Items 7-10 are probably related to the pgsql Python script error.

we may need to hold off until this bug Is removed. We could temporary statically set the database user by removing the init hook for the database since this is set during build

Also I was reading that you can change the admin password inside odoo it's self is this true? If this is true we could keep it as admin and document how to change it. But I think that script is working pretty well.

Member

DocCyblade commented Sep 2, 2015

I am seeing everything you just outlined!

Items 7-10 are probably related to the pgsql Python script error.

we may need to hold off until this bug Is removed. We could temporary statically set the database user by removing the init hook for the database since this is set during build

Also I was reading that you can change the admin password inside odoo it's self is this true? If this is true we could keep it as admin and document how to change it. But I think that script is working pretty well.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

@DocCyblade
Openuser pass was set correctly. Just postgres pass not.

correct wouild be good to watch for the script fix.

Admin can be changed in Odoo itself.

Best is what you have now, but allowing "admin" to be set as a pass (or allowing a default). I like being able to set it at the start as is. Safer that way.

l-arnold commented Sep 2, 2015

@DocCyblade
Openuser pass was set correctly. Just postgres pass not.

correct wouild be good to watch for the script fix.

Admin can be changed in Odoo itself.

Best is what you have now, but allowing "admin" to be set as a pass (or allowing a default). I like being able to set it at the start as is. Safer that way.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

@DocCyblade You know, that is why openuser is setting properly actually and why Odoo is starting I believe.
We are not using the pgsqlconf.py file to set openuser or admin for that matter. It is only postgres that is supposed to be set by the pgsqlconf.py file.

Perhaps that is why I spent 2 months trying to get the script to work... That said, I did think it was setting postgres user most of the time.

l-arnold commented Sep 2, 2015

@DocCyblade You know, that is why openuser is setting properly actually and why Odoo is starting I believe.
We are not using the pgsqlconf.py file to set openuser or admin for that matter. It is only postgres that is supposed to be set by the pgsqlconf.py file.

Perhaps that is why I spent 2 months trying to get the script to work... That said, I did think it was setting postgres user most of the time.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

My sense is that there is a server start/stop that is taking place in Inithooks that is out of sync. The black box is one indicator. Postgres not starting during firstboot is another indicator. I believe postgres did start on 2nd boot.

Technically we don't need Postgres user for our needs right now. We can also just give it a little "reset" in webmin to what we were trying to set in firstboot. Webmin User Admin is pretty convenient. Easy to set a new PW.

I do think it would be nice to get Odoo and PostgresSQL started at first boot rather than requiring a boot cycle. Alternatively, we could put a boot cycle in after PW'd set so it is automated.

Also, would be nice to purge the Stragglers.

l-arnold commented Sep 2, 2015

My sense is that there is a server start/stop that is taking place in Inithooks that is out of sync. The black box is one indicator. Postgres not starting during firstboot is another indicator. I believe postgres did start on 2nd boot.

Technically we don't need Postgres user for our needs right now. We can also just give it a little "reset" in webmin to what we were trying to set in firstboot. Webmin User Admin is pretty convenient. Easy to set a new PW.

I do think it would be nice to get Odoo and PostgresSQL started at first boot rather than requiring a boot cycle. Alternatively, we could put a boot cycle in after PW'd set so it is automated.

Also, would be nice to purge the Stragglers.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

@DocCyblade I am going to test to see if I can get the system halts you were seeing in Odoo.

Both of my last builds are running. Will also try the one I just built from kens-dev-wip1. Report that next.

l-arnold commented Sep 2, 2015

@DocCyblade I am going to test to see if I can get the system halts you were seeing in Odoo.

Both of my last builds are running. Will also try the one I just built from kens-dev-wip1. Report that next.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

Report on kens-dev-wp1 (ver1)

  • Admin Password (req 6 charachters) should have started w some non alphabetic
  • Apache started at first boot
  • Odoo did not start at first boot (I forgot to test postgres server)
  • Odoo started at second boot
  • Stragglers on confconsole second boot

*target shutdown did not cycle (turnoff) on 3rd boot (needed to reset)

  • no Stragglers on 3rd Boot.
    (by the way, most of the builds I made today would not turn themselves off without a VM command to enduce it). Hanging at "reached target shutdown"

All for now. Need to have dinner.
Don't recall the black box. May need to run again.

l-arnold commented Sep 2, 2015

Report on kens-dev-wp1 (ver1)

  • Admin Password (req 6 charachters) should have started w some non alphabetic
  • Apache started at first boot
  • Odoo did not start at first boot (I forgot to test postgres server)
  • Odoo started at second boot
  • Stragglers on confconsole second boot

*target shutdown did not cycle (turnoff) on 3rd boot (needed to reset)

  • no Stragglers on 3rd Boot.
    (by the way, most of the builds I made today would not turn themselves off without a VM command to enduce it). Hanging at "reached target shutdown"

All for now. Need to have dinner.
Don't recall the black box. May need to run again.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

*UPDATE
Rerun kens-dev-wp1 (ver1)

*Postgres Not running on First Boot
*Postgres does start from Webmin
*Odoo does not start after Postgres Start (I expect Service requires Postgres to be running at start)

*Adminer does THIS TIME FINALLY aim for Postgres as default Database
*postgres user does not respond to password set in inithooks
*(I expect openuser responds to mcookie password)

Second Boot:
*No Stragglers on Conf Console
*Odoo Does start and responds to admin password set at firstboot (using # to start) (Progress yes, still requires 6 charachters though so no "admin")
openerp-server.odoo
admin_passwd = (is correct)
db_password = (is correct)
*Not having any Odoo Failures that I can sense. Not that I won't but not yet

System not responding quickly to "shutdown" command but did shutdown from shell type input.
Stragglers on 3rd Boot
ConfConsole shutdown... DID Shutdown

l-arnold commented Sep 2, 2015

*UPDATE
Rerun kens-dev-wp1 (ver1)

*Postgres Not running on First Boot
*Postgres does start from Webmin
*Odoo does not start after Postgres Start (I expect Service requires Postgres to be running at start)

*Adminer does THIS TIME FINALLY aim for Postgres as default Database
*postgres user does not respond to password set in inithooks
*(I expect openuser responds to mcookie password)

Second Boot:
*No Stragglers on Conf Console
*Odoo Does start and responds to admin password set at firstboot (using # to start) (Progress yes, still requires 6 charachters though so no "admin")
openerp-server.odoo
admin_passwd = (is correct)
db_password = (is correct)
*Not having any Odoo Failures that I can sense. Not that I won't but not yet

System not responding quickly to "shutdown" command but did shutdown from shell type input.
Stragglers on 3rd Boot
ConfConsole shutdown... DID Shutdown

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister Sep 2, 2015

Member

@l-arnold - the 6 char requirement is built into inithooks so not easy to change. Also isn't that password for the "super-admin" account? If so it should probably be much more than 6 chars!

Also I'm just having a look at the pgsql inithook. Will let you know how I go...

Member

JedMeister commented Sep 2, 2015

@l-arnold - the 6 char requirement is built into inithooks so not easy to change. Also isn't that password for the "super-admin" account? If so it should probably be much more than 6 chars!

Also I'm just having a look at the pgsql inithook. Will let you know how I go...

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister Sep 2, 2015

Member

I have a fix for the postgresql inithook. I will be pushing the code shortly; will edit this post with updates (or post a new one if anyone replies in the meantime).

PR issued turnkeylinux/common#51 - awaiting merge from Alon.

update it's merged. Update your common again and you should be good to go! 😄

Member

JedMeister commented Sep 2, 2015

I have a fix for the postgresql inithook. I will be pushing the code shortly; will edit this post with updates (or post a new one if anyone replies in the meantime).

PR issued turnkeylinux/common#51 - awaiting merge from Alon.

update it's merged. Update your common again and you should be good to go! 😄

@DocCyblade

This comment has been minimized.

Show comment
Hide comment
@DocCyblade

DocCyblade Sep 2, 2015

Member

Sweet I'll do some test builds this AM

Member

DocCyblade commented Sep 2, 2015

Sweet I'll do some test builds this AM

@DocCyblade

This comment has been minimized.

Show comment
Hide comment
@DocCyblade

DocCyblade Sep 2, 2015

Member

Did a build confirm that it is now fixed
However everything is running now but get database error.

I can confirm that the password for openuser is correct and I can login to adminer with this password.

Need to do some research on the database connection password. If you can point me to artical that shows the config file and database password that would be good. I'll post back my findings and if I find a fix will push it to my branch

Member

DocCyblade commented Sep 2, 2015

Did a build confirm that it is now fixed
However everything is running now but get database error.

I can confirm that the password for openuser is correct and I can login to adminer with this password.

Need to do some research on the database connection password. If you can point me to artical that shows the config file and database password that would be good. I'll post back my findings and if I find a fix will push it to my branch

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

How does the Database error appear? Odoo or somewhere else on the system?

I get dialed in shortly as well.
The db connection should be through openuser but we had a sit two days ago where it seemed to not fully be the case.

Back shortly.

l-arnold commented Sep 2, 2015

How does the Database error appear? Odoo or somewhere else on the system?

I get dialed in shortly as well.
The db connection should be through openuser but we had a sit two days ago where it seemed to not fully be the case.

Back shortly.

@DocCyblade

This comment has been minimized.

Show comment
Hide comment
@DocCyblade

DocCyblade Sep 2, 2015

Member

Issue is with with database connection. It seems that the Python script is still not changing the openuser password. It is changing the Postgres password.

When I mannually run the Python script it says access denied still.

Jermery some time can you see if you can replicate this. I can go in and change the password for the openuser then odoo works

Member

DocCyblade commented Sep 2, 2015

Issue is with with database connection. It seems that the Python script is still not changing the openuser password. It is changing the Postgres password.

When I mannually run the Python script it says access denied still.

Jermery some time can you see if you can replicate this. I can go in and change the password for the openuser then odoo works

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

@docblade Following up. Looking at : kens-dev-wip1 branch

Looking at: tkl-nomadic-odoo/conf.d/30_main
line 31: would the su - postgres command to create "openuser" require a password or can we "su" in without. I thought "postgres" was a "db user" not a "system user".

It further appears that we are setting the "openuser" password at line 38 with "mcookie" which we come back around and do later in (inithooks somewhere)

Line 45 Has a "postgresql stop" command. (Is this causing problems later?)

Line 54 Shouldn't we add the Service user (openerp) "with" a Home Directory. IE, when they su-in they would end up somewhere in the /opt/openerp/ directory. 2 Years ago my manual build was having that result for v 7 OpenERP. I know that there are some places "outside" /opt/openerp where ownership is taken by the service user.

It seems that "System Users" may be getting "db user" type rights in the Postgresql system. Could these "system users" be controlling some of the db function somehow?

I will look at a few different files and post separately: Wish there was easier formatting here.

l-arnold commented Sep 2, 2015

@docblade Following up. Looking at : kens-dev-wip1 branch

Looking at: tkl-nomadic-odoo/conf.d/30_main
line 31: would the su - postgres command to create "openuser" require a password or can we "su" in without. I thought "postgres" was a "db user" not a "system user".

It further appears that we are setting the "openuser" password at line 38 with "mcookie" which we come back around and do later in (inithooks somewhere)

Line 45 Has a "postgresql stop" command. (Is this causing problems later?)

Line 54 Shouldn't we add the Service user (openerp) "with" a Home Directory. IE, when they su-in they would end up somewhere in the /opt/openerp/ directory. 2 Years ago my manual build was having that result for v 7 OpenERP. I know that there are some places "outside" /opt/openerp where ownership is taken by the service user.

It seems that "System Users" may be getting "db user" type rights in the Postgresql system. Could these "system users" be controlling some of the db function somehow?

I will look at a few different files and post separately: Wish there was easier formatting here.

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister Sep 2, 2015

Member

@DocCyblade
So it's changing the openuser DB user password ok? But it is meant to change a user password too?

Oh hang on; you mean it's changing the password for the "postgres" user not the "openuser"... Right? If so that's really weird. The code looks good to me....

When I mannually run the Python script it says access denied still.

Where are you running it from? I bet you're in /root. cd / first should avoid the permission error...

Member

JedMeister commented Sep 2, 2015

@DocCyblade
So it's changing the openuser DB user password ok? But it is meant to change a user password too?

Oh hang on; you mean it's changing the password for the "postgres" user not the "openuser"... Right? If so that's really weird. The code looks good to me....

When I mannually run the Python script it says access denied still.

Where are you running it from? I bet you're in /root. cd / first should avoid the permission error...

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

@DocCyblade
Comparing kens-dev-wip1 seeing points of exploration.

SSL Changes. Got that, though I am concerned about what will happen when we Put REAL CERTS in if we can't point to the cert locations overtly. I have always done it that way anyway. Do we know the "real cert" process in the new system (ie one we buy and ties to our domain etc)?

LIB Creation: Got THAT We should Merge that directly
+# Create lib
+mkdir /var/lib/odoo
+chown -R openerp:openerp /var/lib/odoo

I see your "pulling" the "create DB" functions at Lines 9 and 34. Seems to make sense. Wasn't clear why we had made them last few days.

I think you would "su - openerp" (rather than postgres) to do this sort of thing however. Am I correct? Either that or use a postgresql command not requiring su.

In openerp-server.conf
The Interface = and Proxy Mode = commands... I have been there before. Not quite clear on this but if you look at the history of prior builds you can see some of that exploration. I think basically Proxy Mode and Interface = are controlled in our build now via Apache and XML and RPC interfaces.

xml_interface = 127.0.0.1
rpc_interface = 127.0.0.1

If set with 127.0.0.1 the System is only available via Localhost. That Means Apache can get to it but an outside "non apache routed" user cannot. This way Apache can force SSL. If 127.0.0.1 is removed from those two lines Odoo becomes available on Port 8069 in Pure HTTP (https should still also work on whatever apache is set up to do (our port 443)

l-arnold commented Sep 2, 2015

@DocCyblade
Comparing kens-dev-wip1 seeing points of exploration.

SSL Changes. Got that, though I am concerned about what will happen when we Put REAL CERTS in if we can't point to the cert locations overtly. I have always done it that way anyway. Do we know the "real cert" process in the new system (ie one we buy and ties to our domain etc)?

LIB Creation: Got THAT We should Merge that directly
+# Create lib
+mkdir /var/lib/odoo
+chown -R openerp:openerp /var/lib/odoo

I see your "pulling" the "create DB" functions at Lines 9 and 34. Seems to make sense. Wasn't clear why we had made them last few days.

I think you would "su - openerp" (rather than postgres) to do this sort of thing however. Am I correct? Either that or use a postgresql command not requiring su.

In openerp-server.conf
The Interface = and Proxy Mode = commands... I have been there before. Not quite clear on this but if you look at the history of prior builds you can see some of that exploration. I think basically Proxy Mode and Interface = are controlled in our build now via Apache and XML and RPC interfaces.

xml_interface = 127.0.0.1
rpc_interface = 127.0.0.1

If set with 127.0.0.1 the System is only available via Localhost. That Means Apache can get to it but an outside "non apache routed" user cannot. This way Apache can force SSL. If 127.0.0.1 is removed from those two lines Odoo becomes available on Port 8069 in Pure HTTP (https should still also work on whatever apache is set up to do (our port 443)

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister Sep 2, 2015

Member

@l-arnold

SSL Changes. Got that, though I am concerned about what will happen when we Put REAL CERTS in if we can't point to the cert locations overtly. I have always done it that way anyway. Do we know the "real cert" process in the new system (ie one we buy and ties to our domain etc)?

You can still specifiy them as before. It's just the default cert location has moved and we have consolidated a lot of stuff in common. Apache directives within a site override defaults so adding a custom cert is same as always...

Member

JedMeister commented Sep 2, 2015

@l-arnold

SSL Changes. Got that, though I am concerned about what will happen when we Put REAL CERTS in if we can't point to the cert locations overtly. I have always done it that way anyway. Do we know the "real cert" process in the new system (ie one we buy and ties to our domain etc)?

You can still specifiy them as before. It's just the default cert location has moved and we have consolidated a lot of stuff in common. Apache directives within a site override defaults so adding a custom cert is same as always...

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

@JedMeister (thanks for the clarification Jeremy). I will do some testing on a paid Cert pretty soon then. Scary waters if complicated things get changed is all.

@DocCyblade @JedMeister I will update my "common" again (via Fetch for test or Pull for permanent?)

@DocCyblade Need to see if the current dev-wip1 builds. Should any changes be applied. Seems we the LIB creation moved to dev-wip1 already.

Is "kens-dev-wip1" ready for a test just now also? Seeing Proxy Mode Tests as well as some others in openerp-server.conf . My personal take is that those type tests can be done on a running system with either a reboot or a openerp-init start/stop cycle.

The Create or Don't Create Databases probably want a full cycle test.

Any other changes or should I just manually put in the lib creation?

l-arnold commented Sep 2, 2015

@JedMeister (thanks for the clarification Jeremy). I will do some testing on a paid Cert pretty soon then. Scary waters if complicated things get changed is all.

@DocCyblade @JedMeister I will update my "common" again (via Fetch for test or Pull for permanent?)

@DocCyblade Need to see if the current dev-wip1 builds. Should any changes be applied. Seems we the LIB creation moved to dev-wip1 already.

Is "kens-dev-wip1" ready for a test just now also? Seeing Proxy Mode Tests as well as some others in openerp-server.conf . My personal take is that those type tests can be done on a running system with either a reboot or a openerp-init start/stop cycle.

The Create or Don't Create Databases probably want a full cycle test.

Any other changes or should I just manually put in the lib creation?

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

@JedMeister Can you go over to https://github.com/l-arnold/tkl-nomadic-odoo . I would like to move some of these conversations outside of Tracker Issues.

Some are "tracker issues" some are "not" it seems to me is all. Hate to fill up the mail box for non-participants.

l-arnold commented Sep 2, 2015

@JedMeister Can you go over to https://github.com/l-arnold/tkl-nomadic-odoo . I would like to move some of these conversations outside of Tracker Issues.

Some are "tracker issues" some are "not" it seems to me is all. Hate to fill up the mail box for non-participants.

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister Sep 2, 2015

Member

@l-arnold - NP just tag me where/when you want input.

@DocCyblade we could test the DB setting inithook like

/usr/lib/inithooks/bit/pgsqlconf.py --user=openuser --pass="password";

then see if that works and/or errors or something...?

Member

JedMeister commented Sep 2, 2015

@l-arnold - NP just tag me where/when you want input.

@DocCyblade we could test the DB setting inithook like

/usr/lib/inithooks/bit/pgsqlconf.py --user=openuser --pass="password";

then see if that works and/or errors or something...?

@DocCyblade

This comment has been minimized.

Show comment
Hide comment
@DocCyblade

DocCyblade Sep 2, 2015

Member

Well I am done for the day. Not sure why the openuser password is not being set on first boot.

In a test I removed the init hook that resets the database password and odoo works. It seems my build is not changing the password for the open user

Also I did some reading and we do need to give openuser super user rights per odoo docs we can make that change.

Bottom line the openuser is not being changed

Member

DocCyblade commented Sep 2, 2015

Well I am done for the day. Not sure why the openuser password is not being set on first boot.

In a test I removed the init hook that resets the database password and odoo works. It seems my build is not changing the password for the open user

Also I did some reading and we do need to give openuser super user rights per odoo docs we can make that change.

Bottom line the openuser is not being changed

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

I will do some tests on the two branches and see what I can about db-passwords. I fetched "common" so maybe I can revert.

With yesterdays common postgres was not updating but openuser was updating.
I had understood the openuser was by passin the pgsqlconf.py file and doing it directly in the mcookie inithook.

Anyway, thanks for your efforts. It seems very close.
Will report back soon. (Here or l-arnold/tkl-nomadic-odoo)

l-arnold commented Sep 2, 2015

I will do some tests on the two branches and see what I can about db-passwords. I fetched "common" so maybe I can revert.

With yesterdays common postgres was not updating but openuser was updating.
I had understood the openuser was by passin the pgsqlconf.py file and doing it directly in the mcookie inithook.

Anyway, thanks for your efforts. It seems very close.
Will report back soon. (Here or l-arnold/tkl-nomadic-odoo)

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

@JedMeister
(EDITED) I also said "git fetch" in the common directory rather than "git pull" thinking I could revert if need be.

Just went to do a new build and got bonked? Anyone know how I can fix? Guessing it is some chroot thing. Last I did was type : unset CHROOT_ONLY

I just want to work the way I have been doing full ISO's.

root@tkldev odoo-doc/tkl-nomadic# make clean @@ make
deck -D build/root.sandbox
deck -D build/root.patched
deck -D build/root.build
deck -D build/bootstrap
rm -rf build/root.spec build/cdroot build/product.iso build/log build/stamps
make: *** No rule to make target '@@'. Stop.

l-arnold commented Sep 2, 2015

@JedMeister
(EDITED) I also said "git fetch" in the common directory rather than "git pull" thinking I could revert if need be.

Just went to do a new build and got bonked? Anyone know how I can fix? Guessing it is some chroot thing. Last I did was type : unset CHROOT_ONLY

I just want to work the way I have been doing full ISO's.

root@tkldev odoo-doc/tkl-nomadic# make clean @@ make
deck -D build/root.sandbox
deck -D build/root.patched
deck -D build/root.build
deck -D build/bootstrap
rm -rf build/root.spec build/cdroot build/product.iso build/log build/stamps
make: *** No rule to make target '@@'. Stop.

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

Not sure why it didn't have a "make history" on the folder. Did one yesterday.
got it started by
chroot_only=n
make clean
make

then it started anyway.
We will see how it goes.

l-arnold commented Sep 2, 2015

Not sure why it didn't have a "make history" on the folder. Did one yesterday.
got it started by
chroot_only=n
make clean
make

then it started anyway.
We will see how it goes.

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister

JedMeister Sep 2, 2015

Member

@l-arnold You used @@ when you need to use &&.

Also with CHROOT_ONLY=y a couple of things:

  • it is a global variable and needs to be all caps i.e. CHROOT_ONLY; chroot_only won't work
  • if you look at the build code; it actually only checks to see if CHROOT_ONLY is set; not what it is set to
    • so in effect CHROOT_ONLY=blue-whale will have the same effect as CHROOT_ONLY=y
    • that means that CHROOT_ONLY=n is actually setting it to make a chroot only env; it has the same effect as CHROOT_ONLY=y

So either make CHROOT_ONLY=y or don't use it; e.g. make

Also one other reference thing re git:
git pull is the same as git fetch && git merge. So if you have already done a fetch then rather than doing a pull, you can just do a merge. It doesn't make much difference but it saves you from having to download info from the net again, which saves a few seconds...

Member

JedMeister commented Sep 2, 2015

@l-arnold You used @@ when you need to use &&.

Also with CHROOT_ONLY=y a couple of things:

  • it is a global variable and needs to be all caps i.e. CHROOT_ONLY; chroot_only won't work
  • if you look at the build code; it actually only checks to see if CHROOT_ONLY is set; not what it is set to
    • so in effect CHROOT_ONLY=blue-whale will have the same effect as CHROOT_ONLY=y
    • that means that CHROOT_ONLY=n is actually setting it to make a chroot only env; it has the same effect as CHROOT_ONLY=y

So either make CHROOT_ONLY=y or don't use it; e.g. make

Also one other reference thing re git:
git pull is the same as git fetch && git merge. So if you have already done a fetch then rather than doing a pull, you can just do a merge. It doesn't make much difference but it saves you from having to download info from the net again, which saves a few seconds...

@l-arnold

This comment has been minimized.

Show comment
Hide comment
@l-arnold

l-arnold Sep 2, 2015

Thank you gor both clarifications. Must be the @ call got to me @JedMeister.

We have a very clean build thanks hugely to Ken! Right now in our dev-wip1 branch. Will move up the ladder soon.

Check it out if you have some time. Isos avail.

l-arnold commented Sep 2, 2015

Thank you gor both clarifications. Must be the @ call got to me @JedMeister.

We have a very clean build thanks hugely to Ken! Right now in our dev-wip1 branch. Will move up the ladder soon.

Check it out if you have some time. Isos avail.

@JedMeister

This comment has been minimized.

Show comment
Hide comment
@JedMeister
Member

JedMeister commented Dec 1, 2015

@JedMeister JedMeister closed this Dec 1, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment