How can I prevent vncserver from crashing when I start it? - linux

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.

Related

"NotImplementedError" in theHarvester

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

Getting error in Chef-ERROR: shard_seed: Failed to get dmi property serial_number: is dmidecode installed?

I am getting error while running a code in chef
chef-client -zr "recipe[test-cookbook::test-recipe1]"
[2020-08-05T16:01:06+00:00] WARN: No config file found or specified on command line. Using command line options instead.
Starting Chef Infra Client, version 16.3.45
[2020-08-05T16:01:08+00:00] ERROR: shard_seed: Failed to get dmi property serial_number: is dmidecode installed?
resolving cookbooks for run list: ["test-cookbook::test-recipe1"]
Synchronizing Cookbooks:
test-cookbook (0.1.0)
Installing Cookbook Gems:
Compiling Cookbooks...
Converging 0 resources
Running handlers:
Running handlers complete
Chef Infra Client finished, 0/0 resources updated in 01 seconds

Sql Server 2019 (Fedora 32) - Msg 22022, Level 16, State 1, Line 0 SQLServerAgent is not currently running so it cannot be notified of this action

I am getting this error. Though Agent seems to be running I have checked running state by calling
EXEC xp_servicecontrol 'querystate', 'SQLSERVERAGENT'
And it shows "Stopped." Then I call
EXEC xp_servicecontrol N'START',N'SQLServerAGENT';
And it shows "Running." After that I try executing the job by calling
EXEC dbo.sp_start_job N'SendCollectionSummaryReport' ;
And I get the Error: SQLServerAgent is not currently running so it cannot be notified of this action.
Then I called again EXEC xp_servicecontrol 'querystate', 'SQLSERVERAGENT'
And it shows "Stopped."
I realized that something is causing failure to start SQLServerAgent. Environment details below:
Microsoft SQL Server 2019 (RTM-CU4) (KB4548597) - 15.0.4033.1 (X64)- Developer Edition (64-bit) ort n Linux (Fedora 32 (Workstation Edition))
Access same server using SSME on Windows Client Machine and All Options coming Disabled

"Microsoft Windows 10 Enterprise 2016 LTSB 10.0.14393 Version 1607" fails on boot in qemu/kvm (proxmox)

I have played with different versions of windows 10 inside qemu/kvm (proxmox) and all of them works fine except: "Microsoft Windows 10 Enterprise 2016 LTSB 10.0.14393 Version 1607".
I don't think that the problem is connected with proxmox itself. As I know proxmox is stable and reliable system that use qemu/kvm under the hood. So lets think more about qemu/kvm. However my proxmox versions below.
root#home:~# pveversion -v
proxmox-ve: 5.3-1 (running kernel: 4.15.18-10-pve)
pve-manager: 5.3-8 (running version: 5.3-8/2929af8e)
pve-kernel-4.15: 5.3-1
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-44
libpve-guest-common-perl: 2.0-19
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-36
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-33
pve-container: 2.0-33
pve-docs: 5.3-1
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-17
pve-firmware: 2.0-6
pve-ha-manager: 2.0-6
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 3.10.1-1
qemu-server: 5.0-45
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1
In any case I have not found any similar thread on proxmox forum. That's why I post my problem here.
This is clean original msdn iso from microsoft with confirmed hash sums(installed more then 10 times).
Steps to reproduce:
Create VM with next configuration
root#home:~# cat /etc/pve/qemu-server/102.conf
bios: ovmf
boot: dcn
bootdisk: scsi0
cores: 8
cpu: host
efidisk0: local-lvm:vm-102-disk-0,size=4M
ide2: iso-backs:iso/MS DaRT 10 Eng x86 x64.iso,media=cdrom,size=600320K
machine: q35
memory: 8192
name: win10-test
net0: virtio=C2:25:D9:DD:F2:4F,bridge=vmbr0
numa: 1
ostype: win10
scsi0: local-lvm:vm-102-disk-1,size=100G
scsi1: external:vm-102-disk-0,size=100G
scsihw: virtio-scsi-pci
smbios1: uuid=9d455cbf-1fa2-495f-928d-3935ec39c245
sockets: 1
usb0: host=1c4f:0002
usb1: host=09da:9090
vmgenid: 40cd47b6-35c4-47ab-8f9e-ed2acb618fcc
Install latest virtio drivers (scsi, netkvm, baloon, qemu-fwcfg)
Accept disk auto-partitioning (4 partitions will be created for this iso)
Wait installations end and reboot the system
Boot will stuck at proxmox logo
However, I can always boot from live cd (MS DaRT), to do that I need to manually choose harddisk from "Use a device" menu.
Once it load successfully there is a chance it will boot again an indefinite number of times. I can't figure out the reason of such behavior.
I have tried to avoid this problem by installing grub. But nothing has changed - I am still able to load system through live cd and always have a random chance to stuck at default load process.
Event Viewer errors(repeatable):
Distributed COM Event_id: 10016
Eventlog Event_id: 1101
Kernel-Power Event_id: 41
Eventlog Event_id: 6008
Kernel-Power Event_id: 13

JVM crashes when running SOAPUI on Ubuntu

I just downloaded SOAPUI 4.0.1 and tried to run it in Ubuntu 11.10. I run the file soapui.sh. The application started up and the window actually appeared, but then after a few seconds it closed. Looking at the terminal I saw that the JVM crashed. Below are the details of the error:
(process:4183): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.30.0/./gobject/gtype.c:2708: You forgot to call g_type_init()
(process:4183): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(process:4183): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
Problematic frame:
C [libgconf-2.so.4+0x15b99] gconf_enum_to_string+0xd59
Can anyone help? Thanks.
Look here: http://www.eviware.com/forum/viewtopic.php?f=13&t=7736
Look in ..../soapui-4.0.1/bin/soapui.sh:
#uncomment to disable browser component
#JAVA_OPTS="$JAVA_OPTS -Dsoapui.jxbrowser.disable=true" <- uncomment this line
if you are usising soapui.sh to start soapUI. If you used installer and using launcher than
in soapUI-*.vmoptions add -Dsoapui.jxbrowser.disable=true
that should do the trick.
I also have the same issue
--
DUMP
...
# JRE version: 6.0_33-b03
# Java VM: Java HotSpot(TM) Server VM (20.8-b03 mixed mode linux-x86 )
# Problematic frame:
# C [libgconf-2.so.4+0x176aa] __float128+0x176aa
...
OS:Fedora release 16 (Verne)
uname:Linux 3.3.2-6.fc16.i686 #1 SMP Sat Apr 21 13:23:12 UTC 2012 i686
libc:glibc 2.14.90 NPTL 2.14.90
...
--
This jxbrowser...jar is working with xulrunner-2.8...jar and native code doesn't full compatible with your OS dependencies.
jxbrowser it's used for 'HTML rendering' but works also without it.
--
It works also in FC16

Resources