Hello Group!

 I have situation with crontab -e and crontab -l commands not
functioning properly on an Utlra 1 running SUN Solaris 5.8 Patch_Level
is 13. It was
working fine until one of the Windows Admins tried to edit the crontab
file through a text editor instead of vi. He overwrote the original
files
when he saved the changes to the crontab file. So now when you type in
the
commands <crontab -e> or <crontab -l> you get this error message
below:

#ld.so.l:crontab: fatal: relocation error: file crontab: symbol
audit_crontab_not_allowed: referenced symbol not found.
killed
#

Can anyone shead some light to how I can fix this issue with the
crontab
command?

"Randall" <rlowe62@charter.net> wrote in message
news:dfbedc79.0408120635.1ccafa04@posting.google.com...
> Hello Group!
>
>  I have situation with crontab -e and crontab -l commands not
> functioning properly on an Utlra 1 running SUN Solaris 5.8 Patch_Level
> is 13. It was
> working fine until one of the Windows Admins tried to edit the crontab
> file through a text editor instead of vi. He overwrote the original
> files
> when he saved the changes to the crontab file. So now when you type in
> the
> commands <crontab -e> or <crontab -l> you get this error message
> below:
>
> #ld.so.l:crontab: fatal: relocation error: file crontab: symbol
> audit_crontab_not_allowed: referenced symbol not found.
> killed
> #
>
> Can anyone shead some light to how I can fix this issue with the
> crontab
> command?

How about renaming the problem crontab file or files in
/var/spool/cron/crontabs and then recreating from scratch ?

Or restore them from the last good backup. ?

Matt wrote:

> "Randall" <rlowe62@charter.net> wrote in message
> news:dfbedc79.0408120635.1ccafa04@posting.google.com...
> > Hello Group!
> >
> >  I have situation with crontab -e and crontab -l commands not
> > functioning properly on an Utlra 1 running SUN Solaris 5.8 Patch_Level
> > is 13. It was
> > working fine until one of the Windows Admins tried to edit the crontab
> > file through a text editor instead of vi. He overwrote the original
> > files
> > when he saved the changes to the crontab file. So now when you type in
> > the
> > commands <crontab -e> or <crontab -l> you get this error message
> > below:
> >
> > #ld.so.l:crontab: fatal: relocation error: file crontab: symbol
> > audit_crontab_not_allowed: referenced symbol not found.
> > killed
> > #
> >
> > Can anyone shead some light to how I can fix this issue with the
> > crontab
> > command?
>
> How about renaming the problem crontab file or files in
> /var/spool/cron/crontabs and then recreating from scratch ?
>
> Or restore them from the last good backup. ?

You might consider having someone run pkgchk on SUNWcsu.
The error sounds like /usr/bin/crontab or soemthing it uses may
have been damaged.  You might also consider changing the root
password.

Speaking only for myself,

Joe Durusau

joe durusau <joe.durusau@lmco.com> writes:
> You might consider having someone run pkgchk on SUNWcsu.
> The error sounds like /usr/bin/crontab or soemthing it uses may
> have been damaged.  You might also consider changing the root
> password.

A good idea.

The audit_crontab_not_allowed symbol is normally found in /usr/lib/libbsm.so.
Perhaps that was replaced after somebody hacked in?  Or accidentally deleted?

-- Anton

rlowe62@charter.net (Randall) wrote in message news:<dfbedc79.0408120635.1ccafa04@posting.google.com>...
> Hello Group!
> 
>  I have situation with crontab -e and crontab -l commands not
> functioning properly on an Utlra 1 running SUN Solaris 5.8 Patch_Level
> is 13. It was
> working fine until one of the Windows Admins tried to edit the crontab
> file through a text editor instead of vi. He overwrote the original
> files
> when he saved the changes to the crontab file. So now when you type in
> the
> commands <crontab -e> or <crontab -l> you get this error message
> below:
> 
> #ld.so.l:crontab: fatal: relocation error: file crontab: symbol
> audit_crontab_not_allowed: referenced symbol not found.
> killed
> #
> 
> Can anyone shead some light to how I can fix this issue with the
> crontab
> command?
I don't know what causes this error but if you think the crontab edit
may be the problem why don't you try to copy the current crontab file
and replace it with a very simple one (say a single line written by
you the way you did before and worked or even better the original
crontab that came with Solaris). That way you can easily tell if
there's a problem with the file or anything else.
The crontab file for a user can be found in /var/spool/cron/crontabs/
and has the user's name.

Vlad.

Anton Rang wrote:

