Ransom users group

FAQ

Welcome to the ransom FAQ.

Notes about joule.eecs
Notes about joule.eecs.

Why would I want to use joule.eecs?
One major reason to use joule.eecs is that it is located on campus, and accessible from anywhere in the world which has a terminal server client installed (which is, virtually every Windows 2000 machine and newer, along with most Mac OS X machines, and all sophisticated Linux Desktops.

By logging in to joule.eecs, you can use computational facilities which your location in the world might make difficult (a firewall, slow connection, intermittent connectivity), and use them dependably. If you lose your connection to joule.eecs, your state is saved, and you see the same screen on logging in again as you did when you disconnected--it's like you just locked your screen and walked away!

  • Take advantage of Joule's hardware
  • To use MATLAB from off campus if you can't use your H: drive or find the departmental license server
  • Take advantage of TeX writing utilities without having to install them on your computer
  • Use Cygwin utilities

Why is this group called ransom, what was ransom.eecs?
Ransom was the first machine, which has been retired. See What was ransom?.

We used to use newton, now we use joule.

Using the joule.eecs machine

Who can use the joule.eecs machine?
Anyone who is listed in the list of Remote Desktop Users can use the joule.eecs machine. At this time, selected users are chosen by the administrators, and added to this list.

How to I get to use the joule.eecs machine?
Email one of the administrators of joule.eecs, who will:

See the List of admins.

Where should I keep my stuff?
Joule IS NOT BACKED UP!!!

You should store everything either:

  • on your H: drive, or
  • in a CVS/SVN/Git repository, which you check out into your my documents directory
Persons storing data anywhere on the C: or D: drives are asking to lose it, either when we clear off drive space, or when the machine crashes.

If administrators need to clear up diskspace on the machine, they will start with low hanging fruit like c:temp or c:mytemp or c:temp2. In fact, we might start deleting directories like temp2, tempAug15 or temptemptemp just on principle, since you should be putting that stuff in your %TEMP% folder in your local settings. :)

For more information about backups, see https://iris.eecs.berkeley.edu/15-faq/windows/05-backups.html.

As a matter of practice, we don't backup Windows boxes. The problem is that restoring apps is almost impossible because of registry settings etc. Also RAID (if you have it) and Windows recovery points help make this obsolete.

It is faster to document the setup and then just redo the setup.

Also, if you use version control for your files, then losing a disk matters very little.

Who administers joule.eecs?
Current administrators are:
  • Mary Stewart (marys)
  • Christopher Brooks (cxh)

How do I login to joule.eecs?

Windows

Use the Remote Desktop feature, found in
Start->Programs->Accessories->Communication->Remote Desktop Connection

Or....

Type 'mstsc' into the "Run" box, or at a command prompt. mstsc stands for "Microsoft Terminal Server Client"

Linux

Ensure that
krdc
(or rdesktop if you use Gnome) is installed, and connect using the rdp protocol:
rdp://joule.eecs.berkeley.edu/

Mac OS X

Install the Microsoft Terminal Server Client from the Windows Website.

What happens when I disconnect?
When you disconnect from the newton.eecs machine, your session will stay active. Implications of this are:
  • You are still logged in to newton.eecs. To logout, choose that option from the "Start" menu
  • Your status is "disconnected" (not "active") in the administrator browser
  • Your screen is locked (on newton.eecs)
  • If you disconnect, and reconnect immediately, you will see the same screen, just as if you had locked and then immediately unlocked your laptop or desktop
  • If you reconnect from a different machine, you will see the same screen as when you disconnected. This holds as long as newton.eecs stays up, and you do not log out.
  • All programs which you had open will remain open. This excludes programs which may have an automatic logout or quit function after some time (e.g., a timeout on an SSH session).
Do not disconnect your session without saving all of your files, or being prepared to restore them by restarting your simulation. Generally, if you are doing long simulations, you should save snapshots as you go. The admins will only contact active users before restarting or halting the machine.

Software on joule.eecs
This section describes the major software installed on joule.eecs, and makes any special notes on how to use it, or what to do if you can't use it for some reason.

Software List
This (non-comprehensive) list of software makes up the reasons why most people want to use joule.eecs for its software purposes:

June, 2011: Note, not all of this software is installed on joule yet
  • To be installed As these are installed, move the entries to the above section
  • Computational/research Software
    • coLinux
    • Ghostgum and Ghost Script
    • Mathematica 5.1
    • TeXnic Center
    • TeX4PPT
    • VMWare Player
    • WinEdt (trial version only)
  • General Software
  • Blackberry Redirect Software
  • Bülent's Screen Recorder
  • Hello
  • WinZip 8.0 (Professional) (no need for this, Windows has a zip tool)

I need new software, or an upgrade!
See Who do I contact about this site? and ask that it be installed.

Notes for joule.eecs administrators

DNS is required for remote access
Microsoft's Windows Remote Desktop client can be used to connect to many types of machines running Windows.

To connect from a Mac running Microsoft's Remote Desktop Client, the destination machine must either be in the DNS tables or the IP address of the destination machine must be known.

The way to see this is to run the remote desktop client on the Mac and use a network sniffer such as Wireshark to view the network traffic. Connecting successfully to a Windows client shows traffic to the DNS Server such as:

128.32.171.114 128.32.171.23  DNS 83 Standard query A joule.eecs.berkeley.edu
128.32.171.23  128.32.171.114 DNS 373 Standard query response A 128.32.48.212
Using same client to attempt to connect to a machine that does not have a DNS record shows:
128.32.171.114 128.32.171.23  DNS 88 Standard query A brahms.des.eecs.berkeley.edu
128.32.171.23  128.32.171.114 DNS 138 Standard query respone, No such name
However, it is possible to connect to the machine from another Windows box that is in the domain.

