User Reported Problems - Revision history

Benrwong at 18:31, 26 February 2018

2018-02-26T18:31:05Z

← Older revision		Revision as of 18:31, 26 February 2018
Line 6:		Line 6:
	mag reported that n-1-113 seemed to indicate she had jobs running. Upon checking n-1-113, there was no active process with her name yet the SGE queue indicated she had an active job. This problem only seemed to happen on n-1-113 and n-1-105. We have rebuilt n-1-113 and n-1-105 to see if this will resolve the issue. Foreman/puppet did not indicate any errors with configuration drift.		mag reported that n-1-113 seemed to indicate she had jobs running. Upon checking n-1-113, there was no active process with her name yet the SGE queue indicated she had an active job. This problem only seemed to happen on n-1-113 and n-1-105. We have rebuilt n-1-113 and n-1-105 to see if this will resolve the issue. Foreman/puppet did not indicate any errors with configuration drift.
	8/29/2017 mag's history file keeps blowing up with strange content. When she deletes the .history file and logs back in to gimel, the same content will reappear. Investigate either gimel/dalet. Could be issue on where nfs-homes are or gimel.		8/29/2017 mag's history file keeps blowing up with strange content. When she deletes the .history file and logs back in to gimel, the same content will reappear. Investigate either gimel/dalet. Could be issue on where nfs-homes are or gimel.
			**SOLVED: this was due to a bug with tcsh. Updating tcsh helps.


	9/12/2017 Yvonne's printer is repaired physically but network configuration needs to be set up properly. Having trouble doing that. Reported to UCSF IT INC3423618		9/12/2017 Yvonne's printer is repaired physically but network configuration needs to be set up properly. Having trouble doing that. Reported to UCSF IT INC3423618
			**SOLVED: UCSF IT fixed.


	[[Category:Problems]]		[[Category:Problems]]

Benrwong at 16:52, 12 September 2017

2017-09-12T16:52:23Z

← Older revision		Revision as of 16:52, 12 September 2017
Line 6:		Line 6:
	mag reported that n-1-113 seemed to indicate she had jobs running. Upon checking n-1-113, there was no active process with her name yet the SGE queue indicated she had an active job. This problem only seemed to happen on n-1-113 and n-1-105. We have rebuilt n-1-113 and n-1-105 to see if this will resolve the issue. Foreman/puppet did not indicate any errors with configuration drift.		mag reported that n-1-113 seemed to indicate she had jobs running. Upon checking n-1-113, there was no active process with her name yet the SGE queue indicated she had an active job. This problem only seemed to happen on n-1-113 and n-1-105. We have rebuilt n-1-113 and n-1-105 to see if this will resolve the issue. Foreman/puppet did not indicate any errors with configuration drift.
	8/29/2017 mag's history file keeps blowing up with strange content. When she deletes the .history file and logs back in to gimel, the same content will reappear. Investigate either gimel/dalet. Could be issue on where nfs-homes are or gimel.		8/29/2017 mag's history file keeps blowing up with strange content. When she deletes the .history file and logs back in to gimel, the same content will reappear. Investigate either gimel/dalet. Could be issue on where nfs-homes are or gimel.
			9/12/2017 Yvonne's printer is repaired physically but network configuration needs to be set up properly. Having trouble doing that. Reported to UCSF IT INC3423618

	[[Category:Problems]]		[[Category:Problems]]

Benrwong: included problem that mag informed me about

2017-08-29T21:10:45Z

included problem that mag informed me about

