Server :: VNC On Xen Failure - Hotplug Script Not Working
Jun 10, 2010
The following config works and creates a good VM in Xen:
Code:
# Kernel Setup
kernel = "/boot/vmlinuz-2.6.18.8-xenU"
# Memory
memory = "256"
# Disk
disk = [
"file:/opt/xen/domains/110/sda1.img,sda1,w",
"file:/opt/xen/domains/110/swap.img,sda2,w"
]
# container name
name = "110"
hostname = "boo"
But when I uncomment the VFB line, I get the following error after it hangs for at least 30 seconds:
Code:
[root@customer 110]# xm create boo.cfg
Using config file "./boo.cfg".
Error: Device 0 (vkbd) could not be connected. Hotplug scripts not working.
Part two of this question:
Sometimes it actually works, and a port is opened. When this happens, nmap shows the VNC ports open and I can connect via the VNC client, but it just hangs at "Connection established." and no VNC display shows up. I've tried multiple VNC clients (TightVNC, TightVNC Java Console, RealVNC), but they all fail to connect. Does VNC through Xen require X to be started in order to function? I was under the impression that it would show the console screen.
I'm running Linux 2.6.35.4 on a Kontron COMExpress board. The device has 2 battery slots so that a user can hot swap batteries while the device is running.The problem I'm having is that battery information is never updated in /sys unless I read /proc/acpi/BAT[12]/state.When booting the device, the battery state is correctly detected by the kernel but after that it seems like nothing happens.
My current solution is to poke at /proc from time to time, it works but I'm forced to compile my kernel with CONFIG_ACPI_PROCFS_POWER which is marked as deprecated..
Hotplug of USB not working after yum update.Fedora 11, with KDE4.3.4-1 Kernel 2.6.30.10-105.fc11.i686.PAE.This problem occurred after I ran "yum update" on 28th December 2009, which updated the kernel to the current above version, from 2.6.30.9-96.c11.i686. PAE.Prior to this update, when a USB device(either a scanner, printer, pendrive or camera) was plugged in (hotplug) the device was detected and could be used by the appropriate application. The camera and pendrives were reported by the KDE Device Notifier.
I can mount the pendrive and camera manually, but I cannot use the scanner or printer applications as the devices are not seen.Interestingly if the printer and scanner devices are plugged in/switched on at boot time,they are seen and are usable, eg the Scanner-Tool sees the scanners and the printers print.Logging in as root, exhibits the same symptoms.This feature has occurred on two machines, both after running yum update.Please what has broken with this yum update.How can I overcome this "feature".
Current stable Debian runs on both machines. I connect a digital camera to the USB on the server ("a") and the camera's filesystem is mounted automatically.I want that same filesystem to be made available to the other machine ("b") through nfs.What should be in fstab for that filesystem, or is something else needed in the configuration for "b" in order to access the filesystem which is physically on "a"?
Trying to install Natty 11.04 via PXE. The ethernet is a Realtek RTL8168d/8111d gigabit. It DHCPs and configures just fine. Then it downloads what it needs for partitioning and does that. After partitioning, it runs net/hw-detect.hotplug which discovers the interface as new, then strips it of any configuration so it can not proceed further. Is there any way to disable this secondary hotplug detection of the ethernet interface?
I was just wondering if there's any point having both auto and allow-hotplug against the same interface in network/interfaces as allow-hotplug seems to bring an interface up at boot on its own.
My Ubuntu laptop gets docked into a few different locations per day with different hardware and use cases. I'd like to automate the preference settings for each of these locations:
Work computer, dual head 1280x1024 External USB audio and bluetooth audio Home computer, dual head 1280x1024, 1080p External USB audio
Basically, when I dock the box in either (1) or (2), I want to automagically get the right xrandr settings for the different screen geometries and the right audio routing.
What scripts, etc. are responsible for the inscrutable default behavior?
Are there packages for customizing this?
If I wanted to roll my own, what is the right library to use to catch the hotplug events?
I'm having trouble getting a PCIe device to show up in lspci using pcie hotplug.
After booting the system I load the pciehp module, I then plug-in my PCIe card. After that I do an lspci, but I don't see my PCIe card. When I cold boot with the PCIe card installed the system sees it fine, i.e. it show up in lspci.
Does anyone know of an easy way to figure out if my hardware even supports pcie hotplug?
When I load the hotplug module I just do a modprobe pciehp. Is this all I need to do prior to plugging-in my pcie card?
I will try running pciehp with debugging turn on to see if that gives me any additional info.
Here is what happens. I type in "su", without the quotes, to switch to root. I enter my password. Code: jon-Tuxbox:~$ su Password: su: Authentication failure jon-Tuxbox:~$ It fails, and I get kicked back to the command line. I recently fixed the permissions on the shadows file and the su file in the bin directory, and that is what caused this. Before it would give another error. I tried resetting the password for root, but it didn't fix it.
I am running Fedora 12 on a T400 Thinkpad. When connector my external monitor prior to powering on the computer or if I restart it, I get a lot of resolution choices from xrandr. See below.
Code: $ xrandr Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192 LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 303mm x 190mm 1440x900 60.0*+ 50.0 1024x768 60.0
[Code].....
Is there some daemon I need to restart to detect the monitor resolutions correctly, or is there a module I can reload?
There seem to several variables to reproducing the behavior. If I restart without the laptop without the monitor plugged in, log in, and then, plug the monitor in with the monitor powered on prior to plugging, all resolutions are detected properly. However, if I plug the monitor in with it powered off, then power it on, I only get the few options shown in above. Once I get the reduced number of options, it seems to stay that way till I restart regardless of how I unplug the monitor.
I have found a work-around by just forcing the modes with xrandr --newmode and xrandr --addmode, but I would much rather have the modes autodetected.
I have set up a server box running Ubuntu 10.04 Server 64-bit with Squeezeboxserver, ftp, apache and all the things that I need.I am running it on a Asus P5Q pro with 9 harddrives attached.I have set up 6 1tb disks that run a raid6 array but I am wondering what would happen if the motherboard would fail me.Is it possible to just replace the motherboard with a newer one and would then the raid6 array still be intact?
I used to run a raid10 with the 6 disks on a Windows 7 machine with a software raid card but the card broke and I replaced it with a new one but the array could would not work so I had to forget all my data and this is what brought me to using a Ubuntu server as OS and running the raid array on the motherboard sata instead.Also, is it possible to make an exact copy of the boot drive/partition and easily replace that is the boot hard drive would go faulty? I have heard about the dd command and I feel it would be nice to know that I'm not totally screwed if the boot drive fails.
Dell Mini 9 Netbook with Windows XP OS died. It has a 16GB SSD. I was in the middle of installing HP printer software when it shutdown unexpectedly. Then upon turning it back on it says something about a media test failure, check cable and then Operating System Not Found. I've been able to boot using Damn Small Linux using an external cd drive.
When I type 'fdisk -l' I get: Disk /dev/hda: 15.4 GB, 15408046080 bytes 255 heads, 63 sectors/track, 1873 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/hda doesn't contain a valid partition table
My wife has lots of pictures on the drive that she would like so I took it to a couple data recovery places and they were charging anywhere from $1000 just for jpegs up to $2600 for all files retrieved. That's more than I can budget for this. So my wife accepted the fact that the pictures are gone, but I figured I might as well try what I can because we have nothing more to lose.
I thought I'd try to get a hard drive cubby and attach it through USB to a working PC, but apparently Dell's SSDs are proprietary and the design is not accommodated. I thought maybe just the partition table information got erased somehow, so I tried using gparted and it found nothing. Whenever I use cfdisk and create partitions, I quit cfdisk after writing and it still says there is no valid partition table. I have no other ideas as to what I can do.
I have a new 64 bit workstation (Dell Vostro i7) which I usually keep running for extended periods (read; days and weeks). I have realized that the system completely ignores when I insert a USB stick (LaCie 8Gb USB Key). By ignore, I mean it doesn't get mounted, and /media/ is empty. Interesting enough if I go into YAST and probe for Hardware Information, I find my USB stick there under the USB section. There is no specific entry for the key in /etc/fstab by the way, as far as I know I don't need to specify how a USB stick should be mounted. Auto-mount, when it actually works, is perfectly fine.
It's been a while but I just hit a brick wall. Well, this has been building for a week or so, I can't figure out what's causing it. I thought there was a sudden conflich with the bluetooth dongle, since that one piece of hardware is not listed right from boot (sometimes has a dmesg error related to loading the module), but I find now this is not the case. Today I ran the full update to the current kernel hoping to fix the problem, but to no avail (caused some interesting issued with the video (intel 945) which I ironed out). Symptom: With the exception of the bluetooth, all devices hooked up to the USB ports at boot are recognized and usable. No device that I plug in after booting is recognized, period. lsusb output does not change. Plugging in a USB flash drive produces no output for dmesg.
I've been trying to get SELinux working in OpenSUSE 11.2. So far I can get to runlevel 3 with enforcing=0. Before I start tinkering with audit2allow, The 11.2 repository gives me these policy rpms:
[URL]
But that version of policy has some issues in OpenSUSE:
1) failure to allow the graphical desktop to load (even with enforcing=0) . The following message appears in the console during boot:
** (gdm:1073): WARNING **: Couldn't connect to system bus: A SELinux policy prevents this sender from sending this message to this recipient (rejected message had sender "(unset)" interface "org.freedesktop.DBus" member "Hello" erro name "(unset)" destination "org.freedesktop.DBus") startproc: exit status of parent of /usr/sbin/gdm: 1 Since enforcing is off, I'm surprised to see a message like that. SELinux shouldn't be preventing anything, so I don't see how modifying policy will solve that. Ideas?
2) Attempting to boot to runlevel 5 with kernel parms "security=selinux selinux=1 enforcing=0", I'm dropped off in runlevel 3 instead. I'm getting a couple of pages of AVC errors after boot (see below). I've tried several other versions of the policy without luck:
- the version included in Fedora 12 (refpolicy-2.2009117 - the latest release from Tresys - the latest from the repository at Tresys
Ive been at this for two days now, and cant make any progress.
First, the details: Target OS: Fedora 14, i386 Target Machine: IBM (e)server, xSeries 306 OS: Fedora v.4 Boot Order: 1. CD... 2. Removable Media 3. SATA... USB Drive: adata 8GB Process:
I used the prescribed live usb creator for windows to fill the usb drive with Fedora 14 i386. Ive attempted to boot from the USB at least 4 times, once from each USB port on the box. No luck. There isnt an option in the BIOS to select the specific boot device. I bring that up because my desktop does have that option, and using the BIOS BOOT MENU, I was able to boot from the USB and bring up the Fedora 14 Installation Menu, no problem.
So, it works on the pc thats on my desk (eMachine w/XP), but the IBM doesnt even recognize it.
I have an Ubuntu box running server 11.04 that is displaying a weird behavior when logging into the CLI. The message below will scroll for about 15-20 seconds when you first log in, but then it goes to the normal shell and everything seems to work fine.
I *had* a server with 6 SATA2 drives with CentOS 5.3 on it (I've upgraded over time from 5.1). I had set up (software) RAID1 on /boot for sda1 and sdb1 with sdc1, sdd1, sde1, and sdf1 as hot backups. I created LVM (over RAID5) for /, /var, and /home. I had a drive fail last year (sda).After a fashion, I was able to get it working again with sda removed. Since I had two hot spares on my RAID5/LVM deal, I never replaced sda. Of course, on reboot, what was sdb became sda, sdc became sdb, etc.So, recently, the new sdc died. The hot spare took over, and I was humming along. A week later (before I had a chance to replace the spares, another died (sdb).Now, I have 3 good drives, my array has degraded, but it's been running (until I just shut it down to tr y.
I now only have one replacement drive (it will take a week or two to get the others).I went to linux rescue from the CentOS 5.2 DVD and changed sda1 to a Linux (as opposed to Linux RAID) partition. I need to change my fstab to look for /dev/sda1 as boot, but I can't even mount sda1 as /boot. What do I need to do next? If I try to reboot without the disk, I get insmod: error inserting '/lib/raid456.ko': -1 File existsAlso, my md1 and md2 fail because there are not enough discs (it says 2/4 failed). I *believe* that this is because sda, sdb, sdc, sdd, and sde WERE the drives on the raid before, and I removed sdb and sdc, but now, I do not have sde (because I only have 4 drives) and sdd is the new drive. Do I need to label these drives and try again? Suggestions? (I suspect I should have done this BEFORE failure).Do I need to rebuild the RAIDs somehow? What about LVM?
I had a power failure the other day and my server shutdown abruptly. After bringing the server up I noticed that the /var partition came up as read only. I was not able to edit the crontab, not able to write to files within /var/log/ and do other write operations within /var.
I did a mount and it showed that /var was mounted read and write but when trying to run certain operations the system was still saying that it was read only.
I'm trying to get openssh-server working so I can stop using the family TV and just SSH from my laptop. I've only just installed 10.4 server edition, and I've made a change to /etc/apt/sources.lst by removing the # in front ofdeb cdrom:[Ubuntu-Server 10.04 LTS Anyway I run:sudo apt-get install openssh-server
Code: Reading package lists... Done Building dependancy tree
I know why this happened, but I need to know what problems it's going to cause and how I can re-install / fix the problem. I have my /tmp folder mounted as -noexec ... so when I did a recent update to my 10.04.1 LTS server installation, I got the following errors:
I have 4 WD10EARS drives running in a RAID 5 array using MDADM.Yesterday my OS Drive failed. I have replaced this and installed a fresh copy of Ubuntu 11.04 on it. then installed MDADM, and rebooted the machine, hoping that it would automatically rebuild the array.It hasnt, when i look at the array using Disk Utility, it says that the array is not running. If i try to start the array it says :Error assembling array: mdadm exited with exit code 1: mdadm: failed to RUN_ARRAY /dev/md0: Input/output error
mdadm: Not enough devices to start the array.I have tried MDADM --assemble --scan and it gives this output:mdadm: /dev/md0 assembled from 2 drives - not enough to start the array.I know that there are 4 drives present as they are all showing, but it is only using 2 of them.I also ran MDADM -- detail /dev.md0 which gave:
root@warren-P5K-E:~# mdadm --detail /dev/md0 /dev/md0: Version : 0.90
i installed a new centos 5.5 1 old server hp ml380 g3 series on 2gb ram, 72gb raid 1+0 scsi disk
after running 1 sucessfull day next morning i found no response of ping, telnet, putty, ssh. when i check physically machine the mouse keyboard was hang, i reboot machine, then it says kernel panic failure mounting hardware, then next time i reboot the o/s centos start book properly and running. i check the dmesg logs, can someone guide me how to check cpu,raidcontroller,memory,harddrive are getting failed or what hardware exactly choking out.
I am running or was running a mail server. It used the titles service to scan emails but keeps bringing up a temporary failure right. But when I run the command 'amavisd' It brings up this error here:
