I am testing MongooseIM v.5.0.0 for my project.
I download the deb file for Ubuntu Xenial from this link
And I deployed it under Ubuntu 16.04 Xenial AMD in VM.
I haven't customized its config files and just simply run it. My problem is: after restarting my VM a few times, the MongooseIM doesn't want to start and throws an error like below
root#ubuntu:~# mongooseimctl foreground
Root: /usr/lib/mongooseim
Exec: /usr/lib/mongooseim/erts-12.1/bin/erlexec -noshell -noinput +Bd -boot
/usr/lib/mongooseim/releases/5.0.0/start -embedded -config /etc/mongooseim/app.config -
args_file /etc/mongooseim/vm.args -args_file /etc/mongooseim/vm.dist.args -- foreground
fips.c(139): OpenSSL internal error, assertion failed: FATAL FIPS SELFTEST FAILURE
/usr/bin/mongooseimctl: line 165: 856 Aborted
"$RUNNER_SCRIPT_DIR"/mongooseim foreground
I search for this error, but none seems to answer my problem.
Can anybody help me?
Related
Received the following message:
dpkg-deb: error: 'vagrant_2.3.4_x86_64.deb' is not a Debian format archive
dpkg: error processing archive vagrant_2.3.4_x86_64.deb (--install):
dpkg-deb --control subprocess returned error exit status 2
Errors were encountered while processing:
vagrant_2.3.4_x86_64.deb
While running the following command:
dpkg -i vagrant_$(echo $vagrant_latest_version)_x86_64.deb
I was trying to build a Virtual Machine inside my docker. (https://medium.com/axon-technologies/installing-a-windows-virtual-machine-in-a-linux-docker-container-c78e4c3f9ba1). I cannot get back to the docker since i closed the whole terminal.
How could i download or fix the file missing?
I am using Ubuntu 22.04 version on my Raspberry Pi 4B(RAM 8GB).
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
I tried to install Jenkins here and set it up, but if I do installation, the following error is confirmed.
$ sudo apt-get install -y jenkins
Reading package list... Completion
Creating dependency tree... Completion
Reading status information... Completion
We will install the next new package:
jenkins
Zero upgrades, one fresh installation, zero removal, and seven upgrades.
You must receive 0 bytes/92.9 M bytes of archive.
After this operation, 93.6 M bytes of disk space will be used.
Selecting previously unselected package jenkins.
(Reading database...)There are currently 224160 files and directories installed.)
Preparing to unpack .../jenkins_2.375.1_all.deb ...
Unpacking jenkins (2.375.1) ...
Setting jenkins (2.375.1)...
sed: -e expression 1st row, 65th character: invalid contrast character
Created symlink /etc/systemd/system/multi-user.target.wants/jenkins.service → /lib/systemd/system/jenkins.service.
Job for jenkins.service failed because a timeout was exceeded.
See "systemctl status jenkins.service" and "journalctl -xeu jenkins.service" for details.
invoke-rc.d: initscript jenkins, action "start" failed.
● ● jenkins.service - Jenkins Continuous Integration Server
Loaded: loaded (/lib/systemd/system/jenkins.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: timeout) since Thu 2022-12-15 22:49:44 KST; 24ms ago
Process: 459913 ExecStart=/usr/bin/jenkins (code=exited, status=143)
Main PID: 459913 (code=exited, status=143)
Status: "Jenkins stopped"
CPU: 3min 20.145s
dpkg: error processing package jenkins (--configure):
installed jenkins package post-installation script subprocess returned error exit status 1
There was an error processing:
jenkins
E: Sub-process /usr/bin/dpkg returned an error code (1)
I've tried many things, but I haven't found an answer yet.
If anyone has experienced or solved a similar phenomenon, could you tell me how to solve it?
① I deleted the package and reinstalled it, ② deleted the apt or dpkg cache, and tried to reinstall it, but the same error continues to appear.
In addition, ③ the same error occurs when performing the same operation after rebooting, and if force the Jenkins service to start while installed as above, java accounts for 99% of the CPU and waits indefinitely as shown.
As CPU occupancy continues, Jenkins moves to Bad Message 431.
I am relatively new to Arch Linux.
So i have been dealing with this issue for quite a long time now. I got this new RTL8188FTV wireless USB network adapter and i have tried installing the drivers for it with Paru AUR helper. The installation seems to fail, as it throws this error at the end :
==> ERROR: Missing 5.15.70-1-lts kernel modules tree for module 8188fu/r112.89d7288.
I can confirm the wireless adapter is functional, since it works on Windows
Package Name: 8188fu-kelebek333-dkms-git
Is there a way to install this "kernel modules tree" so i could finish the installation?
Thanks!
Edit: back with more errors
Building module:
Cleaning build area...
'make' all KVER=6.0.5-arch1-1.............(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.0.5-arch1-1 (x86_64)
Consult /var/lib/dkms/8188fu/r113.f5df53d/build/make.log for more information.
error: command failed to execute correctly
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Install DKMS modules
==> dkms install --no-depmod 8188fu/r113.f5df53d -k 6.0.5-arch1-1
Error! Bad return status for module build on kernel: 6.0.5-arch1-1 (x86_64)
Consult /var/lib/dkms/8188fu/r113.f5df53d/build/make.log for more information.
==> WARNING: `dkms install --no-depmod 8188fu/r113.f5df53d -k 6.0.5-arch1-1' exited 10
==> ERROR: Missing 5.15.75-1-lts kernel modules tree for module 8188fu/r113.f5df53d.
(3/3) Performing snapper post snapshots for the following configurations...
The command
echo 'alias usb:v0BDApF179d*dc*dsc*dp*icFFiscFFipFFin* rtl8188fu' | sudo tee /etc/modprobe.d/r8188eu-blacklist.conf
doesn't seem to do much.
Installation still fails.
Your on kernel 5.15 so you have to backlist the rl8188eu driver. You can do that with this command
echo 'alias usb:v0BDApF179d*dc*dsc*dp*icFFiscFFipFFin* rtl8188fu' | sudo tee /etc/modprobe.d/r8188eu-blacklist.conf
The code was taken from the same repo the aur package was made from
https://github.com/kelebek333/rtl8188fu
When running a docker container (arm64v8/aarch64) on my host machine (amd64) and trying to install/configure libc-bin on a debian container, it gives me the following error:
[ cut for size, full log at https://pastebin.com/7ZtvqZsD ]
#6 18.65 Setting up libc-bin (2.31-13+deb11u3) ...
#6 18.92 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#6 19.03 Segmentation fault (core dumped)
#6 19.06 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#6 19.15 Segmentation fault (core dumped)
#6 19.15 dpkg: error processing package libc-bin (--configure):
#6 19.15 installed libc-bin package post-installation script subprocess returned error exit status 139
#6 19.20 Errors were encountered while processing:
#6 19.20 libc-bin
#6 19.31 E: Sub-process /usr/bin/dpkg returned an error code (1)
------
executor failed running [/bin/sh -c apt-get -y reinstall libc-bin]: exit code: 100
Minimal reproducible example
FROM arm64v8/debian
RUN apt-get -y update
RUN apt-get -y reinstall libc-bin
Versions
$ qemu-system-aarch64 --version # installed via pacman -S qemu-full
QEMU emulator version 7.0.0
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developer
$ qemu-system-arm --version # installed via pacman -S qemu-full
QEMU emulator version 7.0.0
Copyright (c) 2003-2022 Fabrice Bellard and the QEMU Project developer
$ docker --version
Docker version 20.10.17, build 100c70180f
## Binfmt extensions installed with
docker run --privileged --rm tonistiigi/binfmt --install all &
$ uname -a
Linux <hostname> 5.18.7-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Sat, 25 Jun 2022 20:22:03 +0000 x86_64 GNU/Linux
## OS
Arch linux
Prior reading
(a.k.a. please don't mark my question as duplicates of these, it is distinct from them)
qemu: uncaught target signal 11 (Segmentation fault) - core dumped in docker containers
None of these answers work for me, I'm running the latest qemu in the arch linux repos, arm64v8/debian is not a deprecated container image as far as I can tell, and I'm not using docker-for-mac. Plus, this question regards the opposite direction (amd64 containers on arm64).
qemu: uncaught target signal 11 (Segmentation fault)
Issue doesn't stem from git, so this question's answer isn't helpful.
qemu-arm qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Not helpful either, I've tried using qemu-user-static v7.0.0 (both compiled and -bin) which didn't fix my issue either. Not sure what the TCG interpreter is, so that could possibly be the issue, but I'm not familiar enough with qemu to know how to "disable the TCG interpreter".
qemu uncaught target signal 11 segmentation fault -- only on arm64 build
My kernel is 5.18.7-zen1-1-zen which is newer than the 5.10.0-8 that the answer suggests, and is the latest available on arch linux repos at time of writing.
qemu: uncaught target signal 11 (Segmentation fault) - core dumped, when trying to return a struct
Answers all related to C, which I'm not using.
Goal
My ultimate goal is to build a root filesystem using multistrap to eventually be put on an arm64 device, but this issue is preventing me from doing pretty much anything, as running dpkg --configure -a is one of the steps that has to be run from the very start.
After bashing my head against this wall for weeks, the solution I found was:
Use a native docker container instead of an architecture-based one
e.g. FROM debian:11 instead of FROM arm64v8/debian:11
Install qemu-user-static inside the docker container
e.g. apt install qemu-user-static
Copy qemu-aarch64-static to the rootfs
e.g. cp $(which qemu-aarch64-static) /rootfs_location/usr/bin/qemu-aarch64 (note the filename change as well)
Chroot normally
e.g. chroot /rootfs_location/
I'm not sure exactly why this works, but it likely stems from an incompatibility between debian and the qemu-user-static binaries that were compiled for arch linux (or whatever OSes happen to be used) but i'm not entirely sure of that.
With Ubuntu 14.04 and Indigo, I cloned the pointgrey_camera_driver to catkinws/src and did catkin_make install. When I:
roslaunch pointgrey_camera_driver camera.launch
if I
rostopic echo /camera/image_color
the camera_nodelet_manager process dies. I don't know where the problem might be. This did work at one time.
I have tried using a calibration file as well as setting the launch argument "calibrated" to 0.
When the process dies this is the message:
[camera/camera_nodelet_manager-2] process has died [pid 14845, exit code -11, cmd /opt/ros/indigo/lib/nodelet/nodelet manager __name:=camera_nodelet_manager __log:=/home/mitch/.ros/log/9c7752b6-2116-11e6-a626-c03fd56e6751/camera-camera_nodelet_manager-2.log].
log file: /home/mitch/.ros/log/9c7752b6-2116-11e6-a626-c03fd56e6751/camera-camera_nodelet_manager-2*.log
The log files are not enlightening.