id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
656	Project server crashed - client messed the computer location.	Pepo	davea	SETI's BOINC database server crashed today. Few minutes later my host contacted it:\r\n\r\n{{{\r\n19:48:15 [SETI@home] [sched_op_debug] Starting scheduler request\r\n19:48:15 [SETI@home] Sending scheduler request: To fetch work.  Requesting 8 seconds of work, reporting 0 completed tasks\r\n19:48:20 [SETI@home] Scheduler request succeeded: got 0 new tasks`\r\n19:48:20 [SETI@home] [sched_ops_debug] Server version 601\r\n19:48:20 [SETI@home] Message from server: Server can't open database\r\n19:48:20 [SETI@home] Project requested delay of 3600.000000 seconds\r\n19:48:20 [SETI@home] New computer location: \r\n19:48:20 [---] General prefs: from SETI@home (last modified 13-May-2008 10:27:28)\r\n19:48:20 [---] Host location: none\r\n19:48:20 [---] General prefs: using your defaults\r\n19:48:20 [---] Reading preferences override file\r\n19:48:20 [---] Preferences limit memory usage when active to 1023.02MB\r\n19:48:20 [---] Preferences limit memory usage when idle to 1841.44MB\r\n19:48:20 [---] Preferences limit disk usage to 0.00GB\r\n}}}\r\n\r\nsched_reply_SETI.xml contained just following:\r\n\r\n{{{\r\n<scheduler_reply>\r\n<scheduler_version>601</scheduler_version>\r\n<master_url>http://setiathome.berkeley.edu/</master_url>\r\n<request_delay>3600.000000</request_delay>\r\n<message priority="low">Server can't open database </message>\r\n<project_name>SETI@home</project_name>\r\n</scheduler_reply> \r\n}}}\r\n\r\nThe host was "thrown off" from its venue and related settings and the mess started: the machine was constantly suspending/resuming CPU throttling, switched off network and effectively nothing was being crunched anymore.\r\n\r\nThe client should be resistent against such empty returned data.	Defect	closed	Major	6.2	Client - Scheduler Policy	6.2.1	fixed		Pepo