This indicates that to use Windows Remote Desktop client on the Mac then the destination machine must be in the DNS tables.

However, the destination Windows machine does not have to have a fixed IP address, the IP address can be allocated from a pool of DHCP addresses.

So, when adding the machine to the network, be sure to request that the machine be added to the DNS tables so that Windows Remote Desktop works from the Mac.

How to enable remote desktop for console login on a Terminal Server?
Windows terminal servers allow arbitrarily many logins to remote terminals, but there is only one console login. In order to connect to the console, a few things must happen:
  1. The user must be in an administrators group of some kind
  2. The console remote desktop must be enabled.
Enabling console remote desktop on the server-side is essentially the same as enabling it for a generic Windows XP machine: Control Panel->System->Remote->Enable Remote Desktop

Connecting to the console, however, is another matter. Once terminal services is enabled, the default connection to remote desktop for the machine will enable a terminal service, not console connection. In order to get a console connection, you must create an *.RDP setting for the machine, and edit it to connect to the console.

For example, for newton.eecs, call up a mstsc (Microsoft Terminal Services Client) or remote desktop connection, add all connectivity info to it, and (after enabling more options), save that remote desktop profile to the desktop as an RDP file, say newton.RDP

Now, edit that file using notepad, and add the following line to the end: connect to console:i:1

Using that connection will connect you to the terminal, if your username allows it. This should only be done with Administrative accounts. Jonathan writes:

... one thing we can try before enabling remote login is to login remotely via the console version of remote desktop.

This is documented via microsoft, but I have not documented it anywhere else, I've attached the console RDP file which I used for ransom and changed the name to newton. When it comes online, you can just use this, and it's like sitting at the console (i.e., no need to be in the machine room). FYI, you can be attached via the console, and via remote desktop, at the same time (w/ two logins).

See this forum article for the RDP file. Microsoft Support notes about using the RDP file.

Microsoft Support: How to enable and to configure Remote Desktop for Administration in Windows Server 2003

How do I allow access?
Note that in Windows 2008 R2, Terminal Server (TS) has apparently been renamed to Remote Desktop Services.

There are two situation:

  1. Terminal Server is not installed
  2. Terminal Server is installed

Terminal Server is not installed

This is probably Window Server 2003 specific.

When a machine is first set up, it does not have Terminal Server installed. See Installing Terminal Server.

If Terminal Server is not installed, then add the user to list of remote desktop adminstrators.

This method will work only if Terminal Server is not installed.

  1. log into the machine using Remote Desktop
  2. In the Start Menu, right click on My Computer and select properties.
  3. In the "Remote" tab, select "Add Remote Users" and then "Add".
  4. Type in the user's name with the domainname, for example:
    EECS/cxh
    
    and the hit the "Check User Name" button
  5. Hit ok until the window is closed.

Terminal Server is installed

If more than two users are to connect, then Terminal Server must be installed. Joule has Remote Desktop Services (formerly known as Terminal Server) Installed.
  1. Start -> Administrative Tools -> Computer management
  2. Select "Local Users and Groups" -> Groups -> Remote Desktop Users
  3. Click "Add"
  4. Type in the user's name with the domainname, for example:
    EECS/cxh
    
    and the hit the "Check User Name" button
  5. Hit ok until the window is closed.
    Note: you must exit the Computer Management tool for the change to take effect.

How to delete a user profile in Windows Server 2003
Grabbed from http://support.microsoft.com/kb/814584

This can be used to delete stale user profile data which is clogging up the c:\ drive.

How to Delete a User Profile To delete a user profile, follow these steps:

  1. Click Start, right-click My Computer, and then click Properties.
  2. In the System Properties dialog box, click the Advanced tab.
  3. Under User Profiles, click Settings.
  4. Click the user profile that you want to delete, and then click Delete.

How do I install matlab on newton?
Borrow the Matlab CD's from the helpdesk. Currently, we are installing Matlab R2006a: Windows.

You will need to install software from 3 CDs. Running autoconf installs all the tool-boxes and simulink. You will need to answer some questions, including the number of CALS to which you are entitled.

When you are asked for the PLP, use the string found in \\winsww\sww\public\matlab\r2006a\. In addition, you will need to add a line to the license.dat file that is installed with the CDs.

If matlab complains that the license file syntax is invalid, it is likely because it is looking for a line in license.dat file that was not installed with the software.

In license.dat, beneath the line:
SERVER cs2.CS.Berkeley.EDU 83052508 27000
insert:
USE_SERVER

For some reason the departmental CDs do not have the latter in the license.dat file, but it is essential.

Members of the appropriate matlab license group should now be able to use remote desktop to run matlab on newton.

This terminal server has exceeded the maximum number of allowed connections

Windows Server 2008

Note that in Windows 2008 R2, Terminal Server (TS) has apparently been renamed to Remote Desktop Session Host. http://www.microsoft.com/windowsserver2008/en/us/licensing-rds.aspx says:
"Remote Desktop Services (RDS, formally known as Terminal Services in Windows Server 2008) functionality in Windows Server 2008 R2"

See http://www.microsoft.com/windowsserver2008/en/us/licensing-terminal.aspx for information about Remote Desktop licensing.

