hadoop-2.7.5 hbase1.2.6 spark flume cygwin - apache-spark

While starting hbase I'm getting the following error.
sh start-hbase.sh
: Name or service not knownstname 127.0.0.1
starting master, logging to /usr/local/hbase-1.2.6/bin/../logs/hbase-manou-master-asus.out
starting regionserver, logging to /usr/local/hbase-1.2.6/bin/../logs/hbase-manou-1-regionserver-asus.out
1 [main] bash 6772 fork: child -1 - forked process 8656 died unexpectedly, retry 0, exit code 0xC0000142, errno 11
/usr/local/hbase-1.2.6/bin/hbase-config.sh: fork: retry: Resource temporarily unavailable
What do I need to look at for this issue?
I'm using windows and cygwin for installation

Related

How to get a basic direvent watcher working?

I have read through the direvent documentation and am trying to get a simple watch working. Since I am having so much trouble with it, I am wondering if the issue has to do with the fact that the system I am using is nixos.
Here is the simple watcher file, watcher, I've created:
watcher {
path ./dir;
command "echo $file";
}
I run it in the foreground, so I can see the output, with direvent --foreground watcher. Once it's running, I create a file in dir, thus creating an event for it to respond to. However, it fails with the following output:
$ direvent --foreground watcher
direvent: [INFO] direvent 5.2 started
direvent: [ERROR] process 8552 failed with status 127
direvent: [ERROR] process 8555 failed with status 127
direvent: [ERROR] process 8557 failed with status 127
Since 127 usually means 'command not found', I tried specifying the path to echo, i.e. running this watcher instead:
watcher {
path ./dir;
command "/run/current-system/sw/bin/echo $file";
}
Then the output still gives an error, albeit a different one:
$ direvent --foreground watcher
direvent: [INFO] direvent 5.2 started
direvent: [ERROR] process 8645 failed with status 1
direvent: [ERROR] process 8651 failed with status 1
direvent: [ERROR] process 8652 failed with status 1
So the failure is now with status 1. I am not sure what to try next. I'm wondering if this issue is due to the fact that I am running nixos. Anyone know what I might try next to get direvent working?
direvent has two other flag that may be useful for you.
--debug(-d) to give extra information.
There's also --lint(t) that check the configuration file for errors, but I suspect this isn't your issue if direvent is running.
Source: https://www.gnu.org.ua/software/direvent/manual/direvent.html

mpirun launching a runtime script for thread binding

Running a program in a MPI process, which exec file is myapp_mpi. The command line below launches the app correctly
mpirun --bind-to none -np 128 myapp_mpi apprun -resethway -noconfout -nsteps 8000 -s benchData.tpr -cpo state.cpt -e ener.edr -dlb no -pin off -v
I now wish to constrain the thread binding with a script pin.sh. The command line below would then produce an error.
mpirun --bind-to none -np 128 pin.sh myapp_mpi apprun -resethway -noconfout -nsteps 8000 -s benchData.tpr -cpo state.cpt -e ener.edr -dlb no -pin off -v
I get the following error
--------------------------------------------------------------------------
Open MPI tried to fork a new process via the "execve" system call but
failed. Open MPI checks many things before attempting to launch a
child process, but nothing is perfect. This error may be indicative
of another problem on the target host, or even something as silly as
having specified a directory for your application. Your job will now
abort.
Local host: machine001
Working dir: /home/user/myapp/bin
Application name: /home/user/myapp/bin/pin.sh
Error: Exec format error
--------------------------------------------------------------------------
mpirun: Forwarding signal 18 to job
mpirun: Forwarding signal 18 to job
--------------------------------------------------------------------------
mpirun was unable to start the specified application as it encountered an
error:
Error code: 1
Error name: (null)
Node: machine001
when attempting to start process rank 0.
--------------------------------------------------------------------------
125 total processes failed to start
File locations are good, a priori. Any clue ?

How to avoid died waiting for dll loading, errno 11 - Win10

