I have a two node test cluster right now running OES 2 SP1/Linux.

I have created resources to load all three iprint managers that I have created.

3 print managers, 1 driver store.

My first test print manager loads without issues on both cluster servers.

I created a new print manager recently, and it will not load.

Like I said, the other print manager I have loads fine. Can someone point me in the right direction with this issue?

I have looked at TID 3006957 but dont' really know if it applies since 1 manager loads but the other does not.

More information: I have created DNS entries for the new print manager DNS name as well as edited the load and unload scripts to resemble the exact same scripts for the working print manager (only changed resource ip and mount point.)

This is from the ipsmd.log file

Oct 24 10:14:25 INFO iPrint Manager 'South-PM.FNP.CLUSTERS.WFISD' has started loading.
Oct 24 10:14:25 FATAL Error (506D0201) occurred while creating the iPrint Manager database.
Oct 24 10:15:26 INFO The iPrint Manager has unloaded successfully.
Oct 24 10:15:26 WARNING The iPrint Manager has just experienced a segfault or fatal error. It will be restarted by its monitor process.
Oct 24 10:15:26 FATAL Error (506D0201) occurred while creating the iPrint Manager database.
Oct 24 10:16:27 INFO The iPrint Manager has unloaded successfully.
Oct 24 10:16:27 WARNING The iPrint Manager has just experienced a segfault or fatal error. It will be restarted by its monitor process.
Oct 24 10:16:27 FATAL Error (506D0201) occurred while creating the iPrint Manager database.
Oct 24 10:17:29 INFO The iPrint Manager has unloaded successfully.
Oct 24 10:17:29 WARNING The iPrint Manager has just experienced a segfault or fatal error. It will be restarted by its monitor process.
Oct 24 10:17:29 FATAL Error (506D0201) occurred while creating the iPrint Manager database.
Oct 24 10:18:30 INFO The iPrint Manager has unloaded successfully.
Oct 24 10:18:30 WARNING The iPrint Manager has just experienced a segfault or fatal error. It will be restarted by its monitor process.
Oct 24 10:18:30 FATAL Error (506D0201) occurred while creating the iPrint Manager database.
Oct 24 10:19:31 INFO The iPrint Manager has unloaded successfully.
Oct 24 10:19:31 FATAL The iPrint Manager has segfaulted or had a fatal error and has been auto-restarted 5 times within the last hour. There appears to be a repetitive problem occurring. The iPrint Manager is exiting.