Re: Print Manager not loading
Jakub Talaš
Aug 31 09:14:05 oes1 /usr/sbin/namcd[5139]: deinitialized the worker threads
Aug 31 09:14:05 oes1 /usr/sbin/namcd[5139]: deinitialized the cache refresh
thread
Aug 31 09:14:05 oes1 /usr/sbin/namcd[5139]: monitorChangesInLDAP:
ldap_result: Can't contact LDAP server
Aug 31 09:14:08 oes1 /usr/sbin/namcd[5139]: deinitialized the LDAP watcher
thread
Aug 31 09:14:11 oes1 /usr/sbin/namcd[5139]: Deleted hash tables and flushed
data into local files
Aug 31 09:14:11 oes1 /usr/sbin/namcd[5139]: Deinitialized threads
Aug 31 09:14:12 oes1 namcd: SIGTTOU caught
Aug 31 09:14:12 oes1 namcd: SIGTTIN caught
Aug 31 09:14:12 oes1 namcd: SIGTSTP caught
Aug 31 09:14:12 oes1 /usr/sbin/namcd[15465]: Starting namcd..
Aug 31 09:14:12 oes1 /usr/sbin/namcd[15465]: namcd populating the user hash
tables
Aug 31 09:14:12 oes1 /usr/sbin/namcd[15465]: namcd populating group hash
tables
Aug 31 09:14:12 oes1 /usr/sbin/namcd[15465]: namcd Populated hash tables
Aug 31 09:14:12 oes1 /usr/sbin/namcd[15465]: Created all the threads
, so your clue might be right. But I have tried LDAP search with Novell LDAP
browser for Windows and it worked, also with 636.
We were replacing certificates like a month ago, but iPrint ceased to work
few days ago. Other systems work properly.
magic31 wrote:
>
> Have you checked LDAP/LUM & server certificates are all still in order?
> As iPrint on OES2 relies heavily on this (and the account you originally
> configured iPrint with) could be that's the source of the problems.. and
> not so much the objects themselves.
>
> Cheers,
> Willem
>
>
Jakub Talaš
Jakub Talaš wrote:
> Certificates and LUM are OK...
Jakub Talaš
Jakub Talaš
section... - eDirectory