ZLMMirror and folder's name

Question

Again I was tackling the configurations to ZLM, and again, I stumbled in something in the ZLMMirror... I starting to have doubts that anyone ever finished a successful mirroring from anything, its amazing!
Now the Java seems to create the wrong name for the target package recently downloaded from NU.
The error I am getting is:
(from services-messages.log)
DEBUG: [4/12/10 4:48:13 PM] Core-API com.novell.zenworks.datamodel.ObjectNotFoundExcept ion: The object(s) do not exist: /Bundles//Bundles/NovellUpd/SLES10-
SP3-Updates.
(from zlmmirror.log )
Error: An error occurred while trying to add the bundle "/Bundles/NovellUpd/SLES10-SP3-Updates/SLES10-SP3-Updates-bundle" to the catalog "/Bundles/NovellUpd
/SLES10-SP3-Updates/SLES10-SP3-Updates". (The object(s) do not exist: /Bundles//Bundles/NovellUpd/SLES10-SP3-Updates.)
com.novell.zenworks.zlmmirror.server.MirrorServerE xception: An error occurred while trying to add the bundle "/Bundles/NovellUpd/SLES10-SP3-Updates/SLES10-S
P3-Updates-bundle" to the catalog "/Bundles/NovellUpd/SLES10-SP3-Updates/SLES10-SP3-Updates".
I am pointing all the downloads to NovellUpd folder, ..., before it was Novell Updates, but it was giving error of "path name too long", after fixing it, I still have this weird error, from apparently nowhere, he repeats the part "/bundle/" to the database and simply die in the middle of the process.
I wonder:
1) Is there a way to make him ignore the error and continue adding packages disregarding one simple error? (like a command switch or a tricky java option?)
2) How would I enable the java debug, where I could see those errors that zlmmirror is generating with more depth, or that's it?
3) What would be the best practice to put RPMs on the ZLM?
3.a) I have a complete, working, repository for YAST / NU with all the Linux and OES updates, this is working pretty fine, after "hacking" some of the novell scripts. Importing this repositories to ZLM (with something like rpm2zlm) could be more easy than use the zlmmirror as I realize now... any comments on this?
4) Any comment or information necessary to figure out problems here?
I can't see any relation with any configuration besides a problem in the Java application...
I getting tired and frustrated, with something that should be so simple turn into a very complicated and entangled task.

Answer 1

jchegedus,
I think this are just a config error in the mirror xml file.
1) Is there a way to make him ignore the error and continue adding packages disregarding one simple error? (like a command switch or a tricky java option?)
No, it has to run without a error, otherwise it will abort.
But there is one command line option that you should use: --force-nevra
The nevra is like a hash over the rpm package and is stored based on the N...rpm name, E...<don't remember>, V...version, R...release, A...architecture of the package. Normally a package should only be available once at the update server. But it happened a few times that the same package was available twice, but it was not really the same file, I was built twice at the rpm build server at different dates and therefor the hashes varied. As ZLM has downloaded the first version in a bundle, it got within a different bundle the same package with a already known name, version, release... a second time, but the hash varied. then it refuses to upload it once again, except the --force-nevra option is set. Therefor add it to the mirror command if you do not already have it there.
This is the command line I use:
# zlmmirror mirror --verbose --force-nevra -c
2) How would I enable the java debug, where I could see those errors that zlmmirror is generating with more depth, or that's it?
The --verbose option provides much more output and in case there is a error you have more information in about it. Depending on what time the error occurs, you might also find error messages in the /var/opt/novell/log/zenworks/services-messages.log. While the packages are downloaded to a temporary folder, the verbose output should show the errors, after they are on the local system and get uploaded into the zlm package repository, errors might also be logged in the service-messages.log file. But parts of it are also reported in the verbose output of zlmmirror. So just look at that, if there are no errors, everything is okay ... if there are errors take a look at what time and then check the other file as well.
3) What would be the best practice to put RPMs on the ZLM?
Do you want to add other 3rd party rpms to the zlm server or those from the mirror ? For third party rpms you can use the web interface ZCC or if you have more then just a few rpms, use the "zlman bap ..." command line. bap ... bundle add package. I create first a empty bundle either via ZCC or also zlman and then add the pacakges.
3.a) I have a complete, working, repository for YAST / NU with all the Linux and OES updates, this is working pretty fine, after "hacking" some of the novell scripts. Importing this repositories to ZLM (with something like rpm2zlm) could be more easy than use the zlmmirror as I realize now... any comments on this?
Use zlmmirror, then you can be sure that the bundles are okay ...
4) Any comment or information necessary to figure out problems here?
Check you mirror xml file, especially the Folder setting.
That must not contain the /BUNDLES/ part at the begin.
It should look like this:
Code:
<Folder>Novell/SLES/11</Folder>
Rainer