After Rohan Dighe emailed the Bug Squad mailing list regarding this issue, I tested this on a properly configured SKS server that has no peer servers. This server has actually been configured, which means that I installed 'sks' and then configured the software for the key database and the web interface. The initial 'sks' installation does not set up the sks keyserver keydb or any other sks required resources, which is why it requires initial configuration by hand before it works.
I was not able to confirm this bug on that fully configured SKS keyserver instance which I just created today. The processes for the sks program, one for sksdb and one for sksrecon, correctly launch when the sks server is properly set up with initial configuration. While my keyserver is brand new today and does not sync with any other keyservers, thereby triggering errors related to no peer servers for syncing, the 'sks' process is correctly running with the included init script. I am not using the backported version of the sks package. (I am not changing the status of this bug off of "Expired" as there is no new information, however if anyone is able to confirm this bug when they attempt to load sks without initially configuring it, they are allowed to change this bug status to "confirimed") -- You received this bug notification because you are a member of Debian OCaml Maintainers, which is subscribed to sks in Ubuntu. https://bugs.launchpad.net/bugs/820354 Title: init script causes error in [re]starting Status in “sks” package in Ubuntu: Expired Bug description: Environnent: #lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 10.04.3 LTS Release: 10.04 Codename: lucid Issue: When you are using the init script file to start or restart SKS you may face to the following error: #/etc/init.d/sks restart Stopping sks daemons: sksrecon..start-stop-daemon: warning: failed to kill 432: No such process sksdb..start-stop-daemon: warning: failed to kill 429: No such process done. Starting sks daemons: sksdb.. sksrecon.. done. Solution: The issue can be fixed in removing all PID files that they still exist in /var/run/sks/ folder. So remove these files and execute again the init script file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ocaml-maint Post to : [email protected] Unsubscribe : https://launchpad.net/~ocaml-maint More help : https://help.launchpad.net/ListHelp
