[opensuse] Rsync daemon dies every hour. Why?
Can anyone tell me why rsyncd won't stay up all the time? I keep getting this sort of stuff in /var/log/rsyncd.log 2010/01/05 09:10:30 [3407] Service registration expired, refreshing it 2010/01/05 09:10:30 [3407] rsyncd registering 12 services with slpd for 3600 seconds: 2010/01/05 10:10:23 [3407] Service registration expired, refreshing it 2010/01/05 10:10:23 [3407] rsyncd registering 12 services with slpd for 3600 seconds: 2010/01/05 11:10:16 [3407] Service registration expired, refreshing it 2010/01/05 11:10:16 [3407] rsyncd registering 12 services with slpd for 3600 seconds: I'm sure it never used to do this. It just started at boot time, and kept running in the background. Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2, Kernel 2.6.31.5-0.1-desktop, KDE 4.3.3 Intel Core2 Quad Q9400 2.66GHz, 4GB DDR RAM, nVidia GeForce 9200GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob Williams wrote:
Can anyone tell me why rsyncd won't stay up all the time? I keep getting this sort of stuff in /var/log/rsyncd.log
2010/01/05 09:10:30 [3407] Service registration expired, refreshing it 2010/01/05 09:10:30 [3407] rsyncd registering 12 services with slpd for 3600 seconds: 2010/01/05 10:10:23 [3407] Service registration expired, refreshing it 2010/01/05 10:10:23 [3407] rsyncd registering 12 services with slpd for 3600 seconds: 2010/01/05 11:10:16 [3407] Service registration expired, refreshing it 2010/01/05 11:10:16 [3407] rsyncd registering 12 services with slpd for 3600 seconds:
I'm sure it never used to do this. It just started at boot time, and kept running in the background.
Given that the process id doesn't change, you're still looking at just one daemon. It isn't restarted. /Per -- Per Jessen, Zürich (-2.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 05 Jan 2010 12:26:34 Per Jessen wrote:
Bob Williams wrote:
Can anyone tell me why rsyncd won't stay up all the time? I keep getting this sort of stuff in /var/log/rsyncd.log
2010/01/05 09:10:30 [3407] Service registration expired, refreshing it 2010/01/05 09:10:30 [3407] rsyncd registering 12 services with slpd for 3600 seconds: 2010/01/05 10:10:23 [3407] Service registration expired, refreshing it 2010/01/05 10:10:23 [3407] rsyncd registering 12 services with slpd for 3600 seconds: 2010/01/05 11:10:16 [3407] Service registration expired, refreshing it 2010/01/05 11:10:16 [3407] rsyncd registering 12 services with slpd for 3600 seconds:
I'm sure it never used to do this. It just started at boot time, and kept running in the background.
Given that the process id doesn't change, you're still looking at just one daemon. It isn't restarted.
/Per
OK. Yes, I was too hasty accusing the process of dying. But what does 'Service registration expired, refreshing it' mean? I've looked in YaST > Network Services > Network Services(xinetd) at the rsync daemon setup, but I can't see any obvious settings that have been changed there. Specifically, I have /usr/sbin/rsyncd --daemon stream tcp no-wait running as user:root Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2, Kernel 2.6.31.5-0.1-desktop, KDE 4.3.3 Intel Core2 Quad Q9400 2.66GHz, 4GB DDR RAM, nVidia GeForce 9200GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Jan 05, 2010 at 01:13:31PM +0000, Bob Williams wrote:
On Tuesday 05 Jan 2010 12:26:34 Per Jessen wrote:
Bob Williams wrote:
Can anyone tell me why rsyncd won't stay up all the time? I keep getting this sort of stuff in /var/log/rsyncd.log
2010/01/05 09:10:30 [3407] Service registration expired, refreshing it 2010/01/05 09:10:30 [3407] rsyncd registering 12 services with slpd for 3600 seconds: [ ... ] I'm sure it never used to do this. It just started at boot time, and kept running in the background.
Given that the process id doesn't change, you're still looking at just one daemon. It isn't restarted. [ ... ] OK. Yes, I was too hasty accusing the process of dying. But what does 'Service registration expired, refreshing it' mean? I've looked in YaST > Network Services > Network Services(xinetd) at the rsync daemon setup, but I can't see any obvious settings that have been changed there.
Hello, Those messages are just informing about SLP advertisements. -- # man rsyncd.conf use slp This parameter is used to determine if the module names are advertised via slp. The default is for this to be enabled, which will advertise your public modules. slp refresh This parameter is used to determine how long service advertise- ments are valid (measured in seconds), and is only applicable if you have Service Location Protocol support compiled in. If this is not set or is set to zero, then service advertisements never timeout. If this is set to less than 120 seconds, then 120 sec- onds is used. If it is set to more than 65535, then 65535 is used (which is a limitation of SLP). Using 3600 (one hour) is a good number if you tend to change your configuration. -- So you can disable slp advertisements in /etc/rsyncd.conf with the following line: use slp = false See https://fate.novell.com/306331 -- Best regards / s pozdravem Petr Uzel, openSUSE Boosters Team ----------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: puzel@suse.cz Lihovarská 1060/12 http://www.suse.cz 190 00 Prague 9, CR
On Tuesday 05 Jan 2010 13:36:01 Petr Uzel wrote:
On Tue, Jan 05, 2010 at 01:13:31PM +0000, Bob Williams wrote:
On Tuesday 05 Jan 2010 12:26:34 Per Jessen wrote:
Bob Williams wrote:
Can anyone tell me why rsyncd won't stay up all the time? I keep getting this sort of stuff in /var/log/rsyncd.log
2010/01/05 09:10:30 [3407] Service registration expired, refreshing it 2010/01/05 09:10:30 [3407] rsyncd registering 12 services with slpd for 3600 seconds: [ ... ] I'm sure it never used to do this. It just started at boot time, and kept running in the background.
Given that the process id doesn't change, you're still looking at just one daemon. It isn't restarted. [ ... ]
OK. Yes, I was too hasty accusing the process of dying. But what does 'Service registration expired, refreshing it' mean? I've looked in YaST > Network Services > Network Services(xinetd) at the rsync daemon setup, but I can't see any obvious settings that have been changed there.
Hello,
Those messages are just informing about SLP advertisements.
-- # man rsyncd.conf
use slp This parameter is used to determine if the module names are advertised via slp. The default is for this to be enabled, which will advertise your public modules.
slp refresh This parameter is used to determine how long service advertise- ments are valid (measured in seconds), and is only applicable if you have Service Location Protocol support compiled in. If this is not set or is set to zero, then service advertisements never timeout. If this is set to less than 120 seconds, then 120 sec- onds is used. If it is set to more than 65535, then 65535 is used (which is a limitation of SLP). Using 3600 (one hour) is a good number if you tend to change your configuration. --
So you can disable slp advertisements in /etc/rsyncd.conf with the following line:
use slp = false
Many thanks. I did, in fact, have the line slp refresh = 3600 in my rsyncd.conf file, but for some reason I never saw it! Another lesson learnt :) Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.2, Kernel 2.6.31.5-0.1-desktop, KDE 4.3.3 Intel Core2 Quad Q9400 2.66GHz, 4GB DDR RAM, nVidia GeForce 9200GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Bob Williams -
Per Jessen -
Petr Uzel