Dan, Thanks a ton for that information. The hostname was good, but key.lic kept getting over-written, killing one of the entries.
jdiag clued me in to a difference though: users. I didn't have the right posix user and file ownerships on any of the jbase stuff. fixed, and restarted, and it is happy now. At least the license is. Thanks you all of your guys' time. Now I can keep this mysterious unicorn running on fresh hardware and take the old machine to the shooting range. J. On Monday, December 9, 2013 6:36:39 PM UTC-7, Daniel Klein wrote: > > That error message indicates that the new server is looking for a license > key. On a 4.1 system the license is stored in '$JBCRELEASEDIR/config/' and > is named 'key.lic'. If the new machine has exactly the same name as the old > one, as given by 'uname -n', then moving that file from the old system to > the new one and then restarting the license services (or rebooting) should > (at least) eliminate that error. > > You can also run the command 'jdiag -vL' on both systems to make sure the > environment of the new system is set up correctly. > > Hope this helps, > > Dan > > -- -- IMPORTANT: T24/Globus posts are no longer accepted on this forum. To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en --- You received this message because you are subscribed to the Google Groups "jBASE" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
