Using webadmin.nsf whilst running Domion 6.5.1 on iSeries. Upgraded server to 6.5.2 and webamin.nsf was removed during the process and not restored.
Subject: 6.5.2 install removed webadmin
Are you sure the webadmin was not deleted (removed) from another process. I would be shocked for that to happen when Windows, Unix, Linux, etc have not had the problem.
Whilst you can upgrade a server more than one way, maybe you can share how you upgrade and maybe their the retracing it would be learned to how the webadmin.nsf was removed.
All in all you can just add the database back – it does not matter what os you pull a copy from becuase the database is standard issue (not os specific).
HTH
Subject: The http server manages the webadmin.nsf automatically
There is no need to “just add the database back”…the HTTP server on startup will check if the database exists, and if not will automatically create it.
Thomas - IBM
Subject: You are “just adding it back” though
Not to be technical, but “just add the database back” is what you are doing when you start the HTTP server task. Yes I was not as explicit as you, but give us some slack here.
The other part to remember is that 1) starting the HTTP task will not create a webadmin.nsf if the filename already exists. Meaning there could be a webadmin.nsf which is not of the webadmin design (I don’t know why, but it is possible) but of a different design. In this situation domino will not do anything with the webadmin.nsf of the wrong design. If the task was going to manage the database it would even check to make sure the template design is correct as well. 2) if the templates were not loaded as you can do this in Unix and Linux, then the user will not have a webadmin.nsf created since there is a template for it to be created from.
Sorry to be critical, but I was using a “simplified term” in my previous post which you critized me (implicitly).
Subject: In a different way, which makes a difference.
The reason I posted was simply to clarify your “simplified term”, and nothing else. And to clarify some more:
Re #1: This works exactly by design. If you already have another db called webadmin.nsf, then we leave it alone. The http server task knows whether it is “the real” webadmin db or not.
Re #2: If the templates were not loaded, then you’ll sure have other issues down the road, as there are lots places in the code where we attempt to auto-create a new database from the template if such a db doesn’t exist yet. This is virtually true for almost all system templates.
Thomas - IBM
Subject: RE: In a different way, which makes a difference.
Update - the webadmin.nsf database was removed during the upgrade.
-
the webadmin.nsf database was not rebuilt when HTTP was started the first time under the new version
-
the webadmin.nsf database was not rebuilt when HTTP was restarted
-
the webadmin.nsf database was rebuilt when the Domino server was restarted
So the database is back, but it was strange that it was put out there the first time HTTP started under the new version.
Subject: 6.5.2 install removed webadmin
No problem on windows. I noticed, that, too, though webadmin.nsf was rebuilt as soon as http finished loading.
Did you try a ‘restart task http’ just to make sure? Also, did webadmin.ntf get installed?