Andy, Hmmm, I changed it back to not using port 80. If you go to http://zopetest.hr.ucdavis.edu/STAGING you get "Zope staging synchronizer" which is the comment for my Zsync defined as: ZSyncer at /STAGING Edit ZSyncer Title: Zope staging synchronizer So I'm looking right at it. Still getting (from Zopedevel): "There was a problem with that comparison. Error: ProtocolError <ProtocolError for zopetest.hr.ucdavis.edu/STAGING: 500 Internal Server Error> Things to check: Your destination ZSyncer is where it is meant to be. The destination server is running and accessible. The user "zopeadmin" has the right to access ZSyncer. The password for "zopeadmin" is correct. I know the accounts in question have access rights, as I just logged on using them. So, your comment means that when I try to sync Zopedevel --> Zopetest, which end is failing? Thanks for your help, --Adam -----Original Message----- From: Andy McKay [mailto:andy@agmweb.ca] Sent: Monday, October 21, 2002 9:18 PM To: Adam Getchell; zope@zope.org Subject: Re: [Zope] Zsync errors

* ProtocolError * <ProtocolError for zopetest.hr.ucdavis.edu:80/STAGING: 500 Internal Server Error>

Are you sure you have the right url? When ZSyncer is doing the request the destination server is encountering a 500 Error on the server, not ZSyncer. -- Andy McKay www.agmweb.ca ----- Original Message ----- From: "Adam Getchell" <AdamG@hrrm.ucdavis.edu> To: <zope@zope.org> Sent: Monday, October 21, 2002 8:29 PM Subject: [Zope] Zsync errors

Hello all,

I moved Zope from an old box to a new one. I installed Zope 2.5.1 (same as previous version), copied all of the products in the lib/python/Products, and copied data.fs to /var/data.fs

There are 3 boxes: zopetest, zopedevel, and production, with ZSyncs of DEVEL, STAGING, and PROD respectively.

Zsyncer seems to have broken between migrations, even though parameters are the same:

There was a problem with that comparison.

Error:

* ProtocolError * <ProtocolError for zopetest.hr.ucdavis.edu:80/STAGING: 500 Internal Server Error>

Things to check:

* Your destination ZSyncer is where it is meant to be. * The destination server is running and accessible. * The user "zopeadmin" has the right to access ZSyncer. * The password for "zopeadmin" is correct.

My destination has the same old Zsync instance. Zope is running and accessible. My account and permissions haven't changed, as they're drawn from the same data.fs.

Any clues?

Thanks,

*************************** * Adam Getchell AdamG@hrrm.ucdavis.edu * System Architect/Programmer (530) 752-1584 * Human Resources Information Systems http://www.hr.ucdavis.edu/ *************************** "Invincibility is in oneself, vulnerability in the opponent." -- Sun Tzu

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