"! bad user" in /var/cron/log - Revision history

Hutch at 18:04, 3 July 2008

Hutch — Thu, 03 Jul 2008 18:04:20 GMT

←Older revision		Revision as of 18:04, 3 July 2008
Line 8:		Line 8:

	Restarting the ''cron'' daemon fixed the problem; sending the ''cron'' daemon a SIGHUP did not.		Restarting the ''cron'' daemon fixed the problem; sending the ''cron'' daemon a SIGHUP did not.
-	! SIGTERM Fri Apr 25 10:36:21 2008	+	! SIGTERM Fri Apr 25 10:36:21 2008
	! ***** CRON ABORTED ****** Fri Apr 25 10:36:21 2008		! ***** CRON ABORTED ****** Fri Apr 25 10:36:21 2008
	! * cron started * pid = 23433 Fri Apr 25 10:36:24 2008		! * cron started * pid = 23433 Fri Apr 25 10:36:24 2008

Hutch at 15:39, 25 April 2008

Hutch — Fri, 25 Apr 2008 15:39:13 GMT

←Older revision		Revision as of 15:39, 25 April 2008
Line 2:		Line 2:
	> CMD: ''command''		> CMD: ''command''
	> lntech 23415 c Fri Apr 25 10:34:00 2008		> lntech 23415 c Fri Apr 25 10:34:00 2008
-	! bad user (lntech) Fri Apr 25 10:34:00 2008	+	'''! bad user''' (lntech) Fri Apr 25 10:34:00 2008
	< lntech 23415 c Fri Apr 25 10:34:00 2008 rc=1		< lntech 23415 c Fri Apr 25 10:34:00 2008 rc=1

Hutch: New page: I received the following error on a Solaris 8 SPARC 2/04 release (117350-50 patch level) system: > CMD: ''command'' > lntech 23415 c Fri Apr 25 10:34:00 2008 ! bad user (lntech) Fri A...

Hutch — Fri, 25 Apr 2008 15:38:17 GMT

New page: I received the following error on a Solaris 8 SPARC 2/04 release (117350-50 patch level) system: > CMD: ''command'' > lntech 23415 c Fri Apr 25 10:34:00 2008 ! bad user (lntech) Fri A...

New page

I received the following error on a Solaris 8 SPARC 2/04 release (117350-50 patch level) system:
> CMD: ''command''
> lntech 23415 c Fri Apr 25 10:34:00 2008
! bad user (lntech) Fri Apr 25 10:34:00 2008
< lntech 23415 c Fri Apr 25 10:34:00 2008 rc=1

The user ''lntech'' is an LDAP account. The account is not expired, although I don't think this would matter (see SunSolve Document ID 204893). The user was added to ''/etc/cron.d/cron.allow'', and could edit its crontab.

Restarting the ''cron'' daemon fixed the problem; sending the ''cron'' daemon a SIGHUP did not.
! SIGTERM Fri Apr 25 10:36:21 2008
! ******* CRON ABORTED ******** Fri Apr 25 10:36:21 2008
! *** cron started *** pid = 23433 Fri Apr 25 10:36:24 2008
> CMD: ''command''
> lntech 23440 c Fri Apr 25 10:37:00 2008
< lntech 23440 c Fri Apr 25 10:37:00 2008