Cronjob not to execute when root password expires

I noticed that when Solaris 10 root password expires, the cron job under root won't run.
Anyone have any suggestion for allow expired root password to run cronjobs?

WorMzy wrote:Why are you using encryption if you want it to be that easy to access your data?
Yea, bypassing the password completely defeats the purpose of encryption. Just decrypt your drive if you don't want to type your password and gain some performance back while you're at it.
DSpider wrote:I think you can use a keyfile instead of a password.
A keyfile can be a decent encryption method but it has to be selected manually or it's worthless. You can't just automatically have everything decrypted on boot or anyone can just boot once then copy all your data unencrypted to another drive.
shadyabhi wrote:
I initially did it for the sake of learning.
But, after I installed systemd, I feel like it's increasing my bootup time.
I don't want to discourage you from learning at all but encryption does come with a performance hit. It can be mitigated if you use AES encryption and have a recent CPU that supports AES-NI (or buy a purely hardware self encrypting drive). But it sounds like you'd best be served just decrypting.
Last edited by weirddan455 (2012-11-03 05:01:15)

Similar Messages

Root password expired - not your typical case

Hello everyone,
I apologize for asking what is a very FAQ, but I am unable to find an appropriate answer anywhere on the interweb.
The facts of my unfortunate situation are:
1. I am a newbie in the SA world.
2. I am even more of a newbie in the Solaris world.
3. I am administering a Production Database system on Solaris 9.
4. Within the last couple days the root password expired.
5. When I attempt to login at the console as root, I receive the following message. "Roles can only be assumed by authorized users."
It seems to me that root ought to be authorized to login to the console.
I've read that I can boot from the CD to resolve this issue, but the system in question has the CD drive disabled. If only I could figure out how to login to the console as root, I'm sure that it would let me update the password, but I don't know how to work around the "Roles can only be assumed by authorized users" issue.
Please help!
Thanks in advance for your assistance. It is greatly appreciated.

