Skip to main content

developerWorks >  Tivoli  >  Forums  >  Tivoli Provisioning Manager (TPM)  >  developerWorks

Error 500: system#notboundexception with Tivoli Provisioning Manager 7.1    Point your RSS reader here for a feed of the latest messages in this thread


     
 
 
My developerWorks
 Welcome, Guest
Sign in or register
This question is not answered.

Reply to this Thread Reply to this Thread Post New Thread Post New Thread Watch list Watch list Forum settings Forum settings Help Help
Permlink Replies: 9 - Pages: 1 - Last Post: Nov 9, 2009 10:01 AM Last Post By: Al_Nagle
Al_Nagle

Posts: 5
Registered: Nov 02, 2009 03:54:08 PM
Error 500: system#notboundexception with Tivoli Provisioning Manager 7.1
Posted: Nov 02, 2009 04:03:21 PM 		 
Click to report abuse...   Click to reply to this thread Reply
Hi all,

I have TPM 7.1 on aix 5.3. As far as I know the installation was fine, but when I go to sign in at http://<my_ip>:9080/maximo/ or https://<my_ip>:9045, all I get is a white page with the following written on it: Error 500: system#notboundexception.
I'm not sure what this means. I did find this log excerpt:

BMXAA6454E - Database configuration is in process. The ConfigDB and
RestoreFromBackup actions must complete before the Maximo server can
start.

ERROR Tpm Engine Startup Thread (Activator.java:136) util.Activator:
access#DBConnectFail
psdi.util.MXSystemException: access#DBConnectFail
at psdi.server.MaxPropCache.reloadCache(MaxPropCache.java:435)
at psdi.server.MaxPropCache.reload(MaxPropCache.java:218)
at psdi.server.MXServer.boot(MXServer.java:1021)
at psdi.server.MXServer.start(MXServer.java:3092)
at com.ibm.tivoli.tpm.util.Activator$1.run(Activator.java:75)
Caused by:
com.ibm.db2.jcc.c.DisconnectException: ibmdb2jcct4204311550
Exception java.net.ConnectException: Error opening socket to server
<hostname>/<ip addy> on port 50,005 with message:
Connection refused.

Does anyone have any ideas?
Martin Carnegie

Posts: 628
Registered: Nov 06, 2006 01:15:07 PM
Re: Error 500: system#notboundexception with Tivoli Provisioning Manager 7.1
Posted: Nov 02, 2009 10:34:24 PM   in response to: Al_Nagle in response to: Al_Nagle's post 		 
Click to report abuse...   Click to reply to this thread Reply
I think that the "ERROR Tpm Engine Startup Thread (Activator.java:136) util.Activator:access#DBConnectFail" would be the first place to start. Make sure that you can connect to the database server on port 50005. Try using the command "telnet 50005" and see if there is a response.

Martin Carnegie
Gulf Breeze Software
http://www.gulfsoft.com
Al_Nagle

Posts: 5
Registered: Nov 02, 2009 03:54:08 PM
Re: Error 500: system#notboundexception with Tivoli Provisioning Manager 7.1
Posted: Nov 03, 2009 09:04:20 AM   in response to: Martin Carnegie in response to: Martin Carnegie's post 		 
Click to report abuse...   Click to reply to this thread Reply
C-bash-3.00$ telnet -d 127.0.0.1 50005
Connected to 127.0.0.1.

Did I do that right? Just doing telnet 50005 gave a 'No route to host' error so I added in the loopback.