Note that in 1/11, we used the CALs from the EECS Dept. See below for how to set up the licensing..

  1. Start the Server Manager, which is the icon with the server and the toolbox to the right of the Start button.
  2. Roles -> Add Roles -> Check the "Remote Desktop Services" box -> Next -> Next -> Check "Do not require network level authentication" > Check "Per user" -> For "Select User Groups Allowed Access To This RD Session Host Server, click Next -> Install. You will be prompted for a reboot.
  3. After the reboot, start Server Manager.
  4. To use Windows Remote Desktop, you must have Client Access Licenses (CALs). Here in EECS, the CALs are provided to fee paying users who have accounts, which is most likely any one in the EECS Windows domain. So, in Server Manager, do: Roles -> Remote Desktop Services -> RD Session Host Configuration. Click on "Remote Desktop license servers"
  5. In the Properties window, open the Licensing tab and check on "Per User", then hit Add and add the EECS license server tsls.eecs.berkeley.edu.
  6. Close the Properties window.
  7. You should be all set. Note that because the local admin does not have adminstrator access to tsls.eecs.berkeley.edu, you will not be able to determine the number of CALs available. Thus, in Server Manager, the Licensing Diagnosis and other tools will return errors messages such as RDS CALs are not available for this Remote Desktop Session Host server, and Licensing Diagnosis Session Host Server or License server tsls.eecs.berkeley.edu is not available. This could be caused by network connectivity problems, the Remote Desktop Licensing service is stopped on the license server, or RD Licensing is no longer installed on the computer.
If you are wondering about the CALs, try logging in to the machine using an EECS account and ask Wendy to generate a report that lists the CALs.
Old Below Here

Windows 2003

If you get a message "This terminal server has exceed the maximum number of allowed connections" . . .

Jon says:

If we setup our TS clients to use testbox.eecs as the license server, then we can use the CALs from UCB, the same ones that Hermes uses. Since we are hardly ever connected to hermes at the same time we're connected to newton, this is not an issue.
Discussion on serverbeach.com: get more cals

It looks like the default set up has licenses for two connections. The solution is to install Terminal Services and then set the license server to point to testbox.eecs.berkeley.edu.

  1. Start -> Add Remove Programs -> Add Remove Windows Components and the select "Terminal Server"
  2. Use testbox.eecs.berkeley.edu as the terminal server.

Enabling automatic disconnect
To enable disconnect after an idle timeout:
  1. Start -> Enter gpedit.msc into the "Search Programs and Files" entry box
  2. open Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> -> Session Time Limits
  3. Click on "Set time limit for active but idle Remote Desktop Services Connection" and set the time limit to 20 minutes as per UC Berkeley's Physical Security page. Since 20 minutes is not an option, choose 30 minutes.

How do I disable IE Enhanced Security Configuration?
Internet Explorer Enhanced Security Configuration (ESC) is this annoying misfeature in IE that constantly asks you to add sites to a list of secure sites. To disable it:
  1. Start the Server Manager, which is the icon with the server and the toolbox to the right of the Start button.
  2. In the "Security Information" section, click on "Configure IE ESC"
  3. Make sure that IE ESC is Off for both Administrators and Users. Click OK
  4. Restart IE

Virtual Machines on Joule
Joule has Hyper-V installed, so we can run virtual machines

Obtaining Red Hat

  1. See UCB Red Hat Linux
  2. See Microsoft TechNote: Create Virtual Machines.

Obtaining Centos

  1. I installed a BitTorrent client to download CentOS

Obtaining ArchLinux

  1. See website.

Legacy Network Adapter

Step By Step Buid to Install CentOS Linux Virtual Machine in Windows Hyper-V Server suggests
  1. Create the virtual machine
  2. Create the Legacy Network Adapter
  3. Install Centos
  4. Install Linux Service Integration Component
However, it is best to set up the Virtual Network first

Configure Hyper-V to use a Virtual Network

  1. Start up Hyper-V Manager with:
    Start -> Administrative Tools -> Hyper-V Manager
  2. In the left hand tree, under "Hyper-V Manager", select your host.
  3. Action -> Virtual Network Manager
  4. Under "Create Virtual Network", be sure "External" is selected. -> Add
  5. Enter a name such as Virtual Network Adapter #N where N corresponds with the active network adapter of the host.
    Don't know which adapter is active, use Start -> Control Panel -> Network
    Note If you already have a virtual machine, then the host machine will be listed on a different adapter than the physical adapter. One thing to do is to go look at the machine. For Joule, the physical adapter is #3.
  6. Be sure that "Allow management operating system to share this network adapter" is checked.
  7. Hit "Apply"
    Note your host machine will temporarily go off the net while the configuration occurs. Merely reconnect after a minute or so.
One way to test the Virtual Network Adapter is to do the above step, create a virtual machine without an OS and turn it out. The default configuration seems to be to get an IP address via DHCP, so this is a good test.

Create the virtual machine

See Step by Step Guide to Create Windows Hyper-V Virtual Machine.
  1. I did not "Change the default Hyper-V folders"
  2. Start up Hyper-V Manager with:
    Start -> Administrative Tools -> Hyper-V Manager
  3. New -> Virtual Machine
    1. Name: joulecentos -> Next
    2. Memory: 4096Mb -> Next
    3. Configure Networking: select "Local Area Connection 4 Virtual Network" -> Next
    4. Connect Virtual Disk: Use the default -> Next
    5. Installation Options: Install an operating system later -> Next

Create the Legacy Network Adapter

