I am trying to configure eJabberd on my server.
I have installed all dependencies and other needed things. ERL also installed success fully through RPM with run result
root#sXX-XX-XX-XX [~]# erl -smp disable
Erlang/OTP 18 [erts-7.1] [source-2882b0c] [64-bit] [async-threads:10] [hipe] [kernel-poll:false]
Eshell V7.1 (abort with ^G)
1>
For final installation of eJabberd i have followed below link :
http://docs.ejabberd.im/admin/guide/installation/
I have tried make clean also for it and after try ./configure --enable-mysql than also i am facing continue below error.
root#sXX-XX-XX-XX [/etc/ejabberd_downloads/ejabberd]# ./configure
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for a sed that does not truncate output... /bin/sed
checking for erl... /usr/bin/erl
checking for erlc... /usr/bin/erlc
checking for erl... /usr/bin/erl
checking for erlc... /usr/bin/erlc
checking Erlang/OTP version...
Crash dump is being written to: erl_crash.dump...
Failed to create aux thread
./configure: line 2523: 1636 Aborted $ERLC conftest.erl
configure: error: "Could not compile Erlang/OTP version check program using '/usr/bin/erlc'"
For erl_crash.dump few lines as below from top
=erl_crash_dump:0.3
Thu Nov 19 01:31:57 2015
Slogan: Failed to create aux thread
System version: Erlang/OTP 18 [erts-7.1] [source-2882b0c] [64-bit] [smp:64:24] [async-threads:0] [hipe] [kernel-poll:false]
Compiled: Wed Sep 23 15:34:00 2015
Taints:
Atoms: 2005
Calling Thread: beam.smp
=scheduler:1
Scheduler Sleep Info Flags: SLEEPING | TSE_SLEEPING
Scheduler Sleep Info Aux Work: SET_TMO
Current Port:
Run Queue Max Length: 0
Run Queue High Length: 0
Run Queue Normal Length: 1
Run Queue Low Length: 0
Run Queue Port Length: 0
Run Queue Flags: NONEMPTY_NORMAL | NONEMPTY
Current Process:
=scheduler:2
which erl result as below :
/usr/bin/erl
I am not able to trace the issue, Any reference will be very helpful. Thanks in advence.
It seems that your Erlang version is corrupted or Old, Reinstall it and try again. For Ejabberd 16.x version 6.1 (Erlang/OTP 17.1) is required.
You can uninstall Erlang with following command:
$ sudo apt-get purge erlang*
And install latest Erlang from http://www.erlang.org/
Related
Overall, I am trying to render images using Unity on a remote cluster.
The cluster does not have an X server; I don't have sudo permissions, or can start a Docker container, but I can start a Singularity container.
My plan is to create a container that would simulate the X Server. I created the following Singularity definition file:
Bootstrap: docker
From: nvidia/cuda:10.1-cudnn7-devel-ubuntu18.04
%post
# xvfb for rendering in headless mode
apt-get update
apt-get install -y xvfb mesa-utils xorg
echo "allowed_users = anybody" > /etc/X11/Xwrapper.config
I started the container with the option --containall. From the container, I launched the command /usr/bin/X :0, but it failed with the following error:
Singularity xvfb.sif:~> /usr/bin/X :0
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.15.0-140-generic x86_64 Ubuntu
Current Operating System: Linux cooper 5.8.0-50-generic #56~20.04.1-Ubuntu SMP Mon Apr 12 21:46:35 UTC 2021 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
Build Date: 08 April 2021 01:57:21PM
xorg-server 2:1.19.6-1ubuntu4.9 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/pierre-louis/.local/share/xorg/Xorg.0.log", Time: Wed May 26 09:17:05 2021
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (No such file or directory)
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/home/pierre-louis/.local/share/xorg/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
Not any /dev/tty* exist. Then I tried to launch startx, but only to get the same message error.
How can I launch an X Server using a Singularity image?
As mentioned in a separate discussion, Xvfb is not supposed to be start through startx or /usr/bin/X but rather with the supplied run script.
I recently installed OpenMPI version 2.0 on my SGE cluster. But when I submit a job I get "Host ket verification failed". Even though I'm able to login to that node(compute10) without the password from the submit host.
The error in the output file:
Warning: no access to tty (Bad file descriptor). Thus no job control
in this shell. Wed Jan 30 15:58:53 EST 2019 Host key verification
failed. [file orca_main/gtoint.cpp, line 137]: ORCA finished by error
termination in ORCA_GTOInt
My SGE script is below:
!/bin/tcsh
$ -q sge-queue#compute10
$ -pe mpi 8
$ -V
$ -cwd
$ -j y
$ -l h_vmem=64G
date
setenv OMP_NUM_THREADS 8
/home/user/orca_4_0_1_2_linux_x86-64_openmpi202/orca ccl3.inp >
ccl3.out
date
And my parallel environment mpi:
pe_name mpi
slots 999
user_lists NONE
xuser_lists NONE
start_proc_args /export/sge6.2_U7/mpi/startmpi.sh -catch_rsh
$pe_hostfile
stop_proc_args /export/sge6.2_U7/mpi/stopmpi.sh
allocation_rule $pe_slots
control_slaves TRUE
job_is_first_task FALSE
urgency_slots min
accounting_summary TRUE
After trying various things, updating OpenMPI to 3.1.0 version and building with the options below solved the issue.
./configure --prefix=/usr/local --with-sge
--enable-orterun-prefix-by-default
Just installed Docker CE following official instructions with the repository in Ubuntu 14.04
Installation went successfully, the daemon is running
$ ps aux | grep docker
[...] /usr/bin/dockerd --raw-logs [...]
My user is in the docker group:
$ groups
[...] docker
The cli can't seem to communicate (same with sudo)
$ docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock.
Is the docker daemon running?
The socket seems to have the correct permissions:
$ ls -l /var/run/docker.sock
srw-rw---- 1 root docker 0 Feb 4 16:21 /var/run/docker.sock
The log seems to claim about some issues though
$ sudo tail -f /var/log/upstart/docker.log
Failed to connect to containerd: failed to dial "/var/run/docker/containerd/docker-containerd.sock": dial unix:///var/run/docker/containerd/docker-containerd.sock: timeout
/var/run/docker.sock is up
time="2018-02-04T16:22:21.031459040+01:00" level=info msg="libcontainerd: started new docker-containerd process" pid=17147
INFO[0000] starting containerd module=containerd revision=89623f28b87a6004d4b785663257362d1658a729 version=v1.0.0
INFO[0000] setting subreaper... module=containerd
containerd: invalid argument
time="2018-02-04T16:22:21.056685023+01:00" level=error msg="containerd did not exit successfully" error="exit status 1" module=libcontainerd
Any advice to make this work ?
Relog and Docker restart already done of course
As #bobbear suggested and is actually mentioned in the official doc one of the prerequisites is:
Version 3.10 or higher of the Linux kernel. The latest version of the kernel available for you platform is recommended.
After having checked my Kernel version:
$ uname -a
Linux [...] 3.2.[...]-generic [...]-Ubuntu [...] x86_64
I searched for candidates:
$ apt-cache search linux-image
And installed my new_kernel:
$ sudo apt-get install \
linux-image-new_kernel \
linux-headers-new_kernel \
linux-image-extra-new_kernel
Same situation happend on me. IS because your linux kernel version too low !!! check it use command "uname -r" , if the version below "3.10" (for example: debian 7 whezzy default version is 3.2 ) ,even you install docker-ce suceessfully, you will still can not start docker daemon success.That why! All most answers on the web tell you to 'restart' bla bla bla... but they did not consider this problem.
i'm used ubuntu 14.04 lts
.and，the module already download
1:Keyboard input
$ sudo -s cpan SDL 1>stdout.txt 2>stderr.txt
stdout.txt:
1 Reading '/home/freakcoco/.cpan/Metadata'
2 Database was generated on Fri, 04 Sep 2015 16:29:02 GMT
3 Running install for module 'SDL'
4 Checksum for /home/freakcoco/.cpan/sources/authors/id/F/FR/FROGGS/SDL-2.546.tar.gz ok
5 ---- Unsatisfied dependencies detected during ----
6 ---- FROGGS/SDL-2.546.tar.gz ----
7 Alien::SDL [build_requires]
8 Running install for module 'Alien::SDL'
9 Checksum for /home/freakcoco/.cpan/sources/authors/id/F/FR/FROGGS/Alien-SDL-1.446.tar.gz ok
10 Configuring F/FR/FROGGS/Alien-SDL-1.446.tar.gz with Build.PL
11 Welcome to Alien::SDL module installation
12 -----------------------------------------
13 checking operating system... linux
14 checking for cc... yes
15 checking build system type... x86_64-linux-gnu-thread-multi
16 checking platform specific module... using 'My::Builder::Unix'
17 Warning: No success on command[/usr/bin/perl Build.PL --installdirs site]
18 FROGGS/Alien-SDL-1.446.tar.gz
19 /usr/bin/perl Build.PL --installdirs site -- NOT OK
20 FROGGS/SDL-2.546.tar.gz
21 Has already been unwrapped into directory /home/freakcoco/.cpan/build/SDL-2.546-1przxQ
22 Warning: Prerequisite 'Alien::SDL => 1.446' for 'FROGGS/SDL-2.546.tar.gz' failed when processing 'FROGGS/Alien-SDL-1.446.tar.gz' with 'writemakefile => NO '/usr/bin/perl Build.PL --installdirs site' returned status 512'. Continuing, but chances to succeed are limited.
23 Configuring F/FR/FROGGS/SDL-2.546.tar.gz with Build.PL
24 Warning: No success on command[/usr/bin/perl Build.PL --installdirs site]
25 FROGGS/SDL-2.546.tar.gz
26 /usr/bin/perl Build.PL --installdirs site -- NOT OK
stderr.txt:
1 Unknown option: installdirs
2 Too early to specify a build action 'site'. Do 'Build site' instead.
3 Can't locate Alien/SDL.pm in #INC (you may need to install the Alien::SDL module) (#INC contains: inc /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at Build.PL line 12.
4 BEGIN failed--compilation aborted at Build.PL line 12.
2:Keyboard input (install the Alien::SDL module)
$ sudo -s cpan SDL 1>stdout2.txt 2>stderr2.txt
stdout2.txt
1 Reading '/home/freakcoco/.cpan/Metadata'
2 Database was generated on Fri, 04 Sep 2015 16:29:02 GMT
3 Running install for module 'Alien::SDL'
4 Checksum for /home/freakcoco/.cpan/sources/authors/id/F/FR/FROGGS/Alien-SDL-1.446.tar.gz ok
5 Configuring F/FR/FROGGS/Alien-SDL-1.446.tar.gz with Build.PL
6 Welcome to Alien::SDL module installation
7 -----------------------------------------
8 checking operating system... linux
9 checking for cc... yes
10 checking build system type... x86_64-linux-gnu-thread-multi
11 checking platform specific module... using 'My::Builder::Unix'
12 Warning: No success on command[/usr/bin/perl Build.PL --installdirs site]
13 FROGGS/Alien-SDL-1.446.tar.gz
14 /usr/bin/perl Build.PL --installdirs site -- NOT OK
stderr2.txt:
1 Unknown option: installdirs
2 Too early to specify a build action 'site'. Do 'Build site' instead.
This might be a bug in Alien::SDL and its use of Getopt::Long (a similar issue was fixed here).
You can try this workaround:
If you run sudo cpan and in that shell o conf mbuildpl_arg, you should get something like this:
mbuildpl_arg [--installdirs site]
Type 'o conf' to view all configuration items
If that is the case, run o conf mbuild_arg installdirs=site (which should output mbuildpl_arg [installdirs=site]), then o conf commit, then exit the cpan shell. I believe that should bypass the option parsing issue.
I found that removing my .cpan folder and reinstalling Module::Build before Alien::SDL resoleved this problem:
rm -rf ~/.cpan
I am trying to use oprofile 0.9.8 under Ubuntu 12.10 running on a Pentium D processor (Dell OptiPlex-GX620 desktop). When I try something simple like "operf ls" I get
perf_event_open failed with Invalid argument
Caught runtime_error: Internal Error. Perf event setup failed.
Error running profiler
I have success running oprofile in legacy mode using opcontrol commands under sudo by installing the module with timer=1 (see below).
It appears that operf is unhappy in this configuration - which is the new preferred method.
I have verified that all the dependent packages are loaded.
On the oprofile website they do not call out pentium D as a seperate architucture so not sure if it is using regular Pentium architecture.
I have searched everywhere and can't find anything like this reported. Any help would be appreciated in identifying the problem here.
P.S. When I run with legacy mode using opcontrol I have some success:
denham#denham-OptiPlex-GX620:~$ sudo opcontrol --start
ATTENTION: Use of opcontrol is discouraged. Please see the man page for operf.
Using default event: GLOBAL_POWER_EVENTS:100000:1:1:1
Error: counter 0 not available nmi_watchdog using this resource ? Try:
opcontrol --deinit
echo 0 > /proc/sys/kernel/nmi_watchdog
**When I force the module to be installed with timer=1**
denham#denham-OptiPlex-GX620:~$ sudo opcontrol --deinit
Unloading oprofile module
denham#denham-OptiPlex-GX620:~$ sudo modprobe oprofile timer=1
denham#denham-OptiPlex-GX620:~$ sudo opcontrol --no-vmlinux
denham#denham-OptiPlex-GX620:~$ sudo opcontrol --start
ATTENTION: Use of opcontrol is discouraged. Please see the man page for operf.
Using 2.6+ OProfile kernel interface.
Using log file /var/lib/oprofile/samples/oprofiled.log
Daemon started.
Profiler running.
denham#denham-OptiPlex-GX620:~$ ./a
^C
denham#denham-OptiPlex-GX620:~$ sudo opcontrol --shutdown
Stopping profiling.
Killing daemon.
denham#denham-OptiPlex-GX620:~$ opreport --callgraph
Using /var/lib/oprofile/samples/ for samples directory.
warning: /no-vmlinux could not be found.
warning: [vdso] (tgid:1697 range:0xb77ab000-0xb77ac000) could not be found.
warning: [vdso] (tgid:1728 range:0xb77b6000-0xb77b7000) could not be found.
warning: [vdso] (tgid:3310 range:0xb7702000-0xb7703000) could not be found.
CPU: CPU with timer interrupt, speed 2992.41 MHz (estimated)
Profiling through timer interrupt
samples % image name app name symbol name
-------------------------------------------------------------------------------
31878 81.1868 no-vmlinux no-vmlinux /no-vmlinux
31878 100.000 no-vmlinux no-vmlinux /no-vmlinux [self]
-------------------------------------------------------------------------------
2820 7.1820 a a main
2820 100.000 a a main [self]
-------------------------------------------------------------------------------
1065 2.7123 vino-server vino-server /usr/lib/vino/vino-server
1065 100.000 vino-server vino-server /usr/lib/vino/vino-server [self]
-------------------------------------------------------------------------------
1056 2.6894 a a b
1056 100.000 a a b [self]
-------------------------------------------------------------------------------
1013 2.5799 a a c
1013 100.000 a a c [self]
-------------------------------------------------------------------------------
968 2.4653 a a d
968 100.000 a a d [self]
-------------------------------------------------------------------------------
264 0.6724 libc-2.15.so libc-2.15.so /lib/i386-linux-gnu/libc-2.15.so
. . . . .
Don't know if this is the main problem but the error message says -
"Error: counter 0 not available nmi_watchdog using this resource.
Try: opcontrol --deinit echo 0 > /proc/sys/kernel/nmi_watchdog".
To get rid of this you have to disable NMI watchdog kernel parameter. On Ubuntu it is done via grub -
Edit /etc/default/grub and add “nmi_watchdog=0” to the GRUB_CMDLINE_LINUX.
Then run sudo update-grub and check the value with
cat /proc/sys/kernel/nmi_watchdog (should be "0"). Reboot to install new config if needed.