Re: Migrated iPrint from NW to OES2, but doesn't autostart?
Joseph Marton
> If we reboot the OES2 server, the driverstore and the manager do not
> seem to auto-start.
Are the driverstore & manager configured to start automatically?
chkconfig --list | grep novell-i
You should see "on" next to runlevels 2-5.
--
Joe Marton
Novell Knowledge Partner
SUSE Linux Enterprise 11 is ready for action.
Joseph Marton
> Yes, they are set for "on" for 2-5 runlevels.
I would take a look in /var/log/boot.msg, then, and hopefully some
indication of the failure will be in there.
Joseph Marton
> skipped services in runlevel 5: smbfs nfs irq_balancer microcode
> suseRegister novell-idsd novell-ipsmd
>
>
> ???
>
> Yet, the checkconfig says "on" for runlevel 5 for both of those.
Hmm... that sure does sound odd. Try turning them off and on.
chkconfig novell-idsd off
chkconfig novell-ipsmd off
chkconfig novell-idsd on
chkconfig novell-idsd on
Joseph Marton
> Is it possible the "boot" is calling the wrong conf file? Whereabouts
> would I find the "startup" files that are used during boot?
I doubt it since the init script itself specifies which conf to use via
the CONF_FILE variable. I know you said you can start the driverstore &
manager using iManager. What if you try starting them manually using the
init scripts?
/etc/init.d/novell-idsd start
/etc/init.d/novell-ipsmd start
Joseph Marton
> Yes, manually starting with scripts or via iManager works fine. Very
> weird.
Sounds like a potential boot order problem, like some service isn't
started yet when the iPrint services attempt to start. Try changing the
symlinks in /etc/init.d/rc3.d or /etc/init.d/rc5.d, depending upon your
runlevel, to force the scripts to start later. This isn't a long term
fix but at least will tell us now if that's the problem or not.
W_ Prindl
does not wait long enough for ndsd and namcd startup - novell-idsd now
does load here during server-startup.
You can try the following:
- use IP-addresses instead of domain-names for the DSserver in the
*.conf files, so the daemons need not wait for named to be up to
connect to edir
- try to use another edir-server as the one you are running the
services on, which is already up when you start your server
- edit the startup scripts in /etc/init.d to wait for ndsd and
namcd being completely up before starting the iprint daemons
My iprint server runs on a VMware ESXi 3.5 host - maybe those issues do
not arise on real hardware.
--
W. Prindl
W_ Prindl
or DS.NLM (on Netware) or another on any other platform is running and
information can be accessed via LDAP.
Additional info: you can add the dns-names needed for ipsmd into the
hosts file on the server - this removes the dependency on named
(novell-named); but do *not* do this on a DSfW server.
--
W. Prindl
kjhurni wrote:
>
>Thanks for the information.
>
>Yes, this is a test server on vmware 3.5i ESX, using the vmi
>paravirtualization kernel. We're doing the "production" server of
>this test server tonight, so I'll see if it happens there as well.
>
>From my looking at the log file, it does seem (for me anyway) that it
>waits for namcd to start, but possibly ndsd isn't up and running fully
>yet.
>
>I saw reference to that dsserver in the .conf file and was a little
>confused by the documentation regarding this.
>
>Is this ANY server that has eDirectory on it (regardless of whether a
>replica is there or not)? and/or does this have to be a server that
>runs LDAP?
>
>The docs mention you could add DSserver2 and 3 I believe as well, but
>I was unclear as to what they meant by eDirectory server (Novell uses
>this in OES2 and depending on what screen you're on it can mean
>different things. Sometimes it means a replica server, sometimes it
>means an LDAP server, sometimes it means an LDAP server with replicas
>on it, etc.)