The virtual machine needs to be registered with the department so that it can get an IP address.
  1. Register the virtual machine via the EECS dept. Register a Device page.
    1. Enter the make and model of the host machine
    2. Make the serial number unique by adding something like "virtual 1" to the serial number of the host machine
    3. In the comments, note that the new device is a Hyper-V virtual device on the host machine.
    4. The MAC Address is tricky. The IRIS form will not let you enter the MAC address of the host, the form helps prevent duplicate addresses. I believe that while adding the legacy network adapter, the MAC Address is checked. Other Hyper-V machines have mac addresses that start with 00:15:5D. Vendor/Ethernet/Bluetooth MAC Address Lookup and Search says that addresses that start with 00:15:5D belong to Microsoft, so that is probably a good choice.

Debugging a Legacy Network Adapter

If, after installing an OS, your virtual machine is failing to get an IP address via DHCP, then install Microsoft Network Monitor and scan the different adapters while running dhclient while logged in to the virtual machine.

Unfortunately, I have not found a way to cause the virtual machine to use a different legacy adapter.

Install Centos

See Step By Step Guide To Install CentOS Linux Virtual Machine in Windows Hyper-V Server

Install Linux Service Integration Component

  1. Download "Linux Integration Components for Windows Server 2008 Hyper-V"
  2. Click on the .exe, which will create LinuxIC v2.iso
  3. Using the Hyper-V Manager, mount LinuxIC v2.iso
    1. In Hyper-V Manager, click on the virtual machine and select Action -> Settings.
    2. Under "IDE Controller 1", click on "DVD Drive", browse to LinuxIC v2.iso and mount it
  4. See Step By Step Guide To Install CentOS Linux Virtual Machine in Windows Hyper-V Server

Installing RedHat

  1. Obtain a .iso as above.
  2. In Hyper-V Manager, mount it by clicking on the virtual machine, selecting Settings -> IDE Controller 1 -> DVD Drive ~> Media and then browse to the location of the .iso
  3. Reboot and install. Note that you may need to select the legacy network adapter. If there are two adapters, try eth0 and be sure that it is set to automatically connect

Install Linux Service Integration Component

  1. RedHat 6.0 and 6.1 and Centos 6 require Linux Integration Services Version 3.1 for Hyper-V
  2. Download and mount via Hyper-V Manager
  3. See the pdf for details, but I did:
    mount /dev/cdrom /media
    cd /media/x86_64
    rpm -ivh kmod*
    rpm -ivh microsoft-*.x86_64.rpm
    reboot
    
    It may be necessary to do
    yum update
    yum install redhat-rpm-config rpm-build gcc gnu-pg unifdef
    

Getting the mouse to work

See http://www.jules.fm/Logbook/files/category-hyper-v.html

Notes about Redhat 6.1

See UCB RHEL

Installing ArchLinux

  1. Obtain a .iso as above.
  2. In Hyper-V Manager, mount it by clicking on the virtual machine, selecting Settings -> IDE Controller 1 -> DVD Drive ~> Media and then browse to the location of the .iso
  3. Start up the VM.
Arch does not provide a wizard that will guide you through the installation process. First, load the necessary modules:
modprobe hv_utils hv_netvsc hv_storvsc
Second, make sure networking is up. Manually run the DHCP Client Deamon:
dhcpcd
Verify the connection using the ping-command. If no IP is obtained, review the networking configuration of your VM in the Hyper-V management tool. Consult the Installation Guide to be guided through the process of installing Arch Linux.

Notes

  1. When using the EXT4 filesystem, the hv_storvsc module attempts to zero out bytes in the image (for security reasons), assuming that the host system has a routine for that, but server 2008 doesn't implement that function. This results in a flood of errors in dmesg. For that reason, it's recommended to use another filesystem, e.g. EXT3.
  2. Make sure to load the hv_* modules at start-up by editing /etc/mkinitcpio.conf
  3. Install additional software using Pacman, also see Yaourt
  4. Automatically start dhcp at boot:
    systemctl enable dhcpcd@
    
    (in my installation the network device appeared as enp0s10f0)
  5. To install packages, use sudo pacman -S emacs(see: https://wiki.archlinux.org/index.php/Pacman). We also have yaourt installed, which provides access to the user repositories (see: https://wiki.archlinux.org/index.php/Yaourt). Note that yaourt should not be run as root.
  6. The ufw firewall is installed to pass traffic on ports 22 and 8078
  7. ptango.eecs.berkeley.edu is a CNAME to joulecentos.eecs.berkeley.edu.
  8. See Ptango->wiki->Sandbox for information about the Sandbox.

Windows Remote Desktop Connection stops working after Symantec Endpoint Install
After installing Symantec Endpoint from Software Central, Windows Remote Desktop Connection into Joule stopped working.

However, it was still possible to use Windows Remote Desktop from Joule to another machine.

The reason is that the Berkeley-specific rule that blocks Windows Remote Desktop Connection.

In the task bar at the bottom, click on the Symantec icon. In the "Network Thread Protection" section, right click on "Options" and select "Configure Firewall Rules".

Look for a "RDP" rule and edit it to allow from all machines.

Slow Windows Remote Desktop Connection
Windows Remote Desktop Connection was slow for me. http://itsolutionsdirect.com/slow-rdp-performance-on-a-server-2008-r2-hyper-v-host/253/ suggests "IPv4 Checksum Offload on the Virtual Network Adapter"

See also http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2management/thread/77397541-608f-4d1c-9856-1593f2186f5b/, which suggests

Using regedit, navigate to

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

And on that key, make a new DWORD, and name it DisableTaskOffload. Set its value to 1.

Compilation speed comparison
Below are various build times for Ptolemy II.

Prerequisites: GNU make + other tools (under Windows, install Cygwin, see the Ptolemy II Cygwin instructions, Java 1.6 or 1.7, ant.

To build using make under Linux and Solaris

svn co https://source.eecs.berkeley.edu/svn/chess/ptII/trunk ptII
cd ptII
export PTII=`pwd`
./configure
time make >& make.out
To build using make under Windows
svn co https://source.eecs.berkeley.edu/svn/chess/ptII/trunk ptII
export PTII=c:/Users/Administrator/ptII
cd $PTII
./configure
time make >& make.out
To build using ant
cd $PTII
cp build.xml.default build.xml
ant clean
time ant
To test
cd $PTII
time ant test.single
Name Purchase Date OS/CPU/Cores/Memory Java make Time ant Time tests Time
schubert 1/2012? Debian GNU/Linux 6.0.5 (squeeze) /Intel(R) Xeon(R) CPU X5690 @ 3.47GHz 24 Cores / 96 Gig, SSD java version "1.7.0_03"
Java(TM) SE Runtime Environment (build 1.7.0_03-b04)
Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode)
real 6m53.540s
user 15m18.045s
sys 0m25.918s

real 6m48.920s
user 15m3.328s
sys 0m26.870s

real 6m48.216s
user 14m54.800s
sys 0m27.406s

real 0m20.547s
user 0m46.947s
sys 0m1.336s

real 0m20.257s
user 0m46.151s
sys 0m1.448s

real 0m20.257s
user 0m46.151s
sys 0m1.448s

real 0m38.507s
user 0m41.919s
sys 0m5.664s

real 0m37.471s
user 0m41.615s
sys 0m5.376s

brahms-des 3/2012? Windows 7 /Intel(R) Xeon(R) CPU X5687 @ 3.60GHz 4 Cores / 94 Gig java version "1.7.0_03"
Java(TM) SE Runtime Environment (build 1.7.0_03-b04)
Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode)
real 10m48.239s
user 0m46.607s
sys 1m40.910s
sisyphus 5/2008 Red Hat Enterprise 5.4 / Intel Xeon E5450 @ 3.00GHz 8 Cores / 16 Gig java version "1.7.0_03"
Java(TM) SE Runtime Environment (build 1.7.0_03-b04)
Java HotSpot(TM) Server VM (build 22.1-b02, mixed mode) java version "1.6.0_21"
real 10m32.026s
user 16m54.359s
sys 1m38.834s

