I am starting a TargetServer of jSCSI (http://jscsi.org/bundles/target/apidocs/org/jscsi/target/TargetServer.html) and I want to know how to check if it is initiated successfuly, than I can proceed doing other things.
Does anyone know how to check it?
Thanks a lot!
on linux you can install open-iscsi (the initiator) and check if the target is available to connect.
iscsiadm -m discovery -t sendtargets -p 127.0.0.1
Related
I tried to install authbind but getting below error,
Can anyone please help me to resolve this error.
There this project here : https://github.com/tootedom/authbind-centos-rpm
You can easely download this file with :
wget https://s3.amazonaws.com/aaronsilber/public/authbind-2.1.1-0.1.x86_64.rpm
and install it with :
rpm -Uvh https://s3.amazonaws.com/aaronsilber/public/authbind-2.1.1-0.1.x86_64.rpm
The previous answer by irrational won't work because that rpm is built against libc2.14 which is only on centos 7 not 6.
rpm -Uvh authbind-2.1.1-0.1.x86_64.rpm
error: Failed dependencies:
libc.so.6(GLIBC_2.14)(64bit) is needed by authbind-2.1.1-0.1.x86_64
I think you have to build the rpm yourself from the instructions at https://github.com/tootedom/authbind-centos-rpm
I'm having some trouble because the spec file appears to have some errors.
UPDATE:
step-by-step instructions:
svn co https://github.com/tootedom/authbind-centos-rpm.git
mkdir /root/rpmbuild
cp -R authbind-centos-rpm.git/trunk/authbind/* /root/rpmbuild/
cd /root/rpmbuild/SOURCES
wget http://ftp.debian.org/debian/pool/main/a/authbind/authbind_2.1.1.tar.gz
mv authbind_2.1.1.tar.gz authbind-2.1.1.tar.gz
cd ../
rpmbuild -v -bb --clean SPECS/authbind.spec
After all that fix up the rpm actually built and is now at:
/root/rpmbuild/RPMS/x86_64/authbind-2.1.1-0.1.x86_64.rpm
You can now install that using rpm -Uvh and have access to authbind like dem debian peeps.
I did this on centos 6.7 minimal os
I have Centos6, and was having trouble getting a version that would work. Perhaps my solution is just cutting the Gordian knot with a sword, but here goes.
I needed to do use authbind in the first place because I was trying to make Tomcat work on port 80. If that's why your messing with authbind, this should be especially helpful.
I also couldn't make Tomcat work with all the various authbind variations. The one thing that I did do that is worth reporting is that you can just get the gnu sources for authbind and build them and run them. They have supported ipv6 since 2012. If you are having trouble wrestling with distribution managers to make authbind work, including problems with glibc, this approach might be useful. As far as I can tell, authbind doesn't do anything that requires a new glibc, so this worked well, and authbind runs on my Centos 6 happily and without problems.
Keep in mind that this is Linux, sources are available, and sometimes it's easier just to rebuild something than try to get it from a distribution source, especially, as here, when the problem in getting established software like authbind to work with an old version of glibc.
So, First get the tarfile. I got it from:
http://ftp.debian.org/debian/pool/main/a/authbind/authbind_2.1.1.tar.gz
create a directory, then "tar xvf", and then do a "make all" and "make install"
However, the solution that worked for me (as I mentioned, I needed authbind in order to make port numbers less than 1024 available to tomcat), was simply to change the iptables, which I did as follows. (You can cut and paste this into a script if you want to save it for future reference.)
# check that rules are not there already
# note: you must be root; if you aren't do a su, or sudo before each line
iptables -L -n -t nat
# Add rules
iptables -t nat -I PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8080
iptables -t nat -I PREROUTING -p tcp --dport 443 -j REDIRECT --to-port 8443
# Check
iptables -L -n -t nat
# Save
service iptables save
iptables -L -n -t nat
Giving credit where it's due, this is described well (but with some errors that should be obvious) at
https://www.locked.de/how-to-run-tomcat-on-port-80/
Marklan
I have a Pi that runs hostapd and dhcpd on arch linux to create it's own land with the Pi's (routers) IP being 10.0.0.1. This uses the wlan0 interface and it only serves as a standalone router running a web server.
Once I connect to the Pi, I use 10.0.0.1 to display the web pages, but I want to use a hostname such as firepi. I have tried using dnsmasq, but I haven't been successful. Any help would be greatly appreciated especially if you can give me some detailed examples as I am a novice.
The purpose of this system is that I have created a web app that you can use to ignite fireworks over WiFi at a safe distance. I would just like the convenience of using a hostname instead of the IP address.
I must add that I will more than likely be using an iPhone to connect to the server, should this affect anything.
Not too sure how or why but this is what I did and it is successfully working now, so this is just for future users who may need a similar setup to mine.
First I installed hostapd and dhcpd and made sure they were working. Next I changed '/etc/hostname' to firepi and the '/etc/hosts' and added '10.0.0.1 firepi'. Then I installed dnsmasq, and set the interface to wlan0, and finally added '10.0.0.1 firepi' to '/etc/resolv.conf'.
After a full reboot, I joined the network on my iPhone, navigated to firepi and sure enough, it worked!
Thanks to the other users for their advice and tips.
You can use avahi on Arch as well to resolve your hostname:
sudo pacman -S avahi nss-mdns
Start the avahi daemon:
sudo systemctl enable avahi-daemon.service
sudo systemctl start avahi-daemon.service
Edit /etc/nsswitch.conf
sudo vim /etc/nsswitch.conf
Change the line:
hosts: files myhostname dns
to
hosts: files myhostname mdns_minimal [NOTFOUND=return] dns
Reboot
Note: don't forget to add .local to your hostname.
See also:
http://blog.pixxis.be/post/77285636682/resolve-hostname-with-arch-linux-on-a-raspberry-pi
If you just want to be able to use "firepi" as hostname to connect to it, you can simply add it to your /etc/hosts file using the syntax "IP host".
To make it as easy as possible, run this command as root:
echo "10.0.0.1 firepi" >> /etc/hosts
That'll do the trick.
Can you try avahi ?
sudo apt-get install avahi-daemon and
sudo apt-get install avahi-browse
I've successfully used that on Raspian. Unless you change the hostname using
sudo raspi-config you will access via raspberrypi.local
Note that if you plan to access the RPi from Windows you will need to install Bonjour Service first(if you have iTunes intalled, you might have those, run services.msc and check if the Bonjour Service is started)
Another note: On a friend's iphone I've installed a generic vnc client and had x11vnc running on the RPi and succesfully managed to connect to the RPi (since avahi-daemon was installed)
I'm not sure if this is more of a sysadmin question but in order to use x-debug, I have to run the following from my terminal everytime I boot up the machine.
setsebool httpd_can_network_connect=1
Does anyone know how I can make this permanent so that I don't have to run this command everytime I start my machine?
Thank you.
----EDIT----
setsebool -P httpd_can_network_connect=1
Now I can debug as soon as the machine boots thanks to Ulrich Schmidt-Goertz
Try running the command with the -P flag. That should make the setting permanent.
Usage: [options]
Options:
--help, -h Show this help message and exit.
--server=SERVER The server to use to determine the latest
-s SERVER SDK version.
--address=ADDRESS The address of the interface on the local machine
-a ADDRESS to bind to (or 0.0.0.0 for all interfaces).
--port=PORT The port number to bind to on the local machine.
-p PORT
--sdk_root=DIR Overrides where the SDK is located.
--disable_update_check Disable the check for newer SDK versions.
--generated_dir=DIR Set the directory where generated files are created.
--jvm_flag=FLAG Pass FLAG as a JVM argument. May be repeated to
supply multiple flags.
I had come across similar problem while working with Google App Engine for Python-loalhost was not getting its connection established.
$fuser -k 8080/tcp
Try this in terminal/command prompt and restart localhost.
It worked for me. Hope it works for you also. Good luck!
I am new to kony, Does anyone know how to restart the memcached server and location of start and stop files ? please help.
thanks
If you server running in Linux server use following comment
%KMAP_SERVER_HOME%\memcached\memcached -p 21201
if your server in windows
double click %KMAP_SERVER_HOME%\memcached\memcached.exe
Please make sure that your middle ware is memcache enabled.
to check your memcache status use following Linux comment
echo status | nc 21201