|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
|
|
Service executableAre Daisy's services supposed to be pointing to
C:\Daisy\daisy-2.4.2\wrapper\bin\wrapper-windows-x86-32.exe? My current DAISY_HOME environment variables points to C:\Daisy\daisy-2.4.2. Currently, they are pointing to another path such as C:\Daisy\daisyhome\wrapper\bin\wrapper-windows-x86-32.exe. Both paths seem to replicating the same tree structure/files. New guy. Existing repo. I'm assuming that the configuration changed at the beginning and somebody failed to update the services? Dan _______________________________________________ daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
Re: Service executableDan
If you want to use the service scripts of the 2.4.2 version I guess it would be best to uninstall the old ones and install the new ones (just to be on the safe side) Go to Open up a terminal console and go to %DAISY_REPO_DATA%\service\ There you can invoke uninstall-daisy-repository-server-service.bat and uninstall-daisy-wiki-service.bat Then reinstall the services using the other batch files found in the directory install-daisy-repository-server-service.bat install-daisy-wiki-service.bat Starting can be done using batch files or the service manager UI. Paul On Mon, Apr 11, 2011 at 9:05 PM, Fournier, Danny G <Danny.Fournier@...> wrote: > Are Daisy's services supposed to be pointing to > C:\Daisy\daisy-2.4.2\wrapper\bin\wrapper-windows-x86-32.exe? > > My current DAISY_HOME environment variables points to > C:\Daisy\daisy-2.4.2. > > Currently, they are pointing to another path such as > C:\Daisy\daisyhome\wrapper\bin\wrapper-windows-x86-32.exe. Both paths > seem to replicating the same tree structure/files. > > New guy. Existing repo. I'm assuming that the configuration changed at > the beginning and somebody failed to update the services? > > Dan > _______________________________________________ > daisy community mailing list > Professional Daisy support: http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
|
|
|
Re: Service executablein windows you could map a folder to a drive letter using the subst
command, after that you can set DAISY_HOME to the drive you chose. http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/subst.mspx?mfr=true Regards, Karel On Tue, Apr 12, 2011 at 10:28 AM, Paul Focke <paul@...> wrote: > Dan > > If you want to use the service scripts of the 2.4.2 version I guess it > would be best to uninstall the old ones and install the new ones (just > to be on the safe side) > Go to > Open up a terminal console and go to > %DAISY_REPO_DATA%\service\ > There you can invoke > uninstall-daisy-repository-server-service.bat > and > uninstall-daisy-wiki-service.bat > > Then reinstall the services using the other batch files found in the directory > install-daisy-repository-server-service.bat > install-daisy-wiki-service.bat > > Starting can be done using batch files or the service manager UI. > > Paul > > > On Mon, Apr 11, 2011 at 9:05 PM, Fournier, Danny G > <Danny.Fournier@...> wrote: >> Are Daisy's services supposed to be pointing to >> C:\Daisy\daisy-2.4.2\wrapper\bin\wrapper-windows-x86-32.exe? >> >> My current DAISY_HOME environment variables points to >> C:\Daisy\daisy-2.4.2. >> >> Currently, they are pointing to another path such as >> C:\Daisy\daisyhome\wrapper\bin\wrapper-windows-x86-32.exe. Both paths >> seem to replicating the same tree structure/files. >> >> New guy. Existing repo. I'm assuming that the configuration changed at >> the beginning and somebody failed to update the services? >> >> Dan >> _______________________________________________ >> daisy community mailing list >> Professional Daisy support: http://outerthought.org/en/services/daisy/support.html >> mail to: daisy@... >> list information: http://lists.cocoondev.org/mailman/listinfo/daisy >> > _______________________________________________ > daisy community mailing list > Professional Daisy support: http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > -- Karel Vervaeke http://outerthought.org/ Open Source Content Applications Makers of Kauri, Daisy CMS and Lily _______________________________________________ daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
RE: RE: Service executableI've been echoing content from various locations in the
install-daisy-repository-server-service.bat file. So far, I can conclude that it goes through without any errors and executes the command to start the service. I've also echoed the command that installs the service: C:\Daisy\daisyhome\wrapper\bin\wrapper-windows-x86-32.exe -i "C:\Daisy\repodata\service\daisy-repository-server-service.conf" When I run this command manually, it goes through without any errors, but yet doesn't create the service. I've compared both service conf files and they are identicial except for the subtleties in creating respective services daisy-repository-server-service.conf daisy-wiki-service.conf I've compared both install files and they too are identical except for the subtleties in creating respective services install-daisy-repository-server-service.bat install-daisy-wiki-service.bat I even tried removing the wiki service and installing the repository service first, but that didn't work out either. Another thing I've tried is the uncommenting of the Wrapper Windows NT/2000/XP Service Properties in the daisy-repository-server-service.conf. No go there either. I don't see any errors in the Event Viewer. I can install and uninstall at will, the wiki service though (hope this doesn't jinx it! LOL) If I could just get the other one installed I'd probably be set. > -----Original Message----- > From: daisy-bounces@... > [mailto:daisy-bounces@...] On Behalf Of > Fournier, Danny G > Sent: April 13, 2011 11:32 AM > To: daisy@... > Subject: [daisy] RE: Service executable > > Paul, > > My goal is now to have everything in daisyhome. Here's what > I've done so > far: > > 1. I've set DAISY_HOME to point to daisyhome (instead of daisy-2.4.2) > 2. I renamed daisyhome to daisyhome_bak > 3. I copied daisy-2.4.2 to daisyhome > 4. I've uninstalled both services (they weren't visible from > the service > console list) > > 5. I've used the install scripts (ie. %DAISY_HOME%/install) to create > the service scripts in both %REPO_DATA%/service and > %WIKI_DATA%/service... I used the following commands: > > daisy-service-install -f -r path_to_repo_data > > daisy-service-install -f -w path_to_wiki_data > > Both these folders show updated modified file dates corresponding to > when I created them. > > 6. I've been able to recreate the Wiki service, using > "install-daisy-wiki-service.bat" file from %WIKI_DATA%/service. I now > see it in the service list. > > However, I've not been able to recreate the Repository service in the > same fashion, using install-daisy-repository-server-service.bat from > %REPO_DATA%/service. If I run it, all I see is "Press a key > to continue > ...". I've not seen a confirmation message in the console compared to > when I created the wiki service. > > Would you have an idea why this is occuring? > > > > Date: Wed, 13 Apr 2011 08:58:03 +0200 > > From: Paul Focke <paul@...> > > Subject: Re: [daisy] RE: daisy Digest, Vol 79, Issue 7 > > To: "Daisy: open source CMS - general mailinglist" > > <daisy@...> > > Message-ID: <BANLkTin+K6NP00vn5o5N3TjU4YchpuedyA@...> > > Content-Type: text/plain; charset=ISO-8859-1 > > > > Dan > > > > It would make the most sense to invoke the services from DAISY_HOME. > > The initial setup of having a c:\Daisy\daisyhome directory > was a good > > idea. This is pretty much how we do things on our own setups. The > > biggest difference being that we use a unix environment and we make > > use of softlinks to link daisyhome to a daisy version. If I had done > > the upgrade I probably would have overwritten the old daisyhome with > > the files found in daisy-2.4.2 that way you don't have to go around > > changing paths in environment variables and services. > > > > The setting in the conf file is to set a default for DAISY_HOME in > > case it isn't found as an environment variable. No harm done if you > > change this to reflect the changes in your current setup. > > > > I would advise reconsidering the current upgrade effort. I > believe you > > can make future upgrades easier if you first move the old > daisyhome to > > daisy-2.4 (if this was the version you were starting from) and then > > moving daisy-2.4.2 to daisyhome. If you can try getting into touch > > with the person who started the upgrade. Maybe he/she had a good > > reason for choosing the current way of doing things. > > > > Paul > _______________________________________________ > daisy community mailing list > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
Re: RE: Service executableThe problem could be related to the wrapper version (we recently
upgraded it in Daisy), and the different versions don't seem to like each other very well. Try the following procedure: * unregister the service (check in services.msc to see that it's really gone) * make sure no wrapper.exe or java.exe processes are lingering around (taskmgr.exe) * reboot * try to re-register the service. HTH, Karel On Thu, Apr 14, 2011 at 3:21 PM, Fournier, Danny G <Danny.Fournier@...> wrote: > I've been echoing content from various locations in the > install-daisy-repository-server-service.bat file. So far, I can conclude > that it goes through without any errors and executes the command to > start the service. > > I've also echoed the command that installs the service: > C:\Daisy\daisyhome\wrapper\bin\wrapper-windows-x86-32.exe -i > "C:\Daisy\repodata\service\daisy-repository-server-service.conf" > > When I run this command manually, it goes through without any errors, > but yet doesn't create the service. > > I've compared both service conf files and they are identicial except for > the subtleties in creating respective services > daisy-repository-server-service.conf > daisy-wiki-service.conf > > I've compared both install files and they too are identical except for > the subtleties in creating respective services > install-daisy-repository-server-service.bat > install-daisy-wiki-service.bat > > I even tried removing the wiki service and installing the repository > service first, but that didn't work out either. > > Another thing I've tried is the uncommenting of the Wrapper Windows > NT/2000/XP Service Properties in the > daisy-repository-server-service.conf. No go there either. > > I don't see any errors in the Event Viewer. > > I can install and uninstall at will, the wiki service though (hope this > doesn't jinx it! LOL) If I could just get the other one installed I'd > probably be set. > > >> -----Original Message----- >> From: daisy-bounces@... >> [mailto:daisy-bounces@...] On Behalf Of >> Fournier, Danny G >> Sent: April 13, 2011 11:32 AM >> To: daisy@... >> Subject: [daisy] RE: Service executable >> >> Paul, >> >> My goal is now to have everything in daisyhome. Here's what >> I've done so >> far: >> >> 1. I've set DAISY_HOME to point to daisyhome (instead of daisy-2.4.2) >> 2. I renamed daisyhome to daisyhome_bak >> 3. I copied daisy-2.4.2 to daisyhome >> 4. I've uninstalled both services (they weren't visible from >> the service >> console list) >> >> 5. I've used the install scripts (ie. %DAISY_HOME%/install) to create >> the service scripts in both %REPO_DATA%/service and >> %WIKI_DATA%/service... I used the following commands: >> >> daisy-service-install -f -r path_to_repo_data >> >> daisy-service-install -f -w path_to_wiki_data >> >> Both these folders show updated modified file dates corresponding to >> when I created them. >> >> 6. I've been able to recreate the Wiki service, using >> "install-daisy-wiki-service.bat" file from %WIKI_DATA%/service. I now >> see it in the service list. >> >> However, I've not been able to recreate the Repository service in the >> same fashion, using install-daisy-repository-server-service.bat from >> %REPO_DATA%/service. If I run it, all I see is "Press a key >> to continue >> ...". I've not seen a confirmation message in the console compared to >> when I created the wiki service. >> >> Would you have an idea why this is occuring? >> >> >> > Date: Wed, 13 Apr 2011 08:58:03 +0200 >> > From: Paul Focke <paul@...> >> > Subject: Re: [daisy] RE: daisy Digest, Vol 79, Issue 7 >> > To: "Daisy: open source CMS - general mailinglist" >> > <daisy@...> >> > Message-ID: <BANLkTin+K6NP00vn5o5N3TjU4YchpuedyA@...> >> > Content-Type: text/plain; charset=ISO-8859-1 >> > >> > Dan >> > >> > It would make the most sense to invoke the services from DAISY_HOME. >> > The initial setup of having a c:\Daisy\daisyhome directory >> was a good >> > idea. This is pretty much how we do things on our own setups. The >> > biggest difference being that we use a unix environment and we make >> > use of softlinks to link daisyhome to a daisy version. If I had done >> > the upgrade I probably would have overwritten the old daisyhome with >> > the files found in daisy-2.4.2 that way you don't have to go around >> > changing paths in environment variables and services. >> > >> > The setting in the conf file is to set a default for DAISY_HOME in >> > case it isn't found as an environment variable. No harm done if you >> > change this to reflect the changes in your current setup. >> > >> > I would advise reconsidering the current upgrade effort. I >> believe you >> > can make future upgrades easier if you first move the old >> daisyhome to >> > daisy-2.4 (if this was the version you were starting from) and then >> > moving daisy-2.4.2 to daisyhome. If you can try getting into touch >> > with the person who started the upgrade. Maybe he/she had a good >> > reason for choosing the current way of doing things. >> > >> > Paul >> _______________________________________________ >> daisy community mailing list >> Professional Daisy support: >> http://outerthought.org/en/services/daisy/support.html >> mail to: daisy@... >> list information: http://lists.cocoondev.org/mailman/listinfo/daisy >> > _______________________________________________ > daisy community mailing list > Professional Daisy support: http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > -- Karel Vervaeke http://outerthought.org/ Open Source Content Applications Makers of Kauri, Daisy CMS and Lily _______________________________________________ daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
RE: RE: Service executableSo far, the only thing I haven't done, is reboot. Unfortunately, I don't have the rights to do so either.
I've double unregistered the service by confirming that it's not showing up in services.msc. There are no wrapper.exe or java.exe lingering around in task manager. I cannot re-register the service for the repository server. The wiki service can be registered and started at will. I wonder if I would use sc.exe to manually create the service? > -----Original Message----- > From: daisy-bounces@... > [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke > Sent: April 15, 2011 5:08 AM > To: Daisy: open source CMS - general mailinglist > Subject: Re: [daisy] RE: Service executable > > The problem could be related to the wrapper version (we recently > upgraded it in Daisy), and the different versions don't seem to like > each other very well. > > Try the following procedure: > * unregister the service (check in services.msc to see that > it's really gone) > * make sure no wrapper.exe or java.exe processes are lingering around > (taskmgr.exe) > * reboot > * try to re-register the service. > > HTH, > Karel > > On Thu, Apr 14, 2011 at 3:21 PM, Fournier, Danny G > <Danny.Fournier@...> wrote: > > I've been echoing content from various locations in the > > install-daisy-repository-server-service.bat file. So far, I > can conclude > > that it goes through without any errors and executes the command to > > start the service. > > > > I've also echoed the command that installs the service: > > C:\Daisy\daisyhome\wrapper\bin\wrapper-windows-x86-32.exe -i > > "C:\Daisy\repodata\service\daisy-repository-server-service.conf" > > > > When I run this command manually, it goes through without > any errors, > > but yet doesn't create the service. > > > > I've compared both service conf files and they are > identicial except for > > the subtleties in creating respective services > > daisy-repository-server-service.conf > > daisy-wiki-service.conf > > > > I've compared both install files and they too are identical > except for > > the subtleties in creating respective services > > install-daisy-repository-server-service.bat > > install-daisy-wiki-service.bat > > > > I even tried removing the wiki service and installing the repository > > service first, but that didn't work out either. > > > > Another thing I've tried is the uncommenting of the Wrapper Windows > > NT/2000/XP Service Properties in the > > daisy-repository-server-service.conf. No go there either. > > > > I don't see any errors in the Event Viewer. > > > > I can install and uninstall at will, the wiki service > though (hope this > > doesn't jinx it! LOL) If I could just get the other one > installed I'd > > probably be set. > > > > > >> -----Original Message----- > >> From: daisy-bounces@... > >> [mailto:daisy-bounces@...] On Behalf Of > >> Fournier, Danny G > >> Sent: April 13, 2011 11:32 AM > >> To: daisy@... > >> Subject: [daisy] RE: Service executable > >> > >> Paul, > >> > >> My goal is now to have everything in daisyhome. Here's what > >> I've done so > >> far: > >> > >> 1. I've set DAISY_HOME to point to daisyhome (instead of > daisy-2.4.2) > >> 2. I renamed daisyhome to daisyhome_bak > >> 3. I copied daisy-2.4.2 to daisyhome > >> 4. I've uninstalled both services (they weren't visible from > >> the service > >> console list) > >> > >> 5. I've used the install scripts (ie. > %DAISY_HOME%/install) to create > >> the service scripts in both %REPO_DATA%/service and > >> %WIKI_DATA%/service... I used the following commands: > >> > >> daisy-service-install -f -r path_to_repo_data > >> > >> daisy-service-install -f -w path_to_wiki_data > >> > >> Both these folders show updated modified file dates > corresponding to > >> when I created them. > >> > >> 6. I've been able to recreate the Wiki service, using > >> "install-daisy-wiki-service.bat" file from > %WIKI_DATA%/service. I now > >> see it in the service list. > >> > >> However, I've not been able to recreate the Repository > service in the > >> same fashion, using > install-daisy-repository-server-service.bat from > >> %REPO_DATA%/service. If I run it, all I see is "Press a key > >> to continue > >> ...". I've not seen a confirmation message in the console > compared to > >> when I created the wiki service. > >> > >> Would you have an idea why this is occuring? > >> > >> > >> > Date: Wed, 13 Apr 2011 08:58:03 +0200 > >> > From: Paul Focke <paul@...> > >> > Subject: Re: [daisy] RE: daisy Digest, Vol 79, Issue 7 > >> > To: "Daisy: open source CMS - general mailinglist" > >> > <daisy@...> > >> > Message-ID: <BANLkTin+K6NP00vn5o5N3TjU4YchpuedyA@...> > >> > Content-Type: text/plain; charset=ISO-8859-1 > >> > > >> > Dan > >> > > >> > It would make the most sense to invoke the services from > DAISY_HOME. > >> > The initial setup of having a c:\Daisy\daisyhome directory > >> was a good > >> > idea. This is pretty much how we do things on our own setups. The > >> > biggest difference being that we use a unix environment > and we make > >> > use of softlinks to link daisyhome to a daisy version. > If I had done > >> > the upgrade I probably would have overwritten the old > daisyhome with > >> > the files found in daisy-2.4.2 that way you don't have > to go around > >> > changing paths in environment variables and services. > >> > > >> > The setting in the conf file is to set a default for > DAISY_HOME in > >> > case it isn't found as an environment variable. No harm > done if you > >> > change this to reflect the changes in your current setup. > >> > > >> > I would advise reconsidering the current upgrade effort. I > >> believe you > >> > can make future upgrades easier if you first move the old > >> daisyhome to > >> > daisy-2.4 (if this was the version you were starting > from) and then > >> > moving daisy-2.4.2 to daisyhome. If you can try getting > into touch > >> > with the person who started the upgrade. Maybe he/she had a good > >> > reason for choosing the current way of doing things. > >> > > >> > Paul > >> _______________________________________________ > >> daisy community mailing list > >> Professional Daisy support: > >> http://outerthought.org/en/services/daisy/support.html > >> mail to: daisy@... > >> list information: http://lists.cocoondev.org/mailman/listinfo/daisy > >> > > _______________________________________________ > > daisy community mailing list > > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > > mail to: daisy@... > > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > > > > > > -- > Karel Vervaeke > http://outerthought.org/ > Open Source Content Applications > Makers of Kauri, Daisy CMS and Lily > _______________________________________________ > daisy community mailing list > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
RE: RE: Service executableI finally got around to rebooting the server. Before I tried to register the service:
- I went into the install folder and ran the appropriate command to create the repodata service install files daisy-service-install -f -r c:\path_to_repo - I then ran the batch file in repo data to install the service install-daisy-repository-server-service I keep getting "Press any key to continue..." while having no service created. > -----Original Message----- > From: daisy-bounces@... > [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke > Sent: April 15, 2011 5:08 AM > To: Daisy: open source CMS - general mailinglist > Subject: Re: [daisy] RE: Service executable > > The problem could be related to the wrapper version (we recently > upgraded it in Daisy), and the different versions don't seem to like > each other very well. > > Try the following procedure: > * unregister the service (check in services.msc to see that > it's really gone) > * make sure no wrapper.exe or java.exe processes are lingering around > (taskmgr.exe) > * reboot > * try to re-register the service. > > HTH, > Karel > > On Thu, Apr 14, 2011 at 3:21 PM, Fournier, Danny G > <Danny.Fournier@...> wrote: > > I've been echoing content from various locations in the > > install-daisy-repository-server-service.bat file. So far, I > can conclude > > that it goes through without any errors and executes the command to > > start the service. > > > > I've also echoed the command that installs the service: > > C:\Daisy\daisyhome\wrapper\bin\wrapper-windows-x86-32.exe -i > > "C:\Daisy\repodata\service\daisy-repository-server-service.conf" > > > > When I run this command manually, it goes through without > any errors, > > but yet doesn't create the service. > > > > I've compared both service conf files and they are > identicial except for > > the subtleties in creating respective services > > daisy-repository-server-service.conf > > daisy-wiki-service.conf > > > > I've compared both install files and they too are identical > except for > > the subtleties in creating respective services > > install-daisy-repository-server-service.bat > > install-daisy-wiki-service.bat > > > > I even tried removing the wiki service and installing the repository > > service first, but that didn't work out either. > > > > Another thing I've tried is the uncommenting of the Wrapper Windows > > NT/2000/XP Service Properties in the > > daisy-repository-server-service.conf. No go there either. > > > > I don't see any errors in the Event Viewer. > > > > I can install and uninstall at will, the wiki service > though (hope this > > doesn't jinx it! LOL) If I could just get the other one > installed I'd > > probably be set. > > > > > >> -----Original Message----- > >> From: daisy-bounces@... > >> [mailto:daisy-bounces@...] On Behalf Of > >> Fournier, Danny G > >> Sent: April 13, 2011 11:32 AM > >> To: daisy@... > >> Subject: [daisy] RE: Service executable > >> > >> Paul, > >> > >> My goal is now to have everything in daisyhome. Here's what > >> I've done so > >> far: > >> > >> 1. I've set DAISY_HOME to point to daisyhome (instead of > daisy-2.4.2) > >> 2. I renamed daisyhome to daisyhome_bak > >> 3. I copied daisy-2.4.2 to daisyhome > >> 4. I've uninstalled both services (they weren't visible from > >> the service > >> console list) > >> > >> 5. I've used the install scripts (ie. > %DAISY_HOME%/install) to create > >> the service scripts in both %REPO_DATA%/service and > >> %WIKI_DATA%/service... I used the following commands: > >> > >> daisy-service-install -f -r path_to_repo_data > >> > >> daisy-service-install -f -w path_to_wiki_data > >> > >> Both these folders show updated modified file dates > corresponding to > >> when I created them. > >> > >> 6. I've been able to recreate the Wiki service, using > >> "install-daisy-wiki-service.bat" file from > %WIKI_DATA%/service. I now > >> see it in the service list. > >> > >> However, I've not been able to recreate the Repository > service in the > >> same fashion, using > install-daisy-repository-server-service.bat from > >> %REPO_DATA%/service. If I run it, all I see is "Press a key > >> to continue > >> ...". I've not seen a confirmation message in the console > compared to > >> when I created the wiki service. > >> > >> Would you have an idea why this is occuring? > >> > >> > >> > Date: Wed, 13 Apr 2011 08:58:03 +0200 > >> > From: Paul Focke <paul@...> > >> > Subject: Re: [daisy] RE: daisy Digest, Vol 79, Issue 7 > >> > To: "Daisy: open source CMS - general mailinglist" > >> > <daisy@...> > >> > Message-ID: <BANLkTin+K6NP00vn5o5N3TjU4YchpuedyA@...> > >> > Content-Type: text/plain; charset=ISO-8859-1 > >> > > >> > Dan > >> > > >> > It would make the most sense to invoke the services from > DAISY_HOME. > >> > The initial setup of having a c:\Daisy\daisyhome directory > >> was a good > >> > idea. This is pretty much how we do things on our own setups. The > >> > biggest difference being that we use a unix environment > and we make > >> > use of softlinks to link daisyhome to a daisy version. > If I had done > >> > the upgrade I probably would have overwritten the old > daisyhome with > >> > the files found in daisy-2.4.2 that way you don't have > to go around > >> > changing paths in environment variables and services. > >> > > >> > The setting in the conf file is to set a default for > DAISY_HOME in > >> > case it isn't found as an environment variable. No harm > done if you > >> > change this to reflect the changes in your current setup. > >> > > >> > I would advise reconsidering the current upgrade effort. I > >> believe you > >> > can make future upgrades easier if you first move the old > >> daisyhome to > >> > daisy-2.4 (if this was the version you were starting > from) and then > >> > moving daisy-2.4.2 to daisyhome. If you can try getting > into touch > >> > with the person who started the upgrade. Maybe he/she had a good > >> > reason for choosing the current way of doing things. > >> > > >> > Paul > >> _______________________________________________ > >> daisy community mailing list > >> Professional Daisy support: > >> http://outerthought.org/en/services/daisy/support.html > >> mail to: daisy@... > >> list information: http://lists.cocoondev.org/mailman/listinfo/daisy > >> > > _______________________________________________ > > daisy community mailing list > > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > > mail to: daisy@... > > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > > > > > > -- > Karel Vervaeke > http://outerthought.org/ > Open Source Content Applications > Makers of Kauri, Daisy CMS and Lily > _______________________________________________ > daisy community mailing list > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
RE: RE: Service executableI'm now in a position to upgrade our wiki to 2.4.2 from 2.4. The service wrapper (not the conf file) and DAISY_HOME variable are pointing to c:\daisy\daisyhome.
I followed this: http://www.daisycms.org/daisy-kb/637-daisy.html Here are my steps: 1. stop the services 2. rename daisyhome to daisyhome_bak 3. rename daisy-2.4.2 to daisyhome 4. restart the services. Then, I immediately get this (literally 1 sec after having restarted): Could not start the Daisy CMS Repository Server service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion In daisy-repository-server-service.log: ** previous entries dated 2011/05/11 ** INFO | jvm 1 | 2011/05/12 08:04:45 | [Thread-17] INFO org.outerj.daisy.runtime.info - Shutting down component containers. STATUS | wrapper | 2011/05/12 08:04:48 | <-- Wrapper Stopped ** EOF ** Is this created due to the previous shutdown or the current startup that has failed? I've looked at the other log files and no entries dated after 08:04 could be found. In the Event Viewer, I get the following data: Source: Service Control Manager Category: None Type: Error Event ID: 7000 Most of the issues I find (for eventID 7000) is that it deals with services that take longer than 30 seconds. If I swap out the daisyhome directories again, the service will start without any issues. Dan > > >> > Date: Wed, 13 Apr 2011 08:58:03 +0200 > > >> > From: Paul Focke <paul@...> > > >> > Subject: Re: [daisy] RE: daisy Digest, Vol 79, Issue 7 > > >> > To: "Daisy: open source CMS - general mailinglist" > > >> > <daisy@...> > > >> > Message-ID: > <BANLkTin+K6NP00vn5o5N3TjU4YchpuedyA@...> > > >> > Content-Type: text/plain; charset=ISO-8859-1 > > >> > > > >> > Dan > > >> > > > >> > It would make the most sense to invoke the services from > > DAISY_HOME. > > >> > The initial setup of having a c:\Daisy\daisyhome directory > > >> was a good > > >> > idea. This is pretty much how we do things on our own > setups. The > > >> > biggest difference being that we use a unix environment > > and we make > > >> > use of softlinks to link daisyhome to a daisy version. > > If I had done > > >> > the upgrade I probably would have overwritten the old > > daisyhome with > > >> > the files found in daisy-2.4.2 that way you don't have > > to go around > > >> > changing paths in environment variables and services. daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
Re: RE: Service executableDan
It seems that the service wrapper is not even being called. Am I right in assuming that the shutdown message you are seeing is when you shutdown the repository before the move? If I were to guess what is going wrong I'd guess that the services need reinstalling. However, if I recall correctly from previous mails you already did this. Paul On Thu, May 12, 2011 at 2:17 PM, Fournier, Danny G <Danny.Fournier@...> wrote: > I'm now in a position to upgrade our wiki to 2.4.2 from 2.4. The service wrapper (not the conf file) and DAISY_HOME variable are pointing to c:\daisy\daisyhome. > > I followed this: > http://www.daisycms.org/daisy-kb/637-daisy.html > > Here are my steps: > > 1. stop the services > 2. rename daisyhome to daisyhome_bak > 3. rename daisy-2.4.2 to daisyhome > 4. restart the services. > > Then, I immediately get this (literally 1 sec after having restarted): > > Could not start the Daisy CMS Repository Server service on Local Computer. > Error 1053: The service did not respond to the start or control request in a timely fashion > > In daisy-repository-server-service.log: > ** previous entries dated 2011/05/11 ** > INFO | jvm 1 | 2011/05/12 08:04:45 | [Thread-17] INFO org.outerj.daisy.runtime.info - Shutting down component containers. > STATUS | wrapper | 2011/05/12 08:04:48 | <-- Wrapper Stopped > ** EOF ** > > Is this created due to the previous shutdown or the current startup that has failed? > > I've looked at the other log files and no entries dated after 08:04 could be found. > > In the Event Viewer, I get the following data: > > Source: Service Control Manager > Category: None > Type: Error > Event ID: 7000 > > Most of the issues I find (for eventID 7000) is that it deals with services that take longer than 30 seconds. > > If I swap out the daisyhome directories again, the service will start without any issues. > > Dan > >> > >> > Date: Wed, 13 Apr 2011 08:58:03 +0200 >> > >> > From: Paul Focke <paul@...> >> > >> > Subject: Re: [daisy] RE: daisy Digest, Vol 79, Issue 7 >> > >> > To: "Daisy: open source CMS - general mailinglist" >> > >> > <daisy@...> >> > >> > Message-ID: >> <BANLkTin+K6NP00vn5o5N3TjU4YchpuedyA@...> >> > >> > Content-Type: text/plain; charset=ISO-8859-1 >> > >> > >> > >> > Dan >> > >> > >> > >> > It would make the most sense to invoke the services from >> > DAISY_HOME. >> > >> > The initial setup of having a c:\Daisy\daisyhome directory >> > >> was a good >> > >> > idea. This is pretty much how we do things on our own >> setups. The >> > >> > biggest difference being that we use a unix environment >> > and we make >> > >> > use of softlinks to link daisyhome to a daisy version. >> > If I had done >> > >> > the upgrade I probably would have overwritten the old >> > daisyhome with >> > >> > the files found in daisy-2.4.2 that way you don't have >> > to go around >> > >> > changing paths in environment variables and services. > _______________________________________________ > daisy community mailing list > Professional Daisy support: http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
RE: RE: Service executablePaul,
I was hoping you would be able to tell me that :) At first, I thought it might be related to the error/startup of the service. But then it dawned on me that it might be due to when I shutdown the service before upgrading to 2.4.2. Currently 2.4 works fine and the services can be started/shutdown without any issues. As soon as I shuffle the folders (rename daisyhome to daisyhome_bak and daisy-2.4.2 to daisyhome), then it stops working. I'm not an expert in regards to services, but the service points to a specific file in a specific folder. In this case, it's the wrapper, and it stays in the same spot between version changes (ie. daisyhome\wrapper\bin). The filepath passed as a parameter to the service remains untouched as does the conf file that it points to. Unless I'm mistaken, the wrapper IS the service once it's launched right? This should work. Does the wrapper in 2.4 and 2.4.2 require any specific java version for instance, or any other specifics of that nature that I may have not met and that would differ from 2.4? All this work as been done on the dev machine. I wasn't able to restore the services even after a reboot of the OS. After having uninstalled the services (only the wiki service was good) and backed up the Daisy folder, I used the installer to see what it would do. It got me a version of Daisy working, which was great. However, I wasn't able to bring it up to our production copy (considerable modifications IMO). There were subtle things that didn't work the same. IMO, I had followed the directions noting the changes made to the generic Daisy. So, I followed the tutorial I mentionned previously to have a copy of production on dev. That worked out great. I had the exact same functionality, but in version 2.4. Made all those hours spent previously look like a complete waste of time :) Now, I'm trying to apply 2.4.2 on dev so that I can duplicate it in production. Which brings us to now. Thanks for all the help BTW! > -----Original Message----- > From: daisy-bounces@... > [mailto:daisy-bounces@...] On Behalf Of Paul Focke > Sent: May 12, 2011 10:24 AM > To: Daisy: open source CMS - general mailinglist > Subject: Re: [daisy] RE: Service executable > > Dan > > It seems that the service wrapper is not even being called. Am I right > in assuming that the shutdown message you are seeing is when you > shutdown the repository before the move? > If I were to guess what is going wrong I'd guess that the services > need reinstalling. However, if I recall correctly from previous mails > you already did this. > > Paul > > On Thu, May 12, 2011 at 2:17 PM, Fournier, Danny G > <Danny.Fournier@...> wrote: > > I'm now in a position to upgrade our wiki to 2.4.2 from > 2.4. The service wrapper (not the conf file) and DAISY_HOME > variable are pointing to c:\daisy\daisyhome. > > > > I followed this: > > http://www.daisycms.org/daisy-kb/637-daisy.html > > > > Here are my steps: > > > > 1. stop the services > > 2. rename daisyhome to daisyhome_bak > > 3. rename daisy-2.4.2 to daisyhome > > 4. restart the services. > > > > Then, I immediately get this (literally 1 sec after having > restarted): > > > > Could not start the Daisy CMS Repository Server service on > Local Computer. > > Error 1053: The service did not respond to the start or > control request in a timely fashion > > > > In daisy-repository-server-service.log: > > ** previous entries dated 2011/05/11 ** > > INFO | jvm 1 | 2011/05/12 08:04:45 | [Thread-17] INFO > > STATUS | wrapper | 2011/05/12 08:04:48 | <-- Wrapper Stopped > > ** EOF ** > > > > Is this created due to the previous shutdown or the current > startup that has failed? > > > > I've looked at the other log files and no entries dated > after 08:04 could be found. > > > > In the Event Viewer, I get the following data: > > > > Source: Service Control Manager > > Category: None > > Type: Error > > Event ID: 7000 > > > > Most of the issues I find (for eventID 7000) is that it > deals with services that take longer than 30 seconds. > > > > If I swap out the daisyhome directories again, the service > will start without any issues. > > > > Dan > > > >> > >> > Date: Wed, 13 Apr 2011 08:58:03 +0200 > >> > >> > From: Paul Focke <paul@...> > >> > >> > Subject: Re: [daisy] RE: daisy Digest, Vol 79, Issue 7 > >> > >> > To: "Daisy: open source CMS - general mailinglist" > >> > >> > <daisy@...> > >> > >> > Message-ID: > >> <BANLkTin+K6NP00vn5o5N3TjU4YchpuedyA@...> > >> > >> > Content-Type: text/plain; charset=ISO-8859-1 > >> > >> > > >> > >> > Dan > >> > >> > > >> > >> > It would make the most sense to invoke the services from > >> > DAISY_HOME. > >> > >> > The initial setup of having a c:\Daisy\daisyhome directory > >> > >> was a good > >> > >> > idea. This is pretty much how we do things on our own > >> setups. The > >> > >> > biggest difference being that we use a unix environment > >> > and we make > >> > >> > use of softlinks to link daisyhome to a daisy version. > >> > If I had done > >> > >> > the upgrade I probably would have overwritten the old > >> > daisyhome with > >> > >> > the files found in daisy-2.4.2 that way you don't have > >> > to go around > >> > >> > changing paths in environment variables and services. > > _______________________________________________ > > daisy community mailing list > > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > > mail to: daisy@... > > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > > > _______________________________________________ > daisy community mailing list > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
RE: RE: Service executableA small, but interesting update...
First, a recap. Here's the typical process that I'm using when upgrading to 2.4.2: - stop the daisy services - rename daisyhome to daisyhome_bak - rename daisy-2.4.2 to daisyhome - restart the daisy services That doesn't work, as the repository service throws an error the second I start it. After having reverted the folders, the service will start properly. I've also done the following: - stop the daisy services - manually uninstall the daisy services using repodata\service\uninstall-repository-server-service (do the same for the wiki service) - rename daisyhome to daisyhome_bak - rename daisy-2.4.2 to daisyhome - rename repodata\service (do the same for the wiki) - go into daisyhome\install and execute daisy-service-install -r c:\daisy\repodata (do the same for the wiki service) - go into repodata\service and execute install-daisy-repository-server-service.bat (do the same for the wiki service) This is where it gets interesting. Everytime I use 2.4.2 in regards to the repository server service, nothing works: - I cannot install the service using the generated files in repodata\service. - I cannot restart the service after having kept the service and swapped the daisyhome folders - I have no issues installing or running the wiki service in either situations for 2.4.2 - I have tried on dev and test boxes and get the same results If I swap back to version 2.4, generate the service scripts (or swap the folders) and install the service, it works! > -----Original Message----- > From: daisy-bounces@... > [mailto:daisy-bounces@...] On Behalf Of > Fournier, Danny G > Sent: May 12, 2011 11:41 AM > To: Daisy: open source CMS - general mailinglist > Subject: RE: [daisy] RE: Service executable > > Paul, > > I was hoping you would be able to tell me that :) At first, I > thought it might be related to the error/startup of the > service. But then it dawned on me that it might be due to > when I shutdown the service before upgrading to 2.4.2. > > Currently 2.4 works fine and the services can be > started/shutdown without any issues. As soon as I shuffle the > folders (rename daisyhome to daisyhome_bak and daisy-2.4.2 to > daisyhome), then it stops working. > > I'm not an expert in regards to services, but the service > points to a specific file in a specific folder. In this case, > it's the wrapper, and it stays in the same spot between > version changes (ie. daisyhome\wrapper\bin). The filepath > passed as a parameter to the service remains untouched as > does the conf file that it points to. Unless I'm mistaken, > the wrapper IS the service once it's launched right? This should work. > > Does the wrapper in 2.4 and 2.4.2 require any specific java > version for instance, or any other specifics of that nature > that I may have not met and that would differ from 2.4? > > All this work as been done on the dev machine. I wasn't able > to restore the services even after a reboot of the OS. After > having uninstalled the services (only the wiki service was > good) and backed up the Daisy folder, I used the installer to > see what it would do. It got me a version of Daisy working, > which was great. However, I wasn't able to bring it up to our > production copy (considerable modifications IMO). There were > subtle things that didn't work the same. IMO, I had followed > the directions noting the changes made to the generic Daisy. > > So, I followed the tutorial I mentionned previously to have a > copy of production on dev. That worked out great. I had the > exact same functionality, but in version 2.4. Made all those > hours spent previously look like a complete waste of time :) > > Now, I'm trying to apply 2.4.2 on dev so that I can duplicate > it in production. Which brings us to now. > > Thanks for all the help BTW! > > > -----Original Message----- > > From: daisy-bounces@... > > [mailto:daisy-bounces@...] On Behalf Of Paul Focke > > Sent: May 12, 2011 10:24 AM > > To: Daisy: open source CMS - general mailinglist > > Subject: Re: [daisy] RE: Service executable > > > > Dan > > > > It seems that the service wrapper is not even being called. > Am I right > > in assuming that the shutdown message you are seeing is when you > > shutdown the repository before the move? > > If I were to guess what is going wrong I'd guess that the services > > need reinstalling. However, if I recall correctly from > previous mails > > you already did this. > > > > Paul > > > > On Thu, May 12, 2011 at 2:17 PM, Fournier, Danny G > > <Danny.Fournier@...> wrote: > > > I'm now in a position to upgrade our wiki to 2.4.2 from > > 2.4. The service wrapper (not the conf file) and DAISY_HOME > > variable are pointing to c:\daisy\daisyhome. > > > > > > I followed this: > > > http://www.daisycms.org/daisy-kb/637-daisy.html > > > > > > Here are my steps: > > > > > > 1. stop the services > > > 2. rename daisyhome to daisyhome_bak > > > 3. rename daisy-2.4.2 to daisyhome > > > 4. restart the services. > > > > > > Then, I immediately get this (literally 1 sec after having > > restarted): > > > > > > Could not start the Daisy CMS Repository Server service on > > Local Computer. > > > Error 1053: The service did not respond to the start or > > control request in a timely fashion > > > > > > In daisy-repository-server-service.log: > > > ** previous entries dated 2011/05/11 ** > > > INFO | jvm 1 | 2011/05/12 08:04:45 | [Thread-17] INFO > org.outerj.daisy.runtime.info - Shutting down component > containers. > > > STATUS | wrapper | 2011/05/12 08:04:48 | <-- Wrapper Stopped > > > ** EOF ** > > > > > > Is this created due to the previous shutdown or the current > > startup that has failed? > > > > > > I've looked at the other log files and no entries dated > > after 08:04 could be found. > > > > > > In the Event Viewer, I get the following data: > > > > > > Source: Service Control Manager > > > Category: None > > > Type: Error > > > Event ID: 7000 > > > > > > Most of the issues I find (for eventID 7000) is that it > > deals with services that take longer than 30 seconds. > > > > > > If I swap out the daisyhome directories again, the service > > will start without any issues. > > > > > > Dan > > > > > >> > >> > Date: Wed, 13 Apr 2011 08:58:03 +0200 > > >> > >> > From: Paul Focke <paul@...> > > >> > >> > Subject: Re: [daisy] RE: daisy Digest, Vol 79, Issue 7 > > >> > >> > To: "Daisy: open source CMS - general mailinglist" > > >> > >> > <daisy@...> > > >> > >> > Message-ID: > > >> <BANLkTin+K6NP00vn5o5N3TjU4YchpuedyA@...> > > >> > >> > Content-Type: text/plain; charset=ISO-8859-1 > > >> > >> > > > >> > >> > Dan > > >> > >> > > > >> > >> > It would make the most sense to invoke the services from > > >> > DAISY_HOME. > > >> > >> > The initial setup of having a c:\Daisy\daisyhome directory > > >> > >> was a good > > >> > >> > idea. This is pretty much how we do things on our own > > >> setups. The > > >> > >> > biggest difference being that we use a unix environment > > >> > and we make > > >> > >> > use of softlinks to link daisyhome to a daisy version. > > >> > If I had done > > >> > >> > the upgrade I probably would have overwritten the old > > >> > daisyhome with > > >> > >> > the files found in daisy-2.4.2 that way you don't have > > >> > to go around > > >> > >> > changing paths in environment variables and services. > > > _______________________________________________ > > > daisy community mailing list > > > Professional Daisy support: > > http://outerthought.org/en/services/daisy/support.html > > > mail to: daisy@... > > > list information: > http://lists.cocoondev.org/mailman/listinfo/daisy > > > > > _______________________________________________ > > daisy community mailing list > > Professional Daisy support: > > http://outerthought.org/en/services/daisy/support.html > > mail to: daisy@... > > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > > > _______________________________________________ > daisy community mailing list > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
Re: RE: Service executableJust to make sure:
-cut- > This is where it gets interesting. Everytime I use 2.4.2 in regards to the repository server service, nothing works: > - I cannot install the service using the generated files in repodata\service. > - I cannot restart the service after having kept the service and swapped the daisyhome folders > - I have no issues installing or running the wiki service in either situations for 2.4.2 Did you mean the repository service here? (If not: can you manually run the repository service with 2.4.2? (Other than that, I'm fresh out of ideas. Perhaps adding 'wrapper.debug=true' in the service conf file will result in some more useful output from the wrapper?) > - I have tried on dev and test boxes and get the same results -cut- -- Karel Vervaeke http://outerthought.org/ Open Source Content Applications Makers of Kauri, Daisy CMS and Lily _______________________________________________ daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
RE: RE: Service executableKarel,
Yes, I did mean the repository service. I added the wrapper.debug=true in the service conf file. When I start/shut down the service, it writes to the log file. However, when I stopped the service, switched the folders from 2.4 to 2.4.2 and started; nothing was written to the log file. It doesn't even run the wrapper it seems. Bizarre Dan > -----Original Message----- > From: daisy-bounces@... > [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke > Sent: May 16, 2011 9:03 AM > To: Daisy: open source CMS - general mailinglist > Subject: Re: [daisy] RE: Service executable > > Just to make sure: > -cut- > > This is where it gets interesting. Everytime I use 2.4.2 in > regards to the repository server service, nothing works: > > - I cannot install the service using the generated files in > repodata\service. > > - I cannot restart the service after having kept the > service and swapped the daisyhome folders > > - I have no issues installing or running the wiki service > in either situations for 2.4.2 > > Did you mean the repository service here? (If not: can you manually > run the repository service with 2.4.2? > (Other than that, I'm fresh out of ideas. Perhaps adding > 'wrapper.debug=true' in the service conf file will result in some more > useful output from the wrapper?) > > > - I have tried on dev and test boxes and get the same results > -cut- > -- > Karel Vervaeke > http://outerthought.org/ > Open Source Content Applications > Makers of Kauri, Daisy CMS and Lily > _______________________________________________ > daisy community mailing list > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
Re: RE: Service executableCan you try using the previous version of the tanuki wrappers on
2.4.2? (Daisy 2.4.2 uses tanuki wrappers 3.5.7) To do this, you should download from http://wrapper.tanukisoftware.com/download/3.5.6/wrapper-delta-pack-3.5.6.zip, unzip, and copy the contents of the bin and lib folders into the respective folders under $DAISY_HOME/wrapper (Again, make sure you completely remove and install the service) Regards, Karel On Tue, May 17, 2011 at 5:51 PM, Fournier, Danny G <Danny.Fournier@...> wrote: > Karel, > > Yes, I did mean the repository service. > > I added the wrapper.debug=true in the service conf file. When I > start/shut down the service, it writes to the log file. However, when I > stopped the service, switched the folders from 2.4 to 2.4.2 and started; > nothing was written to the log file. It doesn't even run the wrapper it > seems. > > Bizarre > > Dan > >> -----Original Message----- >> From: daisy-bounces@... >> [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke >> Sent: May 16, 2011 9:03 AM >> To: Daisy: open source CMS - general mailinglist >> Subject: Re: [daisy] RE: Service executable >> >> Just to make sure: >> -cut- >> > This is where it gets interesting. Everytime I use 2.4.2 in >> regards to the repository server service, nothing works: >> > - I cannot install the service using the generated files in >> repodata\service. >> > - I cannot restart the service after having kept the >> service and swapped the daisyhome folders >> > - I have no issues installing or running the wiki service >> in either situations for 2.4.2 >> >> Did you mean the repository service here? (If not: can you manually >> run the repository service with 2.4.2? >> (Other than that, I'm fresh out of ideas. Perhaps adding >> 'wrapper.debug=true' in the service conf file will result in some more >> useful output from the wrapper?) >> >> > - I have tried on dev and test boxes and get the same results >> -cut- >> -- >> Karel Vervaeke >> http://outerthought.org/ >> Open Source Content Applications >> Makers of Kauri, Daisy CMS and Lily >> _______________________________________________ >> daisy community mailing list >> Professional Daisy support: >> http://outerthought.org/en/services/daisy/support.html >> mail to: daisy@... >> list information: http://lists.cocoondev.org/mailman/listinfo/daisy >> > _______________________________________________ > daisy community mailing list > Professional Daisy support: http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > -- Karel Vervaeke http://outerthought.org/ Open Source Content Applications Makers of Kauri, Daisy CMS and Lily _______________________________________________ daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
RE: RE: Service executableIt works! I had no issues installing and running both services using
this little trick. Still, what's the best way to confirm that I'm running 2.4.2? And what does this mean, having to use an older version? > -----Original Message----- > From: daisy-bounces@... > [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke > Sent: May 20, 2011 5:15 AM > To: Daisy: open source CMS - general mailinglist > Subject: Re: [daisy] RE: Service executable > > Can you try using the previous version of the tanuki wrappers on > 2.4.2? (Daisy 2.4.2 uses tanuki wrappers 3.5.7) > > To do this, you should download from > http://wrapper.tanukisoftware.com/download/3.5.6/wrapper-delta > unzip, and copy the contents of the bin and lib folders into the > respective folders under $DAISY_HOME/wrapper > > (Again, make sure you completely remove and install the service) > > Regards, > Karel > > On Tue, May 17, 2011 at 5:51 PM, Fournier, Danny G > <Danny.Fournier@...> wrote: > > Karel, > > > > Yes, I did mean the repository service. > > > > I added the wrapper.debug=true in the service conf file. When I > > start/shut down the service, it writes to the log file. > However, when I > > stopped the service, switched the folders from 2.4 to 2.4.2 > and started; > > nothing was written to the log file. It doesn't even run > the wrapper it > > seems. > > > > Bizarre > > > > Dan > > > >> -----Original Message----- > >> From: daisy-bounces@... > >> [mailto:daisy-bounces@...] On Behalf Of > Karel Vervaeke > >> Sent: May 16, 2011 9:03 AM > >> To: Daisy: open source CMS - general mailinglist > >> Subject: Re: [daisy] RE: Service executable > >> > >> Just to make sure: > >> -cut- > >> > This is where it gets interesting. Everytime I use 2.4.2 in > >> regards to the repository server service, nothing works: > >> > - I cannot install the service using the generated files in > >> repodata\service. > >> > - I cannot restart the service after having kept the > >> service and swapped the daisyhome folders > >> > - I have no issues installing or running the wiki service > >> in either situations for 2.4.2 > >> > >> Did you mean the repository service here? (If not: can you manually > >> run the repository service with 2.4.2? > >> (Other than that, I'm fresh out of ideas. Perhaps adding > >> 'wrapper.debug=true' in the service conf file will result > in some more > >> useful output from the wrapper?) > >> > >> > - I have tried on dev and test boxes and get the same results > >> -cut- > >> -- > >> Karel Vervaeke > >> http://outerthought.org/ > >> Open Source Content Applications > >> Makers of Kauri, Daisy CMS and Lily > >> _______________________________________________ > >> daisy community mailing list > >> Professional Daisy support: > >> http://outerthought.org/en/services/daisy/support.html > >> mail to: daisy@... > >> list information: http://lists.cocoondev.org/mailman/listinfo/daisy > >> > > _______________________________________________ > > daisy community mailing list > > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > > mail to: daisy@... > > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > > > > > > -- > Karel Vervaeke > http://outerthought.org/ > Open Source Content Applications > Makers of Kauri, Daisy CMS and Lily > _______________________________________________ > daisy community mailing list > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
Re: RE: Service executableYou can check the response headers (both on the wiki and on the repository).
There should be a header named "X-Daisy-Version". For the repository, point your browser to http://localhost:9263/repository/userinfo, enter your credentials and check the headers (Or via the command line: wget -S --http-user={user} --http-passwd={passwd} http://..../repository/userinfo) You don't need to worry about running a different version of the wrapper scripts. You're the second person that I know of running into problems with that version of the wrapper scripts, so I filed a ticket: http://dev.outerthought.org/trac/outerthought_daisy/ticket/855 Karel On Tue, May 24, 2011 at 3:00 PM, Fournier, Danny G <Danny.Fournier@...> wrote: > It works! I had no issues installing and running both services using > this little trick. > > Still, what's the best way to confirm that I'm running 2.4.2? > > And what does this mean, having to use an older version? > >> -----Original Message----- >> From: daisy-bounces@... >> [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke >> Sent: May 20, 2011 5:15 AM >> To: Daisy: open source CMS - general mailinglist >> Subject: Re: [daisy] RE: Service executable >> >> Can you try using the previous version of the tanuki wrappers on >> 2.4.2? (Daisy 2.4.2 uses tanuki wrappers 3.5.7) >> >> To do this, you should download from >> http://wrapper.tanukisoftware.com/download/3.5.6/wrapper-delta > -pack-3.5.6.zip, >> unzip, and copy the contents of the bin and lib folders into the >> respective folders under $DAISY_HOME/wrapper >> >> (Again, make sure you completely remove and install the service) >> >> Regards, >> Karel >> >> On Tue, May 17, 2011 at 5:51 PM, Fournier, Danny G >> <Danny.Fournier@...> wrote: >> > Karel, >> > >> > Yes, I did mean the repository service. >> > >> > I added the wrapper.debug=true in the service conf file. When I >> > start/shut down the service, it writes to the log file. >> However, when I >> > stopped the service, switched the folders from 2.4 to 2.4.2 >> and started; >> > nothing was written to the log file. It doesn't even run >> the wrapper it >> > seems. >> > >> > Bizarre >> > >> > Dan >> > >> >> -----Original Message----- >> >> From: daisy-bounces@... >> >> [mailto:daisy-bounces@...] On Behalf Of >> Karel Vervaeke >> >> Sent: May 16, 2011 9:03 AM >> >> To: Daisy: open source CMS - general mailinglist >> >> Subject: Re: [daisy] RE: Service executable >> >> >> >> Just to make sure: >> >> -cut- >> >> > This is where it gets interesting. Everytime I use 2.4.2 in >> >> regards to the repository server service, nothing works: >> >> > - I cannot install the service using the generated files in >> >> repodata\service. >> >> > - I cannot restart the service after having kept the >> >> service and swapped the daisyhome folders >> >> > - I have no issues installing or running the wiki service >> >> in either situations for 2.4.2 >> >> >> >> Did you mean the repository service here? (If not: can you manually >> >> run the repository service with 2.4.2? >> >> (Other than that, I'm fresh out of ideas. Perhaps adding >> >> 'wrapper.debug=true' in the service conf file will result >> in some more >> >> useful output from the wrapper?) >> >> >> >> > - I have tried on dev and test boxes and get the same results >> >> -cut- >> >> -- >> >> Karel Vervaeke >> >> http://outerthought.org/ >> >> Open Source Content Applications >> >> Makers of Kauri, Daisy CMS and Lily >> >> _______________________________________________ >> >> daisy community mailing list >> >> Professional Daisy support: >> >> http://outerthought.org/en/services/daisy/support.html >> >> mail to: daisy@... >> >> list information: http://lists.cocoondev.org/mailman/listinfo/daisy >> >> >> > _______________________________________________ >> > daisy community mailing list >> > Professional Daisy support: >> http://outerthought.org/en/services/daisy/support.html >> > mail to: daisy@... >> > list information: http://lists.cocoondev.org/mailman/listinfo/daisy >> > >> >> >> >> -- >> Karel Vervaeke >> http://outerthought.org/ >> Open Source Content Applications >> Makers of Kauri, Daisy CMS and Lily >> _______________________________________________ >> daisy community mailing list >> Professional Daisy support: >> http://outerthought.org/en/services/daisy/support.html >> mail to: daisy@... >> list information: http://lists.cocoondev.org/mailman/listinfo/daisy >> > _______________________________________________ > daisy community mailing list > Professional Daisy support: http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > -- Karel Vervaeke http://outerthought.org/ Open Source Content Applications Makers of Kauri, Daisy CMS and Lily _______________________________________________ daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
RE: RE: Service executableWell, the header indicates 2.4.2 so it seems that I'm in business!
> -----Original Message----- > From: daisy-bounces@... > [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke > Sent: May 24, 2011 10:36 AM > To: Daisy: open source CMS - general mailinglist > Subject: Re: [daisy] RE: Service executable > > You can check the response headers (both on the wiki and on > the repository). > There should be a header named "X-Daisy-Version". > > For the repository, point your browser to > http://localhost:9263/repository/userinfo, > enter your credentials and check the headers > (Or via the command line: wget -S --http-user={user} > --http-passwd={passwd} http://..../repository/userinfo) > > You don't need to worry about running a different version of the > wrapper scripts. > You're the second person that I know of running into problems with > that version of the wrapper scripts, so I filed a ticket: > http://dev.outerthought.org/trac/outerthought_daisy/ticket/855 > > > Karel > > On Tue, May 24, 2011 at 3:00 PM, Fournier, Danny G > <Danny.Fournier@...> wrote: > > It works! I had no issues installing and running both services using > > this little trick. > > > > Still, what's the best way to confirm that I'm running 2.4.2? > > > > And what does this mean, having to use an older version? > > > >> -----Original Message----- > >> From: daisy-bounces@... > >> [mailto:daisy-bounces@...] On Behalf Of > Karel Vervaeke > >> Sent: May 20, 2011 5:15 AM > >> To: Daisy: open source CMS - general mailinglist > >> Subject: Re: [daisy] RE: Service executable > >> > >> Can you try using the previous version of the tanuki wrappers on > >> 2.4.2? (Daisy 2.4.2 uses tanuki wrappers 3.5.7) > >> > >> To do this, you should download from > >> http://wrapper.tanukisoftware.com/download/3.5.6/wrapper-delta > > -pack-3.5.6.zip, > >> unzip, and copy the contents of the bin and lib folders into the > >> respective folders under $DAISY_HOME/wrapper > >> > >> (Again, make sure you completely remove and install the service) > >> > >> Regards, > >> Karel > >> > >> On Tue, May 17, 2011 at 5:51 PM, Fournier, Danny G > >> <Danny.Fournier@...> wrote: > >> > Karel, > >> > > >> > Yes, I did mean the repository service. > >> > > >> > I added the wrapper.debug=true in the service conf file. When I > >> > start/shut down the service, it writes to the log file. > >> However, when I > >> > stopped the service, switched the folders from 2.4 to 2.4.2 > >> and started; > >> > nothing was written to the log file. It doesn't even run > >> the wrapper it > >> > seems. > >> > > >> > Bizarre > >> > > >> > Dan > >> > > >> >> -----Original Message----- > >> >> From: daisy-bounces@... > >> >> [mailto:daisy-bounces@...] On Behalf Of > >> Karel Vervaeke > >> >> Sent: May 16, 2011 9:03 AM > >> >> To: Daisy: open source CMS - general mailinglist > >> >> Subject: Re: [daisy] RE: Service executable > >> >> > >> >> Just to make sure: > >> >> -cut- > >> >> > This is where it gets interesting. Everytime I use 2.4.2 in > >> >> regards to the repository server service, nothing works: > >> >> > - I cannot install the service using the generated files in > >> >> repodata\service. > >> >> > - I cannot restart the service after having kept the > >> >> service and swapped the daisyhome folders > >> >> > - I have no issues installing or running the wiki service > >> >> in either situations for 2.4.2 > >> >> > >> >> Did you mean the repository service here? (If not: can > you manually > >> >> run the repository service with 2.4.2? > >> >> (Other than that, I'm fresh out of ideas. Perhaps adding > >> >> 'wrapper.debug=true' in the service conf file will result > >> in some more > >> >> useful output from the wrapper?) > >> >> > >> >> > - I have tried on dev and test boxes and get the same results > >> >> -cut- > >> >> -- > >> >> Karel Vervaeke > >> >> http://outerthought.org/ > >> >> Open Source Content Applications > >> >> Makers of Kauri, Daisy CMS and Lily > >> >> _______________________________________________ > >> >> daisy community mailing list > >> >> Professional Daisy support: > >> >> http://outerthought.org/en/services/daisy/support.html > >> >> mail to: daisy@... > >> >> list information: > http://lists.cocoondev.org/mailman/listinfo/daisy > >> >> > >> > _______________________________________________ > >> > daisy community mailing list > >> > Professional Daisy support: > >> http://outerthought.org/en/services/daisy/support.html > >> > mail to: daisy@... > >> > list information: > http://lists.cocoondev.org/mailman/listinfo/daisy > >> > > >> > >> > >> > >> -- > >> Karel Vervaeke > >> http://outerthought.org/ > >> Open Source Content Applications > >> Makers of Kauri, Daisy CMS and Lily > >> _______________________________________________ > >> daisy community mailing list > >> Professional Daisy support: > >> http://outerthought.org/en/services/daisy/support.html > >> mail to: daisy@... > >> list information: http://lists.cocoondev.org/mailman/listinfo/daisy > >> > > _______________________________________________ > > daisy community mailing list > > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > > mail to: daisy@... > > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > > > > > > -- > Karel Vervaeke > http://outerthought.org/ > Open Source Content Applications > Makers of Kauri, Daisy CMS and Lily > _______________________________________________ > daisy community mailing list > Professional Daisy support: > http://outerthought.org/en/services/daisy/support.html > mail to: daisy@... > list information: http://lists.cocoondev.org/mailman/listinfo/daisy > daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
Re: RE: Service executableJust to add a comment, - I had problems with installing the 2.4.2 repository server as a service in windows (the wiki was ok, no problems). Message: "The service name is invalid".
Could not find any logical explanation on why not, tried to replace the wrapper as Karel suggested here, and the repository server was installed as a service with no problems. Is there a problem with the wrapper version used on 2.4.2? Regards EndreF 2011/5/20 Karel Vervaeke <karel@...> Can you try using the previous version of the tanuki wrappers on _______________________________________________ daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
|
|
Re: RE: Service executableOn the day six months after I experienced this first time, I ran into the same problem. Found my own message searching the mails for a similar issue. Well, I'm known to remember from breakfast to lunch, - but anyhow this was six months :-)
EndreF
2011/5/30 Endre Furnes <endre.furnes@...> Just to add a comment, - I had problems with installing the 2.4.2 repository server as a service in windows (the wiki was ok, no problems). Message: "The service name is invalid". _______________________________________________ daisy community mailing list Professional Daisy support: http://outerthought.org/en/services/daisy/support.html mail to: daisy@... list information: http://lists.cocoondev.org/mailman/listinfo/daisy |
| Free embeddable forum powered by Nabble | Forum Help |