← Older revision		Revision as of 21:10, 29 August 2017
Line 4:		Line 4:

	08/03/2017 11:00		08/03/2017 11:00
	~~mko~~ reported that n-1-113 seemed to indicate she had jobs running. Upon checking n-1-113, there was no active process with her name yet the SGE queue indicated she had an active job. This problem only seemed to happen on n-1-113 and n-1-105. We have rebuilt n-1-113 and n-1-105 to see if this will resolve the issue. Foreman/puppet did not indicate any errors with configuration drift.		mag reported that n-1-113 seemed to indicate she had jobs running. Upon checking n-1-113, there was no active process with her name yet the SGE queue indicated she had an active job. This problem only seemed to happen on n-1-113 and n-1-105. We have rebuilt n-1-113 and n-1-105 to see if this will resolve the issue. Foreman/puppet did not indicate any errors with configuration drift.
			8/29/2017 mag's history file keeps blowing up with strange content. When she deletes the .history file and logs back in to gimel, the same content will reappear. Investigate either gimel/dalet. Could be issue on where nfs-homes are or gimel.


	[[Category:Problems]]		[[Category:Problems]]

Benrwong at 18:16, 4 August 2017

2017-08-04T18:16:20Z

← Older revision		Revision as of 18:16, 4 August 2017
Line 4:		Line 4:

	08/03/2017 11:00		08/03/2017 11:00
	~~mkorcz~~ reported that n-1-113 seemed to indicate she had jobs running. Upon checking n-1-113, there was no active process with her name yet the SGE queue indicated she had an active job. This problem only seemed to happen on n-1-113 and n-1-105. We have rebuilt n-1-113 and n-1-105 to see if this will resolve the issue. Foreman/puppet did not indicate any errors with configuration drift.		mko reported that n-1-113 seemed to indicate she had jobs running. Upon checking n-1-113, there was no active process with her name yet the SGE queue indicated she had an active job. This problem only seemed to happen on n-1-113 and n-1-105. We have rebuilt n-1-113 and n-1-105 to see if this will resolve the issue. Foreman/puppet did not indicate any errors with configuration drift.


	[[Category:Problems]]		[[Category:Problems]]

Benrwong at 18:08, 4 August 2017

2017-08-04T18:08:02Z

← Older revision		Revision as of 18:08, 4 August 2017
Line 1:		Line 1:
	This is a log of errors that users have informed us about. Date & time the error, who reported it, what machine it happened on. Update it when you attempt to resolve it. If it has been resolved, report what was done to address the issue and leave it here for a month. We'll make another page with problems that were resolved (soonish).		This is a log of errors that users have informed us about. Date & time the error, who reported it, what machine it happened on. Update it when you attempt to resolve it. If it has been resolved, report what was done to address the issue and leave it here for a month. We'll make another page with problems that were resolved (soonish).

	~~[[[~~Current Problem List~~]]]~~		===Current Problem List===

	08/03/2017 11:00		08/03/2017 11:00

Benrwong at 18:07, 4 August 2017

2017-08-04T18:07:49Z

← Older revision		Revision as of 18:07, 4 August 2017
Line 1:		Line 1:
	This is a log of errors that users have informed us about. Date & time the error, who reported it, what machine it happened on. Update it when you attempt to resolve it. If it has been resolved, report what was done to address the issue and leave it here for a month. We'll make another page with problems that were resolved (soonish).		This is a log of errors that users have informed us about. Date & time the error, who reported it, what machine it happened on. Update it when you attempt to resolve it. If it has been resolved, report what was done to address the issue and leave it here for a month. We'll make another page with problems that were resolved (soonish).

			[[[Current Problem List]]]

	08/03/2017 11:00		08/03/2017 11:00

Benrwong: A page for current problems users have told us about

2017-08-04T18:07:28Z

A page for current problems users have told us about

New page

This is a log of errors that users have informed us about. Date & time the error, who reported it, what machine it happened on. Update it when you attempt to resolve it. If it has been resolved, report what was done to address the issue and leave it here for a month. We'll make another page with problems that were resolved (soonish).

08/03/2017 11:00
mkorcz reported that n-1-113 seemed to indicate she had jobs running. Upon checking n-1-113, there was no active process with her name yet the SGE queue indicated she had an active job. This problem only seemed to happen on n-1-113 and n-1-105. We have rebuilt n-1-113 and n-1-105 to see if this will resolve the issue. Foreman/puppet did not indicate any errors with configuration drift.

[[Category:Problems]]