Recently updated the Linux kernel from 2.6.18 to 2.6.32, and an existing application starts error out with following error message:
epoll_ctl() failed: No such file or directory [errno = 2].
I did read through the linux man page on epoll_ctl but couldn't make much sense of it. I am trying to understand what the possible cause of such?
Thanks
You should give us the code calling epoll_ctl, but likely the socket behind the file descriptor you are trying to modify has been closed somewhere else. See also Epoll: does it silently remove fds?
Related
i had an error while exporting my schema and then import it into a new database.
My Exporting System is an Oracle Linux 7 with 19c Database and the importing system is Oracle Linux 8 with 21c XE. When i import the schema with impdp i receive the error:
impdp system/password#localhost/xepdb1 full=y directory=data_pump_dir dumpfile=test.dmp
ORA-39001: ivalid argument
ORA-39000: incorrect specification of dump file
ORA-31619: invalid dump file "opt/oracle/admin/XE/dpdump/CC96F85...01/test.dmp"
ORA-27072: File-I/O-Error
Linux-x86_64 Error: 25: Inappropriate ioctl for device
Additional information: 4
Additional information: 1
As stated in the comments
When you got the error Inappropriate ioctl for device , Oracle is not responsible, as the error is coming from Linux.
Most of the times due to:
The datapump file is corrupted.
The file is not not a valid datapump file
The datapump file is empty.
WARNING: Ignoring invalid distribution -ip (c:\users\sangay sherpa\appdata\local\programs\python\python37\lib\site-packages)
WARNING: Error parsing requirements for tensorflow-gpu: [Errno 2] No such file or directory: 'c:\users\sangay sherpa\appdata\local\programs\python\python37\lib\site-packages\tensorflow_gpu-2.1.0.dist-info\METADATA'
You can find some problems in your folder[c:\users\sangay sherpa\appdata\local\programs\python\python37\lib\site-packages],There have some error packet such as the [ip],this packet maybe become ~ip.
like this packet_img
enter image description here
You can del these packets or make a folder to store them.
I'm trying to build automotive grade linux, but I keep getting the same errors.
I tried building on different machines with different linux distributions, but I keep getting the error nevertheless.
I also tried building for different machines without success.
This is the full log of the last time I tried to build automotive grade linux for a raspberry pi 2:
Pt 1: https://pastebin.com/0pqKDdv5
Pt 2: https://pastebin.com/dmRCtTLe
This is my build configuration:
BB_VERSION = "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Debian-9.3"
TARGET_SYS = "arm-agl-linux-gnueabi"
MACHINE = "raspberrypi2"
DISTRO = "poky-agl"
DISTRO_VERSION = "4.0.2"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard"
TARGET_FPU = "hard"
meta-raspberrypi = "HEAD:28d4404f89eb59d406b4976c0e3f5ca19137ba74"
meta-netboot = "HEAD:a5f69d3d31e7d75351f0e2abfc36d35ba39ce304"
meta-security-smack
meta-security-framework = "HEAD:20bbb97f6d5400b126ae96ef446c3e60c7e16285"
meta-app-framework = "HEAD:a5f69d3d31e7d75351f0e2abfc36d35ba39ce304"
meta-qt5 = "HEAD:5f837b47f5c3e462f24cd5abf58ff6ef1dd04932"
meta-agl-demo = "HEAD:65619655cb3f373a1b15da7a4d91191a2867464b"
meta-oe
meta-multimedia
meta-efl
meta-networking
meta-python
meta-filesystems = "HEAD:fe5c83312de11e80b85680ef237f8acb04b4b26e"
meta-ivi-common
meta-agl
meta-agl-distro
meta-agl-bsp = "HEAD:a5f69d3d31e7d75351f0e2abfc36d35ba39ce304"
meta
meta-poky = "HEAD:60402978fe3648bf560b3386c6e9dd661cdf2083"
This is the first error I get:
WARNING: qemu-native-2.7.0-r1 do_populate_sysroot: File '/.../build/tmp/sysroots/x86_64-linux/usr/share/qemu/openbios-ppc' from qemu-native was already stripped, this will prevent future debugging!
WARNING: qemu-native-2.7.0-r1 do_populate_sysroot: File '/.../build/tmp/sysroots/x86_64-linux/usr/share/qemu/openbios-sparc32' from qemu-native was already stripped, this will prevent future debugging!
WARNING: qemu-native-2.7.0-r1 do_populate_sysroot: File '/.../build/tmp/sysroots/x86_64-linux/usr/share/qemu/openbios-sparc64' from qemu-native was already stripped, this will prevent future debugging!
WARNING: qemu-native-2.7.0-r1 do_populate_sysroot: File '/.../build/tmp/sysroots/x86_64-linux/usr/share/qemu/s390-ccw.img' from qemu-native was already stripped, this will prevent future debugging!
WARNING: qemu-native-2.7.0-r1 do_populate_sysroot: File '/.../build/tmp/sysroots/x86_64-linux/usr/share/qemu/u-boot.e500' from qemu-native was already stripped, this will prevent future debugging!
ERROR: qemu-native-2.7.0-r1 do_populate_sysroot: runstrip: ''strip' --remove-section=.comment --remove-section=.note '/.../build/tmp/work/x86_64-linux/qemu-native/2.7.0-r1/sysroot-destdir/.../build/tmp/sysroots/x86_64-linux/usr/share/qemu/palcode-clipper'' strip command failed with 1 (b"strip: Unable to recognise the format of the input file `/.../build/tmp/work/x86_64-linux/qemu-native/2.7.0-r1/sysroot-destdir/.../build/tmp/sysroots/x86_64-linux/usr/share/qemu/palcode-clipper'\n")
This is the second error, which I think is caused by the first one.
ERROR: gcc-runtime-6.2.0-r0 do_compile: oe_runmake failed
ERROR: gcc-runtime-6.2.0-r0 do_compile: Function failed: do_compile (log file is located at /.../build/tmp/work/armv7vehf-neon-vfpv4-agl-linux-gnueabi/gcc-runtime/6.2.0-r0/temp/log.do_compile.30447)
ERROR: Logfile of failure stored in: /.../build/tmp/work/armv7vehf-neon-vfpv4-agl-linux-gnueabi/gcc-runtime/6.2.0-r0/temp/log.do_compile.30447
NOTE: recipe gcc-runtime-6.2.0-r0: task do_compile: Failed
ERROR: Task (/.../poky/meta/recipes-devtools/gcc/gcc-runtime_6.2.bb:do_compile) failed with exit code '1'
I found this thread of someone having the same issue, but there is no fix there, so I thought I'd ask it again, because this issue still persist.
I can see that there is a problem with the stripping of files, but I can't find where to fix this in the recipes.
I'm not sure if this error is caused by the used host system or if it's dependant on the recipes.
I hope someone knows a fix to this issue.
Thanks in advance
Laurens Wuyts
EDIT:
Here is the log file of the gcc error: https://www.dropbox.com/s/4hd5kzgbadhdc9p/log.do_compile.30447?dl=0
Here is the specific error message on pastebin:
https://pastebin.com/H8M3sY6a
Fatal Error -32988: LoadLibrary failed, rc=193 [MsgId: MERR-32988]
Fatal Error -26000: xfbLrwiWebInfraGlobalInitOK failed [MsgId: MERR-26000]
Warning: Extension lrwreplaymain.dll reports error -1 on call to function ExtPerProcessInitialize
Error: Thread Context: Call to service of the driver failed, reason - thread context wasn't initialized on this thread.
Recording is passed but cannot replayed due to the above error.
Thanks for the help in advance.
Either lrwreplaymain.dll or some of the DLLs it depends on were corrupted (error code 193 = ERROR_BAD_EXE_FORMAT). This may have been caused by virus attack, file system corruption etc.
The easiest solution is to re-install LoadRunner. You can also check which DLLs are corrupted by means of the Dependency Walker x86. Just start it and open <LoadRunner installation folder>\bin\lrwreplaymain.dll
How to fix? I can't boot anymore
Jan 24, 2014 10:03:29 AM Error: Starting VM 'CentOS 6 (64-bit)' -
Internal error: xenopsd internal error:
VM = 182361af-d10a-d97b-3a65-346d9cec1bcb; domid = 133;
Bootloader.Bad_error Traceback (most recent call last):
File "/usr/bin/pygrub", line 895, in ?
part_offs = get_partition_offsets(file)
File "/usr/bin/pygrub",
line 105, in get_partition_offsets
image_type = identify_disk_image(file)
File "/usr/bin/pygrub", line 49, in identify_disk_image
fd = os.open(file, os.O_RDONLY)
OSError: [Errno 2] No such file or directory:
'/dev/sm/backend/94b422b6-3e31-88fb-bc55-99b33de9d89a/36bce863-ba6d-4792-b29d-dc6211bd5e8c'
Probably your server was shutdown improperly, hence, the partition was mounted Read Only. You have to unplug your pbd, check and plug again Read and Write.
That did it for me.
Looks like the VDI of the VM is either corrupted or deleted. From Xencenter click on the VM and go to the respective Storage (Local Storage or Shared) to check that the VDI exists or not. I guess you have to re-create the disk again !
I solved this same problem, where I was unable to get my VDIs to mount in any VM, and booting the VMs failed with the "No such file or directory: /dev/sm/backend" error you're getting.
What worked to fix it was to make a snapshot of each VM, creating a new VM from the snapshot and then deleting the old VM.