Posted on 07-24-2011 01:46 AM
A couple of notes from my experience updating my Linux deployment of Casper to 8.21:
==Issue1
Had some difficulty installing new version:
Could not find /etc/init.d/jamf.tomcat7 to stop Tomcat. Aborting installation...
OK
Aborting installation due to unsatisfied requirements.
So, I manually created this file, then the pre-flight was OK, and installation completed.
Thought it might be useful, as many deployments are not using Tomcat 7 already, so this file does not exist by default.
==Issue2
After trying the above, I set out to move my JSS to an OS X server instead. This server had never run Casper in any way, shape or form.
Downloaded updated files, installed Casper using new JSS .pkg.
JSSDatabaseUtil.jar, after a fresh install on a 10.6.8 server, would not restore from my Linux server backup (which I had done with basic mysqldump command, then gzipped). Tried a few times, but couldn't get it to restore. I had already upgraded db to 8.21 on my Linux box, so I was attempting to restore an updated db once I moved it to the OS X server. I had to restore the db manually via Terminal using mysql, which worked fine, but was a little surprised by the behavior.
Not sure if JSSDatabaseUtil was specifically looking for a .gz file, as I noticed that it itself creates a .gz file when backing up. I had manually expanded prior to attempting a restore, and it told me it was complete (almost immediately), even though my db is 1.2 GB at the moment.
I've also sent these comments to JAMF, as perhaps the issue was unique to my environment.
Regards,
Luis
Luis Giraldo | ACSA, ACT | Phone: +1 (604) 638-6551 | luis at monkeymac.com