I am running Grizzly on a two node configuration. If I use the standard images, I.e. cirros-0.3.0-x86_64-disk.img or any of the ubuntu-server-cloudimg-amd64-disk1.img I have no problems, console log is there. But if I create an image using KVM and any of the ubuntu ISO standard files, then I don't get a console log. Instances always run OK and I can access them via the dashboard login screen, and there are no error messages about the console; console.log is always 0 bytes on these cases. Is there any difference on those cloud images that I need to add to my image creation process? I have already tried and added libvirt unsuccessfully.
Thanks for the help
Short answer
Inside of your virtual machine, edit /etc/default/grub so it has the line:
GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0"
Do
sudo update-grub
Longer answer
Grub needs to be configured to write the boot messages to the serial device (ttyS0). In particular, on Ubuntu, in your /boot/grub/grub.cfg, there should be a line that has console=ttyS0, like this:
linux /boot/vmlinuz-3.2.0-49-virtual root=UUID=6d2231e4-0975-4f35-a94f-56738c1a8150 ro console=ttyS0
However, you shouldn't edit this file directly. Instead, you should edit /etc/default/grub to specify the additional parameters to be passed to the kernel and then run update-grub, which will update the files in /boot/grub for you. Specify the console=ttyS0 argument by editing the GRUB_CMDLINE_LINUX_DEFAULT variable defined in /etc/default/grub.
Related
I accidentally set the default systemctl target to basic target while trying to switch from multi-user to graphical target on my raspberry Pi 3B which runs the Raspbian OS. Since then when I boot my RPi it does not start and only displays a welcoming screen. I tried to edit the config and cmdline files while in recovery mode to try to access the command line but I could not. Can someone explain to me what the basic target even is because I have been searching online for hours and cannot find a proper explanation? Do I need to format my RPi now or can I access my command line by some way to switch to multi-user target?
Thanks in advance.
The documentation for all systemd so-called special units is available under systemd.special(7) man page (or in the respective online version).
basic.target is an early-boot synchronization point, ordered even before initrd, so the service for login prompts is simply not started, thus there's no command line to work with. This is nicely described and visualized in the bootup(7) man page.
You can temporarily override the default target from the kernel command line using the systemd.unit= argument (systemd(1), section Kernel Command Line).
In your case, adding systemd.unit=multi-user.target to your kernel command line should be enough to allow you to boot back into your rPi and then make the target change permanent by calling systemctl set-default multi-user.target (or graphical.target, as that seems to be the original way you were trying to follow).
I'm new to Jupyter notebooks/Lab and I've successfully got interaction with pop-out windows and buttons etc with ipywidgets on local instances of Jupyter Lab but not in the cloud when using notebooks.ai - the code runs without error but doesn't create the appropriate windows/button.
Is there anyway to get this working or is this an inherent restriction of using Jupyter Lab in the cloud?
I'm wondering whether there are firewall settings that need configuring to get this to work?
The X11 forwarding is disabled on the docker machines provided by notebooks.ai. Hence, any pop-up interaction is not being forwarded to your machine. However, you can see any inline plot/button in the Jupyter notebook.
If you are interested in this feature there is a GitHub repository to request features (I have never tried it) but might be interesting for you to receive a more in-depth explanation, workaround, or solution.
PROVE:
In the launcher tab you can either run a notebook, a python interpreter or a terminal on the remote docker machine. If you select the terminal and type echo $DISPLAY, you will see that the result is an empty line (if a valid display was attached you will see something like: DISPLAY=localhost:11.0).
For further information about using BASH to check if X11 forwarding is enabled from SSH check this question.
sorry if this question is not as detailed and focused as it should be.
I am a Linux user (so no admin privileges of any sort) and just installed Anaconda3 from here and followed the instructions.
Note that my Linux machine is not connected to the internet, so I had to transfer the file through other means and just run bash Anaconda... as instructed in the Continuum site.
I have then succesfully launched IPython and tried to plot inline, without problems. However, when I tried to use plotting in windows, I got this kind of output from the terminal:
X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea)
And the created graph window was just blank.
I then tried to start Spyder and basically saw the same behaviour: a lot of those errors reported above, and the Spyder window just popped up blank.
Google search for the error gives results reported for Qt, which makes sense since when plotting "offline" (as opposed to inline) then QtAgg is used.
However, I have no clue as to where to look for the version of these libs, how to install/compile new ones, whether that is really the issue or not. I am just to ignorant about Linux.
Anybody can hint on what to look for and how to try to debug this behaviour?
I had the same error. What worked for me is to add this line in /etc/environment.
sudo nano /etc/environment
Add this line
QT_X11_NO_MITSHM=1
Source : https://github.com/P0cL4bs/WiFi-Pumpkin/issues/53#issuecomment-309120875
Note that in my case the fix didn't take effect until I rebooted my machine.
you may simply run on the terminal:
export QT_X11_NO_MITSHM=1
I had this same error, so I'll tell you what worked for me.
I think it is a permissions issue, based on the following:
I was logged in through a VNC server window through my account, but within the VNC server was setting up a user profile for "user2". In a 'user2' console I installed anaconda in user2's directory. When I typed spyder in the user2 console, I got the exact error you describe. I guessed the VNC desktop didn't like user2 trying to open a window on user1's profile. I then logged out of my VNC server window, logged into the user2 vnc server window, and in a console typed 'spyder' and it opened perfectly.
I think for some reason it is trying to open but is installed in a directory that you don't have permissions for or trying to open in a window that you don't have access to.
I downloaded the Teradata express VM today. But I don't use vmware... i use virtual box instead. I created a new VM and added all the vmdk disk files to virtual box.
but it is throwing error could not find /dev/disk/by-label/ROOT-BE1. Want me to fall back to /dev/disk/by-path/pci-0000:00
does anyone know how to boot the vm image with virtual box?
I have the same problem, with the same message. The same mistake.
The solution is simple. Just change the Storage Controler to SCSI. After this, restart the VM and it will start normally, but in command line.
I try, but i can't run the startx command...
Try adding IDE controller and then add the disk as existing hard disk device. This should let you boot into the OS.
I saw this exact error when trying to load the VM in KVM. What seemed to fix it was selecting 'single user mode' in the grub menu. After booting like this once, selecting the default grub option subsequently allowed the VM to boot further than this error.
Note that I haven't been able to successfully bring up the actual database yet - the service doesn't start automatically, and when I start it manually, it reboots the VM, bringing me back to the same state as before. Maybe you'll have more luck with VirtualBox?
I Apologize if this question has already been asked. i can't seem to find it anywhere if it has.
I have a custom build script use to syntax check some php files and upload them to a server, and this is executed as a part of the build process. since this script is used to parse inline php statements (embedded in objective c blocks using macros) it's fairly critical this script happens on each build. the actual execution is working fine, i'd just also like to be able to open a particular file when there is an error, and locate the cursor in the approximate location.
i have found that since xcode is configured on my system to open .php files by default (not sure if that's the norm or if i did it manually at some point), using
open filename.php
in a shell script opens the file.
i'd like to be able to specify the line number too.
eg something along the lines of
open filename.php --args --jump-to-line 1234
(--args is a switch for "open" meaning pass the arguments on to Xcode)
any ideas?
You can use the xed command. Only works for Xcode 3 though, not other editors. For Xcode 4, try this
See man xed