real 7m23.984s
user 6m1.575s
sys 1m2.992s

real 7m13.699s
user 5m52.566s
sys 1m0.052s

real 0m34.615s
user 0m28.222s
sys 0m3.308s

real 0m30.809s
user 0m28.822s
sys 0m3.100s

real 0m31.416s
user 0m28.942s
sys 0m3.032s

real 0m54.357s
user 0m48.851s
sys 0m12.037s

real 0m52.919s
user 0m44.571s
sys 0m12.317s

real 0m53.011s
user 0m44.747s
sys 0m12.369s

Joule 11/2011 Windows Server 2008 R2 (with Cygwin) / AMD Opteron 6174 2.20 Ghz (2 Processors) 24 cores / 64 Gig java version "1.7.0_03"
Java(TM) SE Runtime Environment (build 1.7.0_03-b05)
Java HotSpot(TM) Client VM (build 22.1-b02, mixed mode, sharing)
real 52m3.841s
user 5m29.313s
sys 16m43.239s
real 0m50.372s
user 0m0.303s
sys 0m0.847s

real 1m59.496s
user 0m0.455s
sys 0m1.036s

real 2m15.151s
user 0m0.489s
sys 0m1.125s

To build using ant
cd $PTII
make clean
cd ptserver
time ant
Name Purchase Date OS/CPU/Cores/Memory Java make Time ant Time tests Time
sisyphus 5/2008 Red Hat Enterprise 5.4 / Intel Xeon E5450 @ 3.00GHz 8 Cores / 16 Gig java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
real 10m32.026s
user 16m54.359s
sys 1m38.834s
real 0m13.640s
user 0m27.150s
sys 0m2.636s
sisyphus 5/2008 Red Hat Enterprise 5.4 / Intel Xeon E5450 @ 3.00GHz 8 Cores / 16 Gig java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
real 10m20.012s
user 16m5.192s
sys 1m29.986s
real 0m19.131s
user 0m39.214s
sys 0m2.532s
ealmac10 7/2011 Mac OS 10.7 / 2 GHz Intel Core i7 / 4 cores / 4 Gig 1333 MHz DDR3 java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03-383-11A511)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-383, mixed mode)
real 9m42.541s
user 17m50.451s
sys 1m4.735s
real 0m20.582s
user 0m36.571s
sys 0m1.848s
ealmac2 7/2008 Mac OS 10.5.8 / 2.4 GHz Intel Core 2 Due / 2 cores / 4Gig 667 Mhz DDR2 java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-9M3425)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode)
real 23m34.362s
user 29m3.267s
sys 3m31.452s
real 0m39.443s
user 0m51.384s
sys 0m6.181s
real 89m58.929s
user 92m37.841s
sys 13m4.283s
Joule RH VM 11/2011 Red Hat Workstation 6.1 (VM under MS Hyper-V)/ AMD Opteron 6174 2.20 Ghz (2 Processors) 24 cores / 64 Gig java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)

