Wowza 3.1.2 randomly stops writing into all log files

[markusb79]

Dear Wowza Team,

We are experiencing issues with the logging feature of our Wowza 3.1.2 server. It stops writing any log messages in

/usr/local/WowzaMediaServer/logs/wowzamediaserver_access.log and
/usr/local/WowzaMediaServer/logs/wowzamediaserver_error.log

a few minutes or hours after the server is started. In some occasions it even stops writing log messages in the access log right after this line:

2012-08-03 13:05:37 EDT comment server INFO 200 - Wowza Media Server is started! - - - 1.714 - - - - - - - - -
- - - - - - - - - - - - - - - -

I tried enabling the debug mode in conf/log4j.properties to find out if the server prints any error message that indicates the cause of the logging problem:

#log4j.rootCategory=INFO, stdout, serverAccess, serverError
log4j.rootCategory=DEBUG, stdout, serverAccess, serverError

But we do not get any kind of error when the log writing stops.

The server disk space does not seem to be the problem:

# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 29G 5.3G 23G 20% /
udev 7.9G 4.0K 7.9G 1% /dev
tmpfs 7.9G 0 7.9G 0% /dev/shm
tmpfs 7.9G 628K 7.9G 1% /run
/dev/md2 29G 5.3G 23G 20% /
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
tmpfs 7.9G 0 7.9G 0% /media
/dev/md0 291M 49M 227M 18% /boot
/dev/md3 3.9G 72M 3.6G 2% /tmp
/dev/md4 418G 690M 396G 1% /home

We are using the following kernel and Java versions:

Linux streamer 2.6.40.3-0.fc15.x86_64 #1 SMP Tue Aug 16 04:10:59 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

java version "1.7.0_05"
Java(TM) SE Runtime Environment (build 1.7.0_05-b05)
Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode)

The issue also occurred with Wowza 2.2.4 before we upgraded the Wowza version.

We are using one custom application and a chat application from Flashcoms on the server. Do custom applications have the ability to shut down all the logging of the server through an exception of some kind?

Thank you,
Markus Braasch

[randall]

I have not heard any similar reports so I feel it is unlikely to be a Wowza bug.

I would troubleshoot by trying to either identify steps to reproduce the issue, or by removing your custom module to see if the problem clears up.

It could be a corrupt installation and/or conf file. Did you copy any conf files over from the previous installation when you upgraded? If so, renaming your current Wowza installation folder and reinstalling might fix it.

Have you rebooted the computer lately?

[markusb79]

Thanks for your response. I copied a few application-specific configuration folders from the previous installation to the new one. Other config files were not copied.

The last reboot of the server occurred 36 days ago. The problem is present for more than six months.

I will try to identify the cause of the issue by removing all custom modules and configurations first, and then adding them back one-by-one.

Thank you,
Markus

[flommi]

Dear Wowza Team,

I have the same problem, Wowza 3.1.2 randomly stops writing into database log, while continuing to write correctly on file log (but with on error: "MediaReaderFactory.getInstance: Missing definition for javascript" but I don't know if this error is relevant to the problem).

I have this problem on three server machines with Wowza 3.1.2.

I must restart Wowza service for resolve this problem.

Thanks.

The problem isn't free disk space:

df:
Filesystem blocchi di 1K Usati Disponib. Uso% Montato su
/dev/sda3 31209468 2387512 27249092 9% /


Thank you,

Federico

[randall]

Hello Federico,

Wowza server doesn't have any database or javascript functionality. I would look into your custom modules. Either debug using the Wowza IDE or add getLogger() statements to track down the issue.

[flommi]

Hi randall,

I have only used how to for log wowza into mysql database ( http://www.wowza.com/forums/content....mySQL-database ) and it's works! but randomly stops writing into database.

I must restart Wowza service for resolve this problem.

Database mysql is on the same Wowza server.

Thank you,

Federico

[rrlanham]

Frederico,

This is a known problem, the JDBC connnector does not recover from network problems, but take a look at this recent post from another Wowza admin:

http://www.wowza.com/forums/showthre...abase/page5#49

Richard