Skip to main content

Fixing the macOs command issue

Fixing the macOs command issue



1. Permission denied when running a script file

dheeraj.kumar@LT-0623-011 bin % ./startup.sh

zsh: permission denied: ./startup.sh


execute your command by prefixing it with chmod +x


dheeraj.kumar@LT-0623-011 bin % chmod +x ./startup.sh

dheeraj.kumar@LT-0623-011 bin % ./startup.sh

Using CATALINA_BASE:   /Users/dheeraj.kumar/Downloads/apache-tomcat-8.5.92

Using CATALINA_HOME:   /Users/dheeraj.kumar/Downloads/apache-tomcat-8.5.92

Using CATALINA_TMPDIR: /Users/dheeraj.kumar/Downloads/apache-tomcat-8.5.92/temp

Using JRE_HOME:        /Library/Java/JavaVirtualMachines/jdk-1.8.jdk/Contents/Home

Using CLASSPATH:       /Users/dheeraj.kumar/Downloads/apache-tomcat-8.5.92/bin/bootstrap.jar:/Users/dheeraj.kumar/Downloads/apache-tomcat-8.5.92/bin/tomcat-juli.jar

Using CATALINA_OPTS:   

Tomcat started.



2. Command Not Found



dheeraj.kumar@LT-0623-011 bin % sudo ./startup.sh

Password:

sudo: ./startup.sh: command not found


execute your command by prefixing it with E-



dheeraj.kumar@LT-0623-011 bin % sudo -E ./startup.sh




3. If you are trying to create the myid file with execute permissions, you can use the touch command followed by chmod:



sudo touch tmp/zookeeper-2/myid sudo chmod +x tmp/zookeeper-2/myid



Reference : https://www.baeldung.com/linux/sudo-command-not-found


Labels:

Comments

Post a Comment

Popular posts from this blog

How to create Annotation in Spring boot

 To create Custom Annotation in JAVA, @interface keyword is used. The annotation contains :  1. Retention :  @Retention ( RetentionPolicy . RUNTIME ) It specifies that annotation should be available at runtime. 2. Target :  @Target ({ ElementType . METHOD }) It specifies that the annotation can only be applied to method. The target cane be modified to:   @Target ({ ElementType . TYPE }) for class level annotation @Target ({ ElementType . FIELD }) for field level annotation @Retention ( RetentionPolicy . RUNTIME ) @Target ({ ElementType . FIELD }) public @ interface CustomAnnotation { String value () default "default value" ; } value attribute is defined with @ CustomAnnotation annotation. If you want to use the attribute in annotation. A single attribute value. Example : public class Books {           @CustomAnnotation(value = "myBook")     public void updateBookDetail() {         ...
Post a Comment
Read more

Kafka And Zookeeper SetUp

 Kafka And Zookeeper SetUp zookeeper download Link : https://www.apache.org/dyn/closer.lua/zookeeper/zookeeper-3.8.3/apache-zookeeper-3.8.3-bin.tar.gz Configuration: zoo.conf # The number of milliseconds of each tick tickTime =2000 # The number of ticks that the initial # synchronization phase can take initLimit =10 # The number of ticks that can pass between # sending a request and getting an acknowledgement syncLimit =5 # the directory where the snapshot is stored. # do not use /tmp for storage, /tmp here is just # example sakes. dataDir =/tmp/zookeeper # the port at which the clients will connect clientPort =2181 4 char whitelist in command arguments 4lw.commands.whitelist =* Start ZooKeeper Server $ bin/zkServer.sh start Check zookeeper status dheeraj.kumar@Dheeraj-Kumar bin % echo stat | nc localhost 2181 stat is 4 character whitelisted argument  Check Kafka running status : echo dump | nc localhost 2181 | grep broker Responsibility of Leader in Zookeeper: 1. Distrib...
Post a Comment
Read more

Auto retries in REST API clients On Java On Ease

  Writing REST clients to consume API endpoints has become commonplace. While consuming REST endpoints, we sometimes end up in a situation where a downstream service throws some kind of transient error that goes away when the API call is retried. In such situations, we ask ourselves — “What if my API client was smart enough that knew how to retry a failed call?” Some of us go the extra mile to implement our own custom code that can retry API calls on error. But mind you, it is not only about knowing how to retry. The client also has to know when to retry and when not to. If the error is irrecoverable such as 400 — Bad Request, there is no point in retrying. It might also have to know how to back off and how to recover from the error. Implementing all this by hand, and then repeating it over and over again in every API client is cumbersome. It also adds a lot of boilerplate code and makes things even worse. But if you are a Spring/Spring Boot developer, you will be surprised to know...
Post a Comment
Read more