real 25m54.117s
user 24m7.946s
sys 1m33.509s
real 0m47.529s
user 0m44.869s
sys 0m2.331s
carson 6/2005 Solaris 10 / Sparc v9 1280 MHz/ 2 chips/ 2 Gig java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) Server VM (build 21.0-b17, mixed mode)
1631.0u 118.0s 23:53 122% 0+0k 0+0io 0pf+0w
1631.0 seconds of user time = 27:11
118.0 seconds of cpu time = 1:58
23:53 wall clock
142.0u 3.0s 2:23 101% 0+0k 0+0io 0pf+0w
Joule 11/2011 Windows Server 2008 R2 (with Cygwin) / AMD Opteron 6174 2.20 Ghz (2 Processors) 24 cores / 64 Gig java version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
real 25m53.015s
user 23m59.182s
sys 1m35.926s
real 0m50.372s
user 0m0.303s
sys 0m0.847s

Upgrading Java
  1. Google
    java jdk
    
  2. Click on Java SE Downloads, which is http://www.oracle.com/technetwork/java/javase/downloads/index.html
  3. Click on "Java Platform (JDK) XXuXX", which is the first download link
  4. I believe Newton is 32-bit and Joule is definitely 64-bit. For 32-bit vs 64-bit, right click on "Computer" and select properties or see http://chess.eecs.berkeley.edu/ptexternal/nightly/doc/eclipse/windows/32bitVs64bit.htm

Joule

Initial Installation
When setting up Joule, we had a difficult time because of the 32Gig limit for Windows Server.

We then purchased a license for "Windows Server 2008 R2", but accidentally purchased a distribution of "Windows Server 2008 SP2". We then tried to use a MSDN install, but could not get the licensing to work. Then, when doing the install, we were not wiping the disk, so there were files on the disk that were owned by a non-existent user

  1. Register the machine with the department. Be sure to request that the machine be added to the DNS tables so that we can use Windows Remote Desktop to connect from outside the EECS Windows Domain. Registering need happen only once.
  2. During one of the installs, we upgraded Joule's firmware. This needs to happen only once.
  3. Boot and set up a logical disk of about 1 Gig using three drives and a spare. If you have 1.6 Gig, then the machine is misconfigured and is using all 4 drives, we want to use three.
  4. Install Windows Server 2008 R2 Enterprise (Full Installation). We use Enterprise because we want to use all the memory. Use the Key. Be sure to wipe the disk so that there are not orphan files on the disk
  5. Add it to the domain. First, change the name, then reboot, then add it to the domain and reboot.
  6. Run Windows Update
  7. Enabled remote desktop
  8. Add eecs/marys and eecs/cxh as remote desktop users. See How do I allow access?
  9. Create local accounts for marys and cxh on joule with administrative privileges.
  10. Set up Terminal server. See This terminal server has exceeded the maximum number of allowed connections
  11. Enabling automatic disconnect
  12. How do I disable IE Enhanced Security Configuration?
  13. Install 11.0.6 UCB Custom - AV only from http://software.berkeley.edu. Be sure to choose the AV only version (no firewall or intrusion detection). Also, choose the 64-bit version. Note that Symantec Endpoint may interfere with Windows Remote Desktop, see Windows Remote Desktop Connection stops working after Symantec Endpoint Install.
  14. Install the RAID Driver, Firmware update and Client, see Joule RAID System
  15. Install user Software such as Firefox

Joule Firmware Update
To update Joule's firmware, we first created a bootable USB. Note that the program that creates the bootable USB should be run from a mostly empty drive or else the program will copy the contents of the current directory to the USB stick.

The next step is to copy the update files to the bootable USB drive. In our case, they were in a directory named USB_FILES or something similar.

In the boottable USB drive, view the contents of autoexec.bat and be sure that the file that is listed is present on the USB drive.

Joule RAID System
Joule has an "HP P410 with 1G Flash Back Cache Smart Array Controller". 572532-B21

Driver

Go to hp.com Support & Drivers, search for HP P410, find the Windows Server 2008 x63 drivers, download and install "** CRITICAL ** HP ProLiant Smart Array SAS/SATA Controller Driver for Windows Server 2008 x64 Edition", which requires a reboot.

The HP Array Configuration Utility Software shows that we have "HP EF0600FARNA" drives. So, install "RECOMMENDED * Online ROM Flash Component for Windows - EF0300FARMU, EF0450FARMV, EF0600FARNA drives", which requires a reboot. I'm not sure if this needs to be installed each time or not.

Client Program

Install a client program called the "HP Array Configuration Utility Software" (it is at the bottom of the web page). The client program shows that we have a 1Tb RAID5 with a live spare.

Joule RAID Problem

Joule was failing to boot: It hung in exactly the same spot as before, the first operation in the booting process after you see the 'HP ProLiant' splash screen. Details:

Slot 2 HP Smart Array P410 Controller (1024 MB, V.3.50) 1 Logical Drive

  Press < F8 > to run the Option ROM Configuration for Arrays Utility

  Press  to skip configuration and continue
The boot failure seems intermittent.

6/16/11Updated firmware to 3.66. * RECOMMENDED * Online ROM Flash Component for Windows - Smart Array P212, P410, P410i, P411, P712m, and P812
Downloaded cp014344.exe
Running the Array Configuration Utility shows:

RAM Firmware Revision 3.50
ROM Firmware Revision 3.66
After the update the RAM Firmware Revision changed to 3.66

Installed * RECOMMENDED * HP ProLiant Smart Array SAS/SATA Controller Driver for Windows Server 2008 x64 Edition (6.20.2.64 2 Sep 2010) cp013514.exe

7/15/11: used online chat. Case ID 4632163802. The support person suggested RECOMMENDED * Online ROM Flash Component for Windows - Smart Array P212, P410, P410i, P411, and P812 Firmware - Storage Controller Version: 5.06 (B) (29 Jun 2011) After the above update, the splash screen changed from 3.66 to 5.06.