Also, here is the output of netstat -a | grep 50005:
tcp4 0 0 *.50005 . LISTEN
tcp4 0 0 dctpm2.50005 dctpm2.46953 ESTABLISHED
tcp 0 0 dctpm2.46953 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.47383 ESTABLISHED
tcp 0 0 dctpm2.47383 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38935 ESTABLISHED
tcp 0 0 dctpm2.38935 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38941 ESTABLISHED
tcp 0 0 dctpm2.38941 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38943 ESTABLISHED
tcp 0 0 dctpm2.38943 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38944 ESTABLISHED
tcp 0 0 dctpm2.38944 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38945 ESTABLISHED
tcp 0 0 dctpm2.38945 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38946 ESTABLISHED
tcp 0 0 dctpm2.38946 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38947 ESTABLISHED
tcp 0 0 dctpm2.38947 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38949 ESTABLISHED
tcp 0 0 dctpm2.38949 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38950 ESTABLISHED
tcp 0 0 dctpm2.38950 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38951 ESTABLISHED
tcp 0 0 dctpm2.38951 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38952 ESTABLISHED
tcp 0 0 dctpm2.38952 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38953 ESTABLISHED
tcp 0 0 dctpm2.38953 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38954 ESTABLISHED
tcp 0 0 dctpm2.38954 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38955 ESTABLISHED
tcp 0 0 dctpm2.38955 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38956 ESTABLISHED
tcp 0 0 dctpm2.38956 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38957 ESTABLISHED
tcp 0 0 dctpm2.38957 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38958 ESTABLISHED
tcp 0 0 dctpm2.38958 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38959 ESTABLISHED
tcp 0 0 dctpm2.38959 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38960 ESTABLISHED
tcp 0 0 dctpm2.38960 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38962 ESTABLISHED
tcp 0 0 dctpm2.38962 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38963 ESTABLISHED
tcp 0 0 dctpm2.38963 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38964 ESTABLISHED
tcp 0 0 dctpm2.38964 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38965 ESTABLISHED
tcp 0 0 dctpm2.38965 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38973 ESTABLISHED
tcp 0 0 dctpm2.38973 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38974 ESTABLISHED
tcp 0 0 dctpm2.38974 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38975 ESTABLISHED
tcp 0 0 dctpm2.38975 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38976 ESTABLISHED
tcp 0 0 dctpm2.38976 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38977 ESTABLISHED
tcp 0 0 dctpm2.38977 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38978 ESTABLISHED
tcp 0 0 dctpm2.38978 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38979 ESTABLISHED
tcp 0 0 dctpm2.38979 dctpm2.50005 ESTABLISHED
tcp4 0 0 dctpm2.50005 dctpm2.38980 ESTABLISHED
tcp 0 0 dctpm2.38980 dctpm2.50005 ESTABLISHED
Martin Carnegie

Posts: 628
Registered: Nov 06, 2006 01:15:07 PM
Re: Error 500: system#notboundexception with Tivoli Provisioning Manager 7.1
Posted: Nov 03, 2009 11:08:38 AM   in response to: Al_Nagle in response to: Al_Nagle's post 		 
Click to report abuse...   Click to reply to this thread Reply
Oops forgot the hostname in the telnet ;)

Which log did you see that DBConnectFail in?

Martin Carnegie
Gulf Breeze Software
http://www.gulfsoft.com
Al_Nagle

Posts: 5
Registered: Nov 02, 2009 03:54:08 PM
Re: Error 500: system#notboundexception with Tivoli Provisioning Manager 7.1
Posted: Nov 03, 2009 12:51:45 PM   in response to: Martin Carnegie in response to: Martin Carnegie's post 		 
Click to report abuse...   Click to reply to this thread Reply
I found it in /usr/ibm/tivoli/common/COP/logs/console.log

I just got done doing the ConfigDB and RestoreFromBackup actions and now instead of listing the MBXAA654E error from above, it has the following:

2009-11-03 10:56:18,136 ERROR Tpm Engine Startup Thread (Activator.java:136) util.Activator: access#DBConnectFail
psdi.util.MXSystemException: access#DBConnectFail
at psdi.server.MaxPropCache.reloadCache(MaxPropCache.java:435)
at psdi.server.MaxPropCache.reload(MaxPropCache.java:218)
at psdi.server.MXServer.boot(MXServer.java:1021)
at psdi.server.MXServer.start(MXServer.java:3092)
at com.ibm.tivoli.tpm.util.Activator$1.run(Activator.java:75)
Caused by:
com.ibm.db2.jcc.c.DisconnectException: ibmdb2jcct4204311550 Exception java.net.ConnectException: Error opening socket to server <hostname>/<ip_addy> on port 50,005 with message: Connection refused.

/usr/ibm/tivoli/common/COP/logs/tio_start_service.log states:

03 Nov 2009 10:56:15:514 ERROR BMXAA6421E - The system could not connect to the JDBC source: jdbc:db2://<hostname>:50005/MAXDB71ibmdb2jcct4204311550 Exception java.net.ConnectException: Error opening socket to server <hostname>/<ip addy> on port 50,005 with message: Connection refused.
03 Nov 2009 10:56:16:467 ERROR BMXAA6418E - There was an error reloading the MAXPROP cache: access#DBConnectFail
03 Nov 2009 10:56:17:287 FATAL BMXAA6473E Maximo failed to start.
psdi.util.MXSystemException: access#DBConnectFail

