Hello Steffen, Hope you've fixed the problem over this past week. If not, I have an idea...
While I haven't encountered such errors with SSGD, this looks a bit like a general problem with sudden system poweroffs without a correct shutdown: some programs, services and init-scripts interact via PIDfiles, door/socket files, etc. Sometimes poorly coded init-scripts (rarely programs) expect these filesystem objects to be valid, i.e. that the file /var/run/sendmail.pid contains a number of proccess ID which is indeed currently the sendmail daemon. Or that /tmp/mysql.sock is listened by a process of MySQL server. When the system dies due to poweroff (or simply a service crashes) such files become invalid. Well-behaved scripts usually check in their startup routine whether their managed service is running (PIDfile exists and points to a correctly-named binary); otherwise they "rm -f" the special files used by their program and start the service. Then the program creates the files it needs from scratch and they are correct. I have no idea whether any of this relates to SSGD/Tarantella scripts or binaries, but since this sort of problem is common in my experience - it might be the case here too. My point is: try to look for similar leftover files (probably dated when Tarantella previously started up successfully) with "slocate", "find" or perhaps by debugging the start-scripts (sh -x) or truss'ing the binaries. Clean them up and see if that helps. Tuesday, November 4, 2008, 2:14:31 PM, you wrote: SB> Hi, SB> we?ve got a customer with ssgd version 4.3 SB> Everthing works fine until the server reboots due to a problem with the SB> ups. the server (sles 10) is rebooting without any problems. SB> Now the sgd server does not start anymore. SB> Here are some errors from the error.log SB> 008/11/09 04:07:21.015 (pid 5145) pem/circuit #0 SB> Sun Secure Global Desktop Software(4.3) ERROR: SB> An error occurred reading on circuit fdcircuit. Reason: (9) Bad file SB> descriptor. SB> The current operation has failed. SB> If persistent, restart the server. SB> 2008/11/09 04:07:21.015 (pid 5145) pem/circuit #2 SB> Sun Secure Global Desktop Software (4.3) FATAL ERROR: SB> The program has encountered an error that means it cannot continue. SB> It will now exit. A technical description is given below to help SB> establish the cause. SB> Error on file descriptor circuit. Killing PE Manager. SB> Services unavailable. SB> Restart the server. SB> 2008/11/09 03:09:00.381 ssl6952 SB> ssldaemon/sslindividual/listenfailederror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Secure Global Desktop Security Daemon failed to accept a client connection. SB> The reported error: accept(4,0,0): (24) Too many open files SB> ssldaemon/sslindividual/listenfailederror SB> 2008/11/09 03:09:00.381 ssl6952 SB> ssldaemon/sslindividual/listenfailederror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Secure Global Desktop Security Daemon failed to accept a client connection. SB> The reported error: accept(4,0,0): (24) Too many open files SB> ssldaemon/sslindividual/listenfailederror SB> 2008/11/09 03:09:10.360 ssl6952 SB> ssldaemon/sslindividual/listenfailederror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Secure Global Desktop Security Daemon failed to accept a client connection. SB> The reported error: accept(4,0,0): (24) Too many open files SB> ssldaemon/sslindividual/listenfailederror SB> 2008/11/09 03:09:10.360 ssl6952 SB> ssldaemon/sslindividual/listenfailederror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Secure Global Desktop Security Daemon failed to accept a client connection. SB> The reported error: accept(4,0,0): (24) Too many open files SB> ssldaemon/sslindividual/listenfailederror SB> 2008/11/09 03:09:33.766 ssl6952 ssldaemon/socket/listenbinderror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Couldn't bind to port 443. SB> socket(1): (24) Too many open files ssldaemon/socket/listenbinderror SB> 2008/11/09 03:09:33.766 ssl6952 ssldaemon/socket/listenbinderror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Couldn't bind to port 443. SB> socket(1): (24) Too many open files ssldaemon/socket/listenbinderror SB> 2008/11/09 03:09:33.766 ssl6952 SB> ssldaemon/TTAservererror/badresponseinfo SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Secure Global Desktop server not responding on port 443, closing the SB> connection. SB> TSP=127.0.0.1:443 Client=127.0.0.1:33761 SB> ssldaemon/TTAservererror/badresponseinfo SB> 2008/11/09 03:09:33.766 ssl6952 SB> ssldaemon/TTAservererror/badresponseinfo SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Secure Global Desktop server not responding on port 443, closing the SB> connection. SB> TSP=127.0.0.1:443 Client=127.0.0.1:33761 SB> ssldaemon/TTAservererror/badresponseinfo SB> 2008/11/09 03:11:02.386 ssl6952 SB> ssldaemon/sslindividual/listenfailederror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Secure Global Desktop Security Daemon failed to accept a client connection. SB> The reported error: accept(4,0,0): (24) Too many open files SB> ssldaemon/sslindividual/listenfailederror SB> 2008/11/09 03:11:02.386 ssl6952 SB> ssldaemon/sslindividual/listenfailederror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Secure Global Desktop Security Daemon failed to accept a client connection. SB> The reported error: accept(4,0,0): (24) Too many open files SB> ssldaemon/sslindividual/listenfailederror SB> 2008/11/09 03:13:11.452 ssl6952 SB> ssldaemon/sslindividual/listenfailederror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Secure Global Desktop Security Daemon failed to accept a client connection. SB> The reported error: accept(4,0,0): (24) Too many open files SB> ssldaemon/sslindividual/listenfailederror SB> 2008/11/09 03:13:11.452 ssl6952 SB> ssldaemon/sslindividual/listenfailederror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Secure Global Desktop Security Daemon failed to accept a client connection. SB> The reported error: accept(4,0,0): (24) Too many open files SB> ssldaemon/sslindividual/listenfailederror SB> 2008/11/09 03:17:40.588 ssl6952 SB> ssldaemon/sslindividual/listenfailederror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Secure Global Desktop Security Daemon failed to accept a client connection. SB> The reported error: accept(4,0,0): (24) Too many open files SB> ssldaemon/sslindividual/listenfailederror SB> 2008/11/09 03:17:40.588 ssl6952 SB> ssldaemon/sslindividual/listenfailederror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Secure Global Desktop Security Daemon failed to accept a client connection. SB> The reported error: accept(4,0,0): (24) Too many open files SB> ssldaemon/sslindividual/listenfailederror SB> 2008/11/09 03:17:53.273 ssl6952 ssldaemon/socket/listenbinderror SB> Sun Secure Global Desktop Software (4.3) ERROR: SB> Couldn't bind to port 443. SB> socket(1): (24) Too many open files ssldaemon/socket/listenbinderror SB> any help appreciated SB> Regards SB> Steffen SB> _______________________________________________ SB> SGD-Users mailing list SB> SGD-Users@filibeto.org SB> http://www.filibeto.org/mailman/listinfo/sgd-users -- Best regards, Jim Klimov mailto:[EMAIL PROTECTED] _______________________________________________ SGD-Users mailing list SGD-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sgd-users
