Using the --syslog switch it still produced no logs whatsoever. I took it a step further and tried the --spew switch which should dump huge amounts of log data (I am piping the output to a file) - that produces nothing either. To be honest I think twistd starts up and crashes solidly without being able to log anything.

If I look at all the log files I only see my shell debugging messages that is printed out by the shell script itself, nothing else:
Apr 21 16:34:53 hostname logger: GHServer: Start script executed
Apr 21 16:34:53
hostname logger: GHServer: Starting
Apr 21 16:34:53
hostname logger: GHServer: Started

BTW, it also does not start the server from /etc/rc.local.

I am completely stumped.

Regards,
Don



Itamar Turner-Trauring wrote:
On Wed, 2010-04-21 at 15:37 +0200, Don Schoeman wrote:
  
I still get the same results (or non-results) unfortunately. I have
tried the following options:

1) Tried running twistd by giving the fully qualified
path: /usr/bin/twistd.
2) Tried running the .tac file together with the -g twistd switch
instead.
3) Tried the --syslog switch to see if I can find anything in the
logs.
4) Tried running it without supplying custom log and pid files.
    

What does running under trace tell you?


_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

  
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Reply via email to