Open l-arnold opened 9 years ago
Ah you meant @jedmeister! :smile:
Sounds good. We can move the conversation here then
Made some changes and doing a build now. This will be the last one until after 6 My time
Sounds good.
Doing a build now as well (dev-wip1).
I think you are in the East (EST). I am in Colorado (MST). Need to get on some other projects for sure. Would love to have this close to wrapped.
I put a few "issues" up we might address. (the ARCH/REL/VER) thing I will take a stab at in dependencies. We need it for Gdata and WHTMLTOX
How to make a Smile? :) I am guessing, but no. :smile: (colon : sm) and starts to show. OK Thumbs made with colon :+1:
@JedMeister If I "fetch" Common that is temporary. Correct? Doing a Pull is more permanent. Will the fetch effect the next build as I assume?
Fetch will pull the change down to your repo, pull will fetch and merge
(Updated x 2) Build with Common "Fetch" to turnkey/fab/common USING dev-wip1 for build
Firstboot Postgresql was not running at the end of first boot
2nd Boot. Postgresql running openerp can log in with mcookie assigned to /opt/openerp/odoo/openerp-server.conf
postgres can NOT log in with password set at firstboot inithooks (Was able to by assigning same pw in Webmin Postgresql USER update (postgres)
so exact same as yesterday. Perhap the Common Fetch did not work
Update #1 Very Long Wait for Odoo. It seems that the OpenERP Database could be accessed at login time (I bypass to manage databases) and create a new one. Will see if I can get into OpenERP by itself.
Update #2 Openerp Database is "accessible" to Odoo. However, I do not know the User Login or the Password for it. Normally this would be set in "database creation" but perhaps there is a setting some where defining such.
(Some Merit in having an accessible database at start, however.. need to set controls to it as well) I will look in Postgre to see if there is a user in there. There must e an admin. Perhaps the PW is setting there as well.
As I see you are working to "not" create openerp database per say, I think that is a good direction. If we do create it we need to seed it with a user name and password and that seems complicated and un-needed right now.
Reason for doing so would be to put in TKL logos, branding things like that, but that would be overwritten right away anyway I feel.
Just did a pull trying to have VER/REL/ARCh in 10-dependencies Common next
Will report with a new build soon.
Not sure why I can't use make clean && make any more. Keeps telling me there is no rule
now tried make clean then make
(seems to be building, but I hope it is correct)
what am I missing here?
Just did a successful build with everything seems to be working. Going to do another build to see if this is working again and not just a fluke.
Cool. I'm was prepping such too. Seemes wierd in that I know you made some changes. Just did "git pull" on your branch into the directory I used yesterday. kens-dev-wip1 read this transcript and tell me if it looks ok. Nothing updated which is the wierd part. Same on the Common Branch just now:
root@tkldev products/tkl-odoo-dev# dir kens-dev-wip1 tkl-nomadic root@tkldev products/tkl-odoo-dev# cd kens-dev-wip1 /turnkey/fab/products/tkl-odoo-dev/kens-dev-wip1 root@tkldev tkl-odoo-dev/kens-dev-wip1# git pull remote: Counting objects: 16, done. remote: Compressing objects: 100% (16/16), done. remote: Total 16 (delta 6), reused 0 (delta 0), pack-reused 0 Unpacking objects: 100% (16/16), done. From https://github.com/l-arnold/tkl-nomadic-odoo c8fd28c..737f613 dev-wip1 -> origin/dev-wip1 Already up-to-date. root@tkldev tkl-odoo-dev/kens-dev-wip1# git branch
It seems that everything works fine, however only after a reboot or a restart of the Postgres and odoo services.
Looking at doing a init hook to restart the services
By the way, the default odoo login is admin admin
Cool. Is that set in 10-main ? I did not see where you set that? Perhaps in the "early version" openerp-server.conf
I am doing a build. Last one failed because I needed to uncomment REL and ARCH in my whtmltox wget. Lets see if it works now.
I am working in dev-wip1 can also build kens-dev-wip1
Should I do so before we try a Pull Request?
My last build worked like a treat!
I pushed my changes check out my branch and do a clean build and test the ISO install
I tried three times, each one built and ISO installed.
All services seemed to be working going to main website, asked to create a database!
I am not sure you want to nest directories like that under products. I never have done that.
I just create two directories odoo-1 and odoo2 under products.
Good idea. I will get it flat. Have several folders out under products is all.
my REV/VER/ARCH is not working right for wkhtmltox (will revert) in 10-dependencies(dev-wip1) (updated filename)
---- UPDATE Just added GEN to separate from VER (there is a folder with 0.12) that needs to be called before the full version call there.
will test again after kens-dev-wip1 which is running now (unnested)
kens-dev-wip1 (my rc2 iso) Just built, installed clean
Postgresql running at firstboot Got an error w/ Odoo at first boot (Service not available)
Second Boot Odoo came up after 3 x Refreshes (not sure why the lag) web/database/manager#action=database_manager
But Running.
I have a Snapshot saved. Will revert to "restart point" and see if I wait at "First Boot" (post passwords) I can get Odoo to come up by its own. May be I did not wait long enough.
Would be interesting to have a "console" that said "when ODOO is ready" (complicated)
Round 2
Postgres Running
Logged into postgres via Adminer
Odoo Process "says" running
530 openerp 18:02 python /opt/openerp/odoo/openerp-server --config=/opt/openerp/odoo/openerp-serve ...
Odoo at First Boot Returns:
Odoo Second Boot
Why don't we just put a Reboot in the InitHook? Would this make sense? I realize better to just reboot the services.
Looks great ALL THINGS considered. THANK YOU.
I am working off of all SSD drives. My wait time was like 10 sec.
During first boot did you see it stop and restart the services?
Not visually anywhere. Would that be in the install screen? I will try again and see. Goes quick because I have a snapshot to "reboot" that is part of the Install Protocol.
I will count to 10 and see whether I can get in after setting PW and taking in Updates (Updates could be part of the issue really - so I will skip them this next time)
No visual reboot of services at first boot.
Could have a "restart services" as part of the Advanced Menu... That or some sort of "system check".
We could also just update
confconsole.txt
and Say, Please choose "A" and Reboot your system One Time at First Installation (not sure how we would handle a Amazon Install though.
(reordered EDIT for clarity)
Still 500 Internal Server Error on First Boot
Just tried to "stop/start" openerp-server in "running services" in Webmin. This time 503 Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Prior was 500 error not 503
(Moved line below) Did need a second reboot to bring Odoo Up.
Did Start Clean on Second Boot, no intervention. (UPDATE).. ACTUALLY STRAGGLERS show up on BLUE SCREEN. A (advanced) B (back) clears them
maybe I don't have the "restart" code yet, but I think I do. Also we are both running VMware version I believe (not sure that matters really)
Updated Comment 2 above: Did Start Clean on Second Boot, no intervention. (UPDATE).. ACTUALLY STRAGGLERS show up on BLUE SCREEN. A (advanced) B (back) clears them
in dev-wip1 Looks like I got my "ARCH" version of wkhtmltox to download and dpkg. Great for updates moving forward. Complicated pull.
I have a build. I won't install just now. If its in its in.
Should we do a Pull Request into dev-wip1 ? Should we do a Pull Request into dev ?
What is your testing protocol?
What steps do you take from build to installing to trying to test the app? Maybe I am missing something in your steps
Mine is this
I have a VM that is blank with a snapshot to the blank
Just did another test and I had no issues.
I am basically doing the same except I don't see #11 anywhere.
In TKLDEV I do git pull (occassionally say git branch to make sure I am where I want to be) make clean make (wait a while) In SFTP I rename the ISO using a convention like "kens-dev-wip-rc2.iso" Download Upload to my VM System Define a new VM that boots from the ISO Use guided Full, next, next, next (make a machine snapshot Now before reboot) reboot root password (consistent) postgres password (consistent) admin password (consistent) (ADDED to comment) Skip TKLBAM, Skip Email, (Sometimes UPdate, sometimes Not)
If I do updates, perhaps it restarts all services then, however, no visual (11 should be here, but I don't see anything. MIght be doing it might not)
My system comes up to confconsole (blue screen)
Great that it came up.
Lets do a few Pulls (Pull Requests) kens-dev-wip1 > into dev-wip1
test (this will merge with my ARCH update for 10-dependencie (whtmltox) If good
dev-wip1 > dev
Thoughts?
You wrote: 11: Shows that services are restarting 12.check each port
(can you do a screenshot perhaps ?)
Might be that my old VMWARE doesnt' do that (Version 4.0 I believe)
I updated my last ISO to Sourceforge. Maybe you can try it to see if you get the same result as your ISO: https://sourceforge.net/projects/tklnomadicodoo/files/ called: kens-dev-wip1-rc2.iso
Some old ones there I should delete otherwise. Will do a new GOOD one very soon. Maybe we drop the Nomadic part in the naming.
@DocCyblade Not clear why I am not seeing more changes. Maybe you did a merge already. see this link:
https://github.com/l-arnold/tkl-nomadic-odoo/compare/kens-dev-wip1...dev-wip1
It is directional. That comparison shows "my change" in dev-wip1
Reversing the order shows "your change" https://github.com/l-arnold/tkl-nomadic-odoo/compare/dev-wip1...kens-dev-wip1
I can see from the Changes and My files that I do not have the "restart services" file.
overlay/usr/lib/inithooks/firstboot.d/97-odoo-restart-services
Does it need to be (forgot the word) chmod'd to be "executable"
Just ran and got the updates via PULL
root@tkldev products/kens-dev-wip1# git pull remote: Counting objects: 26, done. remote: Compressing objects: 100% (22/22), done. remote: Total 26 (delta 5), reused 0 (delta 0), pack-reused 0 Unpacking objects: 100% (26/26), done. From https://github.com/l-arnold/tkl-nomadic-odoo 9a81b14..d6e41bf kens-dev-wip1 -> origin/kens-dev-wip1 737f613..4c36f15 dev-wip1 -> origin/dev-wip1 Updating 9a81b14..d6e41bf Fast-forward conf.d/30_main | 9 ++------- .../lib/inithooks/firstboot.d/20-odoo-db-secrets | 1 + .../inithooks/firstboot.d/97-odoo-restart-services | 19 +++++++++++++++++++ 3 files changed, 22 insertions(+), 7 deletions(-) create mode 100755 overlay/usr/lib/inithooks/firstboot.d/97-odoo-restart-services root@tkldev products/kens-dev-wip1#
Do a pull request, just don't approve it yet we can then see what's changing etc. I think I can approve them since I have access to the repo
Ok. Working on a new iso build from kens-dev-wip1 also
PR next.
Which should be "base" ? Which should be "compare" ?
(ie, right and left) in https://github.com/l-arnold/ )
https://help.github.com/articles/using-pull-requests/
(left) = "base branch" (normally goes to default branch . I assume should be dev-wp1) (right) = "head branch" (I assume kens-dev-wip1)
Ran the PR. Have a look if you would.
Just did another build mine works out of the box.
Have not tried your branch yet
Getting there. I am abou 50% on package builds. Running make again.
Should all be good.
FULL START no reboot.
Postgres Odoo No Stragglers yet.
Nice One!
TKL Odoo RC1
What do you think? Lets take a break for a while. I think my little set of changes integrated as well. Will test that to be sure but was mainly a parsing issue with variables in the download name.
How can we put a Marker in Right Now in the Build so we know where we are?
https://github.com/l-arnold/tkl-nomadic-odoo/commit/682a82d5a9c1dabe61e6063999750c2ff109c5ed Uploading ISO TKL Odoo RC1 under Files at: https://sourceforge.net/projects/tklnomadicodoo (takes a while to get up there. First one did not complete as I opened a new page)
I can do a test on your branch and we can merge it into dev, and dev into master as a beta1
RC should only be when everything is done. There are still some things may need to be tweaked or bugs to be shaken out.
Do a Test on the Branch. If looks good we can put it into dev. Makes sense.
beta is a better term than RC for right here.
:+1: Let me know your thoughts on system and also documentation. I was putting some quick info in the documentation Link
https://odooIP:12324 will take you there (4th Icon)
Should also fix up that landing Page getting the column aligned.
We will let Jeremy know when we go into Dev Branch. (he is likely reading this being so short on projects right now :smile: )
Great work guys! :+1:
Yeah @l-arnold I've got nothing much on at the moment...! :stuck_out_tongue_closed_eyes:
@l-arnold I tagged this as beta v0.1
going forward I suggest that if you find big issues or even small ons open an issue on your own repo here to track it. Also lets others know there are known issues. I also created some issue tags for you so you can tag issues a release number like we do in TKL
I propose we move some of these conversations off of TRACKER and into Issues for tkl-nomadic-odoo as I am doing here.
Probably want to have @DocCyblade, @l-arnold and @JedMeister watching (yep) - updated. Also needed to bring JedMeister in as a Collaborator to get an @ to work.