[ 
https://issues.apache.org/jira/browse/OFBIZ-7796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379486#comment-15379486
 ] 

Jacques Le Roux commented on OFBIZ-7796:
----------------------------------------

About the 80/92% it may be a bit disturbing but if you are used to the log 
OFBiz produces you shoul not be worried. Anyway the best way to check things 
are alright is to access to the webapps. 
About you concern Pierre, here is what I wrote in OFBIZ-7795 at  
https://issues.apache.org/jira/browse/OFBIZ-7795?focusedCommentId=15379143
bq. Though I worked carefully, I could have missed something so please check 
(notably typos, I did not test all). Note: we had no "apply-ofbiz-patches" Ant 
target (in applyOfbizPatchesAndHotDeploy.sh)
I mean I did not test all tools/scripts (those are provided as conveniences by 
the community, some even proposed to remove them), but I suppose it's OK apart 
possible typos.

So I think we can close this issue, please confirm, thanks!

> Running OFBiz as a service fails
> --------------------------------
>
>                 Key: OFBIZ-7796
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7796
>             Project: OFBiz
>          Issue Type: Bug
>    Affects Versions: Trunk
>         Environment: Ubuntu 16.04, openjdk-8-jdk
>            Reporter: Pierre Smits
>            Priority: Blocker
>
> In a new ubuntu environment I performed a checkout  from trunk and ran the 
> loadDefault build script.
> After this had completed, I moved the ofbiz directory from my user folder to 
> the /opt folder, and configured the Ubuntu environment to be able to run 
> OFBiz as a service.
> This entails:
> * deploy a script in /etc/init.d
> * set the correct permissions of the service script
> * create the service user 
> * changed the owner and ownergroup of the files and folders in /opt/ofbiz
> and then fire the service:
> sudo /etc/init.d/ofbiz start
> This normally starts the proces java -jar ofbiz.jar
> But now nothing happens.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to