user3259832 wrote:What does +/u01/app/oracle/ovm-manager-3/machine1/base_adf_domain/servers/AdminServer/logs/AdminServer.log+ say on the Oracle VM Manager?
"Unexpected error during login (com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6000E Internal Error: Connection refused Connection refused Tue Nov 15 17:20:22 PST 2011), please consult logs for details."
user3259832 wrote:You need to check higher in the log to see if there's a problem with the OVMDS data source or anything else as the Manager starts up. Essentially, you're looking for problems that are preventing the Manager Core from starting properly.
The limitations of this forum won't let me post the entire log, but I did notice that NOTHING hits this log file when I attempt to login. Here's the tail of the log, but again, nothing is added when watching the log during an attempted login on the GUI.
user3259832 wrote:Well, the Oracle VM guys can't do much about Oracle Database. :) If you're using the supplied XE database, keep in mind that this is not supported in production (as detailed in the documentation) and that you should use SE or EE instead. There is no need to purchase a license for these products if you're only using them for Oracle VM Manager, as we include a limited-use license for Oracle VM. I personally use an Oracle Database 11gR2 Enterprise Edition instance for my Oracle VM Manager and I've never seen this particular issue. Though, that's just an anecdotal reference.
Thanks for your efforts Avi. If I was an Oracle DBA, I'd jump right in and fix the account in the database. Unfortunately that's not my expertise. The previous CSR on this identical error message, the Oracle engineer had me create another account called "admin1" and it received the exact same error message. Seems like they shoud consider fixing this product before releasing it eh?
user3259832 wrote:Yeah, we're making this a LOT more obvious in 3.0.3 -- the "Simple" install becomes "Unsupported" or something like that. I forget the exact term they're using, but it's made a lot more obvious that the default XE database should be used only for test/POC implementations.
Right! Got it. Oracle-XE which is installed by default not supported... Check!
user3259832 wrote:Means that the OVMDS password for the OVS account is wrong. You should use the ovs_admin script in /u01/app/oracle/ovm-manager-3/bin to modify the OVMDS to match the right password:
It's the OVS account in the Oracle-XE database that's getting "locked (timed)". I unlocked the account, then stopped and restarted /etc/init.d/ovmm and tried logging in again. OVS was locked (timed) again...
The option you want to use is "--modifyds" and provide the sid (XE), host (local hostname), port (1521 probably), schema (OVS) and password (whatever the right password is).
[root@ovm3 bin]# ./ovm_admin Oracle VM Manager Release 3.0.3 Admin tool Usage: ./ovm_admin [options] options --help Shows this message --createuser <admin> <password> Create new Oracle VM Manager admin user --deleteuser <admin> Delete Oracle VM Manager admin user --listusers List Oracle VM Manager users --modifyuser <admin> <password> <new_password> Modify Oracle VM Manager user password --lockusers <tries> Max login tries before locking account. This setting is global. --unlockuser <admin> Unlock user account --modifyds <SID> <host> <port> <schema> <password>Modify Data Store 'OVMDS' --listconfig List configuration --rotatelogsdaily <time> Rotate Logs Daily (HH:MM) --rotatelogsbysize <size> Rotate Logs By Size (KB)