I can run a repll and connect but when I try to Jack in I get the following error (shown in debug) - I am using emacs 26.1 on Mojave. I tried reinstalling spacemacs and updating clojure
Debugger entered--Lisp error: (error "Could not start nREPL server:
/usr/local/bin/lein: line 72: basename: command no$ signal(error
("Could not start nREPL server: /usr/local/bin/lein: line 72:
basename: command not found\n/usr/local/b$ error("Could not start
nREPL server: %s" "/usr/local/bin/lein: line 72: basename: command not
found\n/usr/local/bin/$ nrepl-server-sentinel(# "exited abnormally with code 127\n")
Related
I have installed Ambari using the steps as provided in
https://www.linkedin.com/pulse/installing-apache-ambari-20-ec2-centos-65-instance-using-debu-sinha
However ,I am not able to start ambari server as setup itself is giving me error for below command
ambari-server setup -v
File "/usr/lib/python2.6/site-packages/ambari_server/serverSetup.py", line 1013, in setup
retcode = extract_views()
File "/usr/lib/python2.6/site-packages/ambari_server/serverSetup.py", line 905, in extract_views
retcode, stdout, stderr = run_os_command(command)
File "/usr/lib/python2.6/site-packages/ambari_commons/os_utils.py", line 98, in run_os_command
return os_run_os_command(cmd, env, False)
File "/usr/lib/python2.6/site-packages/ambari_commons/os_linux.py", line 45, in os_run_os_command
shell=shell
File "/usr/lib/python2.6/subprocess.py", line 642, in __init__
errread, errwrite)
File "/usr/lib/python2.6/subprocess.py", line 1234, in _execute_child
raise child_exception
OSError: [Errno 8] Exec format error
Please help me on this , I am using Oracle VM VirtualBox with CentOs 6.5
The problem was that the default JDK libraries installed by ambari-server setup is 64Bit version and my VM was 32 Bit.
I skipped the Oracle JDK installation part and selected option 3 that is custome JDK and gave the JAVA_HOME path as that mentioned in PATH variable we can get it by doing following
echo $JAVA_HOME
After doing this,it worked fine.
I installed sbt in my windows 7 machine from http://www.scala-sbt.org/0.13/docs/Installing-sbt-on-Windows.html using msi installer
After installing if i go to Command prompt and while checking the installed sbt version i get the below error
C:\>sbt --version
Getting org.fusesource.jansi jansi 1.11 ...
:: problems summary ::
:::: WARNINGS
module not found: org.fusesource.jansi#jansi;1.11
==== local: tried
C:\Users\rajasure\.ivy2\local\org.fusesource.jansi\jansi\1.11\ivys\ivy
.xml
-- artifact org.fusesource.jansi#jansi;1.11!jansi.jar:
C:\Users\rajasure\.ivy2\local\org.fusesource.jansi\jansi\1.11\jars\jan
si.jar
==== Maven Central: tried
https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1
.11.pom
-- artifact org.fusesource.jansi#jansi;1.11!jansi.jar:
https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1
.11.jar
==== typesafe-ivy-releases: tried
https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/j
ansi/1.11/ivys/ivy.xml
==== sbt-ivy-snapshots: tried
https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi
/jansi/1.11/ivys/ivy.xml
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.fusesource.jansi#jansi;1.11: not found
::::::::::::::::::::::::::::::::::::::::::::::
:::: ERRORS
Server access Error: Connection timed out: connect url=https://repo1.mav
en.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
Server access Error: Connection timed out: connect url=https://repo1.mav
en.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
Server access Error: Connection timed out: connect url=https://repo.type
safe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
Server access Error: Connection timed out: connect url=https://repo.scal
a-sbt.org/scalasbt/ivy- snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
unresolved dependency: org.fusesource.jansi#jansi;1.11: not found
Error during sbt execution: Error retrieving required libraries
(see C:\Users\suren\.sbt\boot\update.log for complete log)
Error: Could not retrieve jansi 1.11
Could somebody help me on fixing this error? I really need some help on this.
I had the same problem! this solved!
" Looks like the dependency manager has a problem with the non-ASCII characters in your user name.
Try adding -Dsbt.global.base=C:/some/other/path to the command line of the SBT process. This will relocate files from the default location of %USERHOME%/.sbt. "
I've installed gdb as per the following steps:
brew install homebrew/dupes/gdb
follow instructions exactly as per http://sourceware.org/gdb/wiki/BuildingOnDarwin
However when I try run inside gdb, I get:
...
(gdb) run
Starting program: /Users/snowch/tmp/myc/main
/bin/bash: /Users/snowch/tmp/myc/main: Permission denied
/bin/bash: line 0: exec: /Users/snowch/tmp/myc/main: cannot execute: Undefined error: 0
During startup program exited with code 126.
I've tried reinstalling gdb and creating and signing with a new certificate. Still no joy.
Any ideas?
When running teaspoon, I'm getting the following errors:
rake teaspoon
Starting the Teaspoon server...
Teaspoon running default suite at http://127.0.0.1:64790/teaspoon/default
sh: line 25: `BASH_FUNC_set_shell_label%%': not a valid identifier
Teaspoon running insight suite at http://127.0.0.1:64790/teaspoon/insight
sh: line 25: `BASH_FUNC_set_shell_label%%': not a valid identifier
Teaspoon running wb5 suite at http://127.0.0.1:64790/teaspoon/wb5
sh: line 25: `BASH_FUNC_set_shell_label%%': not a valid identifier
I haven't yet been able to identify which file's line 25 is the problem.
I'm getting some very unusual behaviour.
I followed these instructions for installing jetty but used the latest version instead (9.1.1v20140108)
I had reason to restart Jetty and found I was getting these errors (logged in as root)
Starting Jetty: FAILED Wed Feb 5 12:35:59 EST 2014
So I spent 30 mins looking for an answer, then for reasons I can't recall, I did service jetty check and it was running (had a pid).
So I tried again with service Jetty stop:
root#erp:/var/log# service jetty stop
/etc/init.d/jetty: line 13: chkconfig:: command not found
/etc/init.d/jetty: line 14: description:: command not found
/etc/init.d/jetty: line 15: processname:: command not found
Stopping Jetty: start-stop-daemon: warning: failed to kill 7817: No such process
1 pids were not killed
No process in pidfile '/var/run/jetty.pid' found running; none killed.
OK
None killed? Ok. Let's check that:
root#erp:/var/log# service jetty check
/etc/init.d/jetty: line 13: chkconfig:: command not found
/etc/init.d/jetty: line 14: description:: command not found
/etc/init.d/jetty: line 15: processname:: command not found
Checking arguments to Jetty:
START_INI = /srv/jetty/start.ini
JETTY_HOME = /srv/jetty
JETTY_BASE = /srv/jetty
JETTY_CONF = /srv/jetty/etc/jetty.conf
JETTY_PID = /var/run/jetty.pid
JETTY_START = /srv/jetty/start.jar
JETTY_LOGS = /srv/jetty/logs
CLASSPATH =
JAVA = /usr/bin/java
JAVA_OPTIONS = -Dsolr.solr.home=/srv/solr -Djetty.state=/srv/jetty/jetty.state -Djetty.logs=/srv/jetty/logs -Djetty.home=/srv/jetty -Djetty.base=/srv/jetty -Djava.io.tmpdir=/tmp
JETTY_ARGS = jetty.port=8085 jetty-logging.xml jetty-started.xml
RUN_CMD = /usr/bin/java -Dsolr.solr.home=/srv/solr -Djetty.state=/srv/jetty/jetty.state -Djetty.logs=/srv/jetty/logs -Djetty.home=/srv/jetty -Djetty.base=/srv/jetty -Djava.io.tmpdir=/tmp -jar /srv/jetty/start.jar jetty.port=8085 jetty-logging.xml jetty-started.xml
No PID? Let's check that:
root#erp:/var/log# service jetty start
/etc/init.d/jetty: line 13: chkconfig:: command not found
/etc/init.d/jetty: line 14: description:: command not found
/etc/init.d/jetty: line 15: processname:: command not found
Starting Jetty: FAILED Wed Feb 5 12:39:43 EST 2014
Ok, is there a PID?
root#erp:/var/log# service jetty check
/etc/init.d/jetty: line 13: chkconfig:: command not found
/etc/init.d/jetty: line 14: description:: command not found
/etc/init.d/jetty: line 15: processname:: command not found
Checking arguments to Jetty:
[edit]
Jetty running pid=7993
Weird. Sure enough, a stop and check will give the same results.
What's going on with the jetty startup script? And why am I getting FAILED errors on start which are incorrect, and fail to remove pid errors on stop which are also incorrect?
I have got a fix for all those who have been using that tutorial to install jetty
nano /etc/init.d/jetty
And change this syntax :
start-log-file="$JETTY_LOGS/start.log"
to
start-log-file="start.log"
It will fix everything in the latest jetty build and make it run like a charm.
Hope I could be of help
Ok, so this was a tricky one that was the result of a recent Java update.
I jumped into the jetty.sh at /etc/init.d/jetty and grabbed out the actually executed line:
$ /usr/bin/java -Dsolr.solr.home=/srv/solr -Djetty.state=/srv/jetty/jetty.state \
-Djetty.logs=/srv/jetty/logs -Djetty.home=/srv/jetty -Djetty.base=/srv/jetty \
-Djava.io.tmpdir=/tmp -jar /srv/jetty/start.jar jetty.port=8085 \
jetty-logging.xml jetty-started.xml
and I got this:
java.io.IOException: Cannot read file: modules/npn/npn-1.7.0_51.mod
at org.eclipse.jetty.start.Modules.registerModule(Modules.java:405)
at org.eclipse.jetty.start.Modules.registerAll(Modules.java:395)
at org.eclipse.jetty.start.Main.processCommandLine(Main.java:561)
at org.eclipse.jetty.start.Main.main(Main.java:102)
Which in turn lead me to this solution on the eclipse dev list:
$ cp /srv/jetty/modules/npn/npn-1.7.0_45.mod /srv/jetty/modules/npn/npn-1.7.0_51.mod
$ chown jetty:jetty /srv/jetty/modules/npn/npn-1.7.0_51.mod
Sure enough, Jetty restarted without hassle.
Try running below command in terminal.
sudo service jetty9 stop
I run Jetty 9.2.10.v201503 on pcDuino v3, Ubuntu 14.04. According to my experience with this relatively slow platform, this message may be reported when Jetty server itself starts longer than internal waiting loop in /etc/init.d/jetty script expects.
After adding “set –x” at the beginning of /etc/init.d/jetty file and running that script I noticed that internal waiting loop is implemented as “for” making 15 steps and periodically checking content of the $JETTY_BASE/jetty.state file.
After waiting additional couple of seconds, Jetty server is up and running ok, no errors/warrnings in log files.