crontab error :- You (user) are not allowed to access to (crontab) because of pam configuration

-

Issue :-

[oracle@testserv1~]$ crontab -l

You (oracle) are not allowed to access to (crontab) because of pam configuration.

[oracle@testserv1~]$


When you will check the log file /var/log/cron you will be able to see the error in logfile.

May 22 12:28:57 testserv1 crontab[48079]: (oracle) PAM ERROR (Authentication token is no longer valid; new one required)

May 22 12:29:37 testserv1 crontab[48205]: (oracle) PAM ERROR (Authentication token is no longer valid; new one required)

Solution :-

There could be two reason for this error:
1. Expired password for the user.
2. User not allowed to cron in /etc/security/access.conf file.

Check for expired user password. 

1. First of all, check the password expiry for the user using chage command.

[root@testserv1 ~]# chage -l oracle
Last password change                                    : Feb 19, 2021
Password expires                                           : May 20, 2021    ## Password Expired for oracle user.
Password inactive                                          : never
Account expires                                             : never
Minimum number of days between password change          : 0
Maximum number of days between password change          : 90
Number of days of warning before password expires       : 7
[root@testserv1 ~]#

From the output above we can say that the password has expired on May 20th 2021. Crontab command will fail if it is run as user whose password is expired. PAM will not allow to run cronjob as user if the password of that user is expired.

2. If password is expired, new password will need to be set for the user in order to allow user to run cronjobs. To set password for user, run following command as root:

[root@testserv1 ~]# passwd oracle
Changing password for user oracle.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.
[root@testserv1 ~]#

After changing the password now you can try to access the cronjobs again.

Hope the above solution helped you to resolve the issue. 

Comments

Post a Comment

Popular posts from this blog

ORA-06512: at SYS.DBMS_METADATA_UTIL Error

-
 If you face an error like the following while performing “impdp” operations: Connected to: Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production ORA-39006: internal error ORA-39065: unexpected master process exception in DISPATCH ORA-01001: invalid cursor ORA-06512: at "SYS.DBMS_METADATA_UTIL", line 3343 ORA-06512: at "SYS.KUPM$MCP", line 2636 ORA-39097: Data Pump job encountered unexpected error -1001 Solution: execute the following command: SQL> exec dbms_metadata_util.load_stylesheets; If the above query executes sucessfully then try the “impdp” command again. Connected to: Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production Version 18.3.0.0.0 SQL> exec dbms_metadata_util.load_stylesheets; PL/SQL procedure successfully completed. SQL>
Read more

RC-00118: Error occurred during creation of database Raised by oracle.apps.ad.clone.ApplyDatabase

-
Error Occurred :– Trying to connect using SID as ServiceName.DomainName getConnectionUsingServiceName() –> JDBC URL: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oratest.tipl.com)(PORT=1532))(CONNECT_DATA=(SERVICE_NAME=TIR12.ticfg.com))) Exception occurred: java.sql.SQLException: The Network Adapter could not establish the connection Connection could not be obtained; returning null RC-00118: Error occurred during creation of database StackTrace: java.lang.Exception: Control file creation failed at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:661) at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:328) at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:304) at oracle.apps.ad.clone.ApplyDBTier.<init>(ApplyDBTier.java:154) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.re...
Read more

The install cannot proceed as service OracleServiceXE is present on the system

-
If you are not able to remove oracle from the above workaround. Please follow below steps to remove OracleServiceXE. Solution:– Try to delete the service using the command prompt: Click Start, type ‘cmd’ in the search field, and when ‘cmd’ shows up in the list of options, right click it and select ‘Run as Administrator’. At the Command Prompt window, type “sc delete OracleServiceXE” without the quotes and press Enter. Type “Exit” and press Enter. Hope it helps. C:\> sc stop OracleServiceXE                      (to Stop service) C:\> sc delete OracleServiceXE                      (to remove)
Read more