I am installing Babun(http://babun.github.io/) to run tmux on Windows 10.
unfortunately, when I am updating Cygwin through update.bat file from the Babun installed folder I am getting below whole message.
While going through some other posts, people are referring to Git, etc , which I do not have anyway.
I had this working on my Win7 laptop, but in office we are forced to switch to win10.
3 [main] -zsh 11180 fork: child 13276 - died waiting for dll loading, errno 11
/usr/local/etc/babun.start:4: fork failed: resource temporarily unavailable
/home/jchadala/.oh-my-zsh/oh-my-zsh.sh:3: command not found: env
/home/jchadala/.oh-my-zsh/lib/theme-and-appearance.zsh:9: command not found: uname
/home/jchadala/.oh-my-zsh/lib/theme-and-appearance.zsh:13: command not found: uname
4439101 [main] -zsh 11180 fork: child 15760 - died waiting for dll loading, errno 11
/home/jchadala/.oh-my-zsh/lib/theme-and-appearance.zsh:18: fork failed: resource temporarily unavailable
compdump:136: command not found: mv
$fg[blue]{ dist } \
$fg[green]$( git rev-parse --abbrev-ref HEAD 2> /dev/null || echo "" )$reset_color \
$fg[red]ยป$reset_color $fg[blue]/cygdrive/c/Users/jchadala/.babun/dist$reset_color ${return_code}
Also if you have any other suggestions to use tmux in windows also is helpful.

Akonadi server does not start

I just upgraded from Ubuntu 14.04 to Ubuntu 16.04. On 16.04 the Akonadi server does not start. I need it for running kMail my mail client. The output I get:
akonadictl start
Is:
starting Akonadi Server...
done.
And then:
$ Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths: ("/home/peter/.sdkman/candidates/grails/current/bin", "/opt/jdk1.7.0_79/bin", "/opt/apache-tomcat-8.0.32/bin", "/usr/local/sbin", "/usr/local/bin", "/usr/sbin", "/usr/bin", "/sbin", "/bin", "/usr/games", "/usr/local/games", "/snap/bin", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin")
Found mysql_install_db: "/usr/bin/mysql_install_db"
Found mysqlcheck: "/usr/bin/mysqlcheck"
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld-akonadi"
arguments: ("--defaults-file=/home/peter/.local/share/akonadi/mysql.conf", "--datadir=/home/peter/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-peter.JeGtpj/mysql.socket")
stdout: ""
stderr: ""
exit code: 1
process error: "Unknown error"
terminating service threads
terminating connection threads
stopping db process
Failed to remove Unix socket
Failed to remove runtime connection config file
Application 'akonadiserver' exited normally...
Peter

What causes BitBake worker processes to exit unexpectedly?

I have a BitBake build process that runs on a Docker container (CentOS 7). The BitBake fails during recipe gcc-cross-i586-5.2.0-r0: task do_compile on each run that I try it in.
An example of bitbake's output:
NOTE: recipe gcc-cross-i586-5.2.0-r0: task do_compile: Started
ERROR: Worker process (367) exited unexpectedly (-9), shutting down...
ERROR: Worker process (367) exited unexpectedly (-9), shutting down...
ERROR: Worker process (367) exited unexpectedly (-9), shutting down...
ERROR: Worker process (367) exited unexpectedly (-9), shutting down...
NOTE: Tasks Summary: Attempted 1538 tasks of which 17 didn't need to be rerun and all succeeded.
Is this a problem with recipe gcc-cross-i586-5.2.0-r0: task do_compile? Perhaps an out-of-memory error? I don't know what the -9 refers to or how to find out more information about it.
Try:
$ bitbake -c cleansstate gcc-cross ; bitbake -k gcc-cross
How much you have memory of ram?
Report log error here.
This worked for me,
Edit conf/local.conf and decrease the number of working threads by adding the following to you conf/local.conf file (under the build directory):
BB_NUMBER_THREADS = "6"
Just a long shot, -9 in kernel land means EBADF (bad file number.) Is it possible you have done some operations as root and some files are not accessible during the build? Is the issue reproducible? ie. can you rm -rf tmp and does it happen again? Make sure you don't have any permissions issues in your project directory and associated file system(s).

Resources