We had to reboot Fileservice for maintenance at 7:50pam.  The 
	reboot intitiated a filecheck that lasts nearly an hour.  This 
	insures the health of the home directory files that are on the 
	disk, but we had hoped that it would not be needed during this 
	reboot.  We regret that it has interfered with scheduled 8am 
	labs in 105 Cory and 140 Cory.

	The Instructional UNIX systems will be inaccessible from about 
	10am-5pm on Wed Aug 20 while we move home directories to new,
	larger disks.  The Instructional UNIX systems include:
	
	workstations in 275 Soda
	SunRays in 271, 273, 277 Soda
	workstations in 353 Cory
	servers listed in http://inst.eecs.berkeley.edu/cgi-bin/clients.cgi?choice=servers

	If you try to login using Putty from a Windows system while the 
	servers are disabled,  Putty will just die after you login.  This 
	is becuase Putty fails to pause long enough for you to read the
	'nologin' message that the server displays.

	Monday 2:40 am:  
	The Instructional UNIX /home/* disk became 100% full tonight.
	This prevents users from saving files and logging out from
	their UNIX accounts and it will prevent them from logging in
	on our UNIX Xterminals.

	It appears that the /home/tmp directories of CS186 students 
	are filling the disk.  CS186 directories on /home/tmp have 
	been restricted to 250 MB each until we can find a new server 
	for them.

	It the meantime, you could save critical files that you have
	opened by emailing them to yourself at another account (not 
	EECS Insrtuctional).

	(Mar 19, 1am) WEB sites under http://inst.eecs.berkeley.edu are 
	accessible again.  The problem was with the firewall, which we 
	had modified in response to the excessive downloads from a non-UCB 
	source that started jamming the server at about 6:30pm.

	The server was mostly down from 6:30pm March 18 until 1am March 19.

	You may have noticed delays of several seconds on some Instructional
	UNIX computers when doing things that accesses files, such as listing 
	a directory ("ls") or saving a file.  We have observed that our main 
	UNIX file server (an old Network Appliance server) is often hitting 
	100% cpu usage, which is a new anomoly this semester.  We are working 
	with an outside vendor to analyze the logs and determine if any 
	components are failing.

	The problem has become more noticable at the end of the semester as 
	user traffic has increased.  We hope to find a solution soon.

	In any case, we plan to retire this server next summer and have 
	already started to migrate software from it to a new server.  In 
	addition, the Network Appliance server includes a second, redundant 
	server.  So we have alternatives if the problem gets worse!

	Reminder - no legitimate service provider will ask you to send your
	username and password in email, so if you receive such a request it is 
	probably from a spammer trying to steal your identify.   Don't reply,
	and don't go to any WEB sites that are referenced in the message.

	Check the return address carefully of any email to which you do reply.

	For example, we recently received email from "helpdesk@berkely.edu", 
	with the signature

		Berkely University Of California
		Campuswide IST Service Help Desk

	 asking you to sent them your ID/EMAIL and Password.   Besides the
	 misspelling of "Berkeley", we noticed that the sender and return 
	 email addresses are really help.desk@inbox.lv and helpdeesk@live.com.
	 In many email programs, you'd have to expand the message to "full 
	 header" before you would see that.

	 Spammers may also pretend to be a bank asking for your account number,
	 on-line banking password, ATM code or etc.

	 Some spammers are very clever, so be aware!

	The popular Instructional UNIX server named cory.eecs.berkeley.edu
	stopped accepting login connections sometime over the weekend and 
	was generally unresponsive until 12:30pm today.  This morning, we
	diagnosed this recurring problem.  We found that there is a bug in 
	the "ldap_cachemgr" deamon.  We will patch it.

	cory.eecs also runs the Synopsys/HSPICE/TCAD license server that
	is shared by the department.  We believe that those licenses were
	accessible even when users could not login to cory.eecs.

	There was an intermittent failure of the department servers for 
	DNS and XNTP services.  Side effects included slow logins, slow
	WEB access and slow access to servers in general (including the
	file servers for programs like firefox).

	DNS resolves hostnames to IP addresses.
	XNTP synchronizes the time on the computers.

	This has been occurring for a week and was particilarly noticable
	today.  The history and symptoms are logged under
	https://iris.eecs.berkeley.edu/news/2092-network-problems-in-eecs

	We believe that the problem was resolved at about 4pm today.

	The popular Instructional UNIX server named cory.eecs.berkeley.edu
	stopped accepting login connections at about 6:30pm, and existing
	login sessions froze erratically.  We rebooting cory.eecs at 8pm
	to fix this problem.  

	cory.eecs also runs the Synopsys/HSPICE/TCAD license server that
	is shared by the department.  Those licenses were not accessible
	during the 10-minute reboot around 8pm.

	These Instructional servers are down for maintenance until further
	notice:

	pulsar.eecs.berkeley.edu
	quasar.eecs.berkeley.edu
	icluster.eecs.berkeley.edu
	ilinux{2,3}.eecs.berkeley.edu
	iserver{2,3}.eecs.berkeley.edu
	anand.eecs.berkeley.edu
	
	This is necessary while an electrical problem is repaired in the
	server machine room.  This problem appeared after the Cory Hall 
	power shutoff on May 29.

	For named accounts:

	Login as 'newacct' (password 'newacct') again (in 199 Cory, 273 Soda or 
	'ssh' to cory.eecs.berkeley.edu).  Enter your Student ID number.  Then 
	select the new "p" option for resetting your password and reprinting a 
	form.  The form with a new password will be emailed to you the next 
	day (weekday) or sooner.

	Named accounts look like 'gbush' or 'bclinton'.

	For class accounts:

	Go to the Instructional sys admin staff in 333 Soda, 378 Cory or 
	386 Cory.  Bring your initial class account form or student ID card.
	There is no on-line procedure for resetting the password of a class 
	account.

	Class accounts look like 'cs61a-aa' or 'ee141-agore'.

Symptoms when UNIX email or home directories are missing:

	- when you try to login the screen freezes 
	- you see the error message "home directory is /" 
	- session hangs up if you try to 'ssh' into an Instructional computer
	- unable to read WEB pages from the http://inst.eecs.berkeley.edu 
	- lots of annoying "NFS timeout" error messages on your screen
	- new email deliveries will be delayed on imail.eecs 

	While the server is down, you may not be able to logout in our labs
	because you can't type any commands.  On a SunRay, even turning it
	off doesn't log you out.  The support staff check the labs after 
	events like this to be sure everyone gets logged out.  We also post 
	information about the problem at http://inst.eecs.berkeley.edu to 
	help students find out when the problem has been fixed.   So all you 
	can really do in this case is to wait until the problem is fixed, go 
	back to the lab (or login to the SunRay server for that lab) and log 
	yourself out, or let us log you out.

	We disable email receipt and relaying through imail.eecs when the
	home directory server (mamba.cs.berkeley.edu) is down.  No mail is 
	lost.  Computers that send mail queue messages that are not accepted
	by a remote server, and they resend the messages periodically until 
	they are received.