May 8, 2013

Hangs on ? F10/PXE F12 screen after patching by Windows. Mary wrote:

Joule is back up. Note that a 'reset' wasn't the cure. It hung in the same place in the boot process (Press F12 for a PXE boot), so I power-cycled it and that did the trick.

This is after the HP Smart Array P410 initialization and the BMC Firmware screen. There is a delay and then we get BMC message

The screen is

 
Press F10 for ROM-based Setup Utility
Press F12 for PXE Boot

Then, nothing happens. The keyboard is not responsive. Resetting via the front panel brings us back to the same place.

Marten installed HP ProLiant Smart Array SAS/SATA Controller Driver for Windows Server 2008 x64 Edition 6.26.0.64 (released on 19 Feb 2013) and rebooted machine several times; seems to have solved the problem.

The configuration of Joule
Joule is a 12 Core machine with 64 Gig of memory and 1000 gig of raid5 disk. See the quote for Joule.

32Gig limit for WIndows Server 2008 R2
Joule was ordered with 64 gig of memory, but can only use 32 gig.

http://msdn.microsoft.com/en-us/library/aa366778%28v=vs.85%29.aspx#physical_memory_limits_windows_server_2008_r2 has the memory limits

The System control panel of this machine says:

Installed memory (RAM) 64.0GB (32.0 GB usable).

We've had the machine longer than 30 days, so returning the memory is probably not possible. Looking at the HP higher education website, the memory is $1820.

The HP Website also has Windows Server 2008 Enterprise for $2788

SHI has Windows Server 2008 Enterprise for $253.50.

See the Microsoft Server 2008 Enterprise PO

15549858 	P72-03638 	Microsoft Windows Server 2008 Enterprise w/SP2 - Media - volume - DVD - 32/64-bit - English
-Media Only, License also needs to be purchased. 	$19.39 	1 	$19.39
 
15901225 	P72-04236 	Microsoft Windows Server 2008 R2 Enterprise - License - 1 server - EDU - Enterprise, Select, Select Plus - 64-bit - All Languages
-License only. Media can be delivered electronically. 	$253.50 	1 	$253.50

After the install, the System Control Panel says:

Windows edition
Windows Server (R) Enterprise
Copyright (C) 2007 Microsoft Corporation
Service Pack 2
http://knol.google.com/k/leonid-shirmanov/find-out-which-version-of-windows-you/2i969eujgjrbz/17# suggests Start - > ms32info.exe
OS Name   Microsoft (R) Windows Server (R) 2008 Enterprise
Version   6.0.6002 Service Pack 2 Build 6002
http://www.microsoft.com/windowsserver2008/en/us/licensing-rds.aspx says: "Remote Desktop Services (RDS, formally known as Terminal Services in Windows Server 2008) functionality in Windows Server 2008 R2"

Old Hardware
Information about old hardware

What type of machine is newton.eecs?
Newton is a Dell Poweredge 1900

Dell Poweredge 1900 docs

Service Tag: FRBZMC1

Below is the quote we received for Newton on 1/25/07.
DELL  QUOTATION
          
QUOTE #:  
344388760
Customer #:  
42477177
Contract #:  
N39913654
CustomerAgreement #:  
NASPO|WSCA # A63307
Quote Date:  
1/25/07
Date: 1/25/07 4:19:24 PM
Customer Name:  
UC BERKELEY

TOTAL QUOTE AMOUNT:  
$5,897.71 
                                   
                
Product Subtotal:  
$5,415.80 
 
  
Tax:  
$473.91 
  
  
State Environmental Fee:  
$8.00 
   
Shipping & Handling:  
$0.00 
   
Shipping Method:  
Ground 
Total Number of System Groups:  

 GROUP: 1
 QUANTITY: 1 
SYSTEM PRICE: $5,423.80 
  GROUP TOTAL: $5,423.80 
 
 

Base Unit: 

Quad Core Xeon Processor E53352x4MB Cache, 2.0GHz, 1333MHz FSB, PE1900 (222-7689)

Processor: 

Quad Core Xeon 2nd Processor E5335, 2x4MB Cache, 2.0GHz 1333MHz FSB, PE1900 (311-7057)

Memory: 

4GB 533MHz (4x1GB), Dual Ranked DIMMs (311-5729)

Keyboard: 

Keyboard, USB, Black (310-8170)

Monitor: 

Dell E177FP,17 Inch Flat Panel17.0 Inch Viewable Image Size for PowerEdge (320-5091)

Video Card: 

BCOM, TOE ENABLED, MS OS ONLY (430-2007)

Hard Drive: 

500GB, SATA II, 3.5-inch, 7.2KRPM Hard Drive (341-3875)

Hard Drive Controller: 

No Controller (341-3933)

Floppy Disk Drive: 

No Floppy Drive (341-3052)

Operating System: 

Windows Server 2003 R2 Enterprise Edition, Academic Includes 25 CALs (420-5801)

Mouse: 

Optical Two-Button Mouse USB, Black (310-8172)

NIC: 

Embedded Broadcom NetXtreme II5708 GigabitEthernet NIC (430-1764)

TBU: 

No Tape Drive (341-4205)

CD-ROM or DVD-ROM Drive: 

48X IDE CD-RW/DVD ROM Drive for PowerEdge 2900/1900 (313-4571)

Documentation Diskette: 

Electronic Documentation and OpenManage CD Kit, PE1900 (310-8292)

Feature 

Integrated SATA, No RAID (341-4014)

Service: 

