Simon Brown Posted January 4, 2010 Posted January 4, 2010 I recently upgraded a system from OSXS 10.5.8 to 10.6.2, and also an update of FMS 10 to 10.0.2. It had a copy SuperContainer installed, which was probably working, but hadn't tested. I ran the .jar installer with the latest version of SC to update the previous install, which seemed to work. After the updates however, it was not working. I could get to the page to enter the serial, but couldn't access files. In the Apache log I was seeing error messages like this: [Fri Jan 01 21:55:26 2010] [error] [client 192.168.5.1] File does not exist: /Library/WebServer/Documents/SuperContainer It then tried to uninstall, but got an "unexpected error" dialog. Same if I tried to update. I then trashed all files in /Library/FileMaker Server/Web Publishing/publishing-engine/cwpe-tomcat/bin/SuperContainer. I then tried running the installer again, but still the "unexpected error" dialog. Here's what I found in the logs: 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] Jan 4, 2010 11:30:54 AM com.prosc.supercontainer.installer.InstallerGUI$1 run 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] INFO: Installing 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] Jan 4, 2010 11:30:54 AM com.prosc.supercontainer.installer.Installer _copySC 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] INFO: Copying SuperContainer to WebApps 1/4/10 11:30:54 AM sudo[61738] simon_b : no tty present and no askpass program specified ; TTY=unknown ; PWD=/Users/badmin/Public/360Works_SuperContainer-2_631 ; USER=root ; COMMAND=/bin/cp -R ./SuperContainer /Library/FileMaker Server/Web Publishing/publishing-engine/cwpe-tomcat/bin/ 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] sudo: no tty present and no askpass program specified 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] Jan 4, 2010 11:30:54 AM com.prosc.supercontainer.installer.InstallerGUI$1 run 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] INFO: Broken pipe 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] java.io.IOException: Broken pipe 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] at java.io.FileOutputStream.writeBytes(Native Method) 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] at java.io.FileOutputStream.write(FileOutputStream.java:260) 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] at com.prosc.supercontainer.installer.SudoEnabler.login(SudoEnabler.java:47) 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] at com.prosc.supercontainer.installer.Installer.executeCommand(Installer.java:193) 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] at com.prosc.supercontainer.installer.Installer._copySC(Installer.java:203) 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] at com.prosc.supercontainer.installer.Installer.installSuperContainer(Installer.java:241) 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] at com.prosc.supercontainer.installer.Installer.runInstaller(Installer.java:351) 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] at com.prosc.supercontainer.installer.InstallerGUI$1.run(InstallerGUI.java:78) 1/4/10 11:30:54 AM [0x0-0xe30e3].com.apple.JarLauncher[61720] at java.lang.Thread.run(Thread.java:637) Hoping for some help. Thanks!
Smef Posted January 5, 2010 Posted January 5, 2010 At this time the installer.jar file does not work with Snow Leopard. You can still do a manual install in the mean time, and SuperContainer will run fine. The instructions to do a manual installation can be found at http://wo.360works.com/cgi-bin/support/productsupport.cgi/SuperContainer#SuperContainer8
Simon Brown Posted January 7, 2010 Author Posted January 7, 2010 Still adjusting a few details, but this seems to of worked. Just be sure to also do the "optional" steps to modify the file at /Library/FileMaker Server/Admin/admin-helper/WEB-INF/conf/mod_jk.conf. The location of this at first threw me off ("why am I modifying the configuration for the admin console"), but apparently this is what SC usually does.
Valentin Posted January 26, 2010 Posted January 26, 2010 This is simply where the JK connector settings file is stored, it happens to be in the Admin folder.
Recommended Posts
This topic is 5415 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now