I have recently download "QuickStart VM" on http://www.cloudera.com
(precisely, the version of virtualbox)
This virtual machine use centOS (and my computer is a macbook air)
I can not fully start this virtual machine(and I do not know why)
I have attached a screenshot of the most advanced state of booting
I've discovered that when your screen appears to be frozen at that location, pressing [ESC] is apparently what you're supposed to do next.
Mine was there, sitting there for a few minutes, I clicked esc and then a whole list of things started checking and installing, then the Cloudera GUI popped up.
Had the similar issue. Fixed with:
Download cloudera-quickstart-vm archive.
Start Virtual Box.
Go to menu: File -> Import Appliance...
Choose cloudera-quickstart-vm-*-virtualbox.OVF file (from downloaded archive)
Follow hints and the new Virtual machine will be created using cloudera-quickstart-vm-*-virtualbox-disk1.VMDK
Enhance the new VM settings like: add CPUs, add RAM, etc.
Start the new VM, takes a few minutes.
Press ESC and rest of startup scripts would run with that. Finally you would land on Cloudera screen.
You may try with the last version, based on CentOS 6.5 (It perfectly works on my iMac, vmware and parallels)
Etan is right, it can be pretty long to initiate CentOS when you are in this particularly point, especially if you didn't modify the default parameters of the quickstart (1 o 2GB RAM, 1 core)
If your macbook have more than 4GB RAM, try to start the VM with 4GB RAM and 2 cores, it should be better. Don't forget you need more than 8GB RAM dedicated to the VM to correctly run the Cloudera Manager, too.
Related
Three weeks ago, I ditched Sublime in favour of Visual Studio Code. Everything was going great till the program started taking upwards of 30 seconds to start up (launch, show visual feedback) and another 20 or so to boot up (fill in syntax colours, load extensions, and stop stuttering). In the worst instances, it takes minutes to boot up (I used a stopwatch).
At first, I guessed that extensions cost me a lot in start-up time, so I uninstalled most of them. After that, I added 2GB of RAM to my system, moved my CPU to another laptop (smaller chassis, less PPI), swapped my HDD to an SSD, and reinstalled Windows. I didn't make these changes to help VS Code's start/boot time but for other reasons. But even after all these upgrades, VS Code's start-up time seems to increase as time goes by (even without changes to my "Workbench"). Is this normal? What makes it so?
My PC setup is: Core i5 520M # 2.4 Ghz, 6GB DDR3 RAM, 128GB Micron SSD.
My VS Code setup has five extensions installed, about thirteen lines in settings.json (including autoSave, JetBrains Mono font, colour themes for Light and Dark mode), and syncs settings to my Microsoft/GitHub account.
Since you've mentioned a DDR3 RAM I assume your system is quite old and 520M i5 CPU is really old (It's a 1st gen processor). Do you have similar problems with any other applications or is it just VSCode?
If you are confident that your system is not the problem you can try this;
As others have noted, It is based on Electron so under the hood you have Node & Chromium. You cannot have high expectations from something built on Electron which is known for it's notorious memory footprints. However, 30 seconds startup time is still long. It takes roughly 5-6 seconds in my machine to load and become fully functional, with 9 extensions installed (which are quite large extensions btw).
Another note here is that even when you uninstall a VSCode plugin/extension the directory of that extension never gets removed, VSCode just marks them as Obsolete in a JSON file and keeps the directories for whatever reason. You could try uninstalling & reinstalling, which might help. A simple uninstall will not be of much help since VSCode has cache & configuration directories that are not typically removed upon an uninstall. You'd have to manually remove them. If you are on a Windows machine check
C:\Users\<your name>\.vscode,
C:\Users\<your name>\AppData\Local\Microsoft and
C:\Program Files\Microsoft VS Code
for any leftovers related to VSCode and remove them.
The reason for this to wipe the previous install without any trace (you'll lose all your customizations since they are stored & kept in these directories even after uninstalls, so that when you reinstall, VSCode can access & load your previous configurations which makes your life easier btw)
Try reinstalling after. If you are on a UNIX system look up the equivalent directories, remove the leftovers and do a clean reinstall. Hope this helps.
I am trying to install CentOs 6.7 on a VPS. I downloaded the LiveCD iso from CentOs's website and put it on a bootable thumb drive, and even burned it to CD, however when booting from either sources, I get this error.
I have even re-download the same file from different source links but the same thing happens.
use second newest kernel.
i.e:
During a startup, press ESC to stop the boot
login and remove the kernel you are using. download the newest kernel then restart
I want to install some plugins and upgrade some to the latest version. They are not included in the Eclipse SDK downloads. So I must install the individuals manually.
The problem is, the network connection to the update site is very slow. (Maybe 1k bytes per second, or lower) Currently, I have an Amazon EC2 box in us-east-1 region, which is a lot faster to the update site. So, I'd like to install the plugins in EC2 box, and then copy them back to my local machine (in China).
That will look like:
very slow, or inaccessible
My machine #China <-----------------------------------> Update Sites
(1k bytes/sec)
|
|
|
V
much faster fast
My machine #China <-----------------> EC2 #US-east <------------------> Update Sites
(100k bytes/sec) (1M bytes/sec)
Now, my EC2 box is running Debian linux, I'm not going to install X windows there, so it can't start Eclipse in GUI mode. Though, I hope I can get updates from command line only.
EDIT
To clarify the question: how to "Install Software" for Eclipse in command line? Since Eclipse is OSGi-based, I guess I can do it using some kind of osgi shell, maybe?
You can install and delete plugins for eclipse through a CLI. This is possible through the p2.director:
https://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fp2_director.html
In regards to updating eclipse through CLI, I stumbled across this question looking for that answer.
When i work with NetBeans 6.9 for PHP the javaw.exe is occupying more then 50% of CPU and about 450mb ram (ram is not really the problem) but CPU tend to overheat.
I had jdk6.5 for 64bit sys and now updated to latest jdk6.21 but it is the same, the CPU is always near 100%
is there a solution to this high requirements of javaw.exe?
OS: Win7 64bit
UPDATE:
I installed the NetBeans 6.7.1 the one that worked EXCELLENT to compare with 6.9.
so:
6.7.1 less memory usage by javaw.exe then 6.9 but cpu still in use > 50% nonstop
then:
I installed the JDK6_21 32bit cause i had 64bit and in the config (netbeans.conf) file set the path of the 32bit JDK.
6.9 less memory CPU still to high
6.7.1 less memory NO CPU usage when idle
SO im gonna downgrade to the 6.7.1 because it works for me and i dont really need the 6.9 cause i dont really use the new features that offers.
btw. 6.8 was crashing with no reason, so that option is out.
You could configure Netbeans to run java.exe instead of javaw.exe, and see if the behavior is still the same.
If it's the same, this is clearly a Netbeans problem, so I would suggest reporting this problem to Netbeans, since this is the way bugs get usually fixed :).
One thing you should consider doing on Netbeans (and Eclipse... and $insertOtherIDE) is to turn off automatic project indexing, compile on save, and other things that cause lots of work to happen in the background without your prompting.
In Netbeans 6.9, external scanning/indexing tends to be the biggest culprit when dealing with projects of considerable size. Try disabling it by (and these instructions are for the Mac, I assume they are similar on Windows)
Go to Preferences
Click on Miscellaneous
Click on the Files Tab
Deselect "Enable auto-scanning of sources"
After this you can force NB to re-scan by clicking Source->Scan For External Changes in the menu (might be Mac specific, again).
See if that helps you out at all...
I had the same problem (Win7 64bit). Everything was working, but suddenly (I think after refactoring some stuff) javaw.exe was constantly using the cpu.
After clearing the netbeans cache, everything was working again (delete the contents of the cache folder and restart Netbeans).
%UserProfile%\.netbeans\6.9\var\cache\
I had to do this before after getting strange errors in Netbeans and most of the time it solved the problems. I think sometimes it just gets out of sync.
I'm using NetBeans 6.7 on win xp*. I'm not really sure what the pattern is, but lately performance has gotten really bad to the point where it's almost unusable. Any ideas for where to look for slowdowns?
Intel Core Duo 2.2 GHz, 3.5 GB or ram, accoring to the system properties panel. 90 GB of free hard disk space.
NetBeans 6.5 "leaks" temporary files. It creates temporary files in %TEMP% (typically c:\\Documents and Settings\\*username*\\Local Settings\\Temp) and does not delete them. When enough files accumulate, access to the temporary directory slows to a crawl. That in turn drags NB down to a crawl.
To clean it up:
Shut down NetBeans
Open a command prompt and type:
cd %TEMP%
del *.java
del *.form
del output*
del *vcs*
Important:
Do not try to do this with windows explorer. It won't work.
The deletes can take several minutes each. Be patient.
This is much better in 6.7 and I have not seen it at all in 6.8.
If you're running on java6 you can use the jconsole app to connect to your running netbeans instance and see among other things, what the threads are doing, memory usage and whether you're in a race condition.