NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MlDonkey killed daily by /etc/cron.daily/logtruncate
Hi all,
I deleted the bitorrent application and replaced it by MlDonkey. After a while working alright the application is always down and needs to be started manually with Frontview.
I've found out that the command "start-stop-daemon -K -n apache-ssl -R 5" in the "/etc/cron.daily/logtruncate" script is having the side-effect of killing "mlnet" every day at 06:25. If I execute manually the script I kill mlnet and get the following messages:
----------------------------------------------------------------------------------------------------------------------------------------
# ./logtruncate
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.2.3 for ServerName
tail: /var/log/frontview/apache-ssl.pid: No such file or directory
Message 1PSjtQ-00014j-00 has been removed
----------------------------------------------------------------------------------------------------------------------------------------
I have tried updating to RAIDiator 4.1.7 from the T60 and also using the power timer, but there is no way arround it, I always need to start manually MlDonkey with Frontview.
Any ideas??
I deleted the bitorrent application and replaced it by MlDonkey. After a while working alright the application is always down and needs to be started manually with Frontview.
I've found out that the command "start-stop-daemon -K -n apache-ssl -R 5" in the "/etc/cron.daily/logtruncate" script is having the side-effect of killing "mlnet" every day at 06:25. If I execute manually the script I kill mlnet and get the following messages:
----------------------------------------------------------------------------------------------------------------------------------------
# ./logtruncate
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.2.3 for ServerName
tail: /var/log/frontview/apache-ssl.pid: No such file or directory
Message 1PSjtQ-00014j-00 has been removed
----------------------------------------------------------------------------------------------------------------------------------------
I have tried updating to RAIDiator 4.1.7 from the T60 and also using the power timer, but there is no way arround it, I always need to start manually MlDonkey with Frontview.
Any ideas??
3 Replies
Replies have been turned off for this discussion
- sadly still no answer to this one. I also have the same problem but only since I upgraded to MLDonkey 3.01. The older package did not do this.
- The 'start-stop-daemon -K -n apache-ssl -R 5' also kills afpd.
I replaced the lines in /etc/cron.daily/logtruncate with these to restart apache:
if( $restart_apache ) {#
# start-stop-daemon kills afpd
#
# system("start-stop-daemon -K -n apache-ssl -R 5");
# system("/usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf");
#
system("/usr/sbin/apache2ctl restart");
}
For this to work you'll have to create a symbolic link first:
(as root on your NAS)
cd /etc/apache2
ln -s ../frontview/apache/httpd.conf apache2.conf
Hope this helps. The start-stop-daemon command seems to be broken. - I also have this problem with MLDonkey.
The solution seems clear to me: delete the 2 offending lines in the logtruncate script. I appreciate the fact that the corresponding 2 files are not truncated but that is not a big problem, or is it?
B.T.W. This problem is mentioned in the release notes of Raidiator 4.1.9 but that one is not available for the Raidynas DUO (sparc). Is the problem really solved in 4.1.9?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