Well, I've learned an awful lot in the process of trying to resolve this issue. I'm still not there, but I'm getting close.
I have done a ton of research on the net, and I am unable to find any specific detailed instructions on how to fix the root password expired issue. So, I figured I would paraphrase what I believe are the detailed steps to be taken. If you see an error in my logic, or my syntax please let me know, as I will be beginning this process soon.
So, we have RBAC or Role Based Access Control on the Solaris 9 box, and the root password has expired. This is a pretty annoying situation to be in, but it can be fixed easily enough.
First, we'll want to gracefully shutdown all the processes which are currently running on the system. This is accomplished by executing the following command which will put the system into single user mode:
init -1
Determine where your root file system (e.g. c1t0d0s0) is located by typing the following command (you'll want to make note of the result):
/etc/vfstab
Next, we need to access the EEPROM. Before doing this, you should do execute the following command to see if your EEPROM is password protected.
eeprom |grep security
Look for the line that reads "security-mode=" If security mode is set to "none" or "none-secure" you're golden, proceed with the next step. If security mode is set to "command" "command-secure" "fully" or "fully-secure" you want to make sure you have your EEPROM password, otherwise you'll be in worse shape than when you started.
Assuming that you either have the EEPROM password, OR the system is set to "security-mode=none" you can proceed to the EEPROM prompt by pressing the following key combination:
Stop + A
You should now have an OK> prompt. Insert the Solaris 9 Installation CD into the CDRom drive. At the prompt type the following command to boot from your CD rom:
boot cdrom -sw
Once the boot sequence is complete, execute the following command to mount your root filesystem.
mount /dev/dsk/<root filesystem device file> /mnt
Once you have mounted the root file system, you will need to change the /etc/user_attr file to allow console access by root. Open /etc/user_attr with your editor of choice. On the line beginning with root::::type=role; etc etc change the setting type=role to type=normal and save the user_attr file.
Enter the following command to go back to the OK prompt:
halt
Then enter boot -s to reboot your system. You should now be able to login to the console with root, which will allow you to update your password. Once you have done so, do an init -3 to bring the user back up to the standard mode of operation.
Thanks again Jeffery for your help in this matter. I hope to have this situation resolved soon, but I want to make sure that all my ducks are in a row before I start playing Russian Roulette with my server. Does the above walkthrough sound accurate? Is there anything that I have misuderstood or overlooked?

ADSI does not return proper code for Password Expired

We are trying to modify a vendor supplied system to get it to authenticate using our LDAPs. The vendor app is a hybrid IIS ASP/ASP.NET application so it seems necessary to use ADSI for authentication. We have had the solution working for more than a year, but now we want to expire passwords in our LDAP.
We have been testing with both Netscape Gateway LDAP engine 4.13 and/or Sun One Directory Server Version 5.2. At the moment, the problem I am facing is that I get the same error code from ADSI whether the attempted password is bad or the user DN and password are good but the account has expired. In other words, I cannot differentiate between an expired password and bad typing during the login attempt.
In either case [bad password or password expired], I get, -2147023570 Automation error Logon failure: unknown user name or bad password. I can log in successfully with an unexpired UID/password using the code so it looks like I have no code error. I have tried several times to make sure I am typing everything OK. My results are consistent.
I have found example code on the web that suggests I should be seeing the "error -2147016672 (1 from NDS) - password expired".
Could there be some sort of Netscape or Sun One LDAP configuration parameter that prevents sending the password expired error code/message?
Any other ideas what might be wrong?
We've tested using VB, VBScript [directly] and VBScript in ASP. Always the same results.
Here are the relevant sample lines {in VBScript}
 Set adsDSO = GetObject("LDAP:")
 on error resume next
 Set adsUser = adsDSO.OpenDSObject("LDAP://ourmachine.cusys.edu:portGoesHere/uid=" & UserName & ",o=whatever,c=US", "uid=" & UserName & ",o=whatever,c=US", Password, 0)
 if err.number 0 then
 if err.number = -2147016672 then
 ' Cannot seem to get here.
 response.write "Error code: " & err.number & ""
 response.write "Error code for expired password"
 elseif err.number = -2147023570 then
 response.write "Error code: " & err.number & ""
 response.write "Error code for bad credentials"
 else
 response.write "Error code: " & err.number & " "
 response.write err.description & ""
 ' do more stuff ...

Did you check SAP notes? Maybe the OS creates the file in DIR_HOME directory when the path is invalid. Could you check in AL11? You may also add "MESSAGE msg" to the "OPEN DATASET", maybe you'll get more information.

WinSCP not being executed when package is ran from job

I have a package in the SSIS catalog. It worked fine when it ran in the file system, but like so many others, died when I called it from a job. I ran the problem down to the fact that the account that the job was running under didn't have access to the directories
that the package was trying to access. That solved half my problem.
In my package I'm calling WinSCP from a script task. I can tell the executable is not getting called. No errors are being thrown. I gave the account in question full access to the folder where WinSCP resides but that didn't fix the issue. What else do I
need to look at?

Arthur, WinSCP has logging functionality. When the executable gets called a log file is created. No log file is being created. I did pull that particular piece of functionality out of the package and unit tested it and it worked fine which has only caused
me further frustration.
I am currently getting this series of errors which I only just found:
The expression for the variable "InitialDirectoryFullPath" failed evaluation. There was an error in the expression.
The variable "User:RootFileDirectory" was not found in the variables collection.
Attempt to parse the expression "@[User:RootFileDirectory] + @[InitalDirectory]" failed and returned error code 0xC00470A6. The expression cannot be parsed.
This makes no sense as it runs just fine in other environments under other accounts. Only when I push this thing to a certain box does it fail like this. RootFileDirectory is being populated by a Windows Environment Variable and I thought the problem was
there except there are other parts of the package that use that variable and they work just fine.

Password expires when using the Remote Desktop App in Android

When the password expires, users using the Microsoft Remote Desktop App in Android cannot logon to the system.
Is there a way for them to be notified of the password expiry and having a chance to change the password?
Cheers.
Andrew

Hi Andrew,
Thank you for posting in Windows Server Forum.
You can set the GPO policy, “Interactive Logon: Prompt user to change password before expiration” under
Computer Configuration\Windows Settings\Local Policies\Security Options which will let the user prompts to change their password before specific limit.
More information.
How to change the password expiry notice default
http://technet.microsoft.com/en-us/library/ee829687(v=ws.10).aspx
In addition, there is script where user get email alert to change their passwords. Please have a look for this gallery article (Password Expiry Email Notification).
Hope it helps!
Thanks.
Dharmesh Solanki

APEX_PUBLIC_USER password expired and now APEX denies access to /pls/apex/f

Hi. I have a problem with expired passwords. We are using APEX 2.2.0 with Oracle 10g. This morning the APEX_PUBLIC_USER and HTMLDB_PUBLIC_USER accounts passwords expired. We have a really weird setup. Our DBA team owns these accounts and our web server team manages the APEX application itself. When the passwords expired, our DBA changed them from Oracle, not from within APEX. Now we are unable to access our application. We get the following error message:
Forbidden
You don't have permission to access /pls/apex/f on this server.
The DBA won't reset the passwords to their prior value because it's against corporate policy to resuse them. The web server team does not know how to go in to APEX and enter the new values. Can someone point me to documentation that explains what we need to do? I just want to get these two teams working together so that my users can get back to work!
Thanks,
Mike

Mike - All you have to do is change the database account password to a new value and enter that same password into the DAD definition, obfuscating it in that file if your policy so dictates.
Application Express, per se, doesn't know anything about that account's attributes such as its password so there is no interface provided for its maintenance.
Scott

Exempt UME user for password expiration

Is there a way to exempt a user from the password expiration setting? For example, passwords for all users are set to expire every 90 days, but a user id, say "monitor_user", is used in monitoring application to perform an automated logon check. Every 90 days when the password expires, the monitor fails. Is there a way to set this user's password not to expire?
Thanks

Glen and Giorgio,
Let me see if I can clear things up a little bit.
First, there is the security policy which is controlled by the UME properties. This defines password length, logon ID length, etc. These properties apply to the entire AS Java and cannot be trimmed down for individual users. How they apply to users in different data sources also varies. For example, these properties are ignored to some extent if you have an ABAP system as your user store. See the following link:
http://help.sap.com/saphelp_nw04s/helpdata/en/7f/c52442ad9f5133e10000000a155106/frameset.htm
Second, as of NW 04s SPS 7 a new user attribute was added, named "security policy". For individual users you can choose one of the following security policies:
default users (user can logon, password rules apply)
technical users (user can logon, password does not expire)
internal service users (user cannot logon, usually do not have passwords)
There is a fourth policy: unknown users, applies to certain users mapped from an AS ABAP.
In SPS 7 I believe and latest in SPS 8, you have limited abilities to change the security policy of the user with identity management. You can change the policy from unknown or default to technical but not back.
In SPS 9 and later you can change the policy from unknown or default to technical and from unknown or technical to default.
I wonder if support misunderstood your question and thought you were referring to the first type of security policy and not the second.
Message was edited by: Michael Shea

F8 doesn't work / query could not be executed

I've had a form that worked perfectly until I started to put some of the fields on a new canvas in a new window (in the same form). Since then, I get the error "ORACLE ERROR: query could not be executed" when pressing F8 or starting "execute_query" by a button trigger.
Can anyone help me where to search the error?

hi
please check out the following link and u will find all documentations.i hope it will also help u.
http://www.oracle.com/technology/documentation/index.html
Block Menu      F5
Cancel            Escape
Clear Block            Shift+F5
Clear Form      Shift+F7
Clear Item            Shift+F3
Clear Record      Shift+F4
Count Query Hits      Shift+F2
Delete Backwards      Backspace
Delete Record      Shift+F6
Display Error      Shift+F1
Down            DownArrow
Duplicate Item      F3
Duplicate Record      F4
Edit            Control+e
Enter Query      F7
Execute Query      F8
Exit            Control+q
Help            F1
Insert Record      F6
List of Values      F9
Next Block            ?
Next Item            Tab
Next Primary Key      Shift+F3
Next Record      Shift+DownArrow
Next Set of Records      Control+>
Previous Block      ?
Previous Item      Shift+Tab
Previous Record      Shift+UpArrow
Print            Shift+F8
Return            Return
Save            F10
Show Keys            Control+F1
Up            UpArrowsarah

Consequences of password expiration AFTER server is started

Hi,
What happens when the LDAP server expires the password for the account specified
in boot.properties?
What are all the activities for which the WebLogic Server keeps checking the validity
of this userid/pwd? For example, Windows checks for your authorization pretty
much for every time you access a resource like a file, etc.
Any pointers to documentation is greatly appreciated. I am curious to know what
exactly happens behind the scenes when the password expires AFTER the server is
up and running.
Thanks,
Anant

On 4 Feb 2004 09:49:20 -0800, Anant Kadiyala <[email protected]> wrote:
>
Hi,
What happens when the LDAP server expires the password for the account
specified
in boot.properties?
What are all the activities for which the WebLogic Server keeps checking
the validity
of this userid/pwd? For example, Windows checks for your authorization
pretty
much for every time you access a resource like a file, etc.
Any pointers to documentation is greatly appreciated. I am curious to
know what
exactly happens behind the scenes when the password expires AFTER the
server is
up and running.
Thanks,
Anant
My guess is that the next time an authentication is required that the
expired password will fail. I don't know of any comprehensive list that
details everytime an authentication is undertaken.

LDAP password expiration

Hi all,
I am new to LDAP. I got through all the authenitcationm pieces. I need to allow a user change his password when his password expired. Could someone please help me on how to detect if a password has expired? And when the password expired, how should I change the password?
Thanks,
Larry

if you use active directory, you can catch an AuthenticationException :
} catch (AuthenticationException e) {
String tempString;
StringTokenizer tokenizerTemp = new StringTokenizer(e.toString());
while (tokenizerTemp.hasMoreElements()) {
     tempString = tokenizerTemp.nextToken();
     if (tempString.equalsIgnoreCase("AcceptSecurityContext")) {
          while (tokenizerTemp.hasMoreElements()) {
               tempString = tokenizerTemp.nextToken();
               if (tempString.startsWith("773"))
                    setIsPasswordExpired(true);
               if (tempString.startsWith("52e"))
                    setIsPasswordWrong(true);
               if (tempString.startsWith("533"))
                    setIsAccountDisabled(true);
throw new NamingException();
}for changing the password in active directory you must have a SSL connection.

Can local admin change the root password in Mavericks

One of my people and I keep going back and forth with this question. I remember reading somewhere (cannot find it now) that in 10.9 Apple changed it, so a local admin could not longer change the root password if it has been enabled by the IT group.

AFAIK, any admin account user can set/change the root password. See OS X Mavericks: Enable and disable the root user for details. If you or IT don't trust your people, don't give them admin privileges.
iMac refurb (27-inch Mid 2011), OS X Mavericks (10.9.4), SL & ML, G4 450 MP w/Leopard, 9.2.2

My iTunes password will update some of my Apps on iPad but not all of them. When I try to update the remaining ones, my password expires. I've just created 5th PW. Does anyone else experience this?

My iTunes password will update some of my Apps but not all of them. When I try to update the remaining ones, my password expires. I've just created 5th PW. Does anyone else experience this?

- Try going to Setings>Store and sign out of the account and then sign back in.
- Reset the iPod. Nothing will be lost
Reset iPod touch: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears

Purge command in cronjob not executed?

Hello dear friends,
I need to purge my RAM on my OS X Mavericks Late 2012 iMac every 5 minutes.
I used to run this command in cronjob on Mountain Lion and it was working great:
*/5 * * * * purge
It would seem that the cron job is indeed executed every 5 minutes, but the memory DOES NOT get purged at all, yet if I run the purge command manually it works.
In fact, to ensure that the command is actually performed, I have tempèorarily modified it as follows:
*/5 * * * * purge >/Users/lab/Desktop/cronpurge.txt
The .txt file is modified every 5 minutes but, as I said, no memory purge occurs.
How can I ensure that the command is run successfully by cronjob as it used to be the case with Mountain Lion?
Thanks!

Hi,
Thanks to both.
I forgot to mention that the cronjob is indeed edited as root, with su command first to get an elevated prompt.
I run 6 Parallels Desktop Windows 7 sessions while I am working with Mavericks, that's why I need frequent purging, for them to run smoothly as Parallels Desktop is pretty much memory hungry.
Although I have 32 GB RAM, I prefer to be able to multitask as best as possible by running a frequent memory purge.
@TonyT1: I am indeed aware that memory management in Mavericks is different, however I can't help wondering why the same command "purge" works perfectly when run manually in an elevated prompt.... hence my curiosity about why the cron job, which is supposed to run the same instruction, is not working. Thanks!

Database Error when starting UCM - Password Expired?

I'm getting a database error (see full stack below) when I try to start UCM after Weblogic. I was not having this problem before. When digging through the stack trace (below) I notice one of the error its outputting is that my password expired. However, I'm able to connect to the database using SQL Plus just fine, and even changed the system password just to be safe. Same error. I tried researching the issue even further: tried following this - http://kishantha.blogspot.com/2010/03/oracle-enterprise-manager-console.html , but when i ran the 'emctl stop dbconsole' i got a config issue, which led me to a different blog post when i tried running 'dbca' to configure and it gave me the following error - "Listener is not up or database service is not registered with it. Start the Listener and register database service and run EM Configuration Assistant again" although from what I can tell my listener is running just fine. what could possibly be going wrong here? any help would be appreciated!
[2012-02-13T12:39:32.115-05:00] [UCM_server1] [NOTIFICATION] [UCM-CS-000001] [oracle.ucm.idccs] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [ecid: 0000JLrn0xj3z0WjLxyGOA1FEKe^000002,0] [APP: Oracle Universal Content Management - Content Server] general exception
[2012-02-13T13:26:43.479-05:00] [UCM_server1] [ERROR] [UCM-CS-000001] [oracle.ucm.idccs] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [ecid: 0000JLrxs2a3z0WjLxyGOA1FELN9000002,0] [APP: Oracle Universal Content Management - Content Server] general exception
[2012-02-13T13:26:43.510-05:00] [UCM_server1] [ERROR] [UCM-CS-000001] [oracle.ucm.idccs] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [ecid: 0000JLrxs2a3z0WjLxyGOA1FELN9000002,0] [APP: Oracle Universal Content Management - Content Server] general exception[[
java.lang.AssertionError: !syNativeOsUtilsNotLoaded
 at intradoc.common.NativeOsUtilsBase.doLoad(NativeOsUtilsBase.java:386)
 at intradoc.common.NativeOsUtilsBase.<init>(NativeOsUtilsBase.java:352)
 at intradoc.common.NativeOsUtils.<init>(NativeOsUtils.java:26)
 at intradoc.common.EnvUtils.initializeOsFlags(EnvUtils.java:169)
 at intradoc.common.EnvUtils.getOSFamily(EnvUtils.java:475)
 at intradoc.shared.SharedLoader.configureBufferPoolUsage(SharedLoader.java:644)
 at intradoc.shared.SharedLoader.loadInitialConfig(SharedLoader.java:230)
 at intradoc.server.IdcSystemConfig.loadAppConfigInfo(IdcSystemConfig.java:370)
 at intradoc.server.IdcSystemConfig.loadAppConfigInfo(IdcSystemConfig.java:259)
 at intradoc.server.IdcServerManager.init(IdcServerManager.java:100)
 at intradoc.idcwls.IdcServletRequestUtils.initializeServer(IdcServletRequestUtils.java:624)
 at intradoc.idcwls.IdcServletRequestUtils.initializeServer(IdcServletRequestUtils.java:455)
 at intradoc.idcwls.IdcIntegrateWrapper.initializeServer(IdcIntegrateWrapper.java:102)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at idcservlet.common.IdcMethodHolder.invokeMethod(IdcMethodHolder.java:87)
 at idcservlet.common.ClassHelperUtils.executeMethodEx(ClassHelperUtils.java:305)
 at idcservlet.common.ClassHelperUtils.executeMethodWithArgs(ClassHelperUtils.java:278)
 at idcservlet.ServletUtils.initializeContentServer(ServletUtils.java:1242)
 at idcservlet.ServletUtils.startAndConfigureServer(ServletUtils.java:542)
 at idcservlet.ServletUtils.initializeAllServers(ServletUtils.java:455)
 at idcservlet.IdcFilter.initContentServer(IdcFilter.java:132)
 at idcservlet.IdcFilter.init(IdcFilter.java:124)
 at weblogic.servlet.internal.FilterManager$FilterInitAction.run(FilterManager.java:332)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.FilterManager.loadFilter(FilterManager.java:98)
 at weblogic.servlet.internal.FilterManager.preloadFilters(FilterManager.java:59)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1876)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
 at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
 at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
 at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
 at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
 at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.lang.UnsatisfiedLinkError: intradoc.common.NativeOsUtilsBase.getNativeVersion()Ljava/lang/String;
 at intradoc.common.NativeOsUtilsBase.getNativeVersion(Native Method)
 at intradoc.common.NativeOsUtilsBase.doLoad(NativeOsUtilsBase.java:382)
 ... 61 more
[2012-02-13T13:26:55.063-05:00] [UCM_server1] [ERROR] [] [oracle.ucm.idccs] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [ecid: 0000JLrxs2a3z0WjLxyGOA1FELN9000002,0] [APP: Oracle Universal Content Management - Content Server] UCM-CS-050021
[2012-02-13T13:26:55.078-05:00] [UCM_server1] [ERROR] [UCM-CS-000001] [oracle.ucm.idccs] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [ecid: 0000JLrxs2a3z0WjLxyGOA1FELN9000002,0] [APP: Oracle Universal Content Management - Content Server] general exception[[
intradoc.common.ServiceException: !csProviderUnableToInitialize,SystemDatabase
at intradoc.server.IdcSystemLoader.loadProviders(IdcSystemLoader.java:2379)
at intradoc.server.IdcSystemLoader.initProviders(IdcSystemLoader.java:2132)
at intradoc.server.IdcSystemLoader.finishInit(IdcSystemLoader.java:401)
at intradoc.server.IdcSystemLoader.init(IdcSystemLoader.java:336)
at intradoc.server.IdcServerManager.init(IdcServerManager.java:120)
at intradoc.idcwls.IdcServletRequestUtils.initializeServer(IdcServletRequestUtils.java:624)
at intradoc.idcwls.IdcServletRequestUtils.initializeServer(IdcServletRequestUtils.java:455)
at intradoc.idcwls.IdcIntegrateWrapper.initializeServer(IdcIntegrateWrapper.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at idcservlet.common.IdcMethodHolder.invokeMethod(IdcMethodHolder.java:87)
at idcservlet.common.ClassHelperUtils.executeMethodEx(ClassHelperUtils.java:305)
at idcservlet.common.ClassHelperUtils.executeMethodWithArgs(ClassHelperUtils.java:278)
at idcservlet.ServletUtils.initializeContentServer(ServletUtils.java:1242)
at idcservlet.ServletUtils.startAndConfigureServer(ServletUtils.java:542)
at idcservlet.ServletUtils.initializeAllServers(ServletUtils.java:455)
at idcservlet.IdcFilter.initContentServer(IdcFilter.java:132)
at idcservlet.IdcFilter.init(IdcFilter.java:124)
at weblogic.servlet.internal.FilterManager$FilterInitAction.run(FilterManager.java:332)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.FilterManager.loadFilter(FilterManager.java:98)
at weblogic.servlet.internal.FilterManager.preloadFilters(FilterManager.java:59)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1876)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: intradoc.data.DataException: !csDbUnableToInitalize,SystemDatabase!csProviderFailedToExtractAndUseDataSource,CSDS
at intradoc.jdbc.JdbcManager.init(JdbcManager.java:92)
at intradoc.jdbc.JdbcWorkspace.init(JdbcWorkspace.java:77)
at intradoc.provider.Provider.init(Provider.java:71)
at intradoc.server.IdcSystemLoader.loadProviders(IdcSystemLoader.java:2369)
... 56 more
Caused by: intradoc.data.DataException: !csProviderFailedToExtractAndUseDataSource,CSDS
at intradoc.provider.ProviderPoolManager.init(ProviderPoolManager.java:134)
at intradoc.jdbc.JdbcManager.init(JdbcManager.java:79)
... 59 more
Caused by: intradoc.common.ServiceException: !csProviderFailedToAccessDataSource
at intradoc.provider.ProviderPoolManager.computeExternalConnectionObject(ProviderPoolManager.java:263)
at intradoc.provider.ProviderPoolManager.init(ProviderPoolManager.java:130)
... 60 more
Caused by: intradoc.common.ServiceException: !csUnableToExecMethod,getConnection
at intradoc.common.ClassHelperUtils.convertToStandardException(ClassHelperUtils.java:202)
at intradoc.common.ClassHelperUtils.convertToStandardExceptionAndThrow(ClassHelperUtils.java:179)
at intradoc.common.ClassHelperUtils.executeIdcMethodConvertToStandardExceptions(ClassHelperUtils.java:410)
at intradoc.provider.ProviderPoolManager.getExternalRawConnection(ProviderPoolManager.java:945)
at intradoc.provider.ProviderPoolManager.computeExternalConnectionObject(ProviderPoolManager.java:243)
... 61 more
Caused by: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: ORA-28001: the password has expired
at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:250)
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:352)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:369)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at intradoc.common.IdcMethodHolder.invokeMethod(IdcMethodHolder.java:86)
at intradoc.common.ClassHelperUtils.executeIdcMethodConvertToStandardExceptions(ClassHelperUtils.java:406)
... 63 more

893410 wrote:
I'm getting a database error (see full stack below) when I try to start UCM after Weblogic. I was not having this problem before. When digging through the stack trace (below) I notice one of the error its outputting is that my password expired. However, I'm able to connect to the database using SQL Plus just fine, and even changed the system password just to be safe. Who said it was SYSTEM that was expired? What do you get from
select username
from dba_users
where account_status like ('EXPIRE%);Oracle isn't smart enough to lie about that particular error message.
Same error. I tried researching the issue even further: tried following this - http://kishantha.blogspot.com/2010/03/oracle-enterprise-manager-console.html , but when i ran the 'emctl stop dbconsole' i got a config issue, which led me to a different blog post when i tried running 'dbca' to configure and it gave me the following error - "Listener is not up or database service is not registered with it. Start the Listener and register database service and run EM Configuration Assistant again" although from what I can tell my listener is running just fine. what could possibly be going wrong here? any help would be appreciated!
As for the listener issue, did you follow the suggestion, or just dismiss it because "from what I can tell my listener is running just fine" Did you verify that the db instance was registered to the listener? What did you see from 'lsnrctl status'?
>
>
>
<snip>
Caused by: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: ORA-28001: the password has expired
<snip>

"Not an executable or is a link" errors when starting Messaging Server

"Not an executable or is a link" errors when starting Messaging Server

If Calendar Server 3.x has been installed to the same server root
as Messaging server, it is possible that the command 'NscpMail start'
to restart the server will return a string of errors:
# /etc/NscpMail start
19971207145610:Dispatch:Notification:Local Module
(Account-Handler) is not a n executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Account-Manager) is not a n executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(AutoReply-Handler) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Configuration-Manager) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Error-Handler) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Mailbox-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Program-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(SMTP-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(SMTP-Router) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(UNIX-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(Finger-Server) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(IMAP4-Server) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(POP3-Server) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(SMTP-Accept) is not an executable or is a link.
Module not loaded.
Startup Problem:
Module Error-Handler is required for proper operation.
Netscape Messaging Server Exiting!
The Calendar server 3.x installation may have changed the permissions
on [server-root]/bin directory from 755 to 750. Simply issue the
command (as root) 'chmod 755 [server-root]/bin' and then start
the server with the 'NscpMail start' command, and it should start
without a problem.

"Not an executable or is a link" errors when starting Messaging Server

If Calendar Server 3.x has been installed to the same server root
as Messaging server, it is possible that the command 'NscpMail start'
to restart the server will return a string of errors:
# /etc/NscpMail start
19971207145610:Dispatch:Notification:Local Module
(Account-Handler) is not a n executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Account-Manager) is not a n executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(AutoReply-Handler) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Configuration-Manager) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Error-Handler) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Mailbox-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(Program-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(SMTP-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(SMTP-Router) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Local Module
(UNIX-Deliver) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(Finger-Server) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(IMAP4-Server) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(POP3-Server) is not an executable or is a link.
Module not loaded.
19971207145610:Dispatch:Notification:Network Module
(SMTP-Accept) is not an executable or is a link.
Module not loaded.
Startup Problem:
Module Error-Handler is required for proper operation.
Netscape Messaging Server Exiting!
The Calendar server 3.x installation may have changed the permissions
on [server-root]/bin directory from 755 to 750. Simply issue the
command (as root) 'chmod 755 [server-root]/bin' and then start
the server with the 'NscpMail start' command, and it should start
without a problem.

Cronjob not to execute when root password expires

Similar Messages

Maybe you are looking for