[389-users] restarting the 389 after a reboot

[Steven Jones]

Hi,

I eventually thought that....ie pin file.....however I am not aware Ive set the admin server for ssl.....the actual directory server is, and has a pin file and it starts....so I'll go back and make one.

However from the docs, starting it at the command line should then see it asking for the password....I dont see that.

There is nothing in the error log....

========
[root at vuwunicooimm001 admin-serv]# ls -l
total 32
-rw-r--r-- 1 root root 28866 Jun 22 14:49 access
-rw-r--r-- 1 root root     0 Jun 23 16:30 error
[root at vuwunicooimm001 admin-serv]# tail access
130.195.53.100 - uid=ldapadmin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot [22/Jun/2010:13:03:44 +1200] "GET /slapd-vuwunicooimm001/Tasks/Operation/Restart HTTP/1.0" 200 2384
130.195.53.100 - uid=ldapadmin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot [22/Jun/2010:13:04:30 +1200] "POST /admin-serv/tasks/configuration/SecurityOp HTTP/1.0" 200 643
130.195.53.100 - uid=ldapadmin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot [22/Jun/2010:13:04:30 +1200] "POST /admin-serv/tasks/configuration/SecurityOp HTTP/1.0" 200 1338
130.195.53.100 - uid=ldapadmin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot [22/Jun/2010:13:04:40 +1200] "POST /admin-serv/tasks/configuration/SecurityOp HTTP/1.0" 200 1872
130.195.53.100 - uid=ldapadmin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot [22/Jun/2010:13:05:06 +1200] "POST /admin-serv/tasks/configuration/SecurityOp HTTP/1.0" 200 643
130.195.53.100 - uid=ldapadmin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot [22/Jun/2010:13:05:06 +1200] "POST /admin-serv/tasks/configuration/SecurityOp HTTP/1.0" 200 1338
130.195.53.100 - uid=ldapadmin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot [22/Jun/2010:13:05:16 +1200] "POST /admin-serv/tasks/configuration/SecurityOp HTTP/1.0" 200 1815
130.195.53.100 - uid=ldapadmin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot [22/Jun/2010:14:47:34 +1200] "POST /slapd-vuwunicooimm001/Tasks/Operation/ViewLog HTTP/1.0" 200 3883
130.195.53.100 - uid=ldapadmin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot [22/Jun/2010:14:47:58 +1200] "POST /slapd-vuwunicooimm001/Tasks/Operation/ViewLog HTTP/1.0" 200 2174
130.195.53.100 - uid=ldapadmin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot [22/Jun/2010:14:49:45 +1200] "GET /slapd-vuwunicooimm001/Tasks/Operation/Restart HTTP/1.0" 200 2270
[root at vuwunicooimm001 admin-serv]# 
========


regards

Steve n

-----Original Message-----
From: 389-users-bounces at lists.fedoraproject.org [mailto:389-users-bounces at lists.fedoraproject.org] On Behalf Of Techie
Sent: Wednesday, 23 June 2010 5:30 p.m.
To: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] restarting the 389 after a reboot

What does /var/log/dirsrv/admin-serv/error say? Should give you a good
clue. Kind of sounds like an SSL instance trying to start without a
pin file but just guessing there.

TC

On Tue, Jun 22, 2010 at 9:27 PM, Steven Jones <Steven.Jones at vuw.ac.nz> wrote:
> Hi,
>
> After a system reboot the Ldap admin service appears not to be running.
>
> How do I restart it?
>
> I tried "service dirsrv-admin start" but this just hangs / never returns to the console.
>
> thanks
>
> Steven
> --
> 389 users mailing list
> 389-users at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users
>
--
389 users mailing list
389-users at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users