Re: WO Apps do not restart automatically after one server upgrade...
Pyramide-Ingenierie Developer List <[email protected]> Wed, 12 Apr 2006 11:49:13 +0200
| Newsgroups | gmane.comp.web.webobjects.admin |
|---|---|
| Message-ID | <[email protected]> |
Hello, Thank you for your information... Unfortunately, I did not had the =20 opportunity to perform this procedure... While I was trying to "control" the server thru Timbuktu, the server =20 crashed and reboot automatically... I then launched a big "Norton =20 Disk Doctor" on the server system disk: it found really many =20 errors... I even had to make a "Recover Disk" on it... After the server restarted, all the WO Apps were automatically =20 restarted ! After all this, I deployed fresh new versions of these WO Apps and =20 restarted the server: everything was restarted automatically, all the =20= services and the WO Apps... In my case, it seems that the problems were related to garbage in the =20= system disk structures... May be you should check your xserve system =20= disk ? Nevertheless, I am a bit disappointed because the server system disk =20 is really fresh: it has been formatted and prepared just 3 month =20 ago... What can create such a garbage when the server never crashed =20 (only once) ? Regards / Cordialement ;-), Luc Demarche .................................................................. Luc Demarche [email protected] Mac OS Software Developer Pyramide Ingenierie sprl Tel: +32 87 292120 188 rue de Liege Fax: +32 87 292129 B-4800 Verviers Mail: [email protected] .................................................................. Le 10 avr. 06 =E0 17:01, Dominique BAILLON a =E9crit : > Hello, > > I had the same problem after I upgraded one of our xserve from =20 > 10.3.9 to 10.4.6 > > It seems that something strange happens between restart of the =20 > computer to the defined host. On my computer the symptom was that =20 > the ethernet address for the specified domain name changed between =20 > restart. > > I also traced a problem to the WOAdaptor not being able to connect =20 > to http://localhost:1085/ to get the configuration for the server. > > What I have done to solve the problem was to change my =20 > configuration in the following way : > > 1/ Update the Adaptor configuration file located in : > /System/Library/WebObjects/Adaptors/Apache/apache.conf > by changing the WebObjectsConfig line from http://localhost:1085 to =20= > http://1.2.3.4:1085 using the real IP of the computer > This problem was detected by logging the WOAdaptor comportement. = =20 > To start the log do : > sudo touch /tmp/logWebObjects > after that it's possible to look at the WebObjects.log in /tmp/ > > 2/ In System/Library/LaunchDaemons/ on : > com.apple.womonitor.plist and com.apple.wotaskd.plist > I have added a new Parameter -WOHost=3D1.2.3.4 using the same IP than =20= > in the apache.conf file > > 3/ when I created my host in JavaMonitor I've done it with the same =20= > IP than above > > 4/ When I created an Application I've added the -WOHost=3D1.2.3.4 in =20= > the "Additional Arguments" textarea for the "New Instance Defaults" =20= > for the Application > > I hope that this informations can help you to solve your problem > > Cordialement > > Dominique BAILLON > Paris France > ------------- > On 10 avr. 06, at 14:35, Pyramide-Ingenierie Developer List wrote: > >> Hello, >> >> We have upgraded one of our Mac OS X Server 10.4.6 server by =20 >> moving all its disks (System and Data) from one PowerMac G4 2*867 =20 >> to a better PowerMac G4 2*1420... Both have the same hardware =20 >> configuration (else the motherboard): more than 1GB RAM on both, =20 >> same PCI-SATA card with same disks and same PCI-Ethernet 1Gb card =20 >> all moved from the old to the new computer... Main MAC address =20 >> changed of course... >> >> If all the other Mac OS X Server services restarted without any =20 >> notice of the move, we were surprised that the WO Applications =20 >> hosted on this server did not restart automatically at server =20 >> start while they were restarting without any problem in the older =20 >> machine... >> >> Using JavaMonitor, the Apps cannot be restarted manually: =20 >> JavaMonitor "tries" to launch them after clicking on the start =20 >> button but does not succeed... >> >> I finally had to "delete" the host and recreate it to be able to =20 >> manually re-add each application instance and re-launch them... >> >> After each server restart, the applications do not start unless I =20 >> repeat all the operation (delete and re-create host, re-add =20 >> instances and launch them)... >> >> I look at the many logs but found not any clue of what was wrong: =20 >> not any trace that the server even tried to launch these apps... I =20= >> have just two clues: >> - when I have to delete the host, its IP address is not written =20 >> under its hostname in JavaMonitor's first column. >> - in Server Admin, the date of WebObjects service start is said as =20= >> "not available" while it was known and more or less equal to =20 >> server start time with the old server... >> >> Does anyone know what is happening ? Where can I look to get some =20 >> info on why the apps do not restart automatically (JavaMonitor =20 >> error log or wotaskd error log) ? >> >> Kind Regards, >> >> Luc Demarche >> _______________________________________________ >> WebObjects-admin mailing list >> [email protected] >> http://www.omnigroup.com/mailman/listinfo/webobjects-admin >