I guess that whole "Maximo failed to start" thing is a problem :)
gdubel

Posts: 2
Registered: Oct 14, 2009 02:58:29 PM
Re: Error 500: system#notboundexception with Tivoli Provisioning Manager 7.1
Posted: Nov 03, 2009 05:52:40 PM   in response to: Al_Nagle in response to: Al_Nagle's post 		 
Click to report abuse...   Click to reply to this thread Reply
I have seen this error on a TPM 7.1 system which had some mileage on it (was not a new install). In my case, I was bitten by our password expiration policy. I reset the password for all userids associated with TPM (maximo, ctginst1 etc) and bounced TPM. Since this is a new install and judging from you logfile exerpts I rather doubt you have the same issue but it's worth verifying the passwords are "OK" by logging into the TPM server as each user.
Martin Carnegie

Posts: 628
Registered: Nov 06, 2006 01:15:07 PM
Re: Error 500: system#notboundexception with Tivoli Provisioning Manager 7.1
Posted: Nov 03, 2009 07:38:47 PM   in response to: gdubel in response to: gdubel's post 		 
Click to report abuse...   Click to reply to this thread Reply
I was kinda wondering if this could be the problem. You would hope the return message would be better though :) Worth a try for sure.

Martin Carnegie
Gulf Breeze Software
http://www.gulfsoft.com
Al_Nagle

Posts: 5
Registered: Nov 02, 2009 03:54:08 PM
Re: Error 500: system#notboundexception with Tivoli Provisioning Manager 7.1
Posted: Nov 04, 2009 09:15:20 AM   in response to: Martin Carnegie in response to: Martin Carnegie's post 		 
Click to report abuse...   Click to reply to this thread Reply
I was told that the password expiration is an issue, but I don't think I have this problem on AIX. At least, I don't think I do. When I look at my users via smit I found nothing that said anything about password expiration (expiration date is set to 0, is that it?), but I have never had a problem logging on with any of the users (maxadmin, wasadmin, tioadmin, idsccmdb, ctginst1). Any ideas?
remesm

Posts: 2
Registered: Jun 03, 2003 10:35:28 AM
Re: Error 500: system#notboundexception with Tivoli Provisioning Manager 7.1
Posted: Nov 09, 2009 05:05:48 AM   in response to: Al_Nagle in response to: Al_Nagle's post 		 
Click to report abuse...   Click to reply to this thread Reply
What about user maximo? That's the user with which TPM is connecting to the MAXDB71 db.
A new user might also exhibit this symptom. Expiration is set to 0, but still the password needs to be changed the first time the user logs in.

Marc
Al_Nagle

Posts: 5
Registered: Nov 02, 2009 03:54:08 PM
Re: Error 500: system#notboundexception with Tivoli Provisioning Manager 7.1
Posted: Nov 09, 2009 10:01:18 AM   in response to: remesm in response to: remesm's post 		 
Click to report abuse...   Click to reply to this thread Reply
I just switched to user maximo and there was no password change request. I'm pretty sure I've signed in with just about every user name involved in this installation by now. I think what happened in my particular case involved some error in the Base Services installation. This is unfortunate because the windows that I used to install the base services was wiped so I don't have error logs to go by. I just tried to reinstall base services in a new Win server 2k3 installation and there were errors with the install (no surprise there):

CTGIN0143E: An action error ocurred during the processing of a deployment operation. Action identifier: "DEPLOY_PORTALLOGTRACEANALYZER_WAR". Action display name: "Deploy Portal Log Trace Analyzer WAR to the WebSphere Application Server".
CTGIN0144I: Completed action "11" of "19". Action display name: "Deploy Portal Log Trace Analyzer WAR to the WebSphere Application Server".
CTGIN0073E: Errors were detected during the installation of the C:\IBM\SMP\pmp\base_services_7.1.1.zip package.

I still have my problem, but I don't know if its fixable. :(
Pages: 1
Go Back Back to Thread List

Update your My developerWorks profile and start connecting with others.

Point your RSS reader here for a feed of the latest messages in all forums