Visit Our UNIX and Linux User Community


KERBEROS_V4 rejected as an authentication type & cron


 
Thread Tools Search this Thread
Operating Systems Linux KERBEROS_V4 rejected as an authentication type & cron
# 1  
Old 08-04-2009
KERBEROS_V4 rejected as an authentication type & cron

Running as cron, I get error msg in mail: KERBEROS_V4 rejected as an authentication type,
even though the ftp does work. Can anyone explain this? Is there a way to stop it?

cron:
35 6 * * 1-5 ./PSS/pss.sh >> ./PSS/pss.log

script pss.sh:
#!/usr/bin/ksh
DIR=/home/informix/PSS
/usr/kerberos/bin/ftp -v -n << _EOF_
open PSSIPADDR
user testuser testpw
ascii
lcd $DIR
put studentinfo.txt
bye
_EOF_

mail:
Message 3:
From informix@pentapp2.iisd1.lcl Wed Jul 29 06:35:08 2009
Date: Wed, 29 Jul 2009 06:35:04 -0500
From: root@pentapp2.iisd1.lcl (Cron Daemon)
To: informix@pentapp2.iisd1.lcl
Subject: Cron <informix@pentapp2> ./PSS/pss.sh >> ./PSS/pss.log
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/home/informix>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=informix>
X-Cron-Env: <USER=informix>

KERBEROS_V4 rejected as an authentication type

---------- Post updated at 09:49 AM ---------- Previous update was at 09:47 AM ----------

BTW, I'm running RedHat 5.3

Previous Thread | Next Thread
Test Your Knowledge in Computers #204
Difficulty: Easy
The BGP routing protocol runs over User Datagram Protocol (UDP).
True or False?

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Cron Authentication Failure error in Linux

I was bogged with an error “Authentication Failure” for all of my cron jobs in Linux Ubunutu. root@Test:~# tail -f /var/log/syslog | grep cron Dec 11 16:38:01 Test cron: Authentication failure Dec 11 16:38:01 Test cron: Authentication failure Dec 11 16:38:09 Test cron: (CRON) INFO (pidfile... (1 Reply)
Discussion started by: SULTAN01
1 Replies

2. Shell Programming and Scripting

"Content-type: text/html No input file specified." Only in CRON but not when executed directly

Hi gang, I have the following code inside a the file script.sh #!/bin/bash todaysdate=$(date --date='7 day' +'%d') todaysmonth=$(date +'%m') todaysyear=$(date +'%Y') yahoodatestring=$todaysyear$todaysmonth$todaysdate nicedate=$(date --date='5 day' +'%A') nice="$nicedate,... (2 Replies)
Discussion started by: phpchick
2 Replies

3. Shell Programming and Scripting

KERBEROS_V4 rejected as an authentication type error

Hi am just trying to FTP am while doing so am getting the "KERBEROS_V4 rejected as an authentication type" error.Please let me know what should be done to avoid this error. The code is #!/bin/ksh -x # # Get new files only ftp # source="source.com" basedir="/home/xyz/"... (0 Replies)
Discussion started by: weknowd
0 Replies

4. UNIX Desktop Questions & Answers

X11 connection rejected because of wrong authentication

I have two Solaris 10 systems, A and B, both of which share home directories via NFS (served from a 3rd, Linux, machine). User names, uids, and home directories are identical when the same user has accounts on both Solaris 10 machines. When I run ssh -X user@A from my home machine, I can easily... (0 Replies)
Discussion started by: WolfyPDX
0 Replies

5. Solaris

Key authentication between solaris & windows server.

Hi Gurus I have a solaris box from which i will have to sftp into a windows box. I have installed core ftp server in the windows box and so am able to log in. My problem is that,I have to enable password less authentication between solaris box and this core ftp server. How do i do this? ... (1 Reply)
Discussion started by: Hari_Ganesh
1 Replies

6. SCO

Cannot type properly in telnet window (windows Xp & SCO Unix)

Hello friends, I am using telnet from windows xp to connect to SCO Unix. Since i am used to telnet environment given by linux from windows, this one is annoying. The cursor movements has no boundary, causing me to type control characters accidentally, which makes it difficult to navigate,... (1 Reply)
Discussion started by: frozensmilz
1 Replies

7. Shell Programming and Scripting

KERBEROS_V4 -help needed ASAP

#!/bin/sh HOST='ftp.bend.com' USER='temp1' PASSWD='temp2' FTPPATH='SY1:' ifile='concat.txt' #FTP concatenated file ftp -n $HOST <<END_SCRIPT quote USER $USER quote PASS $PASSWD binary cd $FTPPATH put $ifile get $ifile retrieval.$$ quit END_SCRIPT if then echo "FTP of... (2 Replies)
Discussion started by: Sgiri1
2 Replies

8. UNIX for Dummies Questions & Answers

Basic Q: getting list of all files of type within folder & subfolders

A painfully rudimentary UNIX question for somebody. I've been puzzling over this for the last hour but can't find the right command. I'm simply trying to get a list of all files - and their full paths - within a folder & subfolders which have extension .php and .js. That's it! No amount of... (1 Reply)
Discussion started by: AtomicPenguin
1 Replies

9. SCO

Stoping & starting the cron

Hi We are running SCO ver 5. Recently the cron daemon stopped running on its own. How do I find out why? How do I restart/stop it? I typed cron but it didn't work. Will rebooting it do the trick or can I manually start and stop the cron daemon? Please help. Thanks & Regards. (9 Replies)
Discussion started by: othman
9 Replies
cron(1M)                                                  System Administration Commands                                                  cron(1M)

NAME
cron - clock daemon SYNOPSIS
/usr/sbin/cron DESCRIPTION
cron starts a process that executes commands at specified dates and times. You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory /var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once can be submitted using the at(1) command. cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This reduces the overhead of checking for new or changed files at regularly scheduled intervals. As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file /etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron. cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was submitted. cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not locked and will have their jobs and processes executed. Setting cron Jobs Across Timezones The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using /etc/default/init. If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed once, twice, or not at all. Setting cron Defaults To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log- ging is done. Keeping the log is a user configurable option since cron usually creates huge log files. You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in /etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH. Example /etc/default/cron file: CRONLOG=YES PATH=/usr/bin:/usr/ucb: This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use /usr/sbin:/usr/bin. The cron log file is periodically rotated by logadm(1M). FILES
/etc/cron.d Main cron directory /etc/cron.d/FIFO Lock file /etc/default/cron cron default settings file /var/cron/log cron history information /var/spool/cron Spool area /etc/cron.d/queuedefs Queue description file for at, batch, and cron /etc/logadm.conf Configuration file for logadm ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5) NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier: svc:/system/cron:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog. SunOS 5.10 5 Aug 2004 cron(1M)

Featured Tech Videos