Hello Thomas,
this happens when assp will make a restart after the autoupdate have
change the assp.pl. After the error i must start assp manualy. (and assp
has the new versionsnumber after the manual start)
The same error come, when i tell assp to make a restart by the gui.
Can i set a switch for a better loging, so that you (or i) can see why
it happens ?
I don´t know how webmin makes a autorestart after updates, but it works
without this error.
Ralf
>>> Thomas Eckardt <Thomas.Eckardt@...> 23.04.10 19.37 Uhr >>>
>Worker_5: error: got unexpected signal TERM in
How ever, this signal is produced inside the threads module. ASSP
captures
all not explicid defined signals (in ASSP) and runs in to a
sub/signal-handler which produces the logged line. After that, the
thread
should go back in to normal state if possible. If not - you have to
restart ASSP - but I never saw this.
Thomas
Von: "admin" <Admin@...>
An: <assp-test@...>
Datum: 23.04.2010 09:35
Betreff: [Assp-test] unexpected signal in ASSP Version 2
Hello,
I have sometimes the following error in my log :
Apr-23-10 09:21:42 Error: Worker_5: error: got unexpected signal TERM in
Worker_5: package - Thread::Queue, file -
/usr/local/lib/perl5/5.10.1/Thread/Queue.pm, line - 51!
I have look at the kill command, the signal TERM exists. I use freebsd
Version 8. Where must the signal TERM defined , that it works correct in
assp?
Best regards
Ralf
------------------------------------------------------------------------------
_______________________________________________
Assp-test mailing list
Assp-test@...
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential,
legally
privileged and protected in law and are intended solely for the use of
the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
|