i installed jetty (distribution-9.0.2) on ubuntu server 12.04
from these links step by step
http://degreesofzero.com/article/19
http://pietervogelaar.nl/ubuntu-12-04-install-jetty-9/
at last when i start jetty with the following command:
sudo /etc/init.d/jetty start
or
sudo service jetty start
i get the following error
Starting Jetty: grep: /var/run/jetty.state: No such file or directory
I'm facing with the same problem but on Debian 6 server. Workaround for this problem and articles above, from my perspective, is:
use JETTY_ARGS=jetty.port=8080 instead JETTY_PORT
Add property to /etc/init.d/jetty: JETTY_PID=/opt/jetty/jetty.state
Please, let me know if you have any questions
I've tested this thoroughly with the latest release of jetty and it's working fine. There's been some changes recently in the jetty.sh script. However the changes look good to me and it's working fine for me with the latest release.
Evgenly is right, that JETTY_PORT is deprecated (see comments in jetty.sh for details), however it also works fine for me using JETTY_PORT instead of JETTY_ARGS to define a non standard port.
Please try the latest release from here in case you didn't do already:
http://download.eclipse.org/jetty/
If jetty.sh reports that the start failed, you'll usually find the reason in stderrout.log inside the JETTY_HOME/logs directory (unless you've changed the logging config).
Related
I am experiencing a problem with codesigning on Mac OSX (Catalina and older), that I cannot find any answer for. I do have a *.component file, that I am codesigning and notarizing with my Apple Developer ID, which is working perfect. As a post-install step on the target machine, I need to include some installation info within the component's Info.plist (so I am writing back to that *.plist file), which would then qualify as a manipulation of the component itself - ergo, the component's signing is going to be corrupt at this point (the host software will not load my software any more).
So I was trying to follow some advice and do a "blind" codesigning as additional post-install step on the user's machine with:
sudo codesign --force --deep -s - ABC.component
This was just working perfect for a few users, just when I found out, not everyone can make use of this (especially older Mac OSX). Sometimes this command will just not result in a properly signed component. One of the users then found out, he had to update Xcode CL Tools, to sign the file. He went:
xcode.select --install
I have tested this with several other users and it worked with them, too.
Here comes the issue:
As a result, I need to make sure, the user has installed the right version of Xcode Command Line Tools, but a lot of my clients do install on an offline device - so I would not be able to have xcode-select --install as a post-install step (because no internet connection).
Is it somehow possible to bundle the proper Xcode Command Line Tools into my installer and make use of it? Or do you see any other solution for the whole problem?
This is somewhat embarrassing, but I'm totally lost when it comes to upgrading from Jetty 9.2 to 9.4. 9.2 was installed two years ago using jetty-9.2.0-setup-package.zip. The file contained commons-deamon and more so that the install could be done using command
create-jetty-dist.bat d:\jetty9 Jetty9 80 50001 D:\etc\gateway NO
Now I've downloaded the latest version from https://www.eclipse.org/jetty/download.html]1 - jetty-distribution-9.4.14.v20181114.zip - but, I cannot figure out how to upgrade the installation. Mostly I find docs about Maven and update the POM, but the installation is standalone and no Maven. There is a Chapter 36. Upgrading Jetty about upgrading - but still does not help much
All my Google-skills does not help either.
I have not found the guts yet to simply replace the folder
D:\jetty9\jetty
Maybe I do overthink and the solution is that simple. But still it keeps bugging me that I cannot seem to find an install file for 9.4 like I did for 9.2
I did overthink - is was almost only to replace the 9.2 distribution folder with the 9.4. But for the service to be reconfigured and also to ensure that all changes from 9.2 to 9.4 was implemented me and my colleague had to do:
Edit the .bat file that came with the jetty-9.2.0-setup-package to support 9.4
Off course change the reference for all 9.2 to 9.4 distribution in the script
9.2 used "logging", 9.4 uses "console-capture"
9.2 used "jetty.port", 9.4 uses "jetty.http.port"
Copy the 9.4 distribution file to the folder where the .bat-file is to be found in the setup-package
Then we sc delete jetty9 the service and ran the script.
In short, that was what we needed to do.
While helping my friend spin up MinGW and a C++ environment on his Windows 8 computer, I ran the get-mingw script and waited as it ran through all the mirrors for required downloads. However, three downloads completely failed:
libltdl - installer script hung and then moved on after pressing "OK"
automake-1.11 - installer script tried finding 1.10, then 1.9, then 1.8, then 1.7 (all of which failed) until finally settling on 1.6
mktemp - script hung and moved on after pressing "OK"
In all three cases, the script gave me a nice error log upon completion, showing that a majority of packages had been downloaded and installed except for these three, which showed up as errors. However during the installation process I had simply gone to the MinGW sourceforge page and manually found and downloaded each .bin.tar.lzma file that was missing.
Now that I have them, is there a good accepted way to unpack and plug them into my friend's existing MinGW install? In case it's tough, I'm comfortable with unix and dos command line so I'll be able to move executables into the MinGW/bin folder if that's what's needed, I just want to check for the best way to 'fix' the install.
As a side note - even though the error log says these are required packages, adding MinGW/bin/ to the PATH still allows for use of gcc and g++, although not make (possibly because of automake failure?). Is this standard behavior?
Firstly, the package issue can be fixed by using the MinGW installer - keep the packages selected and go to "apply changes" and the script will probably try to redownload the missing packages. I think the original problem was probably just a shoddy wifi connection during repository connection.
However, I then ran into a problem where I tried to run gcc and it gave me a missing -lpthread error ... but this question was able to help me fix that, and gcc and g++ are working fine now (haven't opened and tested Eclipse yet though). Just in case of link decay, the issue I cited arises from the MinGW installer script not downloading the lpthread library upon installation. To fix that issue, quoted from link:
Just run and open MinGW Installation Manager, which should be pre-installed with MinGW, select "All Packages" on the left panel, and on the right panel, search for "mingw32-pthreads-w32" packages and install them.
I think the Installation Manager has libpthread and pthread available for install, and pthread libs were the ones that seemed to solve it for me.
I am trying to build syntaxnet using bazel without root rights. I have downloaded bazel 0.2.2b and pulled the syntaxnet git repository as suggested on its website. I have managed to pass the new gcc for the bazel build and set my environment variables to include the local gcc as well as my local python version (2.7). I also added swig and jdk to PATH. Still, I get the following error when trying to run bazel test syntaxnet/... util/utf8/...:
INFO: Found 65 targets and 12 test targets...
ERROR: /home/davba/.cache/bazel/_bazel_debauscd/33ff1ccf943e8d1167bc44c81c9ea8f4/external/org_tensorflow/tensorflow/python/BUILD:1023:1: output 'external/org_tensorflow/tensorflow/python/pywrap_tensorflow.cc' was not created.
ERROR: /home/davba/.cache/bazel/_bazel_debauscd/33ff1ccf943e8d1167bc44c81c9ea8f4/external/org_tensorflow/tensorflow/python/BUILD:1023:1: output 'external/org_tensorflow/tensorflow/python/pywrap_tensorflow.py' was not created.
ERROR: /home/davba/.cache/bazel/_bazel_debauscd/33ff1ccf943e8d1167bc44c81c9ea8f4/external/org_tensorflow/tensorflow/python/BUILD:1023:1: not all outputs were created.
After that, none of the tests are run which means all twelve tests are skipped. Any ideas are highly appreciated.
Edit: I have realized that I used an old version of protobuf. Unfortunately, the problem remains even after updating.
Since it seems to be a python related problem and I had built python from source, I tried to use anaconda but ended up with the same error.
Some more information: I am using CentOS 6.5 and tried python 2.7.11.
I set the environment variables as follows and changed the CROSSTOOL file for building bazel accordingly:
CXX=/soft/csw/linux64/rel6/gccs-4.8.5/bin/c++
CC=/soft/csw/linux64/rel6/gccs-4.8.5/bin/gcc
LDFLAGS="-L/soft/csw/linux64/rel6/gccs-4.8.5/lib -L/soft/csw/linux64/rel6/gccs-4.8.5/lib64":"-L/home/davba/syntaxnet-utils/pcre/lib"
CXXFLAGS="-L/soft/csw/linux64/rel6/gccs-4.8.5/lib -L/soft/csw/linux64/rel6/gccs-4.8.5/lib64"
LD_LIBRARY_PATH=/soft/csw/linux64/rel6/gccs-4.8.5/lib:/soft/csw/linux64/rel6/gccs-4.8.5/lib64:/home/davba/AnacondaPython/lib:$LD_LIBRARY_PATH
SWIG_PATH=/home/davba/syntaxnet-utils/compiled-swig/bin
Thanks!
I tried running it on a different machine with CentOS 7.0, but wound up with the same error.
Finally, I had the opportunity to switch to an Ubuntu machine with sudo rights which enabled me to run the bazel installer and compile syntaxnet without a problem. This solves the problem in my case. For a "real" fix I think we have to wait for someone experiencing the same issue.
I purchased a network card to give a separate network to my virtual machine. My host OS is Ubuntu 14.04 . Also i need to mount the USB to my virtual machine and not my host OS, so i downloaded extension pack version 5.0.2 for Vbox-5.0 . While installing virtual box extension pack, there were two VM's running and i got this popup.
Failed to install the Extension Pack /home/aniket/Downloads/Oracle_VM_VirtualBox_Extension_Pack-5.0.20-106931.vbox-extpack.
Failed to load the main module ('/usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxPuelMain.so'): VERR_FILE_NOT_FOUND - /usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxPuelMain.so: undefined symbol: RTLogRelGetDefaultInstanceEx.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ExtPackManager
Interface: IExtPackManager {3295e6ce-b051-47b2-9514-2c588bfe7554}
Even after power off of VM's and restarting the host OS, I get this similar error code.
Sorry if you think the question is not formatted properly or any other issue with my question. This is my second post, please tell me if there are any things i need to correct in my question.
Thanks in Advance.
After lot of test and trial, the solution I found that the extension pack was not compatible and hence I had to download the compatible version of the virtualbox I am running on.
What happened was this, I was running virtualbox-5.0 and the version I was trying to install was 5.0.20 .
You can check your version by clicking on Help and then About Virtualbox and download the exact compatible extension pack, else it will through the same hex error code 0x80004005 which means file not found.
Run vboxmanage command with sudo, i.e.:
sudo vboxmanage extpack install Oracle_VM_VirtualBox_Extension_Pack-5.1.22-115126.vbox-extpack --replace
From:
https://www.virtualbox.org/ticket/17034
I uninstalled virtualbox,then reinstall it. After this the extension pack got installed successfully. My version is `5.1.12 r112440 (Qt5.6.2)
I encounter this problem again, but this time I disable my antivirus software(mcafee), that is ok. refer by https://www.virtualbox.org/ticket/7972