search for: roolback

Hello Does anybody share how to roll-back configuration if puppet definition on host is change. For example Let''s assume we have host on which initial was web server and bunch of users. All this resources we configured throw puppet. node <some node> { <webserver difinition> <user1 definition> <user2 definition> <user3 definition> } At some

...urce4/dsdb/repl/replicated_objects.c:361(dsdb_repl_make_working_schema) ../../source4/dsdb/repl/replicated_objects.c:361: dsdb_repl_resolve_working_schema() failed: WERR_INTERNAL_ERRORFailed to create working schema: WERR_INTERNAL_ERROR Is there any way to fix this problem? dumb question: Can I roolback the schemaupgrade? :D -- Elias Pereira

...0, 8047dac) + 93 0805a1d8 main (0, 8047e0c, 8047e24, d2bfc7b4) + 598 08053d1d _start (5, 8047ec4, 8047ec8, 8047ecb, 8047ed0, 8047ed3) + 7d So for me this looks like the object_count of a directory is inconsistent. Any idea or hint what I could do now? I read that there is some utility to roolback the pool for simple (mirror) setups. This setup is even more simple as it consists of a single vdev. So I would like to try it out. Does anybody know, where I can get the tool, or how I could use zdb in this situation to rollback the pool? TIA, Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG...

...ma) > > ../../source4/dsdb/repl/replicated_objects.c:361: > > dsdb_repl_resolve_working_schema() failed: WERR_INTERNAL_ERRORFailed to > > create working schema: WERR_INTERNAL_ERROR > > > > Is there any way to fix this problem? > > > > dumb question: Can I roolback the schemaupgrade? :D > > > -- Elias Pereira

...ed_objects.c:361: > >>> dsdb_repl_resolve_working_schema() failed: WERR_INTERNAL_ERRORFailed to > >>> create working schema: WERR_INTERNAL_ERROR > >>> > >>> Is there any way to fix this problem? > >>> > >>> dumb question: Can I roolback the schemaupgrade? :D > >>> > > > -- Elias Pereira

...s.c:361(dsdb_repl_make_working_schema) > ../../source4/dsdb/repl/replicated_objects.c:361: > dsdb_repl_resolve_working_schema() failed: WERR_INTERNAL_ERRORFailed to > create working schema: WERR_INTERNAL_ERROR > > Is there any way to fix this problem? > > dumb question: Can I roolback the schemaupgrade? :D >

.../../source4/dsdb/repl/replicated_objects.c:361: >>> dsdb_repl_resolve_working_schema() failed: WERR_INTERNAL_ERRORFailed to >>> create working schema: WERR_INTERNAL_ERROR >>> >>> Is there any way to fix this problem? >>> >>> dumb question: Can I roolback the schemaupgrade? :D >>> >

...t;> dsdb_repl_resolve_working_schema() failed: WERR_INTERNAL_ERRORFailed >> to >> >>> create working schema: WERR_INTERNAL_ERROR >> >>> >> >>> Is there any way to fix this problem? >> >>> >> >>> dumb question: Can I roolback the schemaupgrade? :D >> >>> >> > >> > > > -- > Elias Pereira > -- Elias Pereira

..._working_schema() failed: WERR_INTERNAL_ERRORFailed >>> to >>> >>> create working schema: WERR_INTERNAL_ERROR >>> >>> >>> >>> Is there any way to fix this problem? >>> >>> >>> >>> dumb question: Can I roolback the schemaupgrade? :D >>> >>> >>> > >>> >> >> >> -- >> Elias Pereira >> > > > -- > Elias Pereira > -- Elias Pereira

Hiya, I sent this bugfix to the asterisk-dev mailing list, and modified it as I noticed side effects, but now it appears to be finished. Nobody seemed to notice it there, so I thought I'd post here, as it seems to be something that will be needed as people update to the latest CVS version. So...read on :) Ted programmer_ted@hotmail.com P.S. Read to the very end. The original bugfix