https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-590 controller <p>if run.sh is not exec in opendaylight, the error msg will be shown:<br/> $ run.sh -Xmx2G -start<br/> find: `configuration/initial': No such file or directory</p> <p>Can opendaylight start properly with such error?</p> <p>Operating System: Windows<br/> Platform: PC</p> CONTROLLER-590

run.sh error

Bug Resolved Done Unassigned Connie Chan Mon, 30 Jun 2014 20:37:06 +0000 Tue, 25 Jul 2023 08:23:57 +0000 Tue, 5 May 2015 15:17:09 +0000 adsal 0 3 <p>$ cat version.properties <br/> org.opendaylight.controller.version = 0.1<br/> org.opendaylight.controller.build.scm.version = 60b06b4e58f33d4fbd44da3d8cc982a7d26880d0<br/> org.opendaylight.controller.build.user = root<br/> org.opendaylight.controller.build.workspace = **********<br/> org.opendaylight.controller.build.timestamp = 1404131807720<br/> org.opendaylight.controller.build.machine = **********</p> <p>Information in this link may be relevant:<br/> <a href="http://superuser.com/questions/393812/supresss-the-no-such-file-or-directory-message-from-find" class="external-link" target="_blank" rel="nofollow noopener">http://superuser.com/questions/393812/supresss-the-no-such-file-or-directory-message-from-find</a></p> <p>&gt; Can opendaylight start properly with such error?</p> <p>Yes.</p> <p>This is the guilty line in run.sh (with comment):</p> <ol> <li>clean available optional configurations (links)<br/> find configuration/initial -type l -exec rm {} \;</li> </ol> <p>The problem is that while run.sh detects the directory where it is located<br/> RUNSH_DIR=$(dirname $0)<br/> it does not cd there, so the "find" command may start from unrelated directory, with no configuration/initial sub-branch; hence the error is printed.</p> <p>But usually there are no optional configurations present, no links for the find command to remove, so ODL will start properly.</p> <p>The fix is easy: prepend ${RUNSH_DIR}/ before appropriate relative paths (there are more of them, not just the first find).</p> <p>Now, let me see if I can submit a patch.</p> <p>I have received a warning "commit subject &gt;65 characters" but here is this:<br/> <a href="https://git.opendaylight.org/gerrit/#/c/8485/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/8485/</a></p> <p>Commit was merged.<br/> My understanding of interactions between Jenkins jobs is not deep enough to deduce which build contains the full ODL with this fix, but you can simply replace run.sh with the new version, for example from here: <a href="https://git.opendaylight.org/gerrit/gitweb?p=integration.git;a=blob;f=distributions/base/src/assemble/resources/run.sh;h=ece3a515193b591427696bfafad428bfeeb555dc;hb=bea9f341e6503a72083db5c9c973001f587498a7" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/gitweb?p=integration.git;a=blob;f=distributions/base/src/assemble/resources/run.sh;h=ece3a515193b591427696bfafad428bfeeb555dc;hb=bea9f341e6503a72083db5c9c973001f587498a7</a></p> <p>This bug is part of the project to Move all ADSAL associated component bugs to ADSAL.</p> Development External issue ID 1268 External issue URL Rank 0|i02lc7: