The comment in the config file is wrong. Add a line: products $INSTANCE\Products to your config file and restart, all should be ok. On Fri, 2003-08-15 at 10:43, andre wrote:

:) Thanks. I read it before asking my question but as there's nothing about differencies between 2.7 and 2.6 in products installation and as the only instruction in instance's products directory is : "" Additional products for your Zope instance should be installed in this directory. A freshly created instance should only contain this README.txt file in this directory. "", i supposed that i only had to copy my package in the Products' directory of my instance am i right ?

But when i restart the server and my instance, nothing happens, the product doesn't appears in the products' list in control panel.

Well, i searched in cvs.zope.org to see if there was something, i only found files edited 12 months ago.

I am using Zope2.7.0.b1 on windows XP.

I found nothing in the faq, in the collector, in this mailing list, in the txt files. I didn't get errors and i didn't find a log file. My package is simply ignored by Zope2.7.0b1.

I think it can't be a bug but it must be something so obvious that i can't see it. :). I can't restart the server using the restart button in control panel. I need to restart in windows service manager.

Noticed that i have a Zope 2.6 server on the same machine on port 8080 (2.7 on 8081) but that doesn't affect my Zope 2.6 and basic products of Zope 2.7 are running well.

So do you know something.txt that i can read :). Thanks Andre

Andreas Jung a écrit:

...

Read doc/CHANGES.txt...that's why it is called as it is.

-aj

--On Freitag, 15. August 2003 0:45 Uhr -0400 andre <borelan@wanadoo.fr> wrote:

...

I have a product developed for Zope 2.6 and want to use it in an instance of Zope 2.7. Is there something different than in previous versions of Zope ? Thanks Andre

_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )

_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )

_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )

If you're running this as a service, the Zope Windows service stuff has fairly poor failure reporting support. It sounds like something is blowing up in your local Products directory. Try running Zope manually via the "bin\runzope.bat" batch file with the "product $INSTANCE\Products" directive in your config file and look at the console output. It should tell you what is going wrong. ----- Original Message ----- From: "andre" <borelan@wanadoo.fr> To: "Chris McDonouogh" <chrism@zopemafia.com> Cc: "Andreas Jung" <andreas@andreas-jung.com>; <zope@zope.org> Sent: Saturday, August 16, 2003 10:15 AM Subject: Re: [Zope] How to install a new product in Zope 2.7

Thanks but i tried that too. When i change something to the zope-conf, the server doesn't start. i just uncommented the products directive, then i used \ instead of / same result. "Connection refused to http://localhost:8081" Same thing happens if i change datetime format, locale, etc. if i comment out "products $INSTANCE\Products" i can access http://localhost:8081/manage

looking at the event.log, the server didn't start. after uncommenting the line : http server started, ftp server started, Zope ready. no errors in z2.log, no messages.

i think that there are no interaction with my instance of Zope 2.6 as i stopped Z2.6 before trying Z2.7 even with candies it doesn't work. big whim! Mystery ? Magic ?

Thanks

Andre

Chris McDonouogh a écrit:

...

The comment in the config file is wrong. Add a line:

products $INSTANCE\Products

to your config file and restart, all should be ok.

On Fri, 2003-08-15 at 10:43, andre wrote:

...

:) Thanks. I read it before asking my question but as there's nothing about differencies between 2.7 and 2.6 in products installation and as the only instruction in instance's products directory is : "" Additional products for your Zope instance should be installed in this directory. A freshly created instance should only contain this README.txt file in this directory. "", i supposed that i only had to copy my package in the Products' directory of my instance am i right ?

But when i restart the server and my instance, nothing happens, the product doesn't appears in the products' list in control panel.

Well, i searched in cvs.zope.org to see if there was something, i only found files edited 12 months ago.

I am using Zope2.7.0.b1 on windows XP.

I found nothing in the faq, in the collector, in this mailing list, in the txt files. I didn't get errors and i didn't find a log file. My package is simply ignored by Zope2.7.0b1.

I think it can't be a bug but it must be something so obvious that i can't see it. :). I can't restart the server using the restart button in control panel. I need to restart in windows service manager.

Noticed that i have a Zope 2.6 server on the same machine on port 8080 (2.7 on 8081) but that doesn't affect my Zope 2.6 and basic products of Zope 2.7 are running well.

So do you know something.txt that i can read :). Thanks Andre

Andreas Jung a écrit:

...

Read doc/CHANGES.txt...that's why it is called as it is.

-aj

--On Freitag, 15. August 2003 0:45 Uhr -0400 andre <borelan@wanadoo.fr> wrote:

...

I have a product developed for Zope 2.6 and want to use it in an instance of Zope 2.7. Is there something different than in previous versions of Zope ? Thanks Andre

_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )

_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )

_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )

The product is failing to initialize and Zope refuses to start as a result. Nothing is written to the log due to the decision to defer logging to a file until after we've been able to do some houskeeping (which, ironically, is vital under UNIX but totally unnecessary under Windows). In any case. we just need to see the error messages to understand what's happening. What's happening is that Python isn't printing the messages to the console because it's using "pythonw.exe" which (I think) suppresses standard error output instead of "python.exe". Change the line in runzope.bat that says @set PYTHON=c:\some\path\pythonw.exe to @set PYTHON=c:\some\path\python.exe Then start up a DOS box and run runzope.bat again from the DOS box (dont try to run it by clicking the "start zope in a console" link in the start menu). You should see some error messages print to the console. If you don't we'll go back to the drawing board. FWIW, the lack of adequate error reporting under this circumstance is a real issue and needs to be fixed. For now, let's just try to find - C On Sat, 2003-08-16 at 11:11, andre wrote:

Chris McDonough a écrit:

...

Try running Zope manually via the "bin\runzope.bat" batch file with the "product $INSTANCE\Products" directive in your config file and look at the console output. It should tell you what is going wrong.

No messages on console output except : "c:\Zope-Instance\bin .... -C ..zope.conf etc... then the windows is closed, the server doesn't start (even with the products directive commented out). No messages, no errors in logs. If i suppress the product from Zope-Instance\Products, the server starts normally even if i modify the zope.conf. When i add a product in the directory, i can't restart the server. I deleted the directory, re-created it, same result.

I tried to add the product in Zope-Home Products' directory, same result. It seems that Zope2.7 doesn't want a new product.

Stuck?

Andre

_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )

There was a reference to another product(not installed) in my product. Using the method you suggested, i immediately found the error.

Great.

I have now three zope running (2.6, 2.7, 3) the 2.x versions as services and z3 in a console window.

I saw an interface package in Zope 2.7 does that mean that this version is a path between Z2 and Z3 ?

Zope 2.6 has an interface package too.

If true, how to follow this path ?

There is no predetermined path. Zope 2 products are not compatible with Zope 3 products at this time. In the future there may be automated tools to translate them. For now, you need to rewrite your products to use them under Zope 3. - C

...

The product is failing to initialize and Zope refuses to start as a result. Nothing is written to the log due to the decision to defer logging to a file until after we've been able to do some houskeeping (which, ironically, is vital under UNIX but totally unnecessary under Windows).

Should we rethink about this decision?

The log file has been the main source to analyse startup problems. How should they be analysed for Zope 2.7?

Well, I don't think so. Here's why. A failing startup can be debugged via looking at console output. This is simple on UNIX, and would have been simple under Windows had I corrrectly used "python.exe" instead of "pythonw.exe" in the runzope.bat batch file. When someone asks why Zope doesn't start under UNIX and there are no messages in the event log file, the stock answer will be "run it using the 'runzope' shell script in a console window". When someone asks why Zope doesn't start under Windows, the stock answer will be "run it using the 'runzope.bat' batch file in a console window." I think that's acceptable. FWIW (and you probably know this already, but others might not), the reason for holding off on logging startup messages to a log file is to allow the application time to setuid before writing any log files, so that if Zope is initially started as root, subsequent startups under a nonroot user account won't fail due to an inability to write to the logfile (which would be owned and writable only by root). This is (or at least used to be) a frequent source of complaints on the list for all previous Zope versions. All that said, I think (over time) we might be able to do less before we have the opportunity setuid so that these kinds of messages would indeed be written to the logfile. - C

This can easily modify the context (environment, etc.) under which the process is born, bugs which are context dependant may vanish or change in nature because of this. I suppose only time will tell how much pain will be rooted in this choice of direction.

I suppose. But on UNIX the other primary way to run Zope (zopectl) runs runzope behind the scenes, so the difference between running the two will be fairly small. On Windows, you're right, but because of Windows' process model we can't call a batch file from the service controller. But under Windows we're going to change it to write to the logfile sooner anyway.

The benefits of being able to bind to a privileged port are imaginary. The setuid code should be removed entirely.

Yeah, well. - C