On Fri, May 29, 2009 12:32 AM, "Josh Campbell" <[email protected]> wrote:
I'm troubleshooting the final portions of a Cosign v3.0.2 install and
seem to have hit a problem but I can't figure this out. When starting
cosignd I'm getting output as follows:
]# service cosignd start
Cosign daemon starting...
cosignd: can't find cosign service
cosignd: continuing...
nohup: appending output to `nohup.out'
That means that cosignd could not find an entry in /etc/services mapping
the service name ("cosignd") to a port (normally, 6663). In this case,
it prints a warning message and uses the default port (6663). This does
not actually affect anything. You can get rid of the warning message by
adding a line for cosignd to /etc/services if you find the message
annoying, though.
The Apache site is up, I have no idea what's wrong here. SSL certs
have passed verification as sslclient and sslserver certificates. Any
help is greatly appreciated.
What is not working? What are the symptoms of the problem you are having?
Mark Montague
ITCS Web/Database Team
The University of Michigan
[email protected]
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
