Your message dated Mon, 18 Sep 2006 08:49:36 +0200
with message-id <[EMAIL PROTECTED]>
and subject line tomcat4: Stopping Tomcat with a cronjob sometimes crashs the
System!
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: tomcat4
Version: 4.1.31-3
Severity: critical
Justification: breaks the whole system
I've running a cronjob that stops Tomcat, runs updates to the webapps and
starts Tomcat again. Normally its running perfectly. But already two times
in this month the server wasn't reachable and hasn't any log entrys after
running the cronjob. The server answer only to ping, but to nothing else,
so a external restart is necessary. Heres the line in /etc/crontab:
30 3 * * * root /etc/init.d/tomcat4 stop >/dev/null; /root/bald.sh
>/dev/null; /etc/init.d/tomcat4 start >/dev/null
The bald.sh-Script have only one rsync-command, that normally has nothing
to do! The same error already arose without this Script on
running "/etc/init.d/tomcat4 restart" in /etc/crontab!
When the cronjob running correctly, theres a logentry like
Aug 23 03:30:01 a15176472 /USR/SBIN/CRON[6072]: (root)
CMD (/etc/init.d/tomcat4 stop >/dev/null; ...
in "/var/log/syslog" but after crash, theres really absolutely nothing
after 03:30:00!
I need the restart of Tomcat also, because after few Days Tomcat forget
the correct Charset. After a restart everything is right!
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.30 GrSec
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored:
LC_ALL set to [EMAIL PROTECTED])
Versions of packages tomcat4 depends on:
ii adduser 3.63 Add and remove users and groups
ii apache2-common 2.0.54-4 next generation, scalable, extenda
ii apache2-utils [apache-utils] 2.0.54-4 utility programs for webservers
ii j2re1.4 [java-virtual-machine 1.4.2.02-1 Blackdown Java(TM) 2 Runtime Envir
ii j2sdk1.4 [java-compiler] 1.4.2.02-1 Blackdown Java(TM) 2 SDK, Standard
ii libcommons-beanutils-java 1.6.1-4 utility for manipulating JavaBeans
ii libcommons-collections-java 2.1.1-3 A set of abstract data type interf
ii libcommons-digester-java 1.5.0.1-4 Rule based XML Java object mapping
ii libcommons-logging-java 1.0.4-2 The commmon wrapper interface for
ii libtomcat4-java 4.1.31-3 Java Servlet engine -- core librar
-- no debconf information
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Nitsche wrote:
> Hi Arnaud,
>
> You can close this bug. I've never had this problem on Tomcat4 (sarge),
> 5 and 5.5 since that time.
Thanks Michael.
- --
Arnaud <http://www.ressource-toi.org>
Java Trap: http://www.gnu.org/philosophy/java-trap.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFDkGA4vzFZu62tMIRAic3AKCY+c0aAbiSgIvNfj2qyp1G+xWtqwCfbn3d
8vQGeCHynSeGNuzzDfIEYCE=
=FZLe
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
pkg-java-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