GOLD Enterprise Support: 4-Hour 7x24 Onsite Service with Emergency Dispatch, Initial Year (980-7120)

Service: 

Dell Hardware Warranty, Extended Year (985-3298)

Service: 

Dell Hardware Warranty Plus Onsite Service Initial Year (985-3307)

Service: 

Premier Enterprise SupportService Gold Welcome Letter (310-3785)

Service: 

GOLD Enterprise Support: 7x24Escalation Manager, Hw/Sw TechPhone Support, Enterprise Command Center, 3 Year (980-0682)

Service: 

GOLD Enterprise Support: 4-Hour 7x24 Onsite Service with Emergency Dispatch, 2 Year Extended (980-0492)

Installation: 

On-Site Installation Declined (900-9997)

 
 

SALES REP:  
  PETE OTERO
PHONE:  

  1800-274-7799 

Email Address:  

  Pete_Otero@Dell.com

Phone Ext:  

  72-45526


For shipments of certain products to California, a State Environmental Fee of up to $10 per item has been added to your quote.

For your convenience, your sales representative, quote number and customer number have been included to provide you with faster service when you are ready to place your order. Orders may be faxed to the attention of your sales representative to 1-800-365-5329. You may also place your order online at http://www.dell.com/hied/qto

Unless you have a separate agreement with Dell, the terms and conditions found at http://ftpbox.us.dell.com/slg/resellers/resellertcs.htm shall govern the sale and resale of the Products and Services referenced in this quotation

Prices and tax rates are valid in the U.S. only and are subject to change.

**Sales/use tax is a destination charge, i.e. based on the "ship to" address on your purchase order. Please indicate your taxability status on your PO. If exempt, please fax exemption certificate to Dell Tax Department at 888-863-8778, referencing your customer number. If you have any questions regarding tax please call 800-433-9019 or email Tax_Department@dell.com.

All product and pricing information is based on latest information available. Subject to change without notice or obligation.


LCD panels in Dell products contain mercury, please dispose properly. Please contact Dell Financial Services' Asset Recovery Services group for EPA compliant disposal options at US_Dell_ARS_Requests@dell.com. Minimum quantities may apply.

Dell has a 30 day return policy for new products purchased directly from Dell.

Dell's Total Satisfactions Return Policy may be found at "http://www.dell.com/us/en/hied/misc/policy_010_policy.htm"

Shipments to California: For certain products, a State Environmental Fee Of Up to $10 per item may be applied to your invoice as early as Jan 1, 2005. Prices in your cart do not reflect this fee. More Info: or refer to URL www.dell.com/environmentalfee

Why is the name "newton"?
The machine "newton.eecs.berkeley.edu" is named after Professor A. Richard Newton.

What was ransom.eecs?

Ransom retired in April, 2007, see What's newton?

ransom.EECS.Berkeley.Edu was a dual processor, Pentium Xeon 3.06 GHz, with 4 GB of RAM and 240GB of hard drive space. It was running Windows Terminal Server 2003, and has a bunch of software installed, which can be used by any user on the machine.

Ampere
Ampere is a proposed new machine.

Ampere Specification
Joule seems slow for high performance activities, see Compilation Performance.

So, we are specifying a new machine.

We need:

Schubert is an IBM 3550 M3, Xeon(R) CPU X5690 @ 3.47GHz 24 Cores / 96 Gig, SSD

/proc/cpuinfo says 24 cores which is because this machine has two chips with 6 cores with 2 threads each. See https://answers.launchpad.net/ubuntu/+source/linux/+question/187310.


Below here is from August, 2011 HP ProLiant DL380 G7 High Performance Server

CPU

Joule has two 12-Core AMD Opteron Processor Model 6174 (2.2GHz) The proposal is for: 2 Six-Core Intel Processors X5690 (3.46GHz, 12M L3 Cache, 130 Watts) Note that Wikipedia says there is Xeon X5698 4.40Ghz. CPU World says a $43,842. This machine has 2 2 core chips.

Memory

Memory is confusing, there are many options.
  • Proliant Servers White Papers
    • HP ProLiant Intel-based 300 series G6 and G7 servers
      • HP Memory Configurator
        • RDIMM vs UDIMM
          "RDIMM or Registered - Highest maximum capacity Larger capacities and include address parity protection & advanced memory protection. Less electrical load on the memory controller; allows systems to remain stable with more memory modules. Used for applications requiring scalability and stability."

          "UDIMM or Unbuffered - Limited capacity. Lower power consumption, limited in capacity but generally lower in price."

          This says we want RDIMM.
        • The configurator says to get 144Mb, we want
          Qty 6 x HP Option Part# 500662-B21 HP 8GB 2Rx4 PC3-10600R-9 Kit (HP Module Part# 500205-071) STD
          Qty 6 x HP Option Part# 627812-B21 HP 16GB 2Rx4 PC3L-10600R-9 Kit (HP Module Part# 628974-081) LV
  • Intel DDR3 Memory suggests 1333Mhz memory with 1dimm/channel (X5690 has three channels). This points to 8gig of 16gig dimms

Disk

15k SAS 3.5" so we have larger capacity. This means a LFF (Large Form Factor) disk.

Machines

HP ProLiant DL360 G7
X5690 3.46Ghz, 2.5" disk
HP ProLiant DL370 G6 LFF Rack Server
X5690 3.46Ghz, 3.5" disk. Rack Server?
HP ProLiant DL380 G7 High Performance Server
X5690 3.46Ghz, 3.5" disk.
You are not logged in 
Contact 
©2002-2014 U.C. Regents