When running the command theHarvester -d microsoft.com -l 200 -b baidu , I do not get successful result instead I get the error shared in the screenshot.
Error
Note: I have updated my system to the latest version along with dist-upgrade as well.
Operating System Details:
PRETTY_NAME="Parrot OS 5.1 (Electro Ara)"
NAME="Parrot OS"
VERSION_ID="5.1"
VERSION="5.1 (Electro Ara)"
VERSION_CODENAME=ara
ID=parrot
ID_LIKE=debian
HOME_URL="https://www.parrotsec.org/"
SUPPORT_URL="https://community.parrotsec.org/"
BUG_REPORT_URL="https://community.parrotsec.org/"
This is the whole command with error:
Whole Page
Related
I see the following error running dmesg in my Linux running on a embedded board (Qualcomm RB5). The Linux is built using Yocto.
/ # dmesg
dmesg: klogctl: Operation not permitted
As you see, I'm running as root. I am also aware of the question here. But when I issue the solution given there I get the following error:
/ # echo 0 > /proc/sys/kernel/dmesg_restrict
sh: write error: Operation not permitted
Any idea how should I get around with it?
I am trying to run glxgears or glxinfo from a server and I am receiving the following error:
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 149 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 25
Current serial number in output stream: 26
My server is a Linux server and my local machine is OS X. However, I have tried running the same thing on a Linux machine and I am receiving the same error. I can run xeyes and xclock on the server and see the window pop up locally. If I saw nothing then I would think XForwading wasn't working at all, but since xeyes and xclock work then I am not sure what is going on.
What could be causing the BadValue (integer parameter out of range for operation) error?
In order to fix this issue I downgraded Xquartz from 2.7.11 to 2.7.8. For some reason the newer version of Xquartz doesnt work...
We have deployed our application on rhel 7 from rhel 6 and after deployment we are seeing following error in the catalina.properties, due to this my vm link is getting down frequently. We are using Documentum CMIS 16.4 version on tomcat 8.5 version.
Following is the error's details:
27-Nov-2018 01:57:00.536 SEVERE [https-jsse-nio-0.0.0.0-12510-Acceptor-0] org.apache.tomcat.util.net.NioEndpoint$Acceptor.run Socket accept failed
java.io.IOException: Too many open files
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422)
at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250)
at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:457)
at java.lang.Thread.run(Thread.java:748)
Here are my efforts in order to solve this problem:
I have increased ulimit value from 1024 to 8192 for specific user and rebooted it, recycled tomcat service but nothing happened. I had done changed to file named /etc/security/limits.d/20-nproc.conf/20-nproc.conf. kindly help here.
I don't have privileges to add a comment, so posting as an answer. Try to find out which files are open by using the command
lsof -p <pid> | wc -l.
That will tell you which files are not getting closed.
You can also check the limits of a running process by
cat /proc/<pid>/limits
I am trying to run the command:
mongod --storageEngine wiredTiger --dbpath data --logpath logs/mongo.log
in a linux server but it gives me the error
cannot execute binary file: Exec format error
when I try to see the dependences of the file mongod with readelf -d it gives too many errors:
readelf: Warning: The e_shentsize field in the ELF header is larger than the size of an ELF section header
readelf: Error: Reading 0x9c00000 bytes extends past end of file for section headers
I didn't find any information about this error
The problem was on linux versions I was working with mongodb 32bit in my linux server 64bit
I have an Ubuntu 16.04 droplet on DigitalOcean and I'm trying to set up remote desktop capabilities for it. I followed these instructions through Step 2. However, when I start the VNC server using the vncserver command, it goes haywire and bogs down the server until it crashes. Here are excerpts from the log file:
19/12/17 23:47:52 Xvnc version TightVNC-1.3.10
19/12/17 23:47:52 Copyright (C) 2000-2009 TightVNC Group
19/12/17 23:47:52 Copyright (C) 1999 AT&T Laboratories Cambridge
19/12/17 23:47:52 All Rights Reserved.
19/12/17 23:47:52 See http://www.tightvnc.com/ for information on TightVNC
19/12/17 23:47:52 Desktop name 'X' (thoughtful:1)
19/12/17 23:47:52 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
19/12/17 23:47:52 Listening for VNC connections on TCP port 5901
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring
/home/epoirier/.vnc/xstartup: 1: /home/epoirier/.vnc/xstartup: Cannot fork
xrdb: Resource temporarily unavailable
xrdb: cannot run '/usr/bin/cpp -P -DHOST=thoughtful -DSERVERHOST=thoughtful -DSRVR_thoughtful -DDISPLAY_NUM=1 -DCLIENTHOST=thoughtful -DCLNT_thoughtful -DVERSION=11 -DREVISION=0 -DVENDOR="AT&T Laboratories Cambridge" -DVNDR_AT_T_Laboratories_Cambridge -DRELEASE=3332 -DNUM_SCREENS=1 -DEXT_XC_MISC -DEXT_SYNC -DEXT_MIT_SUNDRY_NONSTANDARD -DEXT_BIG_REQUESTS -DEXT_XTEST -DEXT_MIT_SHM -DEXT_SHAPE -DSCREEN_NUM=0 -DWIDTH=1024 -DHEIGHT=768 -DX_RESOLUTION=2951 -DY_RESOLUTION=2954 -DPLANES=24 -DBITS_PER_RGB=8 -DCLASS="TrueColor" -DCLASS_TrueColor=34 -DCOLOR -DCLASS_TrueColor_24=34 /home/epoirier/.Xresources'
/usr/bin/startxfce4: X server already running on display :1
xrdb: Resource temporarily unavailable
xrdb: cannot run '/usr/bin/cpp -P -DHOST=thoughtful -DSERVERHOST=thoughtful -DSRVR_thoughtful -DDISPLAY_NUM=1 -DCLIENTHOST=thoughtful -DCLNT_thoughtful -DVERSION=11 -DREVISION=0 -DVENDOR="AT&T Laboratories Cambridge" -DVNDR_AT_T_Laboratories_Cambridge -DRELEASE=3332 -DNUM_SCREENS=1 -DEXT_XC_MISC -DEXT_SYNC -DEXT_MIT_SUNDRY_NONSTANDARD -DEXT_BIG_REQUESTS -DEXT_XTEST -DEXT_MIT_SHM -DEXT_SHAPE -DSCREEN_NUM=0 -DWIDTH=1024 -DHEIGHT=768 -DX_RESOLUTION=2951 -DY_RESOLUTION=2954 -DPLANES=24 -DBITS_PER_RGB=8 -DCLASS="TrueColor" -DCLASS_TrueColor=34 -DCOLOR -DCLASS_TrueColor_24=34 /home/epoirier/.Xresources'
/usr/bin/startxfce4: X server already running on display :1
/etc/xdg/xfce4/xinitrc: 8: /etc/xdg/xfce4/xinitrc: Cannot fork
/etc/xdg/xfce4/xinitrc: 8: /etc/xdg/xfce4/xinitrc: Cannot fork
cpp: error: vfork: Resource temporarily unavailable
/usr/bin/startxfce4: X server already running on display :1
sh: 1: Cannot fork
This is the beginning of the log and it descends into more chaos from here with many different "Cannot fork" warnings. Nothing from the command line indicates that something is going wrong when starting the VNC server. Anyone have any ideas on what's going wrong here?
You are probably running out of file descriptors for the user running that process.
Check what is the current limit with ulimit -n and change accordingly.