Menu

#10 Daemon doesn't start corrctly

open
5
2002-10-27
2002-07-23
Anonymous
No

When i try to start ctsd it appears to run, but looks like it
drops out of memory. It never apears in the process list.

Typical log entries are:
+-+-+-+-+-+-+-+-+ Starting Daemon +-+-+-+-+-+-+-+-+
CTS Deamon 1.0beta (C) 2002 MyCTS group
CVS tag: $Id: main.c,v 1.30 2002/06/13 12:59:59
falseprophet Exp $
Running server on 194.223.2.134:5137
+-+-+-+-+-+-+-+-+ Starting Daemon +-+-+-+-+-+-+-+-+
CTS Deamon 1.0beta (C) 2002 MyCTS group
CVS tag: $Id: main.c,v 1.30 2002/06/13 12:59:59
falseprophet Exp $
Running server on 194.223.2.134:5137

No log entries for shutting down, nothing in memory.

Any clues?

Running on Red hat linux 7.3 as root

Discussion

  • Jilles Oldenbeuving

    Logged In: YES
    user_id=307556

    Would you like to attach the output of the daemon with the -v
    option? Not all start-up errors are correctly reported to the
    logfile... Have you edited the config file correctly, do you have
    MySQL setup properly?

     
  • Nobody/Anonymous

    Logged In: NO

    I have the same problem.

    Using ltrace and strace it appears that the program returns
    -1 soon after writing the log data.

    Otherwise it is pretty hard to give some debugging
    information, because the code uses logging quite sparsely.
    using -v doesn'r really help either.

    It might be just that the connection to the database fails,
    but I have configured the connection and tested it using
    MySQL and the cts web interface.

    Any tips would be more than welcome.

     
  • Anonymous

    Anonymous - 2002-10-27
    • assigned_to: nobody --> falseprophet
     
  • Anonymous

    Anonymous - 2002-10-27

    Logged In: YES
    user_id=483465

    Hmm ok, seems we have some research to do again,
    I will see where that -1 can come from when stracing

     
  • Florent

    Florent - 2005-06-24

    Logged In: YES
    user_id=1276184

    I suspect the problem is simply that ctsd will not attempt
    to db_connect() unless HAVE_LIBMYSQLCLIENT is defined in
    databaseabstraction.c.

    The configure script should be checking if libmysqlclient is
    present and if so AC_DEFINEing HAVE_LIBMYSQLCLIENT.

    To test this change add #DEFINE HAVELIBMYSQLCLIENT 1
    in databaseabstraction.c and make && make install.

    If this doesn't fix it then the problem is elsewhere :D

     

Log in to post a comment.