> The audit_crontab_not_allowed symbol is normally found in /usr/lib/libbsm.so.
> Perhaps that was replaced after somebody hacked in?  Or accidentally deleted?

It's there on Solaris 9/10 but I don't see it in Solaris 8.
I suspect someone tried to "fix" crontab by copying /usr/bin/crontab
from Solaris 9 to Solaris 8.

# uname -r
5.8
# nm /usr/lib/libbsm.so.1 | grep crontab
audit_crontab.c
audit_crontab_delete
audit_crontab_get_diffs
audit_crontab_modify

# uname -r
5.9
# nm /usr/lib/libbsm.so.1 | grep crontab
audit_crontab.c
audit_crontab_delete
audit_crontab_get_diffs
audit_crontab_modify
audit_crontab_not_allowed
audit_crontab_process_not_audited

[Randall]

|   So now when you type in the commands <crontab -e> or <crontab -l> you
|   get this error message below:
|
|   #ld.so.l:crontab: fatal: relocation error: file crontab: symbol
|   audit_crontab_not_allowed: referenced symbol not found.
|   killed
|   #

You haven't by any chance applied an old version of the patch 109007
recently? I think it was 109007-09 which broke crontab in the way you
describe above (unless 108875-13 was also applied). Newer versions of
109007 fixed this problem. You might try installing 109007-18.

Regards,
	-Anders.
-- 
  Anders Odberg, <anders.odberg@usit.uio.no>
  Center for Information Technology Services
  University of Oslo, Norway

--------------13FC0CC258AE07F743CB7CB7
Content-Type: text/plain; charset=iso-8859-7
Content-Transfer-Encoding: 7bit

Randall wrote:

> Hello Group!
>
>  I have situation with crontab -e and crontab -l commands not
> functioning properly on an Utlra 1 running SUN Solaris 5.8 Patch_Level
> is 13. It was
> working fine until one of the Windows Admins tried to edit the crontab
> file through a text editor instead of vi. He overwrote the original
> files
> when he saved the changes to the crontab file. So now when you type in
> the
> commands <crontab -e> or <crontab -l> you get this error message
> below:
>
> #ld.so.l:crontab: fatal: relocation error: file crontab: symbol
> audit_crontab_not_allowed: referenced symbol not found.
> killed
> #
>
> Can anyone shead some light to how I can fix this issue with the
> crontab
> command?


Randall

 There may be some non printable characters (escape sequences) left
behind in the crontab file.
 try doing:

cp /var/spool/cron/crontabs/root /var/spool/cron/crontabs/root.save
cat /var/spool/cron/crontabs/root | col -b -x > /tmp/x
cp /tmp/x /var/spool/cron/crontabs/root

now try crontab -l and ctontab -e again and see if you still get
the error messages.

Good Luck

--
[mailto:kanejm@netheaven.com]



--------------13FC0CC258AE07F743CB7CB7
Content-Type: text/html; charset=iso-8859-7
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Randall wrote:
<blockquote TYPE=CITE>Hello Group!
<p>&nbsp;I have situation with crontab -e and crontab -l commands not
<br>functioning properly on an Utlra 1 running SUN Solaris 5.8 Patch_Level
<br>is 13. It was
<br>working fine until one of the Windows Admins tried to edit the crontab
<br>file through a text editor instead of vi. He overwrote the original
<br>files
<br>when he saved the changes to the crontab file. So now when you type
in
<br>the
<br>commands &lt;crontab -e> or &lt;crontab -l> you get this error message
<br>below:
<p>#ld.so.l:crontab: fatal: relocation error: file crontab: symbol
<br>audit_crontab_not_allowed: referenced symbol not found.
<br>killed
<br>#
<p>Can anyone shead some light to how I can fix this issue with the
<br>crontab
<br>command?</blockquote>
&nbsp;
<br>Randall
<p>&nbsp;There may be some non printable characters (escape sequences)
left behind in the crontab file.
<br>&nbsp;try doing:
<p>cp /var/spool/cron/crontabs/root /var/spool/cron/crontabs/root.save
<br>cat /var/spool/cron/crontabs/root | col -b -x > /tmp/x
<br>cp /tmp/x /var/spool/cron/crontabs/root
<p>now try crontab -l and ctontab -e again and see if you still get
<br>the error messages.
<p>Good Luck
<pre>--&nbsp;
[<A HREF="mailto:kanejm@netheaven.com">mailto:kanejm@netheaven.com</A>]</pre>
&nbsp;</html>

--------------13FC0CC258AE07F743CB7CB7--